Building Automation Knowledge Base

  Issue PCT v1.3.3.75 fail to start SmartX server in versions 1.8.x and 1.9.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Defect, user can create SmartX server v1.8.x and 1.9.x but the servers can't start properly. Resolution Uninstall PCT v1.3.3.75 Install PCT v1.3.2.110 (Download), (Client Installer) Install server packages 1.8.x and 1.9.x

Issue Added multiple Lon devices to Lon Network and need to mirror SNVTs from more than one device to the Local Node Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Enterprise Server Cause Using SNVT bindings between devices and the Local Node of the EBO server allows LON communications bandwidth to be optimized by using the LonWorks protocol Send and Receive Heartbeats configured per device. However, it can be a time-consuming task to mirror SNVTs from multiple identical devices. This time can be reduced by selecting SNVTs in multiple devices using search. Resolution Create a new search Search for one SNVT that is available on multiple devices Use this article to create the mirrored SNVTs in the local node: Creating Network Variables Automatically Search for the next SNVT that is available on multiple devices Repeat until all desired SNVTs are mirrored. RECOMMENDATION: Save the searches for use later when adding more new devices.

Issue Troubleshooting steps for the Infinet and MSTP bus. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum SmartStruxure RS-485 Infinet BACnet MSTP Cause Methods are needed to troubleshoot the Infinet and MSTP bus Resolution This is not a comprehensive list of all methods for troubleshooting, but a starting point. The Infinit-mstp troubleshooting document is available here. NOTE If BACnet MSTP devices do not support COV subscriptions, then care must be taken when reading values (eg EBO trends or alarms) as excessive traffic can be created that overwhelms the communication bus. For example, if 30 non-COV BACnet devices have EBO alarms (or EBO change of value trends) bound to 4 objects in each controller, this will create 240 packets (reads/replies) that will be attempted every "Minimum polling Interval". This is likely to fill the MSTP bus bandwidth  

Issue Does the Automation Server support network authentication via Radius Server (IEEE 802.1X)? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause AS supports network authentication via Radius Server (IEEE 802.1X)? Resolution RADIUS and IEEE 802.1X are not the same thing, although they can be used together. Remote Authentication Dial In User Service (RADIUS) is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for computers to connect and use a network service. RADIUS is a client/server protocol that runs in the application layer, using UDP as transport.   The RADIUS server is usually a background process running on a UNIX or Microsoft Windows server. RADIUS serves three functions: to authenticate users or devices before granting them access to a network, to authorize those users or devices for certain network services and to account for usage of those services.  IEEE 802.1X is an IEEE Standard for port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. It is a mechanism used in (mostly) switches and wireless access-points to allow or block devices to access the network (or granularly allow access to parts of it).   For example, if you have a network port in a meeting room, you can enable 802.1x on the switch port and configure it in such a way that when an employee connects they have access to the entire network, but if a guest connects (with a temporary password) they can only reach the Internet and if a passer-by is tempted to try his luck, they cannot access anything at all. Does IEEE 802.1X also use RADIUS as it's underlying authentication mechanism? Yes and no. IEEE 802.1x uses Extensible Authentication Protocol (EAP), the drawing below shows that for wired 802.1x: EAP over LAN (EAPoL) is used between the Supplicant (software on a computer) and the Authenticator (switch). EAP is then usually tunneled over Radius between the Authenticator and the Authentication Server, but it can also be done over Diameter (the successor to Radius). For wireless, it is similar in the sense that there is also no Radius between the supplicant and the authenticator, only between the authenticator and the Authentication Server (to tunnel the EAP). From EBO 2022 the AS-P and AS-B can be configured as supplicants on a network protected by IEEE 802.1X security. See the IEEE 802.1X Security Webhelp topic for further details.   Note: MPx/RPx do not support 802.1x network authentication, see the SpaceLogic controllers MPx/RPx do not support 802.1x network authentication Knowledge Base article  for further details.    

Issue Getting the connection error below when using Microsoft SQL server as External Log Storage for EBO. Error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] SSL Security error [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] ConnectionOpen (SECDoClientHandshake()). [Microsoft][ODBC Driver Manage     Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Enterprise Central (EC)   Cause When EBO connects to the Microsoft SQL server it uses the ODBC installed on the computer. It will use the ODBC version which comes with the OS and not the newest one installed on the computer. In this case that was too old to work with the Microsoft SQL server Resolution It is possible to specify what ODBC version EBO should use. First check what ODBC version is installed on the computer. Enter ODBC in the search bar on the computer Open ODBC Data sources and select the Drivers tab. Open EBO and navigate to the properties /External Log Storage/Microsoft SQL Server in the system tree. In the Database name field it is possible to specify which ODBC version EBO should use, see picture below

Issue MQTT client from an AS-P cannot establish communication with the Mosquitto broker installed on the machine that hosts the Enterprise Server (ES). At the same time, the MQTT client from the ES was online with the Mosquitto broker. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server IoT messaging MQTT (Messaging Queuing Telemetry Transport) Cause In version 1.6.x and earlier from the Mosquitto broker, the option - allow_anonymous [ true | false ] from the configuration setup (e.g. mosquitto.conf — the configuration file for mosquitto) of the broker was defaulted to  true  unless there were other security options set.   In recent versions of the broker, the option allow_anonymous defaults to  false - Unless no listeners are defined in the configuration file, in which case it set to  true  - but connections are only allowed from the local machine if external connections are required; specific port listeners need to be set. Resolution To configure the MQTT Mosquitto broker for insecure communication with an EBO server, follow these steps.  Download the Mosquitto broker latest version from the Eclipse website and install it on the host machine. Locate the mosquitto.conf file in the  Mosquitto installation folder (Default: C:\Program Files\mosquitto). Edit the mosquitto.conf file with a text editor application (e.g. Notepad, Notepad++). Setting up the  allow_anonymous configuration as true and the listeners to the desired communication ports (e.g. 1883: This is the default MQTT port. 1883 is defined at IANA as MQTT over TCP. 8883: This is the default MQTT port for MQTT over TLS.)   Check the Video attached, which includes the basic configuration of the mosquitto.conf file.   

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Page 1031 of the hardware reference guide only states wire cross-sectional area: 0.34 to 2.5 mm 2 (22 to 14 AWG) and not the number of wires allowed to terminate. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24V Building Operation Room Controller (RPC) 230V Cause Documentation clarification. Resolution It is OK to terminate up to 2 wires into each terminal as long as the total area of the wires does not exceed 2.5mm 2 .  

Issue Model and Device Name from SLP sensor via Modbus RTU Product Line EcoStruxure Building Operation Environment Automation Server AS, ASP, ASB SpaceLogic Sensor SLP Cause The Model, Device Name and Serial number are 64bit values and need to be collected with a single query to get the correct data. Script and Function Block programs can not manipulate 64 bit values - Model Register 9, 64bit, read only, Read Function Code 4 - Serial number Register 42, 64bit, read only, Read Function Code 4 - Device Name Register 7, 64bit, read/write, Read Function Code 3 (currently the documentation shows these as 32bit) Resolution A simple way to collect the Model and Serial Number is shown below This involves creating a Modbus Poll Group for the 4x 16bit parts of the 64bit Modbus Register. This will effectively query the 4 registers in a single packet, ensuring the correct data is collected. The same method can be used to collect the Device Name, but this value cannot be written using the same Group, as block/group write is not supported in EBO Create a Modbus Poll group containing the four 16bit registers, then create a String variable Then create a script to convert to ASCII characters

Issue Upgrading SQL Express to a paid Edition of SQL for EcoStruxure Reports Server Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Express Cause SQL Express 2008 R2 (for example) is limited to 10 Gb of Storage and 1 Gb of Ram usage. Many sites need a larger, more robust database than this allows. Resolution NOTICE: Before beginning, it is important to understand the difference between the Instance name and the version of SQL running.  The default instance name used in the the SQL Express version of SQL is SQLEXPRESS. This can be changed to anything during installation, but cannot be changed later.  This means that when upgrading to SQL Enterprise edition, the SQL instance name will still need to be SQLEXPRESS. The instruction below assumes the instance name is SQLEXPRESS and will be typed in that manner.   Perform a full backup of the Enterprise Server and Reports Server before beginning any upgrade process. Save these files to an external drive. Purchase a supported edition of SQL for the revision of EcoStruxure Building Operation WebReports being used. Please check the data sheet for the release to obtain this information. Open the Command Prompt and Browse to the location of the installation files for SQL. This should be the folder containing the setup.exe file for the new version of SQL Enter the Command "setup /ACTION=editionupgrade /INSTANCENAME=SQLEXPRESS /PID=XXXXX-XXXXX-XXXXX-XXXXX" NOTE:If  not using the default instance name, enter the correct instance name in place of SQLEXPRESS. PID is the product ID that came with the installation media. In some cases, this will be left out of the command string and entered later. (setup /ACTION=editionupgrade /INSTANCENAME=SQLEXPRESS) The SQL Installer will open. After the Setup Support Rules operation runs, click OK Click Next Verify the Product Key and click Next. Accept the License Agreement and click Next Ensure that the correct instance of SQL is selected and click Next. After the Edition Upgrade Rules runs, click Next Review the Upgrade Summary and click Upgrade When Complete click Close Open the SQL Server Configuration Manager using the start menu and verify that the SQL Server (SQLEXPRESS) service is running and that the SQL Server Reporting Services service is running. If either are stopped, right click and select the start option. Verify the upgrade is successful by opening a Web Browser and entering the URL "http://localhost/Reports_SQLEXPRESS" It should now be possible to see the option to directly edit reports in Report Builder. Log into the WebReports Interface. Notice that the initial report showing Database usage no longer runs.

Issue Device Administrator is not able to load new database version into AS-P. Error message “New database failed” Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause The new McAfee firewall policy where Local the firewall is blocking ICMP6 to the PC. The device needs to be able to "call back" to the PC. If that doesn't happen, the upgrade will not continue and stop at exactly 70%. This is seen in 3.x, EBO 2.0 does not exhibit this issue The device may be defective due to software or hardware error. Resolution   The McAfee firewall issue can be resolved by:  Temporarily disabling the local firewall Trying another PC since McAfee policy or some restriction might have caused installing 3.2 to fail. Another possible solution for this issue which we have seen working is to first install version 3.1 using DFU mode and create a new database and then upgrade to version 3.2 using IP connection.   How to cross-testing and identify if the device is defective? Use the same PC and Device Administrator to install a new DB on a different AS-Ps.  If the same PC can install a new DB on a different AS-P then the issue is not on the PC. Use another PC with the same version of Device Administrator to install a new DB on the suspecting device. If it fails to install a new DB then RMA is needed. Remember to DFU the device before installing a new DB.

Issue Error messages in Workstation saying "No valid license to add AS found", when trying to add one more AS-P to the ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium (AS-P) Demo License file Cause The error message is caused by an expired demo license. When using the Demo License file, the ES checks the Licence at startup, and when doing some operations, like adding AS-Ps. If the Demo license expires, the ES may still work, but you cannot add any more AS-Ps. License Administrator is unable to locate the License Server by using @localhost or IP address(@xxx.xxx.xxx.xxx). Resolution Download a new demo license file from EcoXpert Extranet – The Exchange, and upload it to License Administrator. After the new Demo license file has been added to the License server, you may also need to restart the ES to make sure the new license file will be in use. For more information about the Demo license, please refer to the article EcoStruxure Building Operation Evaluation License for 2.0 and up. When using EBO 2022 v4.0.x and later, the error message (No Valid License to add AS found) can also be displayed if the attached AS-x embedded demo license has expired. Add a current embedded demo license to the device administrator and then re-activate the license to all AS-x servers that require it. Please refer to the article How to activate a demo license on an Automation Server at EBO 2022  Go to Control Panel> System and copy the Device Name Update @localhost in License Administrator > License Server Address to the @"Device Name" Reboot the System(PC) Example The Device Name is "computer1".     Update the License server address to "@computer1" since the Device Name is "computer1"  

  Issue In a system that is working normally for about 3 years EBO 3.1.1.312, appeared an alarm message saying there is a “Duplicate of Local Network” in “BACnet Gateway to network 1”.     Product Line EcoStruxure Building Operation Environment • Building Operation Workstation • Building Operation Automation Server Cause Sometimes there is a device (you can check under device discovery) possibly a router or a gateway where the primary network has NOT been configured as 1, and the secondary network was set as 1 which should be assigned a unique network ID. Also sometimes gateways only require configuring one network which also in this case should be assigned the unique ID, not 1. Resolution The main site network was set as Network 2 Another network, that was routed from the site network was set as Network 1 The main site network was changed to 1 and the other network needs to have a unique network number, so was changed to 2. They also have Cisco and Philips controllers which have their standalone networks and had already been configured with used network numbers so were changed to 3 and 4 accordingly. *Please Note: All controllers must be warm started after the Network number changes so the BACnet network can be remapped in the controller

Issue When DHCP network configuration is Enabled, the gateway changes when connected to an ADv3 through a Y-Cable. If other applications or devices need to route to the AS-P through the Gateway, the change of gateway will break the connection.       Product Line EcoStruxure Building Operation Environment Advanced Display v3 Cause AS-P overwrites its Default Gateway when connected to an ADv3   Resolution Update the Address Method to Static then enter the IP and Subnet address manually.  

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 For various reasons, it may be necessary at times to change a b3's Device ID (Object ID) to avoid a duplicate. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) BACnet Cause There is little or no formal documentation on steps to change the Device ID of an existing B3 controller. Resolution As seen in the screenshot below, once a b3 is added to the network, its Device ID, EBO Object ID, can not be changed.  The reason for this is that the Device ID references the device and objects contained within it.  Once the ID is changed, such references will become orphans. To successfully give the b3 a different Instance/Device ID the b3 must be deleted from the MSTP Network in the Building Operation database and recreated   Write down the b3's Serial Number, MAC Address, Model, and BACnet Name before deleting it. Right-click and Export all BACnet Objects within the b3's Application Folder to file (.xml) Delete the b3 from under the MSTP network. Re-create the b3 manually using its S/N, MAC, Model, Name, etc but enter the new Device ID Commission/Download the b3 to get the new ID to take effect Import the File (.xml) exported in step 2 back into the newly created b3's Application Folder Commission/Download the controller again Important: References to the old Device ID will no longer work and must be re-created.

Issue Are the Infilink and B-Link interchangeable or can they be converted? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infilink 200 B-Link Cause Both units are RS-485 repeaters; is there a difference? Resolution You cannot convert from an Infilink 200 to a B-Link. They are both RS-485 repeaters, but the circuitry is slightly different to handle the electrical requirements of the BACnet MS/TP and the Infinet. You must use the correct unit for the network type you have. The multiple ports on both repeaters (Infilink and B-Link) allow you to construct a star topology configuration, but note that devices in each spoke (port on the repeater) MUST be connected in a daisy chain topology. Neither product contains any firmware that can be changed.

Issue Values in EBO from a PM5000 series energy meter do not update Product Line EcoStruxure Building Operation, Field Devices Environment Building Operation Server BACnet PM5000 series energy meter Cause The EBO trace log shows a lot of BACnet related error messages, such as:   nsp.pin.BACnet.VariableProperty Subscription to ~/BACnet Interface/IP Network/PM 5340/Application/THD Current - Ph G attempted COV, but will POLL due to BACnet error: 0x00030013 (resources,no_space_to_add_list_element)   This error indicates that a Change of Value (COV) subscription is being attempted but has failed. This is due to a resource issue with the device, i.e., error class 0x0003 from error code 0x00030013. The error is no space to write property (0013 part) which suggests the subscription limit of the device has been reached. Refer to the Decoding BACnet Errors Knowledge Base article for further information on decoding the error code.   Reviewing the PM5300 series user manual reveals that the device only supports 20 COV subscriptions.     Resolution Remove BACnet objects that are not required in EBO, it is unlikely that fewer than 20 values will be practical. Disable COV for the device in EBO. This can be done via the service_blacklist as noted in the BACnet RULES implementation to disable features such as readPropertyMultiple, COVs etc How to disable RPM (readPropertyMultiple), COVs etc services in AS/ES BACnet interface. Knowledge Base article. The following is an example service_blacklist for the PM3450 <blacklist> <rule> <vendor>10</vendor> <model>PM5340</model> <no-cov/> <no-rpm/> </rule> </blacklist> Polling can put an unintended load on the polling device and the polled device. The polling intervals should be adjusted using the settings on the BACnet Interface. This is available from BACnet Interface -> Properties -> Advanced and scroll all the way to the bottom as shown below for an ES. If looking at the option for an Automation Server it will also have additional options for the RS485 communication ports. Minimum polling intervals in the range of 5,000 to 10,000ms are a good starting point.  

Issue Chinese characters in TGML graphic become odd characters in WebStation, but display fine in WorkStation Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista Webstation EcoStruxure Building Operation WebStation Chinese OS Cause The encoding method of WebStation is different from the one used in WorkStation. So the font of the Chinese characters should be changed. Resolution Change the Chinese character to Chinese font, like YouYuan or SimHei, etc, then it will work fine.

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 In some cases the event and trend database can grow really big although not all the space in the files is used Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Resolution Stop the Enterprise Server Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Select the event.db or trend.db file from the "historical" folder of the SmartStruxure database folder Execute the following command: vacuum;

Issue WebReports returns only partial results for the Consumption Report when using the Meter Utility Type   Product Line EcoStruxure Building Operation  Environment Building Operation Report Server Building Operation WebReports Cause This is a limitation of the Meter report, where the report returns approximately 50 Meter reports at a time regardless of how many meters are selected. Resolution It is recommended that 30 - 40 meters at most be selected at a time for this report.  Selecting more meters for the report may result in data overlap and unexpected output. For more information regarding Consumption Reports, see the following help topic Energy Monitoring Reports

Issue After configuring the system per Setting up a Local / Internal NTP Server, the Automation Server's time would not sync to the local NTP computer's time. Wireshark capture shows a 'Root Dispersion' greater than 10 seconds. In the screenshots below, 10.169.90.13 is an Automation Server (NTP client), and 10.169.90.6 is the NTP server. CLIENT REQUEST SERVER REPLY This behavior of adding 10 seconds to the root dispersion is only observable when using the internal clock otherwise it is 0. This appears to be the intended behavior by Microsoft so that this NTP server would rank lower if using multiple NTP servers that might have more reliable time. Product Line EcoStruxure Building Operation Environment Automation Server (AS) Network Time Protocol (NTP) Cause The NTP client in the AS ignores the time sent by the NTP server if the root dispersion is greater than 'X' seconds (not known at this time) Resolution In the Windows registry of the machine being used as the time server, make the following change:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\LocalClockDispersion The default for this key is “A” in hex. Change this to “0” and then restart the Windows Time service.  Do this by running the following command net stop w32time && net start w32time. Here is what Wireshark shows after the time has been synchronized. SERVER REPLY