Building Automation Knowledge Base

Issue The hard drive fills up with logs generated by PostgreSQL/Timescale. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause Trend meta table missing information Resolution In the ES, go to the TimeScaleDB configuration. Set Trend and Event storage to false and click save. Set Trend and Event storage to true and click save.

Issue How to connect a 4 wire PT100 or PT1000 sensor to a 3-wire RTD input. Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch RTD Cause Some PT100/PT1000 sensors have only 3 terminals to connect to. Resolution The wires to the sensor are often color marked in pair, like two red cables and two white cables. As we only have 3 terminals to connect to, the solution is to only connect 3 of the cables, and not connect the 4th cable.   As the RTD device also measure the resistance of the cables, to make a correct temperature reading, it is important that all three wires used do have the same length and resistance. Therefore, the fourth wire should NOT be connected in parallel, it has to be un-connected.

Issue Unable to read the Analog Inputs / Universal Inputs values in StruxureWare Building Operation. Product Line EcoStruxure Building Operation Environment Xenta I/O Modules Xenta  421A, 422A, 451A, 452A as standalone LON nodes StruxureWare Building Operation (SmartStruxure) Cause When using the Xenta Input Output modules 421A, 422A, 451A, 452A as stand alone Lonworks node, the UCPTConfiguration must be set to the necessary integer value for the required input, by default the values are set to zero so can not be configured. Resolution Please see the supporting documentation for the TAC Xenta 421A/422A and TAC Xenta 451A/452A that gives each nci value for the needed input type. To configure each input to the correct type please follow these steps: Navigate to the node in your Lonworks network Expand the controller to view all of the inputs, outputs, and configuration properties. Find the Universal Input module for the input you need to configure, and locate the nciInput(x) variable within that module Set the value of Absolute count to one of the following : 1 = 1.8 kohm thermistor 2 = DI with green indication 3 = 0-10 vdc 4 = 0-20 mA 5 = 10 kohm thermistor 6 = DI with red indication 7 = DI with green inverted indication 8 = DI with red inverted indication   Up to SBO Version 1.7.x     SBO Version 1.8.x and on in the "Variable Fields" tab overwrite the string "Min" with for example 6 

Issue Errors variable increasing rapidly and frequent 182a errors seen in the Controller Error Log. 0x0000182a - COMM_ERR_IV_IPADDR (Invalid Internet network address) Product Line Andover Continuum Environment All IP Level Controllers bCX ACX57xx Netcontroller Netcontroller II Cause The 182a error indicates that there is an issue with the controller IP Address settings. Some potential causes of this are: Duplicate IP Address, improper subnet mask, improper gateway, BACnet routing issues. It seems that it is logged when trying to change the IP address or use an encode id already used by another device. This error can be caused by misconfigured IP address information including mask and gateway addressing.  Can also be due to improper BACnet routing. In one specific scenario the issue was the default router setting in the Controller. This was set to a device that was not a router to the network. Confirming the configuration of all IP Devices on the network and getting a Wireshark capture can help to identify the potential cause.  Resolution Removed the invalid IP address from the Default Router field and the 182a errors stopped appearing in the Controller Error Logs.

Issue When being discovered by a 3rd party system what names will be seen? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS-P, AS-B, AS) Cause How is an Enterprise Server or Automation seen by a 3rd party system? Resolution The Enterprise Server (ES) and Automation Server (AS) conform to a specific BACnet Protocol Revision depending on version and firmware and the capabilities of a particular BACnet implementation are described in the Protocol Implementation Conformance Statement (PICS).  The PICS contains, amongst other details, a list of all standard and proprietary object types that are supported.  Please see BACnet Testing Laboratories (BTL) for a Listing of Tested Products.    For each object type supported the PICS describes: any optional properties that are supported which properties can be written-to using BACnet services if the objects can be dynamically created or deleted using BACnet services any restrictions on the range of data values for properties For a third party to discover an ES or AS it needs to be a BACnet Operator Workstation (BOWS).  Please see BACnet Testing Laboratories (BTL) for a list of tested BACnet Operator Workstation (B-OWS) and BACnet Advanced Operator Workstation (B-AWS)   Of the objects types detailed in the PICS the specific BOWS will determine what properties are shown.  An application such as YABE can provide an indication of these properties.  For example with a device the Vendor Name (1), Protocol Revision (2), Object Name (3),  Model Name (4) and Firmware Revision (5) are amongst the properties available. For an object such as an analog point the Object Name (6), Present Value (7) and Object Identifier (8) are examples of what will be seen.    Every BACnet device contains a device object that defines certain device information, including the device object identifier or instance number.  For additional information please see Introduction to BACnet.  

Issue Alarm Pane not shown in Webstation Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause The User is viewing a Workspace which does not contain the Alarm Pane Resolution In the Top Left hand corner of the screen click View>Workspaces Select Engineering (or other applicable workspace)

Issue Moving the Enterprise Server database path on an existing system Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Cause The Enterprise Server database can be affected by system changes (system restore, Windows reinstall, reformatting the system drive, etc.) if it is located at the default path on the system drive. In some instances, the default location is not the best for the customers' site. Resolution The default path where the Enterprise Server database is installed depends on the operating system it is installed on as well as the version:  The default database path for Building Operation 1.9 and below: C:\ProgramData\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server For 2.0 and above  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation x.x\Enterprise Server To move or change the Enterprise Server database path. Log on to the Enterprise Server from Workstation. Perform a backup (all data) of the Enterprise Server (right-click on the server and select 'Backup'). After the backup completes, save the backup set to the local drive (server > System > Backup and Restore > Backup sets > Local).  Exit the Workstation. Stop and uninstall the Enterprise Server. Install the Enterprise Server (same version as the version that was uninstalled). When prompted for the database path, browse to the new directory where the Enterprise Server database is to be located. In the example below, the new Enterprise Server database path is  After the Enterprise Server is installed, run the Software Administrator. The database path should now point to the new database directory. Start the Enterprise Server if it is not already running.  Log on to the Enterprise Server from Workstation and restore the backup set (all data) which was saved.  Log on to the Enterprise Server and verify operation. 

Issue From a legal Microsoft Licensing point of view, it is important to be clear how many Client Access Licenses (CALs) are required when using a Report Server with SQL in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause While Microsoft Client Access Licenses are not required to make a Report Server installation function, ANY system which makes use of Microsoft SQL must consider the provision of sufficient purchased CALs to remain legally compliant and avoid potential fines. Resolution The Report Server Reporting Agent Service which is responsible for reading the data from the Enterprise Server (ES) and storing it the Microsoft SQL Server Database, will use one connection to the SQL Server. and therefore, requires one CAL. 

Issue Online Device shows "0" for one scan, but the device is still online from TAC Vista. This is enough for the unit to stop and close dampers. Product Line TAC Vista Environment Vista Server Xenta 281 Xenta 301 Xenta 401 Cause The Online Device function depends on your network.  If two controllers are within the same TAC Xenta group, there should be no extra traffic the asking device could just check in the online table if the other device has sent out its poll lately. If it is outside the actual TAC Xenta group, it will be like a TACNV connection, within the limits for TACNV. However, there are no re-sends. A single missed message will result in an Offline status. If there is a lot of traffic, there could be a collision on the network traffic and this could result in an Offline status. The next scan time, the messages might work correctly again, and resulting in online status. Resolution The best solution is to have a Delay block in the TAC Menta code, to get a delay-off (when the value goes from Online (1) to Offline (0)). Make sure the device is offline for at least a few program cycles before taking any action in the application program logic.  

Issue Unsure what options are available in the Lua smtp.send() function. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager (MPM) Cause The Lua smtp.send() function is not fully documented. Resolution The syntax of the smtp.send() function is: smtp.send { from = string, rcpt = string or string-table, source = LTN12 source, [server = string,] [user = string,] [password = string,] [port = number,] [domain = string] }   From above you can see that the "from", "rcpt" and "source" fields are required. Whilst "server", "user", "password", "port" and "domain" fields are optional. Example Lua code is: --============================================================================== -- SSL email notification script example --============================================================================== -- Define the input you want to monitor below var("temperature", "ME.AI1") -- Room Temperature limit = 78 -- define the threshold now = scl.sysclock() if (temperature > limit) then -- When temperature is above threshold     if (sent == nil) -- Check if e-mail was already sent     and ((last == nil) or (now - last > 15 * 60)) then -- Maximum every 15 minutes         sent = true -- Only send e-mail once         last = now -- Keep track of last time     result, reason = smtp.send {     user = "alerts@server.com",  -- Enter your existing SMTP username     password = "test1234",  -- Enter your existing SMTP password     from = "alerts@company.com",  -- Enter your existing Source address     rcpt = {             "user1@company.com",  -- First recipient             "user2@company.com",  -- Second recipient             "user3@company.com"  -- Third recipient             },     source = smtp.message( {     headers = {     from = "alerts@company.com",  -- Displayed source address     to = "technicians@company.com",  -- Displayed recipients     subject = "Temperature Alert"  -- E-mail title                 },     body = "Current temperature is: " .. temperature .. " (above " .. limit .. ")" .. " [" .. os.date() .. "]"}),     server = "server.com" – enter your SMTP server                 }     if result ~= 1 then         print(os.date(), "E-mail was NOT sent:", reason)     else         print(os.date(), "E-mail was successfully sent.")     end end     else     sent = nil -- Re-enable alerting on condition end   --[[ Disclaimer: We hope that this script example and associated information (the "information") is valuable to you. Your use of this information, however, is at your sole risk. All information is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Schneider Electric.. Further, Schneider Electric. shall not be liable for any damages you may sustain by using/installing/modifying this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages. --]]  

Issue Adding StruxureWare Building Operation license from file fails. The following are the error messages. "License Administrator Major error number: 50044 Minor error number: 71013 System error number: 1 System error message: Description: Error occurred during call to repair locally. Define: LM_TS_LOCAL_REPAIR"   Environment StruxureWare Building Operation License Administrator Cause The cause for this problem is unknown at this time.  Resolution If the problem is not resolved after an uninstall and re-install of the License Server / Administrator then follow the procedure listed below.  Please contact Product Support for further investigation if the problem is not fixed with this procedure.  Exit all StruxureWare Building Operation applications. Stop the License Server (in Windows Services). Uninstall the License Administrator / Server using Windows Add/Remove Programs. If you have multiple versions installed, uninstall all versions. In Windows paths detailed below, search for files that are in the format 'taclic_*_tsf.data' and delete them. There could be other files in the this directory that ends with 'tsf.data' as there could be other 3rd party applications using FLEXnet licensing. Delete only the files that starts with 'taclic'. Windows 7 go to the 'C:\Program Data\FLEXnet\' directory (Windows 7).  Note:This folder may be hidden by Windows 7, Click Here on how to view these paths. Windows XP, the path to the FLEXnet folder is 'C:\Documents and Settings\All Users\Application Data\FLEXnet'. or C:\Documents and Settings\All Users.Windows\Application Data\FLEXnet). Note:This folder may be hidden by WindowsXP. Install the License Administrator and add the license file as per the normal procedure.  Note: If you are unable to delete the files in step number 4, go to Windows Services and stop the FLEXnet Licensing Service and try again. 

Issue After moving the License server to another computer the license server address in the License Administrator is changed to the IP address of the new computer, but EBO Workstation gets a license error when trying to login to it. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The License Administrator can be used to select which license server EBO uses. This is done by going to the License Server Address tab and entering the license server address in the License Server Address field. Note that the license server address must be preceded by an @ in order for it to work, e.g. @servab48. The License Server Address in The License Administrator is not always used when Workstation or the Enterprise server asks for a license, Resolution The request for a license is handled in the following order:   If there are licenses located locally on the machine running WorkStation/Enterprise server (activated from ASR files), those are used first. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is used. This registry key contains all license server addresses that have been successfully used to obtain a valid license previously. If this key is not empty, each server contained in the registry key value is asked for a valid license until one is obtained. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, and the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is empty, the license server set in License Administrator is used. The license server address is stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Electric\StruxureWare\License Administrator\TACLIC_LICENSE_FI

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Under rare circumstances, resetting your Manager to its factory defaults may be necessary.  For example, if you have forgotten your Manager's IP address, or if you are experiencing login problems.  Environment SmartStruxure Lite Web Browser SmartStruxure Lite MPM Cause All SmartStruxure Lite™ Managers are equipped with a bootloader, accessible via a special IP address that lets you access several Manager firmware functions, among them, a factory reset.  Resolution WARNING: Restoring your Manager to factory settings should only be performed as a last resort; doing so will erase all its objects and devices, requiring you to reconfigure your Manager from scratch. Accessing the Bootloader As its name suggests, you access the bootloader at boot time, i.e., when you power up your Manager. To perform a factory reset: 1. Disconnect electrical power from your Manager by unplugging its power connector or unplugging its power supply from the AC outlet. 2. Ensure that your computer's TCP/IP settings are on the same subnet as the bootloader IP address:10.50.80.X.     IMPORTANT: Upon restarting your Manager, you will have only a brief interval–approximately 5 seconds–during which you will be able to access the bootloader. As such, we recommend that you perform the following steps 3.  Open your browser and type the following IP address into the address bar, but do not click the browser's Go icon or press any  key on your keyboard: 10.50.80.2 4. Reconnect your Manager's electrical power. 5. Within approximately 5 seconds, click your browser's Go icon or press the key to navigate to the  bootloader's IP address.  The bootloader screen displays.    6. In the Restore factory defaults area, click Submit. The Manager begins restoring its settings to the factory defaults. When completed, a success message displays.  7. Restart your Manager by clicking the Submit button in the Restart system area. 8. You may now log in to the Manager using its restored IP address: 10.50.80.3. If you cannot connect successfully to the bootloader using the above steps, chances are you are not navigating to the bootloader's URL within the defined 5-second window.       As an aid, some users may find it useful to do the following:      Open a command window and type the following: ping 10.50.80.2     As soon as you see a ping reply, return to your browser window and press the key to navigate to the address previously entered into the address bar.   Restoring your Manager to Factory Settings download as PDF.

Issue The IO Module does not report input signals and all physical outputs are turned off. The IO module status LED blinks at a rate of one blink per second. Product Line EcoStruxure Building Operation Environment I/O Module Cause The IO module has been placed into Low Power Mode. Resolution  I/O Module Low Power Mode In order to save energy, an I/O module can be placed in low power. When an I/O module is in low power, the following conditions apply: The I/O module does not report input signals and all physical outputs are turned off. The Module status reports low power. The I/O module's LED pattern indicates low power (the slowest green LED blink pattern, approximately once every 3 seconds). When you set an I/O module to low power, the software turns off all outputs. When you want to recover an I/O module from low power, there are several points to consider: Make sure all I/O module Output values are set to a safe level before a return to normal power conditions. This prevents "power surge" conditions. After normal power resumes, the Output values set are reached immediately after any timing delay occurs. Setting and Recovering an I/O Module from Low Power Place an I/O module in low power mode in order to save energy and then recover that module later.   To set and recover an I/O module from low power In WorkStation, in the System Tree pane, expand the IO Bus. Click the I/O module that you want to put in Low power mode. Click File and then Properties. Under Configuration Settings, in the Low power box, select True. Click OK to change the value and close the Properties tab. If the physical I/O module, shown in the System Hardware folder, matches the logical I/O module defined in the I/O Bus, the I/O module goes into Low power. After the physical module enters low power, the Module status attribute in the Status Information area displays Low power.  To set and recover an I/O module from low power In the System Tree pane, expand the IO Bus to recover from low power mode. Click the I/O module to recover. Click File and then Properties. Under Configuration Settings, in the Low power box, select False. Click OK to change the value and close the Properties pane. If the physical I/O module, shown in the System Hardware folder, matches the logical I/O module defined in the I/O Bus folder, the I/O module exits from low power. After the module resumes operation from low power, the Module status returns to the status it had before it went into Low power. NOTE: If unable to change the Low Power property: Export the contents of the I/O module Deleted it from the AS Re-add it to the AS Import the XML back into the module

Issue SP-RDM2 Reader Expanders running firmware 1.12.544 appear to fail whenever an attempt is made to update their firmware revision. Product Line Security Expert Environment SP-RDM2 SP-MRDM2 Cause There is a known defect in 1.12.544 (Build .544) which prevents the SP-RDM from being upgraded or even downgraded. However, a number of SP-RDM units have been shipped from the factory with this build pre-installed. Any attempt to select an SP-RDM running this firmware and upgrade or downgrade it to a different revision will consistently fail with an error: 'Module not responding'. There is also a possibility that the SP-RDM can be permanently disabled in the process Resolution Since the .544 Build defect cannot be resolved the only recourse at this time is to swap out the unit via the Returns Material Advice (RMA) process for a new unit.      List of SP-RDM2 Serial #s affected thus far: Note: All other SP-RDMs running firmware both above and below .544 Build are unaffected

Issue Import of BACnet/IP device is missing Device ID value. The device is indicated as offline and will not communicate. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause A device instance number is not preserved in an export. An imported BACnet device must be associated with a device.  Resolution Use the Associate with Device option on the BACnet/IP device object, refer to: Associating a BACnet Instance Number with a Device (se.com). Specify the device instance number.

Issue RTD-DI-16 temperature input range is -50C to 150C, some applications require a wider range. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation I/O Module 16 Ch RTD Cause Script program sample and guidelines needed for implementing resistance to temperature table lookup and further temperature calculation using linear interpolation. Resolution We will present two solutions, the first solution is very simple to implement but at the expense of accuracy. The second solution retains the 0.3C accuracy of the native RTD inputs. For simplicity, both solutions implement a range of -50C to 250C using the RTD Resistance electrical type to convert resistance to temperature, the program can be easily modified to implement a wider range.     SOLUTION #1 This solution simply uses the conversion settings of the RTD-Resistive input to convert from Ohms to Degrees C. Because the change in resistance is not exactly linear across the temperature range, the accuracy of the converted value varies across the range as much as +/- 4 degrees C      STEPS TO IMPLEMENT SOLUTION #1 Under the RTD-DI-16 IO module, create RTD-2W-Resistive input. Change the units to degrees Celsius. Select the sensor class, in this example, we are using the pt100 sensor. Look up the resistance value in the table for -50C and  250C and set the upper/low-level reliability. (see attached R versus T table from Omega) Use values from step #4 to set the input's conversion electrical scale.  Set the engineering scale top/bottom to 250 and -50 respectively.    STEPS TO IMPLEMENT SOLUTION #2 Under the RTD-DI-16 IO module, create RTD-2W-Resistive input. Look up the resistance value in the table for -50C and  250C and set the upper/low-level reliability. (see attached R versus T table from Omega) In the Automation Server, create an Analog Value object. This object will receive the calculated temperature value from the Script program. Set the AV units to degrees C In the Automation Server create a Script program, this program will read the resistance from the input object, look up the corresponding temperature range in the table, and then using linear interpolation calculates the temperature to an accuracy of +/- 0.3C. To ensure the program when runs when necessary, configure the program's flow type for fall thru and trigger the program off of the RTD-2W-Resistive input. Bind the RTD-2W-Resistive input and the Analog Value in the Script program as Numeric Input and Numeric Output respectively.  Here is the code for the script program   'This program uses RTD temperature vs. resistance table combined with linear interpolation 'to implement RTD temperature input over the range -50C to 250C 'Program Flow Type is FallThru 'Program is triggered by the RTD resistance input. 'This program is provided as a sample for illustration purposes, it is not intended to be a complete solution 'SE PSS v1.0 101010111110 Numeric Input RTD_Raw 'the RTD Resistance input where the RTD sensor is connected Numeric Output RTD_Temp 'Analog Value that receives the calculated temperature Numeric RTD_R[31]'Resistance to Numeric RTD_T[31]'temperature table for 100 Ohms based sensor 'NOTE: Since the resistance value changes in a nearly linear way over any 10 degree section 'of the table, we can use 10 degree increments of resistance/temperature values and apply linear 'interpolation to calculate readings in between those values, this method greatly reduces the size 'of the table in the program while maintaining very good accuracy. 'Accuracy is +/-0.3C for 100 Ohms based sensors and can be improved to +/-0.03C if 1000 Ohms based sensor used. Numeric n, sLow, sHigh,sMid Line INIT 'Due to limitations in Script we will use 2 arrays to implement the resistance to temperature table. RTD_R[1]=80.31 RTD_R[2]=84.27 RTD_R[3]=88.22 RTD_R[4]=92.16 RTD_R[5]=96.09 RTD_R[6]=100 RTD_R[7]=103.9 RTD_R[8]=107.79 RTD_R[9]=111.67 RTD_R[10]=115.54 RTD_R[11]=119.4 RTD_R[12]=123.24 RTD_R[13]=127.08 RTD_R[14]=130.9 RTD_R[15]=134.71 RTD_R[16]=138.51 RTD_R[17]=142.29 RTD_R[18]=146.07 RTD_R[19]=149.83 RTD_R[20]=153.58 RTD_R[21]=157.33 RTD_R[22]=161.05 RTD_R[23]=164.77 RTD_R[24]=168.48 RTD_R[25]=172.17 RTD_R[26]=175.86 RTD_R[27]=179.53 RTD_R[28]=183.19 RTD_R[29]=186.84 RTD_R[30]=190.47 RTD_R[31]=194.1 'The temperature array could be easily omitted since once we have the first array index (n) we could easily calculate 'the corresponding temperature value, I have kept it for the purpose of simplicity. RTD_T[1]=-50 RTD_T[2]=-40 RTD_T[3]=-30 RTD_T[4]=-20 RTD_T[5]=-10 RTD_T[6]=0 RTD_T[7]=10 RTD_T[8]=20 RTD_T[9]=30 RTD_T[10]=40 RTD_T[11]=50 RTD_T[12]=60 RTD_T[13]=70 RTD_T[14]=80 RTD_T[15]=90 RTD_T[16]=100 RTD_T[17]=110 RTD_T[18]=120 RTD_T[19]=130 RTD_T[20]=140 RTD_T[21]=150 RTD_T[22]=160 RTD_T[23]=170 RTD_T[24]=180 RTD_T[25]=190 RTD_T[26]=200 RTD_T[27]=210 RTD_T[28]=220 RTD_T[29]=230 RTD_T[30]=240 RTD_T[31]=250 n=0 sLow = 1 sHigh = MaxItem(RTD_R) 'Initialize to the size of the table Line calculateTemp 'Bottom of range If RTD_Raw <= RTD_R[1] then RTD_Temp = -50.0 Stop Endif 'Top of range If RTD_Raw >= RTD_R[sHigh] then RTD_Temp = 250.0 Stop Endif 'Find the resistance input reading in the table using a binary search 'NOTE: 'In our case, what we are looking for is the lower value of the resistance range in the table that 'the input reading falls under. 'EXAMPLE if input value is 160.9 Ohms then it is in the range of RTD_R[21]=157.33 AND RTD_R[22]=161.05 'so the binary search will give us 21 While(1) If sHigh < sLow then n=sHigh 'the input value is not in the table but we now have RTD_R[n] of the range it is within break Endif 'calculate the mid point sMid = Round(sLow + (sHigh - sLow) / 2) if RTD_R[sMid] < RTD_Raw then sLow = sMid + 1 'if read value is larger then look again in upper half if RTD_R[sMid] > RTD_Raw then sHigh = sMid - 1 'if read value is smaller then look again in lower half if RTD_R[sMid] = RTD_Raw then n = sMid 'we've located the input value in the table, this is actually the exception Break endIf EndWhile 'Now, use linear interpolation to calculate the temperature If n > 0 Then RTD_Temp = (RTD_T[n+1]-RTD_T[n])*(RTD_Raw-RTD_R[n])/(RTD_R[n+1]-RTD_R[n])+RTD_T[n] Endif Stop Line E stop   NOTE: The accuracy of the temperature reading can be further improved by the use of 1000 Ohms based sensors as well as the use of 3 wire sensors so that the resistance of the leading wires can be taken into account. If 1000 Ohms based sensors are used then the resistance values in the table implemented in the Script program must be multiplied by 10

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Elements in Sigma Graphics within EBO are not displaying correctly when its bound object commands the element to display or not to display. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause The issue arises on a machine that has a Windows Language Pack e.g. Norwegian Bokmål installed where the decimal separator uses a comma (,) rather than a dot (.).   In the example, using the EBO Graphics Editor, it can be seen that the decimal separator in 0,5 is a comma in the 'condition' command, other commands are also effected e.g. Bitmap, Alarm etc; Resolution When a Sigma graphic Data Import is undertaken the decimal separator dot (.) used by the Sigma machine is replaced by a comma (,).   On the Sigma server machine using Registry Editor. Registry Edit can be run by typing RegEdit in the Windows search box on the Task Bar. 1. Goto > Computer\HKEY_USERS\S-1-5-18\Control Panel\International\ 2. Locate sDecimal. 3. sDecimal will be set to a comma (,). Change to a dot (.). 4. Re-import the Sigma graphics using the Graphics Data Import in EBO. 5. Select a graphic and edit using the EBO Graphics Editor, select an element and check that a .(dot) is used.   Finally, check operation by changing object states on the graphics and the respective element changes state too. Note: This will be auto checked and be incorporated into the Sigma Transition Tool in the future.

Issue What can be used to get the Device Log (aka Error Log) from a b3 or Infinet connected to an Automation Server (AS)? Product Line EcoStruxure Building Operation Environment Building Operation Server Bacnet Infinet Cause Need to get the Device Log (aka Error Log) from a b3 and/or Infinet connected to an AS. Resolution A tool called Building Operation Device Log Viewer (SE.SBO.Device.Log.Viewer.exe), starting with v1.9 now contains a dropdown used to choose BACnet (b3) or Infinet.  Prior to v1.9, it was limited to only obtaining b3 error logs.   64-bit Windows OS Default Location: "C:\Program Files (x86)\Schneider Electric [EcoStruxure|Struxureware]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   32-bit Windows OS Default Location: "C:\Program Files\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   Note: Based on the EBO system version you are connecting, use either [EcoStruxure|StruxureWare] and version [n.n] that matches. Note: Before v1.6 it was called Building Operation b3 Device Log Viewer and had a similarly named EXE file.   The Log Viewer tries to connect to the AS-P via UDP port 33487 when BACnet is selected and UDP port 33488 when Infinet is selected.

Issue How is time synchronized between the Controllers and Security Expert Server?  Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controllers (SP-C, SP-ACX, SP-AC1, SP-DCU) Cause Require details on different ways the Controllers can have their time set. Resolution There are two methods for synchronizing time on the Controllers. Periodically updated by the SNTP Time Server configured under the controllers Time Update tab. (Note: the controller polls its SNTP Time Server every 11 minutes.) SNTP Time Server Without an SNTP Time Server configured, time is updated on the Controllers by the following methods. Time is updated manually by the Operator right-clicking the controller and selecting Set controller date/time. This will set the controllers time to the current time of the Workstation. Set Controller Time Time is updated to the server time whenever a “Force Download” is initiated for that controller. Force Download