Building Automation Knowledge Base

Issue External resistors are required for Biasing and Terminating RS-485 trunks connected to an Automation Server (AS) Product Line EcoStruxure Building Operation Environment SmartStruxure Automation Server (AS) with  RS-485 trunk(s) under it. Field controllers on the RS-485 trunk; for example, the Network 8000 ASD controllers (MZ2, PEM1, etc)  Cause Bias and terminating resistors are not built into the AS hardware. Resolution External resistors are required for Biasing and Terminating RS-485 trunks connected to an  Automation Server (AS). See the Technical Reference Guide, revision 1.3, pages 2723, 2724, and 2771. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange. Biasing and Termination details are now found in the "RS-485 Communications" chapter of SpaceLogic - Hardware Reference Guide

Issue The extended trend log contains approximately 50% of the configured storage capacity. For example, only 250 entries are in the Trend log view even though the ETL is configured for 500 entries.   After the ETL runs long enough to fill up the 500 entry capacity, ONLY 250 entries are shown in a Trend log list view. (see below)   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause An extended trend log (ETL) includes an equal number of internal entries hidden from view; these entries are overhead incurred in the operation of the ETL. For example, each time a transfer takes place, an internal entry is added. Depending on the specifics of the configuration (i.e., Maximum Transfer Interval), the percentage of internal entries for a given ETL relative to its full size varies. From EBO 3.2.3, the internal entries of an ETL are hidden, and no information is provided to give any visibility into how much storage is being used by internal entries. Resolution The solution is to increase the size of the ETL to ensure there is enough storage capacity for data and overhead. Typically, the size must be doubled (in this case, 1000) in the particular ETL to make sure 500 entries of data can be stored.  Although these transfer events are hidden, it is possible to identify these events by adding the Sequence number column in the trend log list.  It is also possible to decrease the overhead amount stored in the ETL by increasing the "Maximum transfer interval" in the ETL properties, as shown in the screenshots.  Here it can be seen that by increasing the Maximum transfer interval to 1 hour for an interval log of 5 minutes that ONLY 1 'overhead' record (sequence # 565) is added per 10 entries.   Using this or a similar setting will allow to reduce the storage requirement of the ETL.

Issue When a Zigbee device is imported to EBO there is a lot of different configuration settings for the device, like the below settings for the Wiser Radiator Thermostat: How do I know what the different settings do? Do we have any documentation explaining that?  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RPC) Cause The different objects under the Zigbee device like "Thermostat" and "Power Configuration" is coming from something called clusters and a cluster is defined in the "Zigbee Cluster Library Specification". For example the "Remote sensing" attribute for the "Thermostat"   Look like this in the "Zigbee Cluster Library Specification" When joining a Zigbee device it will specify what cluster it support and that information is what will be used when building the import file which is imported to EBO. Resolution EBO doesn't know anything about the functionality of the Zigbee device. Instead it gets information from the device what clusters it supports, and will make sure the correct objects and attributes for the different clusters are created in EBO so it is possible to set all configuration parameters in the device. So to know what the different settings actually do in the device please contact the manufacturer of the device.

Issue RP-C-16B-230V Transformer 24Vac output Product Line EcoStruxure Building Operation Environment SmartLogic SmartX IP Controller RPC-16B-230V Cause More details about the internal transformer power supply required. Resolution The voltage regulation of the transformer is around 15%, thus if the "230Vac supply" is towards it's upper tolerance (230Vac +10%, 253Vac) the no load voltage of the "24Vac output" can be about 30Vac. If the RPC power supply is 230Vac, then the no load voltage of the 24Vac output will be around 28Vac With the 224Vac output" half loaded, the voltage is around 26.5Vac With the "24Vac output" fully loaded the voltage is around 24Vac See SpaceLogic - Hardware Reference Guide

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 Need to backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause One way of sharing a project is to move it and another way is to Export the project. Resolution Move the project Stop all servers in each project and stop all projects. Close PCT application. Copy the “projects” folder from the PCT storage location and paste it to another storage location (suggested by WebHelp topic Move a Project) OR backup all servers through Workstation. Default PCT Project Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\storagemodule\projects PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects Default PCT Template Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\templates PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\templates   Export the project In Project Configuration Tool, in the Project view, select the project you want to export. On the Header toolbar, click the Export project button or right-click on the project and select "Export". On the Export selected project(s) dialog box, in the Folder box, browse to the folder on your hard drive where you want to save the exported project. Click OK. TIP: You can select multiple projects and export all of them at once. Note: In order to be more future proof, there is a new export/import format of PCT projects starting in PCT v1.3.2 with exports having an extension of '.pct_export'.  Projects exported at an earlier version have an extension of '.ppb' and they must be converted to '.pct_export' files before import into PCT v1.3.2.    Please refer to point 2.1 in the release notes.   Also prior to PCT v1.3.2 the project had to be stopped before export was possible.  In PCT v1.3.2 the project has to be running before it can be exported.    

Issue System was running fine with EBO version 3.2.3 and Active Directory (AD) integration. But after upgrading to EBO version 2022 no AD user could login to the ES. The Workstation Error when trying to login is: User_Not_Associated_With_A_Group And the error message seen in the ES trace log is: WinES\server\nsp_servers\csc\accountaccess\source\AccountAccess.cpp(486) Workstation Error: User_Not_Associated_With_A_Group (0xc002a) in module Account_Access(28).  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The Windows AD integration performance in EBO was improved in version 2022 by storing and comparing the SID for the AD-groups. During the upgrade from version 3.2.3 to EBO 2022 all EBO groups should have been updated with an AD-connected group SID. This was not done as the AD server was offline when doing the upgrade of the ES. Resolution If turning on the below property in the properties the old way used in EBO version 3.2.3 of matching groups during logon will be used: In the "ES.properties" file usually placed in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\etc\config add and save: NspServer.Windows.Group.MatchByName = true   To utilize the AD performance improvement in EBO 2022 re-connect the AD group to their respective EBO group. This is done by changing the "Windows group name" property in the EBO group to anything else or an empty string and then change it back to its proper value, i.e. the AD group name. Doing so should correctly populate the hidden "External SID" property for the EBO groups that is missing as the upgrade was done with no connection to the AD server.  

Issue As per RFC 4510 The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. Do EBO servers support LDAP protocol? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Need to know if EBO supports LDAP protocol. Resolution EBO doesn't support LDAP protocol. EcoStruxure Windows based BMS servers (Enterprise Server/ Enterprise Central) support integerationto Windows Active directory. The Active Directory integration is not using LDAP directly, but the NetLogon service on the Windows OS that ES/EC is running on.  This connection enables inherited user account groups from the Windows Active Directory to EcoStruxure Building Operation software, and allows users to log on to WorkStation with their Windows user accounts. Refer to: Windows Active Directory User Groups and Integrating Windows Active Directory user accounts with EcoStruxure - Communities For EBO 2022 or higher, Authentication using SAML 2.0 is also supported (Edge Server, AS-P, AS-B, ES and EC) . This enables configuring WebStation to use single sign on (SSO) using Federated Authentication, refer to: Federated Authentication. SAML Authentication feature requires license.

Issue SLP Sensor Modbus RTU issue when used with RPC or AS Communication errors are seen during normal Values are updated very slowly, can take up to two minutes to populate/update the 15 objects within the SLP.   Product Line EcoStruxure Building Operation Environment Modbus RTU RPC Modbus Automation Server + Premium  SLP SpaceLogic Sensors LSA_APP_REV2.03.19 and REV2.05.21 Cause Once the Modbus communication is set up between RPC (or AS) and the SLP,  although the values updates fairly regularly, multiple communication errors are also seen The SLP read speed needs to regulated to prevent overwhelming it The SLP Modbus transmission voltage is less than the AS Resolution Use with RP-C SLP struggles to respond to every request from the RP-C, changing the baud rate to 9600/19200 and increasing the "Silence characters" in the interface to 255 (maximum possible) should stabilize the communications.  The character spacing cannot be adjusted enough in the RP-C to allow communication at 38400 or 76800 Use with AS/AS-P  Adjust the “Poll point delay” in the Modbus Interface to 80ms The Silence characters and Transmit guard bits may also need to be increased Baud rate up to 38400 has been tested.  

Issue Can Enterprise Servers inherit licenses from a parent Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Need to know if Enterprise Central Licenses can be inherited by an Enterprise Server, and then, in turn by Automation Servers. Resolution An Enterprise Server cannot inherit its licenses from a parent Enterprise Central. Licenses can only be inherited from an Enterprise Server by the attached automation servers. Refer to WebHelp article Inherited Licenses and Knowledge Base article SmartX Server License Inheritance in EBO 3.x.

Issue When WebReports is installed, two users called "appuser" are created. One is a local Windows user, and one is a SQL user. Product Line EcoStruxure Building Operation Environment WebReports User accounts Cause These users are or have been needed by WebReports Resolution EBO version 2.0 and above: the Windows user account "appuser" is no longer required to operate WebReports.  It is only a requirement during installation. SBO/EBO version 1.8 and above:  In SQL, the "appuser" user account has been removed as it's not essential for the Web Reports to operate correctly. In these versions, if an upgrade from an earlier version is performed and this user account is still present, it can be safely deleted /disabled.     In all other versions: The local Windows user account ([PC_NAME]\appuser) is used for importing report packs (RDL files) and synchronizing between WebReports and Microsoft Reporting Services.   For more information about this account, refer to SmartStruxure WebReports Installation Errors (1001 while importing report pack). To change the password for this Windows user, refer to Changing Report Server "appuser" password.    

Issue Moving from Webreports going to Postgres/TimescaleDB instead, leaves us without a reporting engine. SSRS can supposedly utilise a PostgreSQL database, but SSRS is a licensed part of MSSQL. Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Cause From EcoStruxure Building Operation version 4.0 (2022) the Building Operation Report Server is no longer supported. Instead, we support PostgreSQL/TimescaleDB, using Dashboards and Excel from within EBO, to make reports, using Notification reports to start Excel and reports. Resolution EBO 3.2 introduced Enhanced Reporting, based on the current feature Notifications in combination with Notification Report Template, which also supports report data such as Alarms, Groups, Multi Log list, Relative events and Users. The Notification result can also be presented in XLSX format and converted to PDF with signing capabilities. If External Log Storage is configured and connected (PostgreSQL/TimescaleDB), then historical report data can be fetched from there.   EBO 2023 introduced External Log Storage support for Microsoft SQL Server in addition to PostgreSQL/TimescaleDB   Information  and examples of Enhanced Reporting and Dashboards can be found in EBO Webhelp, My LearningLink and the Automation Experts Community.   NOTIFICATION REPORTS : EBO Webhelp: Notification Reports  Community: Reporting in EcoStruxure Building Operation 3.2 Community: Reports showcase - share your reports! Community: Get more data out of the system with Notifications! EcoXpert Extranet Video: Community Video : Fusion Fridays - Session 20 Community: Change Control and Enhanced Reporting Lab Guides Community: Example Report Templates  Community: Forced Values Report Example My LearningLink: EcoStruxure Building: Enhanced Reporting and Dashboards 3.2 My Learning Link: EBO 2022: Enhanced Reporting and Dashboards   DASHBOARDS : EBO Webhelp: How Dashboards Work EcoXpert Extranet Video: Dashboards EcoStruxure Building Operation 3.0 - Informational Video Community: What Custom Types have to do with Dashboards Community: Public vs Personal Dashboards Community: Graphics in Dashboards [Advanced] Community: Dashboards: Share your screenshots! EcoXpert Extranet: PA-00701 EcoStruxure™ Building Operation 3.0 Captures the Spotlight

Issue When binding Output points in the script editor to the desired outputs, the bindings are not working. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation All Versions Automation Server Central I/O Modules Cause When bindings to the output points the incorrect attribute is being used. Resolution Open binding editor for the desired program. In the right hand pane, choose the desired output to be bound. Expand the point and select Requested Value. Drag the Requested Value to the desired output in the program. Save settings.

Issue Sometimes the availability count for license features are displayed as double the actual available count for Entitlements. The problem has no functional effect on the system other than that the visual indication of the feature count is wrong. Issue seen in Entitlement View - Features inside a License Product are doubled. Issue seen in Server View. -The issue can be seen temporarily during activation on the server line. -The number of features inside the License Products available for activation under the server are doubled permanently. Server line view after activation. - After the license product has been activated the features on the server are shown correctly. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Secure Boot Building Operation Automation Server Bundled (AS-B) Scalable Cause AS-P Classic and AS-B Classic licenses are NOT affected. None of the Windows licenses are affected.   EBO releases affected: All EBO versions up to and including 4.0.3. The EBO systems that are already running licenses are Not affected. Customers that for any reason reinstall an Entitlement in DA will be affected by the issue. EBO 5.0.1 Resolution This issue is planed to be resolved in the following EBO versions: EBO 4.0.4 EBO 5.0.2

Issue Is it possible to use a TAC Xenta 1.8 kOhm thermistor on an RTD-16 Central I/O module? Product Line EcoStruxure Building Operation. Environment Building Operation I/O Module 16 Ch RTD Cause Wants to use existing modules instead of adding new modules. Resolution The RTD-16 module is designed to interface with linear resistive inputs such as PT100, PT1000. Thermistors generally have logarithmic scales, therefore it will be hard to program a correct curve function to get an acceptable sensor accuracy. Using a universal input that is made for thermistor readings will give a more accurate reading without additional programming.

Issue Is it possible to use both Modbus/IP and BACnet/IP on the same AS-P Ethernet Port 2? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium Cause There is a need to have both Modbus TCP as well as BACnet/IP devices on the same AS-P secondary Ethernet port. Resolution This is not a common configuration so it has not been tested extensively. With regards to the architectural guidelines, consider the Modbus/IP as BACnet/IP devices. For example, where the maximum number of SpaceLogic BACnet/IP devices per private IP field-bus is 200, adjust this limit to 190 if you have 10 Modbus/IP devices on the secondary Ethernet port.

Issue When connecting MP-C controllers in a daisy chain, do they act as a repeater and boost the signal thus allowing total network distances of greater than 90 meters. Product Line EcoStruxure Building Operation. Environment Building Operation Multi-purpose Controller. Cause Each MP-C acts as a switch and decodes and generates a new fresh packet. Resolution Maximum 100 meters between each device when using daisy chain when connecting MP-C.

Issue After configuring SSL certificates manually, having an incompatible Host Certificate and Key file can cause the import to EBO to fail. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Cause Host Certificate provides the public key for which the private key is paired. An unmatched Host Certificate and private key will cause the certificate import to fail. Resolution While managing certificates manually, it is recommended to check that the Host Certificate and Key files are a matching pair.   Using the provided Host Certificate (.pem) file and private key (.key or .prv) file Download OpenSSL v1.1.1 Light choosing the EXE file type and correct version (Win64 or Win32), as the latest version letter will be posted to Win32/Win64 OpenSSL Installer for Windows - Shining Light Productions (slproweb.com) or OpenSSL installed with EBO If using Shining Light installer, it is recommended to open command prompt from where certificates are stored on the desktop and substitute openssl with "C:\Program Files\OpenSSL-Win64\bin\openssl.exe". Working with certificate files on the Windows desktop ensures the user will have the correct permission to run the commands, unlike putting certificate files in the Program Files directory where openssl.exe resides. Open PowerShell or Command Prompt Obtain the host certificate md5 hash with this command: openssl x509 -noout -modulus -in filename.pem | openssl md5 Obtain the private key md5 hash using the command below. Use the correct command based on the key file file type openssl rsa -noout -modulus -in filename.prv | openssl md5 openssl rsa -noout -modulus -in filename.key | openssl md5   In this example, the Host Certificate is HostCert.pem and the private key is EcoStruxure.key. The private key was converted to EcoStructure.prv using Step 12 of Installing an SSL Certificate from an External CA - Communities (se.com) These commands make the hash more readable to human eye. We use openssl to inspect the x509 for Certificate and encryption type rsa for the key to produce the modulus (-modulus), which is a long string. You then use (-noout) to prevent the full modulus from printing to the screen. You then create a shorter md5 hash so the human eye can easily compare them. If the md5 hashes match, that indicates that the modulus is a match and proves that the certificate/key is a pair.

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 Cybersecurity vulnerability scans are flagging the Building Operation License Server because it is using HTTP rather than HTTPS Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation License Server Cause The Building Operation License Server contains a web portal for diagnostics and administration. By default, the Building Operation License Server Administration web portal is configured to use HTTP Resolution It is possible from the Administration area of the Building Operation License Server Administration web portal to configure HTTPS communications. Note: this does not change how Ecostruxure Building Operation connects to the license server.   The following process configures the Building Operation License Server Administration web portal to use HTTPS   From a web browser open the Building Operation License Server Administration web portal by typing http://localhost:8888 Once the web portal opens, select Administration at the top right. You will be prompted to log on, use "admin" as the user name. If you have logged in before, use the password you have defined. If not, enter "admin" as the password, and you will then be prompted to create a password. Once signed in Select the Server Configuration tab. Under the Secure Web Server Configuration section, select Enable HTTPS Change HTTPS Port to a unique number e.g. 8443 Select Redirect Non-Secure Web Access to Secure Web Access At the bottom of the page click the Save button and close the web browser tab. Restart the Building Operation X.X License Server from the Windows Services app (services.msc) If the license server is opened using http://localhost:8888 it will now redirect to HTTPS using the port specified in step 4 above

Issue How can I find out whether the EBO 2022 multi-version support applies to AS Classic module?  Does it apply to all the AS, AS-P, and AS-B modules? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The EBO 2022 Release Note describes that the EBO 2022 Device Administrator software is not supported on the original AS classic (part number SXWAUTSVR10001) but there is no description of the software backward compatibility of the EBO on AS classic. Resolution An AS classic can continue to exist in a multi-version system; the maximum version an AS classic can operate at is 3.1.2. It is nowhere implied that it is not supported under a multi-version setup. The statement “EBO 2022 does not support AS classic” in the EBO 2022 Release Note is misunderstood. It simply means that one cannot install EBO 2022 on an AS Classic, the same as the previous EBO 3.2 version. Note that the AS Classic will not inherit any features introduced in later EBO releases when operating in a multi-version system.

Issue When performing a backup of all Servers and All Data on an Enterprise Server the backup fails and generates an error in Software Administrator indicating the backup is corrupt although the backup is not corrupt. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Building Operation Enterprise Server Cause There is not enough free disk space on the Enterprise Server to save the backup file created.  The error generated in Software Administrator is a generic error. Resolution Check the Trace Log for Internal Server Error: Insufficient_Space_For_Backup If this is evident free up additional space on the Enterprise Server and re-try saving the backup.