Building Automation Knowledge Base

Issue Graphics are not displayed via the WebStation. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Graphics Trends Display issues Long hyphen # character Cause When a graphic is requested on a Building Operation Webstation, it is not displayed. The display will remain blank. Resolution Try the following steps below to correct the WebStation loading issue. Check the file size of the graphic page. If the TGML graphic size is too large it can have issues loading in WebStation. Majority of the times it is due to an image that is too large such as a floor plan.  If a graphic, or trend chart object, is created through a EcoStruxure Building Operation WorkStation and its name contains a "long hyphen", the graphic and trend chart objects cannot be viewed through WebStation. The long hyphen is not a supported character. When creating object names do not use the long hyphen (—) only use the short hyphen if required (-) If the version being used is 1.3, upgrading to 1.4.1x may resolve the issue. Check the name of the AS, an unsupported character may have been used e.g.#, to resolve, remove the character.

Issue How does the import/export (IE) system work in the Continuum controllers? Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller. The principle is that the value of a controller point that is referenced by other controllers on the network only needs to be sent out when it changes, much like the BACnet COV which stands for Change Of Value. The two parties involved in the IE transaction are the controller that owns the point (the owner) and the controller(s) referencing the point's value (the subscribers), a second CX controller may also be involved and acting as a router when a value is imported/exported from/to a remote field device under a remote CX. Resolution Read more in the attached document, Understanding Continuum IE System.  See how to correct Import Export tables KBA

Issue Controller fails to backup to flash. See error message "Unable to backup objects to flash ..." ACCStatusFlash variable should be ACCFlashValid not ACCFlashFailure Product Line Andover Continuum Environment Continuum Controllers NetController 2, bCX9640, bCX4040 Cause A Program or Function in the Controller is corrupt and cannot be compiled or is blank and does not have any Plain English code in it. Resolution Go to the config page (Controller Configuration) Clear database backup Fix up or delete the offending programs Re-attempt to save the database to flash

Issue Details on how Modbus IP Multiple Queries and Multiple Query Packets work Product Line EcoStruxure Building Operation Environment Building Operation SmartX Servers Modbus IP Cause Understanding of how the Modbus synchronous and asynchronous transport layers differ. Resolution By default, the Multiple queries is Disabled, this is the synchronous transport layer. To enable the asynchronous transport layer the Multiple queries must be Enabled within the Modbus TCP Network properties as shown below. Setting to "Enabled" allows multiple queries (packets) to be sent to multiple Modbus devices, thus reducing wait times.  It also enables further settings in the Modbus Device properties "Maximum concurrent queries" and "Multi-query packets".   The maximum concurrent queries and multiple-query packets as shown below are configurations for the Modbus asynchronous transport layer. The Maximum concurrent queries setting is only enabled if the "Multiple queries" is enabled in the Network Properties. When enabled, this allows the "concurrent queries" to be sent as a single packet.     Modbus Synchronous Transport Layer Each Modbus query is sent out one after the other. Before sending out the next query the transport layer waits for a specified period for the previous query. Example Poll Sequence Device No. Objects 1 2 2 1 D=Device, Q=Query, R=Reply D1 Q1 Send D1 R1 Receive  D2 Q1 Send D2 R1 Receive  D1 Q2 Send D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 3 seconds. Modbus Asynchronous Transport Layer With the asynchronous transport layer enabled, the queries are transmitted to multiple devices at the same time. The maximum number of queries that are transmitted to that one device is controlled by the “Maximum concurrent queries” setting. The “Multiple-query packet” specifies whether the queries are transmitted in one TCP frame or not. Simple Example Poll Sequence Device No. Objects Multiple-query packet Maximum concurrent queries 1 2 False 1 2 1 False 1 D=Device, Q=Query, R=Reply D1 Q1 Send D2 Q1 Send D1 Q2 Send D1 R1 Receive  D2 R1 Receive  D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 1 second Complex Example Poll Sequence Device No. Objects Multiple-query packet Maximum concurrent queries 1 10 True 5 2 4 False 2 D=Device, Q=Query, R=Reply D1 Q1, Q2, Q3, Q4, Q5 Send D2 Q1 Send D2 Q2 Send D1 R1, R2, R3, R4, R5 Receive  D2 R1 Receive  D2 R2 Receive  D1 Q6, Q7, Q8, Q9, Q10 Send D2 Q3 Send D2 Q4 Send D1 R6, R7, R8, R9, R10 Receive  D2 R1 Receive  D2 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 2 seconds   NOTES The use of this feature should be avoided before EBO v3.1, there is also a defect in EBO v3.2 that means v3.2.3.5000 should be used (minimum) Some Modbus devices do not support multiple queries or multiple query packets, so the feature should be tested on an individual basis. (Some devices may even go offline until manually reset) This feature will increase the CPU usage on the EBO server. It should be avoided on EBO Servers that are already heavily loaded This feature also has the ability to reduce the system stability, it is usually better to optimize the use of Modbus Register Groups to increase performance

Issue Configuring the Workplace Tech encrypted LON Tunnel Client  Product Line TAC IA Series Environment I/A Series WorkPlace Tech 5.9.4 Click for WorkPlace Tech 5.10.4 information I/A Series N4 Jace Cause How to handle the encrypted LON tunnel for single and multiple LON networks.  Understanding possible errors during tunneling. Resolution The following video will help us, Apply the Encrypted LON Tunnel in an N4 Jace Configure the Tunnel Client for use with multiple LON Networks on a single Jace Recognize a Timeout Error and how to handle it

Issue When launching a program or when working with a program, you get an error from "Microsoft .NET Framework".   Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC INET, TAC Vista Environment Windows .NET Framework Cause Microsoft .NET Framework is used in almost all larger applications, and there can be various reasons why you see an error. One reason can be application specific, meaning that there is an actual issue with the software and the way the software is using .NET Framework, but another reason can be that the .NET Framework installation itself is corrupted. If it's an application specific issue, you need to contact product support, but in many cases simply repairing the .NET Framework installation has proven to solve the issue. Resolution 1: Close all applications 2: Make sure you have the correct version of .NET Framework installed for the software you use referencing the product's data sheet. You can use this tool to check what versions you have. Here is a direct download link. 3: Install versions that might be missing. You can download the various versions from the tool linked above. 4: Download Microsoft's .NET Framework repair tool and run it applying all fixes the tool suggests. Here is a direct download link.

Issue There is an error message on the LCD display of the old style Infinet controllers. What do these errors mean? Product Line Andover Continuum Environment Infinet Controller Cause Information on the error code received on the LCD display. Resolution Infinet controller is displaying error 1 on its LCD display. This message indicates that the controller received a bad packet of data on the Infinet. If the problem persists follow troubleshooting instructions. Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched. Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level Infinet controller is displaying error 2 on its LCD display. This message means that it could not pass a token to another controller on the Infinet. If the problem persists follow troubleshooting instructions. (No response to the Infinet token pass) Verify Infinet cable connections, approved twisted shielded pair cable, less than 4000 feet of network cable between Infilink repeaters, no more than 31 controllers between Infilink repeaters. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Check the baud rate switch on the Infilink repeater module, although the Infinet controllers auto baud, the Infilink baud rate must be manually switched. Break down the network in segments to identify the bad controller or network segment. A binary search is recommended. (i.e. break the network in half, if this resolves the problem add half of the deleted back on, if it does not resolve the problem cut the remaining network in half, etc.). Once the offending segment has been identified, troubleshoot to the cable segment or controller level Infinet controller is displaying an error 3 on its LCD display. This means that the input reference voltage is out of range on the analog inputs. Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Infinet controller is displaying an error 4 on its LCD display. This means that the analog output reference voltage is out of range. Verify that inputs coming from external transducers are not exceeding the voltage input range, either 5 or 10 volts depending on model, if so use a voltage divider on the input. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Power down the Infinet controller and restart while connected to network. This will eliminate this unit having a duplicate ID on the network and it will also run the power up diags. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it. Infinet controller is displaying an error 5 on its LCD display. This indicates the controller underwent a reset of power down and retained memory ( warm start). If there is not reason for this to occur power outages etc., then troubleshoot the problem. Verify proper grounding at the Infinet controller on the AC power terminals, poor grounding can cause erratic operation and communication problems. Easiest method to verify ground is to connect a digital voltmeter between the earth ground terminal on the power strip of the controller and the shield of the Infinet. this method will only work if you have connected your shields all through the network back to the Infilink and CX controller. Measure the AC power at the controller, Verify it is within specification (nominal +/- 20%). Typically 24 VAC power that is daisy chained will drop the voltage along the connections leaving the power below the acceptable level even if the transformer is sized correctly. Verify that any outputs that are driving inductive loads such as relays, actuators, or valves, have a varistor across the coil n the field device. Verify that any input wiring is not run in the same conduit as high voltage cable, or is properly shielded and grounded. If there is voltage getting coupled into the input wiring, separate the input wiring from the interference, or shield the cables. If the interference is being caused by the end device such as an auxiliary contact form an high voltage device, a cap between .01 and 1 microfarads across the input terminal to earth ground may alleviate the problem. Remove field I/O wiring from the controller and recheck operation. If the problem goes away determine which I/O wire is the culprit and correct it.

Issue AVUE 5 Series Actuator does not actuate Control Valve correctly when installed in place of AVUE 2, 3 or 4 Series Actuator. Product Line Field Devices Environment AVUE 5304, AVUE5305, AVUE5354 and AVUE5355 Actuators installed on FEU, MEU, VEU Unit Control Valves. AVUE 5304, AVUE5305, AVUE5354 and AVUE5355 Actuators installed on MZX, VZX Plant Control Valves. Cause AVUE 5 Series Actuators are available with stoke lengths of 9.5mm and 12.7mm AVUE 5304 and AVUE 5354 Actuators provide a stroke length of 12.7mm AVUE 5305 and AVUE 5355 Actuators provide a stroke length of 9.5mm   AVUE 2, 3 and 4 Series Actuators provided universal stroke compatibility. Control Valves having either 9.5mm or 12.7mm stroke could be actuated.  Resolution Select AVUE 5304 (Direct Acting) or AVUE 5354 (Reverse Acting) to actuate MZX or VZX Plant Control Valves. Select AVUE 5305 (Direct Acting) or AVUE 5355 (Reverse Acting) to actuate FEU, MEU or VEU Unit Control Valves.   For further AVUE 5 Series Actuator information please refer to Data Sheet DS 3.002  11/06   The AVUE is no longer available, check the 2022 Valves & Actuators Catalog - EMEA & APAC for a replacement. Note: The valve would need to be replaced to accommodate the replacement actuator.

Issue Communications with other Lon network devices are lost after the IC-Lon/IC3-Lon has cold-started. Product Line Satchwell Sigma Environment Sigma IC-Lon Integration controllers IC3-Lon Integration controllers Cause The controller has been cold-started either manually or through the automatic process. Resolution The final part of the engineering process of the IC-Lon/IC3-Lon, is for the file named NVConfig.bin to be uploaded from the IC-Lon/IC3-Lon to the Sigma server. If this file is not uploaded, then the IC-Lon/IC3-Lon reverts to its non-bound state. The NVConfig.bin file contains information about the Lon bindings and is modified during the binding process when using LonMaker. To upload the NVConfig.bin, carry out the following: Open "System Diagnostics"  on the Sigma server. Select the correct controller number. From the "Options" menu select "Upload Files" and NVConfig.bin This file will now be uploaded and overwrite the existing file in the controller folder, and therefore when the controller next cold-starts, the correct file will be downloaded to it. For more information on the Engineering process of an IC-Lon/IC3-Lon, please click here.   The Sigma system is now out of its support period, consideration should be given to transitioning or upgrading to SpaceLogic - EcoStruxure Building Operation.

Issue Continuum 1.9x and above will not install correctly on a PC / Laptop that is on a domain, One example: When trying to run the Continuum Database Initialization program the following error message may pop up: You must have local NT administrative privileges to run this application. Environment Windows OS 7 8 10 Continuum 1.9x 2.x Inet SQL 2005 SQL 2008 SQL 2012 Cause Microsoft has introduced the use of a higher level of security in the install of their SQL database software SQL 2005 / SQL 2008 / SQL 2012. When you install Continuum you need to make sure you are logged onto the PC / Laptop as a local administrator, in the case of a lot of a corporate networks, you are most likely logged on as ether a restricted user or a domain administrator, these logons do not have the privileges you need to install an SQL database. Resolution Step by step guide to creating a local administrator user on your PC / Laptop Go to "Start" then "Control Panel" in Windows (Windows 7 and above, top right corner change "view by" to "small icons" this will show all icons) Go to "Administrative Tools" Go to "Computer Management" / "Local Users and Groups" In users, right click on the right panel and add new user Fill in the user name and password, un-tick user must change password Tick password never expires then ok it Now go back into control panel and click on "User Accounts" Click on the name you just created, this will open the properties screen (Windows 7 and above click on "Manage user accounts") Click on "Group Membership" then select others, and highlight administrators (Windows 7 and above double click on name you created, click "group membership" click "other" then in the drop down select "Administrator") Apply this and then ok it. Log off your normal account and log back on as the new user you have just created

Issue Controller lost power or is new and needs to be reloaded Product Line Andover Continuum  Environment Continuum Cyberstation Cause How to reload a Continuum controller Resolution Steps to reload a Continuum controller Open Continuum Explorer Right-click and select Send to> Controller Open up the distribution window from the system icon tray(lower right-hand side) The distribution window will show controller reload progress and state when the reload is finished The attached documen provides additional information on the controller reload options that are available in the Continuum Explorer Options menu.  

Issue What are CZT, CXT, CXR Controllers? Why are CZT, CXT, CXR Controllers used? What is Proportional, Integral Action and Derivative control. Why does a controller deliver different pulse lengths to the valve and not drive it fully open or closed? What is Pb, IA, PID? Environment CZT CXT CXR DC1100 DC1400 Proportional, Integral Action, Derivative, Pb, IA, PID Cause What do these controllers do and what are their applications? What is Proportional, Integral Action and Derivative control. Why does a controller deliver different pulse lengths to the valve and not drive it fully open or closed? What is Pb, IA, PID? Why is a 0-10V Signal used? Why is a 3 point control / Open Closed actuator used? Resolution Proportional Controllers are used in applications where there are long time lags e.g. room control, return air control, storage calorifier (HWS). Where the controlling sensor is a medium to long distance from the heat/cooling source. An example of a proportional controller is the Satchwell CZT. Integral action controllers are used in applications where there are short time lags e.g. supply air control, frost coil control, non-storage calorifiers. Where the controlling sensor is a short distance from the heat/cooling source. An example of a integral controller is the Satchwell CXT or the CXR. The CXR is a controller where the supply air is controlled, but the setpoint is reset by the return air or space temperature, therefore the time lag is short. Other controllers that fall into this category are the DC1100, DC1400 again the controlling sensor (mixed flow temp) is located a short distance from the heat source.  The term proportional band (Pb) is where the valve is moved to a position proportional to the deviation from setpoint. 0-10V modulating actuators are generally used on these controllers. The term integral action (Ia) is where the valve is moved at a rate according to the deviation from setpoint i.e. the valve is given longer pulses the further away from setpoint, shorter pulses as it gets closer. 3 point control/pulsed pair/open-close actuators are generally used on these controllers. Further to proportional controllers, inherent offset (the setpoint is never quite reached) can be an issue. Integral action can be applied to remove this offset. These controllers are primarily proportional, but integral action can be found on them and is applied. Hence the term PI or PI controller. Derivative control is generally only found on BMS controllers and is used occasionally with PI control, hence the term PID. Here the derivative action moves the valve proportionally to the change from setpoint. It is complex and is rarely used. Further detail about CSC controllers can be found here. Further detail about CXT controllers can be found here. Further detail about CXR controllers can be found here. Further detail about CZT controllers can be found here. Further detail about DC1100 and DC1400 controllers can be found here.

Issue Use the block DI to monitor an IO module, and generate an alarm when it is offline. But the above-mentioned function cannot be realized. Product Line TAC Vista Environment Menta Xenta 301, 302, 401 Xenta I/O Modules Cause If there is a configuration error in block DI, the right alarm cannot be generated. It is necessary to check and correct the configuration error. Resolution Create and configure the block DI and Alarm block according to the following procedure, then the IO module status can be monitored. When it is offline, an alarm will occur in the alarm window in TAC Workstation.   1. Create a block DI. (See the Figure 1) Figure 1 2. Edit the block DI and input DI identifier such as the monitored module name, Status_411 in instance. (See the Figure 2)           Figure 2 3. Click BIND in Edit window, select the Online Device in BIND TO column, and input the IO module number in DEVICE ADDRESS. (See the Figure 3)               Figure 3 4. The module number can be found in IO Expansion and Wall Module Table of DEVICE SPECIFICATION in Menta Options toolbar. In the under instance picture, the M1 module, TAC Xenta 411, its device address is 1; the M2 module, TAC Xenta 421A, its device address is 2; and so on, the M5’s device address is 5. (See the Figure 4)       Figure 4 5. After creating and configuring the block DI, the block Alarm should be created. (See the Figure 5)                Figure 5 6. Then connect the block DI and Alarm. When the IO module is online, the DI value is generally 1. So the block NOT must be used. (See the Figure 6)         Figure 6   You can also reference Monitor the online status of a base unit's associated I/O modules.

Issue Using a Lon Binding in EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Cause Binding LON objects to LON objects using the SmartStruxure Variable Connector can cause increase traffic on the LON FT-10 network. Resolution To correctly Bind the LON objects: Edit this bindings of the node object, (not the SNVT object) Use the binding Browser to navigate to the appropriate node/SNVT to bind to Drag and drop the object to create the bind When you are finished you will see a Hexagon button, which will allow you to edit the Lon Binding Properties. This is the indicator that you are using a LON binding and not a Variable Connector object, which would be represented by a gear and pencil icon. Click the Hexagon to edit the Lon Binding properties Do not use the default of Acknowledged Profile.  Unless the device has a specific reason not to, the best option is to use Unacknowledged Profile.  Please see below for the explanations of the LON Message ServiceTypes. Message Service Type You can specify one of the following message service types for each connection description. The message service types vary in reliability and resources consumed. • Acknowledged - means that the sending device expects to receive confirmation from the receiving device or devices that a network variable update was delivered. The sending application is notified when an update fails, but it is up to the developer of the sending device to handle the notification in the device application. While acknowledged service is very reliable, it can create excessive message traffic, especially for large fan-out or polled fan-in connections. When acknowledged messaging is used, every receiving device has to return an acknowledgment.  Acknowledged messaging can be used with up to 63 receiving devices, but an acknowledged message to 63 devices generates at least 63 acknowledgements—more if any retries are required due to lost acknowledgements. • Repeated - means that the sending device sends out a series of network variable updates, but does not expect any confirmation from the receiving device. Repeated service with three repeats has a 99.999% success rate in delivering messages. Repeated service provides the same probability of message delivery as acknowledged messaging with the same number of retries, with significantly lower network overhead for large multicast fan-out connections. For example, a repeated message with three retries to 64 devices generates four packets on the network, whereas an acknowledged message requires at least 64 packets • Unacknowledged - means that the sending device sends out the network variable update only once and does not expect any confirmation from the receiving device. This message service type consumes the least amount of resources, but is the least reliable.

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  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope. Environment Infinet Field Bus MSTP Field Bus Cause Documentation Resolution See  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope.pdf

Issue Untranslated infinity error when creating object in b3 or i2 device. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Infinet i2 Controller BACnet b3 Controller Cause b3/i2 devices do not support certain characters in their objects name. Resolution b3/i2 devices do not support certain characters in their objects name. For example, creating an analog input using the name AI-1 will cause the error is the BACnet field is left blank, the EBO name AI-1 can be used but a name needs to be specified in the BACnet name field that is consistent with the b3 naming convention such as AI_1.

Issue How to get data from Rayleigh Instruments RI-78-80-C kWh power meters Product Line EcoStruxure Building Operation Environment Modbus RTU Interface Automation Server Continuum X-driver Cause The Rayleigh Instruments RI-78-80-C has a single 48bit Modbus RTU word available to be read (kWh) It does not respond with an exception when an incorrect register is requested (or a single 16bit part of the 48bit word requested) Only half of each 16bit registers within the 48bit word is used Thus Register address 0, 1 and 2 can have a value 0-255 (00 00 to 00 FF) only The value are actually in 1/100 kWh Reg2 0 to 255 (255 = 255/100 kWh)Reg1 0 to 255 (255 = 255 x 256/100 kWh)Reg0 0 to 255 (255 = 255 x 256 x 256/100 kWh) So if Reg0 = 3, Reg1 =167 and Reg2 = 59Then the reading would be(3 x 256 x 256 / 100) + (167 x 256 / 100) + (59/100)= 2394.19 kWh The value is in 1/100 kWh Reg2 0 to 255 (255 = 255/100 kWh) Reg1 0 to 255 (255 = 255 x 256/100 kWh) Reg0 0 to 255 (255 = 255 x 256 x 256/100 kWh) Example So if Reg0 = 3, Reg1 =167 and Reg2 = 59 Then the reading would be(3 x 256 x 256 / 100) + (167 x 256 / 100) + (59/100) = 2394.19 kWh   Resolution To read the three registers, Modbus Register Groups must be used within SmartStruxure, this ensure a single read is done for the 3 registers comprising the 48bit value. Then a program can be used to calculate the actual meter value. This device will not appear as online in SmartStruxure as the Device Online mechanism requires a response from a 16bit register read (this device does not respond with an exception when an incorrect register is requested and has no 16bit registers to read)   Download an example of Modbus Objects and Script. The below example script could also be atapted for Continuum Plain English Program Numeric Input ModReg0, ModReg1, ModReg2 Numeric Output kWReading Line Calc1 kWReading = ((256*256*ModReg0) + (256*ModReg1) + ModReg2)/100 Note This device may not operate correctly in v2.0 and v3.0 due to a change in the method of offline detection, but this is fixed in v3.1 Numeric Output kWReading   Line Calc1 kWReading = ((256*256*ModReg0) + (256*ModReg1) + ModReg2)/100

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 Cybersecurity vulnerability scans are flagging the Building Operation License Server because it is using HTTP rather than HTTPS Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation License Server Cause The Building Operation License Server contains a web portal for diagnostics and administration. By default, the Building Operation License Server Administration web portal is configured to use HTTP Resolution It is possible from the Administration area of the Building Operation License Server Administration web portal to configure HTTPS communications. Note: this does not change how Ecostruxure Building Operation connects to the license server.   The following process configures the Building Operation License Server Administration web portal to use HTTPS   From a web browser open the Building Operation License Server Administration web portal by typing http://localhost:8888 Once the web portal opens, select Administration at the top right. You will be prompted to log on, use "admin" as the user name. If you have logged in before, use the password you have defined. If not, enter "admin" as the password, and you will then be prompted to create a password. Once signed in Select the Server Configuration tab. Under the Secure Web Server Configuration section, select Enable HTTPS Change HTTPS Port to a unique number e.g. 8443 Select Redirect Non-Secure Web Access to Secure Web Access At the bottom of the page click the Save button and close the web browser tab. Restart the Building Operation X.X License Server from the Windows Services app (services.msc) If the license server is opened using http://localhost:8888 it will now redirect to HTTPS using the port specified in step 4 above

Issue When creating an ETL task the "Run Once" option works, but when configured to run as a service, it doesn't work and an error occurs in the error log: 2015-05-22 17:13:59,069 ERROR ETLEngine (TaskName) - Thread ID (119) - Power Monitoring Expert Load Task: Task Power Monitoring Expert Load Task failed System.ApplicationException: Failed to populate the MetaDataSet. ---> System.Data.SqlClient.SqlException: Cannot open database "ION_Data" requested by the login. The login failed. Login failed for user 'NT AUTHORITY\SYSTEM'. Product Line EcoStruxure Building Operation, Other Environment Power Monitoring Expert Energy Expert (formerly Power Manager) ETL Tool Cause When testing the ETL task using "Run Once", the Windows account currently logged in, will be used to access the SQL database. However, when the same Task is then configured to run as a service, the account configured on that Service will be used to access the SQL database instead.  By default that account is the built-in account 'NT AUTHORITY\SYSTEM'.   The Position values for all of the mapped trend logs are set to an unreasonable timestamp. The timestamp is either very old or a date the preceeds the oldest values in the database.  Resolution Changing the Windows system account for the ETL service Either give the system account access to the database, or change the account used to run the service. Correct/Adjust the timestamp values in Positions tab of ETL The timestamps can be changed all at once by setting the Initial value field at the top of the "Positions" window in the ETL tool.