Building Automation Knowledge Base

Issue Is it possible to monitor the status of a Modbus interface/device from within a TGML graphic? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation Building Operation Server Serial Modbus device Cause It's a very common requirement to monitor Modbus devices and interfaces and show this value on a TGML graphic page. Resolution The attached TGML graphic gives a simple example of how to do this. The screenshot below shows the property to bind the TGML binding to. To see the property "NetworkStatus" for the Modbus network in the binding view double click on Modbus Master Network. To see the property "Status" for the Modbus device double click on the Modbus device in the binding view.   

Issue Is it possible to have different stop bit settings in different Serial Modbus devices on the same bus? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Modbus serial communication Cause In Building Operation there is an "Auto" setting for the Serial Modbus communications "Stop Bit" setting. This could be interpreted as "automatically" detecting the Serial Modbus devices stop bit setting. Resolution The "Auto" setting is only designed to detect how many stop bits are required in certain circumstances, such as when the parity setting is set to none and therefore 2 stop bits must be used. The settings used are the Serial Client settings for the entire bus and all the Modbus devices have to be set to match the Serial Client.

Issue The Modbus Server / Client is unable to read the values from address of a 32 bit Modbus register in a Building Operation server Product Line EcoStruxure Building Operation Environment Building Operation server Modbus Cause The original Modbus/JBUS protocol specifies the use of 16-bit integer registers for Analogue Inputs and Analogue Outputs. The number range able to be represented in 16-bits is: Unsigned: 0 to 65353 Signed:     -32768 to 32867    In order to represent larger numbers, it is common for 16-bit registers to be combined to represent 32-bit or 64-bit numbers. When a Modbus Client or Server reads a 32-bit Modbus value, it will be reading two consecutive 16-bit registers. An error will occur if  two 32-bit Local Modbus registers are created in Building Operation using consecutive register addresses since only the starting modbus register address is used for the request.  Resolution When configuring 32-bit Local Modbus registers in Building Operation, the next register address should not be used. Create the next Local Modbus register using the 3rd available Modbus register address. 

Issue What register type should be used for the type called INT64 in the documentation Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Modbus PM Energy meter Cause It is not clear what  Modbus register type should be configured for INT64 Resolution For reading the INT64 on this range of power meters the register definition you need to apply is the "64 bit signed swapped".   Note that this register type is not available in Building Operation versions earlier than 1.5. For further information on Modbus Register Types see the Point and Value Configuration EBO Webhelp topic

Issue When numerically evaluating in a program, what day = 1? Is Sunday or Monday the first day of the week? Product Line EcoStruxure Building Operation Environment Building Operation Script Editor Building Operation Builder for Function Block Building Operation Function Block Editor Cause What is the first day of the week in EBO, this may be required when using ">" or "<" logic in the program. Resolution Script programs handle this differently from Function Block programs.  Function Block programs use Monday as the first day of the week and therefore assign a value of 1 to Monday. Refer to: WDAY – Week Day Script program uses Sunday as the first day of the week and therefore assigns a value of 1 to Sunday. These differences are not handled by the regional settings of the local workstation. WEEKDAY *Exercise caution when using Script or Function Block programming which relates to the first day of the week. 

  Issue The shadow schedule in subordinate AS-Bs is not following the lead Schedule in the ES. When ES transitioned to occupied all of the Shadow Schedules went into Fault and did not transition, leaving the required spaces unoccupied. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Bundled Building Operation Workstation Cause The "Gameday Schedule [Shadow-Read only]" configuration shows that the Exceptions at Priority 10 do not have names.  As such, don't have access to the 'properties'.   Resolution By detaching the server and deleting the binding to the 'Lead object', we can delete these events and the fault condition will disappear. As a workaround, delete these exceptions from the Lead Schedule, save, and then add them back (with a name)

  Issue Site upgraded SmartX IP Controller from 2.00.03.1203 to  v3.02.03.02109. When the upgrade was completed, they attached the SmartX room sensor to the controller.  The sensor appeared to update but the screen display was distorted.             Product Line EcoStruxure Building Operation Environment • Building Operation Multi-purpose VAV • Building Operation SmartX Living Space Sensor • Building Operation Workstation   Cause With a blank database, an MP-V with firmware V2.00.03.1203, when the sensor is connected the screen is distorted, but  after upgrading the MP- V to firmware V3.02.03.02103 , the screen display shows up with no issues Something is breaking for the site when attempting to go from 2.0.3.1203 to 3.2.3.02103 Resolution Upgrade the firmware to a higher version (ex 4.x). After the MP-V is upgraded, the sensor will upgrade automatically which takes about 10 to 15 minutes and the status will be operational. The screen will then display properly.

Issue The Enterprise Server shows that licenses are not available on the license server which is installed on the local host machine. The Flexnet server webpage shows that licenses are available but have not been used by the Enterprise Server.   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause In some cases, the Enterprise Server may have trouble resolving the @LocalHost address. It is not known why this affects only some licenses. Resolution On the License Server Address page of the License Administrator enter the IP address or computer name of the local host machine instead of @localhost.      

Issue When trying to change the Debug Mode from False to True for enhanced Troubleshooting the setting is returning back to False and no extra Debug Data is generated. Product Line EcoStruxure Building Operation, Other. Environment Web Services Cause For troubleshooting of the Web Service Handler application, a Debug Mode can be enabled by editing the settings.xml file in the installation directory and changing the Debug Option from False to True.  The Service needs to also be stopped before the change is made and saved.     However, users can find that even when the Service is stopped and the Debug Option is changed and saved,  as soon as the Service is restarted the Debug setting reverts back to False and no Debug Data is generated.  Resolution If users are using the Configuration Dialogue to Stop the Service and then leave that Dialogue open it locks the settings.xml file and the change to Debug Mode cannot be saved.     If all Dialogues are closed before the settings.xml file is changed/saved, the Debug Mode change to True is successful and a new debug.log file is generated in the installation directory as soon as the Service is started.

Issue The connection to the MQTT broker is not working and the MQTT client in the ES is offline following an upgrade from EBO 2022 to EBO 2023. The following error message can be seen in the ES trace.log: nsp.csc.mqtt.MqttNetwork Connection failed: TCP/TLS connect failure  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central MQTT integration Cause The reason for the connection issue is that the client certificate that is used is (self-signed) signed using SHA1. Since OpenSSL 3.0 this is forbidden at the default security level (which EBO is using) due to it having less then 80 security bits. See text in picture below taken from https://www.openssl.org/docs/man3.0/man3/SSL_CTX_set_security_level.html The default level is 1 and that is the setting EBO is using. Resolution Change the client certificate to one not using signing signature MD5 or SHA1. The certificate signature can be checked using the following OpenSSL command: openssl x509 -in cert.pem -noout -text Below is an example of how to use OpenSSL to check the certificate signing signature on the client certificate:

Issue The System License Information screen has a lot of useful data on the status of licenses in the EBO system. Is there a way to export or screenshot the entire System License Information page? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Cause Unable to save or export the System License Information screen Resolution There is no option to print or export the Control Panel System license Information screen. It is possible to get a reasonably close facsimile by viewing the LicenseStatus item in System>LicenseManager and adding columns for Required Licenses, Checked Out Licenses, Installed Licenses, Available Licenses, and License Violation.   This can then be Exported in XLSX format for future reference or if required by Product Support  

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 AS status LED solid red for a few seconds followed by a quick blink. Device administrator and/or event log shows system alarm ..."Error - Upgrade using DFU mode"  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS, ASP, ASB Building Operation Device Administrator Building Operation WorkStation Cause The indication of "Error – Upgrade using DFU mode" occurs due to the fact that a possible problem with writing to the file system has been detected when booting the system. This error can be seen in WorkStation as an Alarm Event, in the Server Logs, or in Device Administrator. Nosync errors are usually seen in the system log. The configuration of the system could have been compromised as a result, although the issue is not necessarily fatal and therefore the AS is allowed to run and the situation is indicated via the red status light. A system alarm is also generated as a warning as seen in the screenshot above. Resolution Since the AS file system could have been compromised, it must be re-initialized from scratch. To clear the red light: Make sure a backup of the AS is available. Attach the Device Administrator to the AS via USB and put the AS in DFU mode (press the reset button 3 times in rapid succession) Install a new database Once the AS has had its FW and database reinstalled, restore the backup using Workstation. NOTES See Error – Upgrade Using DFU Mode  If this error occurs, especially if it occurs multiple times on the same server, check the site installation include Grounding/Earthing and power supplies and for possible EMC issues (Electromagnetic Compatibility)

Issue When trying to use WriteProperty to a 3rd Party BACnet device the following error is generated : "An attempt has been made to write to a property defined as inaccessible through the BACnet protocol write service" Product Line Andover Continuum Environment BACnet  Cause The error can be seen when using WriteProperty OR when attempting to Manually Command a BACnet Point on a 3rd Party Device Resolution The property that is being commanded, is not available to be written to in the 3rd party device. Many properties and object classes cannot be written to on BACnet devices, this is often defined in the devices PIC Statement which has hopefully also been BTL Tested. Some BACnet devices allow writing to be enabled/ disabled, but this must be set up on the 3rd Party device itself depending on the site requirements.  An example of this is in the Jace unit where there is a regular BACnet user that has no write capabilities from 3rd party devices, so to allow this requires a tick a box for "Super user".

Issue When the EWS is installed on the same machine using the service then all packets will be going to the localhost and will not hit the NIC so will not be captured in a Wireshark packet capture. Product Line EcoStruxure Building Operation, EcoStruxure Security Expert Environment Security Expert Building Operation Enterprise Server Building Operation Automation Servers (AS-P, AS-B) Cause Packets sent between services on the same machine (like SOAP and EWS) do not hit the NIC and therefore cannot be captured with the default configuration of Wireshark using the WinPcap packet sniffing library.  Resolution Replace WinPcap with Npcap to emulate a loopback NIC for packet capture. Go to https://nmap.org/npcap/ for details on the library. Download the library installer from https://nmap.org/npcap/#download Uninstall WinPcap. Install Npcap. Npcap will then create an adapter named Npcap Loopback Adapter. In Wireshark choose this adapter to capture, loopback traffic will be the seen the same way as other non-loopback adapters. This can be tested by typing in commands like "ping 127.0.0.1" (IPv4)  or "ping ::1" (IPv6).

Issue How to associate BACnet IO points created under the BACnet Interface of the Automation Server with IO points on the Automation Server's IO bus. Product Line EcoStruxure Building Operation Environment Building Operation Servers 1.4 and above Building Operation Workstation Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Connect physical IO points to BACnet network controllers. Resolution BACnet Association Tool (EBO V3.0 or higher) BACnet Association Tool will map properties of a central IO point with corresponding properties of a BACnet point. The tool is capable of mapping a single IO point with a single BACnet point, optionally by also creating a BACnet point, and removing the association between IO and BACnet points. To open the BACnet Association Tool, Select the IO Bus or IO Module, BACnet Interface, Application Folder, or the BACnet point, then in the Actions menu, click BACnet Association Tool. Most useful is the ability to associate multiple IO points with their corresponding BACnet points in one operation. The tool can be run from a variety of different container types in the WorkStation Tree view, including an IO point, BACnet Point, CIO Module, or the entire IO Bus (as shown below). For more information refer to WebHelp articles: Creating and Associating BACnet Points to I/O Points (se.com) and Associating or Updating BACnet Point Associations to I/O Points (se.com) NOTE: Please be aware applying the BACnet Association Tool retrospectively, to an already configured site, can remove bindings to outputs.  For example output bindings in Script or Function Block programs.  As shown below, if the tool is used to create a BACnet Associated point for an output already bound to a program (1) the Requested Value will be replaced by the Associated Value of the BACnet point (2). This is due to how the BACnet Association Tool uses the bindings, where the newly created BACnet point should be used instead of the IO point.  The solution is to update the removed program binding (3) to use the BACnet Associated point value (4).   SBO 1.4 to 2.x To associate BACnet IO points created under the BACnet Interface of the Automation Server to points in the IO Bus in SBO 1.4 and above... The association is made via a read reference, so if we think of the two objects as one being the source and the other the destination you configure the association from the destination object so in the case of an output you configure the association from the BACnet object (in this example BO1). In the case of an input, you'd configure the association from the IO Bus input as that would be the destination object, in other words, the recipient of the value. (NOTE: for versions prior to 1.4 see Bacnet and StruxureWare Building Operation Central IO points) Create the points. In this example, we are associating an IO output point named 'Digital Output 1' with a BACnet Binary Output named BO1. From the properties page of the IO Bus point (Digital Output 1 in this example) click on the gear icon to the right of the 'Requested value' field. In the 'Requested value' editor click the navigation icon (...) to the right of the 'Reference' field and navigate to the 'Associated Value' of the BACnet point. Save the configuration changes. Now that the values have been associated setting the BACnet output value (BO1) will drive the IO Bus output (Digital Output 1)  

Issue How to configure search object to display SpaceLogic controllers IP settings "Changes pending" in the search's list view Product Line EcoStruxure Building Operation Environment Space Logic IP controllers  Cause Confusion when attempting to find the appropriate type to include in the search  Resolution The IP settings "Changes pending" property is not a property of the device but rather a property of the IP Network Port as seen in the screen shot below  

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 correctly. Before beginning these steps, ensure all necessary 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 MNB firmware may not match the version reported in EBO and Building Advisor Portal. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment I/A Series MNB I/A Series WorkPlace Tech Building Operation Workstation Building Operation Building Advisor EBO Health Module Cause MNB firmware is upgraded via the WorkPlaceTech Commissioning Tool independent of EBO, and EBO reports firmware to Building Advisor Portal for use in BMS Health Module. Example cases where controllers are upgraded after adding to EBO are: MNB controllers added with factory default firmware version MNB controllers transitioned into EBO with existing older firmware version MNB controller that was upgraded to the latest was replaced with MNB Controller at factory default firmware version Resolution Create a Saved Search to identify all MNB controllers in the system Create New Search Enter * in Object Name Field Click ... button next to Include Types: and add all the MNB controller models Right-click on Column Header and select Add/Remove columns to select Firmware revision and Model name, and remove Description Save the search and select a location and name it Run the search to identify all the MNB controllers Sort by Firmware Revision to find older versions. MNB-1000 will end in 01.5xx and all other MNB ASC models will end in 01.4xx Update firmware version from the controller(s) Select one or more MNB controllers Right-click and select Device -> Upload Configuration. *WARNING*: Ensure you do NOT select Download Configuration  Now EBO is reporting the correct firmware in the controller and will upload this information to Building Advisor Portal, if cloud connectivity is established. Upgrade any MNB controller firmware with WorkplaceTech Commission Tool to the latest version and perform Steps 2 and 3 to keep EBO updated.

Issue It is not clear how to replace an existing AS with a new AS-P Product Line EcoStruxure Building Operation Environment Automation Server (AS) Automation Server Premium (AS-P) First detected in version 1.7 Cause Detailed instructions on how to replace an existing AS with a new AS-P are needed Resolution WebHelp references Automation Server Replacement Using Restore Automation Server Replacement Using Restore Workflow Overview Main differences between an AS and an AS-P: In the AS-P, the RS-485 ports have been re-located to the top. The AS-P has 2 Ethernet ports; port 2 can be used as a switch only as of SBO version 1.81. AS-P device USB port format changed to mini USB. Operator Panel port has been removed. Hardware factory reset has been removed. AS-P uses pluggable connectors for field buses. (not shown in picture above) Consider the power consumption. AS-P requires 10 watts, while the Automation Server only required 7 watts. Preparations In preparation for replacing an Automation Server with an AS-P the following considerations must be made: Power consumption Since the AS-P consumes three more watts than the classic Automation Server, the power budget needs to be reviewed to check whether an additional power supply and/or rearrangement of the current configuration is needed, if the configuration includes IO modules. Terminal base The terminal base for the classic Automation Server can be used with the new AS-P after removal of the upper terminal block. Note though that all field buses wiring has to be moved to the pluggable connectors used with the AS-P. RS-485 field bus re-wiring Since the RS-485 ports and connectors have been relocated, the termination at the server of any field bus located on those ports will need re-wiring. Also, the physical specification of the RS-485 port is changed in the AS-P, so review whether the termination resistors needs to be replaced. Refer to Configuration Selection for Generic RS-485 Network Devices AS-P firmware Unlike the classic Automation Server, the AS-P ships from the factory with no firmware installed. Make sure to procure the appropriate Device Administrator firmware to install in the unit. First version that supports the AS-P is 1.7. Note once again that the USB port format in the AS-P is mini USB, so procure the appropriate USB cable. Backup file Make a backup of the classic AS to be replaced, the AS-P will restore from a classic AS backup but this is a one way process, the classic AS will not restore from an AS-P backup file. If the classic AS is running an older version of firmware, it will have to be upgraded first to at least 1.7.2. Power budget review Since the AS-P consumes 10 watts of power versus 7 watts for the classic Automation Server, it is necessary to review the power budget to ensure there is enough power for the AS-P, if the Automation Server being replaced is hosting IO modules. One power supply (PS-24V) can supply 30W. The following table shows power consumption for the different device types Device Power AS-P 10 AS 7 DO-FA-12-H 1.8 DO-FA-12 1.8 DO-FC-8-H 2.2 DO-FC-8 2.2 DI-16 1.6 RTD-DI-16 1.6 AC-4 11.1 UI-16 1.8 AC-2 5.5 AO-8-H 4.9 AO-8 4.9 AO-V-8-H 0.7 AO-V-8 0.7 UI-8-AO-4 3.2 UI-8-AO-4-H 3.2 UI-8-DO-FC-4 1.9 UI-8-DO-FC-4-H 1.9 UI-8/AO-V-4 1.0 UI-8/AO-V-4-H 1.0 In case one or more additional power supplies are needed, refer to the example given in last part of this article.   Note: The following "replacement procedure" applies to SBO 1.7.x, 1.8x, 1.9x, EBO 2.0x and 3.0.x and 3.1.x. The AS-P must be running the same version as the original AS backup. The AS was no longer supported from EBO 3.2.x. If the site needs to take the AS-P to EBO 3.2 or later, the following should be followed at the AS supported version, then once the AS backup has been restored to the AS-P, the AS-P can be upgraded further, following the supported upgrade path, which can be found in the release notes for the specific EBO version.   Replacement procedure The following procedure assumes the classic Automation Server is being replaced with a brand new AS-P from the factory If the Automation Server is hosting IO modules then perform the steps in the 'Power Budget' section below before going to the next step. Perform pre-maintenance procedure per site requirements, i.e. put equipment in hand control mode etc. Pull out the classic Automation Server from the terminal base. The hardware is designed for hot swapping so there is no need to power down the system. Remove the terminal block from the terminal base as indicated above. Insert the AS-P in the terminal base. Connect Device Administrator to AS-P via USB and install a new database on it. You may want to check the 'Set time on device' check box to initialize the time in the AS-P since its current time is most likely at default if this is a brand new unit or a unit that has been powered down for a while. Using Device Administrator set the communication parameters of the AS-P (IP address etc) to match the settings of the classic Automation Server being replaced. Connect Ethernet cable from network switch to Ethernet 1 port on the AS-P. If a hotfix was installed on the Automation Server that is replaced, apply any hotfix needed to match the version of the firmware in the AS-P to the version of the backup from the Automation Server. Since the AS-P should now be able to communicate over IP the application of any HF can be done either over USB or IP. Using WorkStation, log in directly into the AS-P and restore the backup from the classic AS. Insert pluggable connectors for field buses. If there is an Enterprise Server, log into Enterprise Server from WorkStation and verify the newly swapped AS-P is online. Verify IO modules (if any) are online. Verify field devices (if any) are online. Return the system to software control per site requirements. Verify the system is operating correctly then perform a backup of the AS-P. Power supply addition example Consider the following system If we do the math, the power consumption of this system is 29.8 watts. To avoid exceeding the capacity of the existing PS we need to add an additional PS to the configuration before we replace the Automation Server with an AS-P. In order to maximize the use of the capacity of the first PS we will add a new PS at slot #7 and move the UI8AO4 IO module from slot #7 to slot #8.   Steps Disconnect the UI8AO4 IO module making sure it powers down. It is necessary that any IO modules being relocated on the IO bus are powered down so that they 'forget' their current module IDs. *** Logon to the Automation Server, make sure UI8A04 shows offline then edit the module and change its Module ID from 7 to 8. Insert power supply at slot #7 Attach the UI8A04 after the new PS (slot #8), when it powers up it will obtain its new Module ID (8) from the Automation Server. Last, if the module’s name contains the ID (Slot07:UI8AO4) it may be a good idea to rename it using the new ID to avoid confusion. (Slot08:UI8AO4) *** It is absolutely necessary that all the modules that will change IDs be powered down, if there are multiple power supplies in the chain make sure to power down all power supplies that are supplying power to any modules that will change slot #. When removing or inserting IO modules or handling S-Cables, care should be taken not to bend or otherwise damage the pins that connect the module to its IO terminal base, any damage to the pins may cause the module address to shift.   Tip There is a tool on the community (SBO xbk Analyzer) that can be used to automatically calculate the power budget from a backup of the AS/AS-P. Here is the power budget report generated from the tool after addition of second power supply at slot #7 before replacing the classic AS with an AS-P. The total power consumption is 29.8 watts but we have increased the power capacity of the system to 60 watts with the addition of the second power supply.   The instructions above are available as a PDF: Replacing a classic AS with AS-P

Issue After installing or upgrading from EBO 2.0.x to EBO 3.x.x or EBO 4.0.x, the Enterprise Server or Enterprise Central will not start. When the "Start Service" button is pressed in the Building Operation Software Administrator the server status is stopped and does not change and no activity is seen in the system log area. Product Line EcoStruxure Building Operation Environment Enterprise Server Enterprise Central Cause The vcruntime140.dll file is missing from the Window’s system32 folder. Resolution The vcruntime140.dll file is installed as part of the Visual C++ Redistributable for Visual Studio 2015 installation. Visual C++ Redistributable for Visual Studio 2015 can be downloaded from the link below. https://www.microsoft.com/en-in/download/details.aspx?id=48145   If you have later versions Visual C++ Redistributable for example Visual C++ Redistributable for Visual Studio 2017, Visual Studio 2015, 2017, 2019, and 2022 can be used to save uninstalling version 2017. https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170  

Issue Do the SpaceLogic controllers MPx/RPx support network authentication via Radius Server (IEEE 802.1X)? Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Room Controller Cause As noted in the AS supports network authentication via Radius Server (IEEE 802.1X) Knowledge Base article the Automation Servers (AS-P, AS-B) support the 802.1x protocol.   The SpaceLogic controllers MPx/RPx do not support it. Resolution Since the  SpaceLogic controllers MPx/RPx do not support 802.1x network authentication, alternative mechanisms must be provided to authenticate MPx/RPx controllers.   The SpaceLogic controllers MPx/RPx send a gratuitous ARP containing the device MAC address on start up and it is possible to use the MAC Authentication Bypass (MAB) option on the network switch. When MAB is configured on a port, that port will first try to check if the connected device is 802.1X compliant, and if no reaction is received from the connected device, it will try to authenticate with the AAA server using the connected device's MAC address as username and password. The network administrator then must make provisions on the RADIUS server to authenticate those MAC-addresses, either by adding them as regular users, or implementing additional logic to resolve them in a network inventory database. Many managed Ethernet switches offer options for this.