Building Automation Knowledge Base

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.  

Issue The site has a program that writes to a Value where the value is bound to Priority 16. The graphic maps to that same point at Priority 16. Previously they were able to click on the point on the graphic and edit the value, and the program could still count it down or clear it out. But they cannot do that anymore. Product Line EcoStruxure Building Operation Environment • Building Operation Workstation • Building Operation Automation Server Cause Prior EBO versions allowed to modify the value property of the BACnet object bound to priority 16 and vice versa, however as of 3.1 the system now makes each property read-only. Resolution There are a couple of options : It is recommended to use Numeric Public in the script Program. It will allow the modification without having to Force the value. There is also a feature in EBO 4.0 that will allow the change of the value without having to force it

  Issue EBO 4.0.3.176 When trying to import anything (Custom type, Script Program, etc.), Workstation will crash immediately with an error stating "The path is not a legal form.". You cannot navigate to the location that the file will be imported from. It will generate a Workstation error after clicking import. The issue only occurs on Windows 11 machines.     Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The wrong file format might have been used Resolution When you select "import", WorkStation looks in the bin file for the last path used. If it finds a path entry it tries to use that path. If it can't find that path, it defaults to the users' Documents folder. In this case, there was no entry in the bin file, which means WorkStation defaulted to MyDocuments. For some reason, the MyDocuments path on that PC could not be parsed, and WorkStation crashed.   The resolution is to manually add an entry in the bin file (you can get the file from support), pointing to the user's desktop. That means, that when the user selects "import", it first tries to open the user's desktop, and when it succeeds, it never falls back to the MyDocuments folder.

Issue How many concurrent users can connect to the system Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause In the datasheet it is unclear how many concurrent users can connect to an AS without affecting performance Resolution The intent in the guidelines is to provide the concurrent user connections given that the clients are not all accessing data through the same Automation Server to the same Field Controller.  Therefore, if the load is distributed –  ES Clients viewing data from the ES (or a scattered variety of Automation Servers and below) AS Clients viewing data from that AS  Then it should be safe to add the client totals for all AS and ES clients together. The local AS connections are intended to help with scaled use of clients at a site-wide or multi-site system. The typical use case is for operators within a building, floor or tenant to connect locally to the AS, while central operators connect to the ES without impacting each other.  If all ES Clients and all clients on a single AS are all accessing data from that AS and below then the performance could drop below acceptable levels.

Issue Binding to a Graphic, what is the correct method? Product Line EcoStruxure Building Operation Environment Bindings Graphics Cause In the chapter "Binding Templates - Binding Values Using a Binding Template" in the "EcoStruxure Building Operation - Technical Reference Guide" it states "When creating bindings, follow the recommended general guidelines: create binding between Inputs and Outputs only, and do not create binding to Public Signals". Does that mean that you should not bind constants used in e.g. curve block or time delays or outputs from expression blocks to a graphic? Does that mean that you should not bind constants used in e.g. curve block or time delays or outputs from expression blocks to a graphic? Resolution Bindings from public signals to graphics is appropriate. When dealing with directional bindings (i.e. in from a schedule, out to an alarm, in from or out to another program, etc.), it's best to bind to input blocks or output blocks.  Graphics bindings are a different animal, though.  Among other things, they are bi-directional and only affect the system when the graphic is displayed.  They also exist to give the user access and control to values throughout the system (rather than to control routine data flow). Our primary reason for communicating this best practice is to help with the binding process.  Programs will operate with un-bound points, but we're encouraging users to simplify the binding process by relying on just inputs and outputs to interconnect a program with other logic and alarms.  In this way, you can visually scan the list of inputs and outputs to see which points still need to be bound. Since most programs typically have a much longer list of public signals, it's easier to overlook a missed public signal binding. Missed graphics bindings should be easier to catch but bindings to another program or alarm may be difficult to identify.

Issue Memory and System Memory in the AS Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause What is the definition of the two different memory types shown in the AS? It is not clearly defined in the documentation. In various places, one can see Memory and System Memory, or even add a column to show.  Resolution For the AS, System Memory is the RAM used by the AS Linux OS. The rest of the memory is what is being used for the processes, such as programs, trends, etc. Memory is the amount of memory consumed by the AS (nsp_servers application), system memory is that used by the Linux OS, however there is much debate about how this is calculated and allocated, so too much should not be read into this, it is there primarily for developers.

Issue Building Operation Server backup set is incompatible for restore. "Importing Backup Set" "Backup set is of a different server type" Product Line EcoStruxure Building Operation Environment Automation server (AS) Enterprise server (ES)  Cause The backup set is for a different server type (version). Determine the server type from the .xbk file to determine which server version will allow a restore. Resolution The quickest method is to run the following tool SBO xbk Analyzer - Communities (se.com) and open the backup (xbk).  It will identify the  File name Controller Type Version / Serial Number Time and type of backup.  i.e., Contents. Config only, Events and Trends, etc. And much more.  See the link above or the Help topic on the tool for further information   Alternative methods are provided below:    The backup set contains information in the compressed .xbk file that can be retrieved this way ... Make a copy of the backup set as a precaution for safety reasons On the copy, for AS change the file extension from .xbk to .zip. For ES change to .tar Use a tool such as 7zip to decompress the file Look for a file by the name x.x.x.xxxx.serverrevision (i.e. 1.3.0.4602.serverrevision) This is the revision that the backup set was created at.    The Backup set can only be restored into a server running this revision.   Look for a file by the name xxxxxxxx-xxxxxx.backuptime This is the date/time when the backup set was created.   Look for a file by the name Automation/Enterprise.servertype This indicates whether the backup set is for AS or ES   Look for a file by the name xxxxxxxxxxxxx.servername This is the name of the server when the backup set was created     Version 1.5 and above There is a file by the name TDxxxxxxxxx.serverserialnr This is the Serial Number of the server.  

Issue The port range used by the Project Configuration Tool is unclear Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The ports used by PCT are located in different documents Resolution • TCP on port 4444 (fixed) • HTTP on port 80 (default) • HTTPS on port 443 (default) • Server port 9091 (default) • Server port 9090 (default) • Engineering port 32768-61000