Building Automation Knowledge Base

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 ES takes up to 30 minutes to perform a shutdown. Trace log contains multiple entries indicating "Subscription service forcefully shutting down; [sub-server name]"  "Subscription service forcefully shut down; [sub-server name]"   A secondary issue - When performing Windows Updates automatically, Windows attempts to shut down all running services within one minute which can end the Enterprise Server service prematurely Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server 3.1.x and below Large Multi-server installation  Cause During a shutdown procedure of the Enterprise Server a call to every sub server is made to remove subscriptions. However, the thread pool that executes these commands may already be stopped and the server then waits the 15 seconds timeout period prior to moving to the next item.  On a large 100+ multi-server installation, this 15 second delay can accumulate to a lengthy shutdown period.     The trace log will contain the messages shown  in the issue and the 15-second delay between each server  Enterprise Server Trace log messages seen during shutdown showing the 15-second timeout delay. Resolution Upgrading to 3.2.2 (and above) will rectify the timeout issue provided that the subscription thread pool has already stopped.  These versions now ignore the 15-second timeout for each sub-server if the thread pool has already stopped.   It is possible to extend the Windows service shutdown time by adding or adjusting a registry entry called WaitToKillServiceTimeout .   To change the timeout: Start the registry editor (“Regedit”) In the tree on the left, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control In the right panel, find the WaitToKillServiceTimeout value. If you don’t see it, create it by: Selecting Control on the left Choosing Edit > New > String Value (not DWORD) from the menu Naming the new value WaitToKillServiceTimeout. Double-click the WaitToKillServiceTimeout entry to bring up the Edit String window. Enter a numeric value (e.g. 60000) in the Value data field in milliseconds and click OK to save your change. Reboot your computer. The new timeout setting will not take effect until Windows restarts. Note that this modification will not make Windows wait indefinitely for your service to finish. If your service takes longer than the entered time (in this example 60 seconds), it will still be terminated. Be sure to choose a timeout value that is long enough to cover your scenario, but not too long to make shutdown time intolerable.

Issue Upgrading from EBO 2.0.x to 3.0.x causes I/NET to become incompatible. After upgrading to 3.x the I/NET controllers do not come online. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure Building Operation (version 3.0.1 and later) I/NET Seven Software (version 2.44 and above) Cause I/NET Seven Software is built using a 32-bit interface. Starting with EBO 3.0.1, EcoStruxure requires the use of a 64-bit interface. Resolution For INET seven to operate with EcoStruxure Building Operation 3.0.1 it is necessary to obtain a 64-bit DLL from the Exchange and install it in the INET installation prior to the upgrade. Search for INET IPortAPI64 - Software on Exchange.  Download the IPortAPI64_EBO.dll. Unzip the DLL and copy the DLL to the same folder as the 32bit INET install, by default this will be C:\Program Files (x86)\INET Seven folder. Note: if INET was installed in a different folder this can be found by examining the Windows registry key ”INETSevenPath” at HKLM\SOFTWARE\WOW6432Node\CSI - Control Systems International\I/Net 2000/Configurations. Install EcoStruxure Building Operation 3.0.1 When the ES restarts the InetPlugIn will connect to InetIoSrv via the 64-bit IPortAPI64_EBO.dll.

Issue When setting up the TH90x series thermostats there are communication limitations.  Unable to pull multiple registers.  Some registers are only in Celsius, regardless of the display setting. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic TH903 Series Thermostat SpaceLogic TH907 Series Thermostat Cause The TH903/TH907 does not support multiple/block register reads in Modbus.    The following parameters will show their value in Celsius only via Modbus communication regardless of whether the display is showing values in Celsius or Fahrenheit:   All SpaceLogic Series TH9xx thermostats Register 30 - Function Code 3/6 - Room Temperature (from the remote Modbus Controller) Register 1 - Function Code 4 - Actual Room Temperature 7 Day Programming Versions of TH900: Register 26 - Function Code 3/6 - 7 Day program schedule, heat set-point Register 27 - Function Code 3/6 - 7 Day program schedule, cool set-point Register 30 is used by the customer to override the current temperature. This register expects a value to be written to it every 15 seconds. If no values are written to it every 15 seconds, then it will populate with our internal temperature sensor value. Resolution Registers must be read one at a time rather than in groups. When using Modbus write the set-point values in Celsius. 

Issue Getting error message when selecting Character set file for the TAC  Xenta Operator Panel (OP).     Product Line EcoStruxure Building Operation, TAC Vista, Xenta OP Environment TAC Xenta OP EcoStruxure Building Operation Microsoft Windows 10 Cause Microsoft Windows 10 does no longer allows the software to change files in all directories. Resolution Manually open up the directory C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\CharSet.lib Select the Charset you want to use, depending on the language, and copy the file. Remove the extension, so that the file is named Charset, without any extension. Manually open up the directory C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation\Function Block Editor Paste the copied file here.

Issue Automation Server Classic support for hosting MPX or RPC Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Classic, AS-P, AS-B Building Operation SmartX MPX, MPC, MPV field controller Building Operation SmartX RPC field controller Cause The original Automation Server (Classic) can be set up to fully host (host server) and configure both MPX and RPC devices, but the Architectural Guidelines do not specify how many devices can be fully hosted. Resolution Full hosting of MPX, RPC is only supported and tested on AS-P, AS-B and Enterprise Server. This is confirmed in the MPX and RPC Specification Sheet. "MP-C/MP-V/RPC can either be used as a standalone BACnet/IP field controller or as part of an EcoStruxure BMS with a SmartX AS-P or AS-B server or an Enterprise Server as the parent server." MPX, RPC can be simply be BACnet hosted on an Automation Server Classic, but the use as parent or host server is not supported or tested.

Issue TLS Error seen when attempting to export WebReports data from the displayed report as follows: Unable to download ReportsView.aspx (IP address) Unable to open Internet site, the requested site is not accessible or can not be found  Product Line EcoStruxure Building Operation Environment Building Operation WebReports 3.0.x and above  Internet Explorer (used within WorkStation) and Google Chrome Web Browsers Cause To download files, Internet Explorer must create a cache or temporary file. In Internet Explorer 9 or a later version, if the file is delivered over HTTPS, and any response headers are set to prevent caching, and if the Do not save encrypted pages to disk option is set, a cache file is not created. Therefore, the download fails Resolution See Microsoft documentation on how to correct this.  Typically Method 1 will correct the issue. Cannot download files from secure websites - Browsers | Microsoft Docs

Issue PCT workstation displays message “Server version not compatible with client", when restoring a server configuration with new IDs. Product Line EcoStruxure Building Operation Environment Buildings Operation Project Configuration Tool Cause When backing up and restoring an AS-P/AS-B with a new ID in PCT at EBO 3.2.2.61, when logging back on with PCT using the installed EBO workstation,  the message “Server version not compatible with client" is displayed Resolution PCT is the offline programming tool but, it launches the workstation installed on the computer. If the workstation version on the computer is EBO 3.2.2.61, Hotfix 3.2.2.4002 (CP3) is required to be installed on the computer running PCT, taking the computer’s installed workstation version to 3.2.2.4002.

Issue Clarity is needed on the new ES License Inheritance feature available in EBO 3.x Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server  Building Operation Enterprise Central Building Operation SmartX Server (AS-P, AS-B) Cause The evolving Licensing Model of EBO has offered the option of Embedded Licenses in SmartX Servers, such as SNMP Licenses, since EBO 2.x.  The concept of Inheriting Licenses from an ES into a SmartX Server is a new option which can be used from EBO 3.1 onward, although the original Embedded License option still remains, but what does this actually mean? Resolution In EBO 3.1, SNMP Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   In EBO 3.2 SNMP and TimescaleDB. Licenses may be inherited from an ES into any number of child SmartX Servers (up to limits defined in relevant Architectural Guideline documentation).   'Inheritance' means that an ES License will be shared down to its child SmartX Servers while also being retained for use by the ES.   Note: SmartX Servers must be running the minimum supported 3.x version for Inheritance to function There is no such thing as a 'Site License' that can accommodate multiple ES There is no Licenses Inheritance from an EC

Issue The Optimum Stop feature of the OPT function block in Menta / Building Operation Function Block Editor does not auto-adjust, even when the auto-adjust parameter is enabled. Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 281 Xenta 301 Xenta 401 Menta FBD Cause This behavior is by design, although it is not made clear in the Menta documentation.  The auto-adjust feature only works with Optimum Start, not Optimum Stop.  The optimum stop time is calculated from a fixed Outside Air Temperature vs time curve.  As some compensation, both end points of the curve are manually adjustable for both time and temperature.  For the optimum start, only the time parameters of the curve end points are manually adjustable. Resolution The optimum stop curve must be manually adjusted over succeeding days until an acceptable stop time is achieved.

Issue Samsung’s Knox security protection on your phone or tablet data is out of date. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Advanced Display v2 Cause   One of the security features contained within the Android operating system is Samsung Knox which the Advanced Display uses. Samsung Knox needs to get security updates periodically and needs to be online to the Internet to receive these updates. As a security feature if Samsung Knox is out of date it can stop the operation of some of the apps. For further information, see the Samsung’s Knox website. If Samsung Knox security needs an update when the AD-Link is launched then one or both the following messages may appear on your display.   Resolution Firstly, if the Advanced Display v2 is not running SmartXKiosk v8.2 and SmartX AD-Link v8.0.apk, then the latest versions are not installed and a request can be made by raising a case with your local product support team for the latest releases. To resolve the Samsung Knox issue, carry out the following procedure: Connect the Advanced Display to a WiFi network that has Internet access. Re-start the device. Confirm the phone or tablet still has an internet connection. Launch AD-Link. (several license windows will appear on your display). The SmartX AD-Link app should now run.

Issue EBO 3.2.x SNMP Engine ID seen in EBO 3.2.x is not the one used by the EBO 3.2.x system. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v3.2) Building Operation Automation Server (AS-P and AS-B) (from v3.2) SNMP Cause EBO 3.2.1 introduced a new SE3Linux operating system for the AS-P and AS-B servers. The engine ID: seen in Device Administrator or Workstation is the engine ID: contained in Linux, this is not the one used by EBO 3.2.x Resolution The SE3Linux engine ID:  “0x80001f8803005006042bd7” viewed using the Device administrator: The SE3Linux engine ID:  “0x80001f8803005006042bd7” viewed using the Workstation The engine ID used by EBO for this example would be: 0x80002a1d03005006042bd7 The difference is always 2a1d compared to 1f88 and the rest of the bytes are the same. For further information see the attached document SNMP SBO 3.2.x Engine ID Explained.

Issue The 0–10 measured output voltage from the RP-C’s Ub terminals may not provide the expected voltage. Product Line EcoStruxure Building Operation Environment SmartX Controller RP-C Cause On the RP-C controller's the Ub return terminals although internally connected to each other are isolated from ground (-). Resolution Add a ground reference connection between ground and one of the return terminals of the controller. Example if the controller is stand-a-lone using terminal 3, which is an isolated terminal and can be used for the connection.  

Issue How to create a proper XLSX/Excel template under Alarm Triggered Notification of EcoStruxure Building Workstation, in order to receive the Multi trend logs report in the XLSX/Excel format. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation Cause Additional information is needed to create a template for presenting multi-trend log information in Excel XLSX format.    Resolution Below screenshot shows where users can select the Report format and XLSX template.   The multi trend log containing four Interval Trend Logs 1 to 4 with their time stamp is shown as below as an example   In order to get the XLSX multi trend log report in XLSX/Excel format upon receiving a trigger, the following XLSX template needs to be used containing two rows: The first header row contains the column headers from the trend log. The second row include the <Multi Log List> command   Here is final report in Excel/XLSX format:  

Issue Notification Report Template creates blank data if External Log Storage is enabled Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Notification Report Template External Log Storage PostgreSLQ TimeScale Cause The default timeout for a Notification Report Template is 5s. If External Log Storage is enabled and logs are being added to the report, the timeout may need to be increased. Resolution The screenshot below shows a Notification Report Template where the default timeout of 5s caused an empty Report to be created (both an email and csv file were seen to be empty). Increasing the timeout to 20s resolves the issue.    

Issue Want to add the RP-C devices to the PCT project by using Device Discovery Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Building Operation Workstation Cause All communication from the SmartX Servers is blocked when using the PCT. Resolution The Device Discovery command does not work in the PCT.  This can be done after the project has been deployed.

Issue Could we have 128 characters passwords in Struxureware?  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Workstation Cause In earlier versions of SBO (version 1.7), the password was limited to 100 characters.   Resolution In EBO version 2.0 and 3.0, 128 character passwords are allowed. Passwords have been tested with 500 characters.    

Issue Existing documentation for showing damper feedback and provide damper calibration is applicable only for Continuum and the same steps will not work in SmartStruxure. Product Line EcoStruxure Building Operation Environment SmartStruxure i2866-V b3866-V Cause Damper feedback and calibration for these controllers do not work the same in SmartStruxure as they do in Continuum. Resolution The correct damper feedback can be shown, but will require a script program to correctly calculate this and then write this back to an Analog_Value. Unfortunately, it is not possible to bind directly to the "LCD State" attribute to be able to toggle this (and the damper calibration feature) from within a Script Program. For now, toggle this attribute of the Damper Output manually from "enabled" to "disabled" and back. This will set the damper to drive closed fully, then open fully, then to about 75%. After this is calibrated properly the "Override Value" attribute in the Damper Output will update with likely a very large and strange-looking number. To convert this to something usable, multiply this value by 100 to give a percentage open value. See Zip file with XML code and screenshots of the configuration with notes. Either import supplied XML file into b3866-v or create below objects: Create DamperOutput as a multistate output. Assign to channel 1. Create DamperPos AnalogValue. Create Script Program Damper_Position and input code as shown in image. This will be a looping program. Bind DamperOverrideValue to the OverrideValue attribute of the Damper Output and DamperPosition to the DamperPos AnalogValue we created earlier. See image for details. After the points and program is created and the damper calibrated, you should see the DamperPos AnalogValue update with a live representation of the current Damper Position.

Issue AS-P that has infinet devices connected to it, crashes during the Spring time-change of daylight savings. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Andover Continuum, infinet devices Cause Infinet schedules are sent down to the controller on a weekly basis. Having changed from default to be on Sunday between the time of 2:00 AM and 2:59 AM causes issues during daylight savings time "spring forward" due to that hour time span not existing. This causes the AS-P to crash. Resolution If you have schedules being download differently from the default time interval, ensure that they are not being done on Sundays, between the time of 2:00 AM and 2:59 AM. If they are, update them forward or back an hour to avoid further issues.

  Issue When upgrading a MP-V from v1.xx to a later release the Box Flow reading is zero when there is a velocity pressure. Product Line EcoStruxure Building Operation Environment SmarX IP controller MP-V   Cause When a MP-V-7A or MP-V-9A is upgraded from v1.xx to v3.xx firmware. The MP-V does not control and the Box Flow reading is zero. The damper will rotate to 100% with a Velocity Pressure reading.   The Balanced k-factor and the Balance flow correction are found to be at zero:       Resolution During the upgrade process the flow data is not retained.   Before the upgrade at v1.xx, backup the flow balance data under the Flow Balance Data object,     Continue and complete the upgrade process, re-hosting the controller and downloading the objects. Finally, restore the flow data.

Issue All Custom Types in an AS-P suddenly disappeared and it is not possible to create any new Custom Types. When trying to create a Custom Type it results in an invalid Custom Type object:   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause For an unknown reason, the Configuration database has become corrupt. Resolution Workaround 1: Do an upgrade of the AS-P to the same version which should fix this issue.   Workaround 2: Restore a backup taken before this issue appeared.