Issue How to use the Zoning feature in a Standalone Automation Server (AS-P) Product Line  EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The zoning licenses for individual automation servers have not yet been commercialized and is not an option to purchase for a standalone Automation Server. Resolution At this point, the license is required when using the Zoning feature at the Enterprise Server level only. The zoning feature is available without the need to purchase any license in a standalone Automation Server and can be used in this environment.

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.   

Issue When external internet access is not possible an alternative NTP Server is required to allow ES and AS to by time synchronized onsite. Product Line EcoStruxure Building Operation Environment Enterprise Server / Automation Server on closed network Eg Windows 7 Cause AS will not synchronize the time with a local NTP such as Windows 7 (32 or 64 bit) without it first being configured. Even then, increasing Cyber Security features within EBO means that the use of a 3rd Party NTP is becoming a much better option. Resolution Preferred Solution The very best option for the latest versions of EBO would be to investigate. Meinberg NTP which is a third party NTP server that runs on the Win7 or Win10 OS and provides NTP by synchronizing with four or more Internet clocks and is a trusted time source in NTP.  It is not an officially supported PSS tool, but it does fix the issue of the ES/AS not trusting the time.   Windows 7  Config If you still wish to attempt the Windows 7 NTP option first the procedure to setup is as follows:    In the 'Services' window (part of Administrative Tools) Stop the 'Windows Time' service if already running. The 'Startup Type' could be set as Manual or Automatic depending on the user needs. In the Registry Editor following changes to be made under the Key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time: ** Config -> AnnounceFlags = 5. ** HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpServer -> Enabled = 1. Start the 'Windows Time' service in the 'Services' window(part of Administrative Tools). Note: NTP uses UDP Port 123 Below is a Wireshark capture using filter udp.port == 123 indicating the “Leap indicator” bits are 11, meaning “clock unsynchronized”. NOTE: The NTP client in the AS may ignore the time sent by the NTP server if the root dispersion is greater than 'X' seconds (unknown at this time). See Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for information on how to determine whether this is a problem at the site and how to resolve it. Note: Test Lab results show that once validated and synchronized, the AS asks the time from the NTP about every 17 minutes. Two enhancements have been requested for a future release: Workstation gets an alarm if the NTP is not a valid reply A tick box setting in Workstation so the ES/AS can accept an invalidated reply(time)

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 The 6 character PIN for the SmartXKiosk has been forgotten so the user cannot exit Kiosk mode Note the PIN is case sensitive Product Line EcoStruxure Building Operation Environment SmartXKiosk Advanced Display v1 Advanced Display v2 Advanced Display v3  SmartX Controller Cause The 6 characters PIN for the SmartXKiosk has been forgotten or lost and the user cannot locate it. Resolution In order to reset your SmartXKiosk PIN, follow the steps below:   In the SmartXKiosk application, click on Exit Kiosk Mode in the bottom right corner of the screen. In the Exit Kiosk Mode window, click on Forgot PIN?. An 8 characters or 15 characters Session ID will be generated.  Take note of this Session ID.    Open a ticket with Support to request a SmartXKiosk PIN reset and provide them with the Session ID. Once Support sends you back the Recovery PIN, click Continue on the Session ID window. In the next window fill in the Session ID from step 2. and the Recovery PIN that Support has provided. Click Continue. You can now reset your PIN. Enter your new 6-digit PIN number and confirm it before clicking Submit. The PIN is case sensitive. It must be exactly 6 characters, otherwise an error will occur.  Important Note: The Session ID generated and the Recovery PIN provided to you by Support will expire at midnight on the day that the Session ID was generated.  

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.  

Issue When trying to activate a license in an AS-P/B the following error message was shown and the activation failed: Online activation: 12:57:24: Executing licensing command 12:57:24: Executing embedded operation: Activate ActivationID: ACT-xxx 12:57:32: Embedded operation: Activate failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information: FNO server response: Z(BACK_OFFICE%DEBACK_OFFICE+']\dBl&%MSM230312018I|B}~%ACT-xxxxx/jlSkkj1%<K!,b7OnpUy7 zqDFG#I$QGGR0:SYWJVGIuW}+iea 0\wR/`;yX'HGX*;;nEl]d0I+nHWh(VD"+a uwpf%XF[N6~!,^?R]y?VPCw\gB{"dSy2K7ph;_=qw.|c]Vp;.nlMbLl-~Z!UY<:=TFZEL~h=\V)>ML)ld0g'PPcjrosy&]p9Y((?II#*B5/U16X;o- 12:57:32: Licensing command completed 12:57:34: Activating licenses failed   Offline activation: 12:56:02: Executing licensing command 12:56:02: Executing embedded operation: ProcessResponseFile ResponseFile: C:\Users\Mitthem\Desktop\Garage\response\xxxxxxx\8ba20b60-b19c-4a5d-8fea-693ef9282c8c.bin 12:56:03: Embedded operation: ProcessResponseFile failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information:  12:56:03: Licensing command completed 12:56:05: Activating licenses failed Product Line  EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Device Administrator (DA)  Cause The reason for the issue was that the number of available licenses for activation was 0, but the error message in DA was not indicating that. The Device Administrator(DA) showed that two licenses were available, but it was out of sync.   Resolution When looking at the Entitlement in DA, it had a yellow dot on it, indicating that it was added offline. In DA version 5.0.2 and later, DA contacts the License server directly when adding an Entitlement in prior versions this was done through the AS-P. DA version 5.0.2 and later it is enough that the computer where DA is installed has an internet connection when adding an Entitlement online. After upgrading DA to version 5.0.2 and refreshing the Entitlement, the Device Administrator showed the correct number of available licenses.    If upgrading the site to this version is not possible, the Entitlement ID / Activation ID availability and device list can be verified by using the User Portal FlexNet Login (flexnetoperations.com) It is also possible to run Device Administrator version 5.0.2 (or above) with the concurrent site version used as long as the Servers are at 4.0.4 and above to check, verify and activate licenses.   Further information on Automation Server Licensing Overview is available through the online WebHelp.  

Issue In a multi-version system, will the database schema in the PostgreSQL database be compatible with EBO servers with lower versions? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Timescale Database Cause In a multi-version system the database schema in the PostgreSQL database needs be compatible with all servers in the system. Resolution The DB schema is backward compatible. The same schema can be used for the complete system and it can be upgraded to the latest version compatible with the top level server. Compression is done on the PostrgreSQL/TimescaleDB side and since it’s not configured in EBO, the compression will work for EBO servers with lower versions. Compression needs at least schema version 7 and TimescaleDB version 2.0 or higher.

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 Error messages in Workstation saying "No valid license to add AS found", when trying to add more AS-P to an ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium (AS-P) Cause License Administrator is unable to locate the License Server by using @localhost or IP address(@xxx.xxx.xxx.xxx). Resolution 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 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