Building Automation Knowledge Base

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

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP server from the virtual machine. Resolution To change the Notification Address in the "Setup for use with remote server" to "localhost". 1. Select "Setup for use with remote server" after PCT start. 2. Update the "Notification address" to localhost  

Issue How to get server date and time into a datetime variable. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building  Operation Enterprise Server Cause Documentation Resolution Create a 'Value' object of type 'Time Stamp Value' in the server. Right click on the server's name and select 'Edit bindings' Find the time stamp value created in step 1 in the object tree on the right. Bind the value of the time stamp object to the server's time as seen in the screen shot below.

Issue Update OS, changing a controller, BACnet to Infinet or Infinet to BACnet Can b3 controllers be converted to i2 controllers? Can i2 controllers be converted to b3 controllers? Converting between bCX4040 and bCX9640   Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 Controllers - See Compatibility Matrix bCX Controllers - Continuum 1.7 onwards Cause Only a limited number of controllers can be converted, BACnet to/from Infinet, using Update OS. Resolution The following controllers can be converted between Infinet and BACnet, using the appropriate firmware files: bCX (bCX4040 to/from bCX9640) (options like Xdrivers, node count, IO modules and expansion IO modules are not effected) i28xx-V - b38xx-V (i2865-V to/from b3865-V, i2866-V to/from b3866-V, i2885-V to/from b3885-V) Please see link for swapping the firmware of non -V model i2/b3 Attempting to flash (Update OS) any other controllers BACnet to/from Infinity is not recommended. In nearly every instance, the result will be a non-functioning controller.   UPDATE: A procedure is now available to convert the non -V i2s to b3s in the field https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/416712    (Note: In the bCX controllers, the ACCNetID will revert back to the default of "1", you may need to change this in the Controllers configuration webpage back to what it should be.  See Will IP settings persist when flashing a bCX4040 (BACnet) to a bCX9640 (Infinet)? for details.)   Please refer to Exchange for specific firmware: BACnet Firmware Infinet Firmware The following can be used as a general rule to determine which OS is currently running in the controller. bCX only. (b3 & i2 CPU is green) CPU LED is Green = BACnet OS CPU LED is Yellow = Infinet OS

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. 

Issue What type of objects can be viewed using "Edit in Spreadsheet" mode Product Line EcoStruxure Building Operation Environment Edit in Spreadsheet mode Building Operation WorkStation Cause The objects that can be edited in Spreadsheet mode vary depending on the device or object you are viewing Resolution When you are viewing the AS IO Bus or an AS IO module, then clearly the only objects that cab be configured are Points. Below you can see the "IO" tab, but the "New" tab is greyed out. When viewing a "Folder" in an AS then possible tabs are "Alarm", "Value", "Folder" or "Trend". Below this can be seen (v1.3) LON device, Modbus Devices etc. will allow different access via the spreadsheet mode. This will vary for different versions If you need to find out what spreadsheet access is possible with your chosen device/folder, then it is best to navigate to the relevant Object, folder or device, enter Spreadsheet mode, then check what tabs are available when "New..." is select NOTES: If there is only a single possible spreadsheet object type, then even if there are zero of these object types created, then a blank spreadsheet is shown. If there is more than a single possible spreadsheet object type, and none of these object types are created, then no blank spreadsheet is shown. "New..." needs to be selected. When a row is selected, then an entry modified, all the text data in that row that is visible will be modified. Most EBO objects can be edited using Spreadsheet View with the exception of BACnet Objects. It follows that all objects that exist within MP/RP series controllers cannot be edited in Spreadsheet View as these are all BACnet Objects (This would include Modbus objects within the RP controllers that are actually BACnet objects) For further information refer to the Spreadsheet Overview EBO Webhelp topic  

Issue System memory usage stays high after exporting projects in PCT (Project configuration tool) Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The exporting process increases memory usage but is still withheld by the project after the process finishes.   Resolution Close the project exported.

  Issue For an AS-P running on EBO 4.0.3.176, in Device Administrator, it is showing the State-Ready (Device crash logs available). When trying to download the debug info, it populates the below error and does not get rid of the logs.   ERROR: Failed to run devadmin3 command cmd with arguments -u -m devadmin3 --sa -v cmd 172.20.214.78 -b *** "rm -f /var/sbo/log/crash/coredump_SM222432005_nsp_servers_2022-09-03_110836.tgz" :rm: can't remove '/var/sbo/log/crash/coredump_SM222432005_nsp_servers_2022-09-03_110836.tgz': Permission denied   Product Line EcoStruxure Building Operation Environment • Building Operation Workstation • Building Operation Automation Server Cause Not running Device Administrator correctly Resolution When opening Device Administrator, ensure to run as administrator as below. This will clear device logs.  

Issue Enterprise Server is taking a very long time to run after restoring the database. Example: in EBO 3.2.3, It would start after 2.24 hours with about 20,000 trend logs, and with 10,000 it would take about an hour. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause When restoring the configuration only of a Database, specifically one that has a lot of Trend logs configured, EBO initializes the Trend DB before starting the ES. Resolution Select to restore ALL DATA of the database, thus the Trend Database has already been initialized and the Enterprise Server will Run.