Building Automation Knowledge Base

Issue The customer requests End User License Agreement (EULA) Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Requests for the End User License Agreement (EULA) Resolution The EULA can be found in the following locations:   "About" box for WorkStation under the "Help" menu. See the screenshots below. WorkStation Help menu EULA   WorkStation Log on Page It is also available in the installation folder (under Workstation\language). WebHelp LICENSING END USER LICENSE AGREEMENT

  Issue  A flaw was found in handling multiplexed streams in the HTTP/2 protocol. A client can repeatedly make a request for a new multiplex stream and immediately send an RST_STREAM frame to cancel it. This creates extra work for the server setting up and tearing down the streams while not hitting any server-side limit for the maximum number of active streams per connection, resulting in a denial of service due to server resource consumption(CVE-2023-44487 from Redhat). All versions 2.13 and higher with HTTP/2 enabled are affected: 2.13, 3.0, 4.0, and 5.0. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation SmartX AS-P Server SmartX AS-B Server Cause HTTP vulnerability raised security concerns for EBO Resolution EBO isn't affected by the impacted protocol since EBO doesn't utilize HTTP 2.0 and 3.0.

Issue SpaceLogic IP device is located in a remote subnet and EcoStruxure BMS server can't discover it. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation IP-IO Cause BACnet broadcast messages, such as Who is/I am that are used for device discovery, will not be forwarded between the two IP subnets. BACnet Broadcast Management Device (BBMD) is required to allow BACnet to operate through IP routers. Resolution Scenario 1: SpaceLogic BACnet/IP device is located in remote subnet with no EcoStruxure BMS server or BBMD located in same subnet. EcoStruxure BMS server will be configured as BBMD, and SpaceLogic BACnet/IP device will be configured as foreign device and register itself with BBMD (which is the AS-P in our example).    The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in foreign IP subnet as a foreign device. Configure an EcoStruxure BMS server as BBMD. View foreign device registration on the EcoStruxure BMS Server. Discover and host the SpaceLogic BACnet/IP device.   Scenario 2: SpaceLogic BACnet/IP device is located in remote subnet with a 3rd party device that can be configured as BBMD. In the other subnet, EcoStruxure BMS server will also be configure as BBMD. SpaceLogic IP device will not be configured as foreign device as there is BBMD device in the same subnet. This BBMD will redistribute the essential broadcast messages to it. Once configured, EcoStruxure BMS server will be able to discover and host the SpaceLogic BACnet/IP device and other BACnet deviced located in the remote subnet.   The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in a remote IP subnet. Configure an EcoStruxure BMS server as BBMD. Configure Broadcast distribution table (BDT) in EBO. Use BACnet browser to check and verify the BDT configuration of a 3rd party BACnet device. Discover and host the SpaceLogic BACnet/IP device and 3rd party BACnet devices located on remote subnet.

Issue How to Discover devices on the LonWorks network. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause When adding LonWorks devices to the network, it is possible to let the SmartX server scan the LonWorks network. Resolution Open Workstation and locate your SmartX server. Left-click on the SmartX server to select it. Select the "Discovery Devices" tab. In the "Select device Type" drop-down list, click to expand the options and choose "Lonworks". Right-click on the "Devices" folder. From the context menu, select "Scan network for devices". Drag from the discovered devices and drop them into your Lonworks network under the SmartX server. Commission the devices. Following these steps should initiate the device scanning process and help you discover Lonworks devices on the network.   This video will show how to discover lonworks devices on a lonworks network.   At the end of this session you will be able to: Discover devices on the LonWorks network Add the discovered devices to your system  

Issue Licenses are becoming damaged repeatedly over time and/or licenses are going in to a disabled state. Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure License Administrator Virtual Machine Cause Damaged Licenses: If the license server / license administrator is installed on a virtual machine, the common reason for damaged licenses is that the MAC address of the virtual machine is not set to be static. Every time the MAC address changes, the license will become damaged. Disabled Licenses: This is usually caused when the license fails to complete a process such as a return or repair. This could be due to an intermittent internet connection or the process timed out while trying to communicate with the license server. Resolution Repair License with License Administrator The first step to take with a damaged or disabled license is to use the repair function in license administrator. Follow the steps from WebHelp topic Repairing an EcoStruxure Building Operation Software License. If the repair function does not work, then the license server will need to be reset.  Reset License Server (Unable to Repair License) Below are the steps to remove the damage or disabled licenses before reactivating the permanent licenses again: Put a SBO demo license on the site to get it back up and running right away. Locate the Entitlement ID and/or activation ID of the impacted licenses. Open a case with your local BMS support group and provide them this information. This information will be used to release the licenses to prepare them to be rehosted. There are then two potential methods to  reset the license server: Download and run the SBO License Server Reset tool from the Community Manually reset the License Server Stop the License Server. In the License Server application folder, remove all files:                 - File path for Windows 7, Windows 8.1, and WIndow 10: \ProgramData\FLEXnet                 - File path for Windows Server 2008 and Windows Server 2012: \ProgramData\FLEXnet   Start the License Server Reactivate the returned network licenses.   Note: When you reactivate all returned network license, new License Server .data files are created together with the activation of the first license. For more detail, reference WebHelp: Resetting the License Server.

Issue Need to bind program objects and as detailed in Deploying a Function Block Program to a Server it is not possible to interact (eg. bind its objects to the EcoStruxure BMS objects) with a saved program outside of Builder until it is deployed.  After creating a Builder for Function Block program it saves successfully but generates an "Undefined Problem" error when trying to deploy. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Project Configuration Tool (PCT) Building Operation Builder for Function Block Cause Program execution is not enabled on the specific server within PCT Resolution Follow the steps to enable program execution: In the PCT Client select the server containing the program Expand the Properties on the right hand side Check the "Enable Program Execution" box Save the changes Stop and Start the server as per the message to restart for the changes to apply Clear the message after restart Finally, back in Workstation observe when trying to deploy the program it is successful

Issue Which SpaceLogic Sensors could be used with the TAC Xenta 100 series controllers? Product Line TAC Vista Environment ZBuilder Xenta 122 Cause The STR100-series sensors will be withdrawn, and SpaceLogic Sensors have been identified as suitable replacements. Resolution Only TAC Xenta 122 controllers can be configured to use 10K Type 3 Thermistor.   To integrate SpaceLogic Sensors with the TAC Xenta 122 controllers, follow these steps in ZBuilder: Access the Configuration tab. Navigate to the Room unit settings. Locate the checkbox labeled "Use STR-5xx series" and select it.   Please note that only the SLASXXX, SLABXXX, and SLAWXXX models are compatible with the TAC Xenta 122 controllers. These sensors, however, do not feature buttons for setpoint adjustment or fan control.  

Issue How can the AS-P be used as an LPA interface? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium. Cause Working with Loytec LPA in  Building Operation and needing a remote interface for connectivity. Resolution To configure the AS-P as an interface in Loytec LonWorks Protocol Analyzer (LPA), follow the steps below: Ensure that you have the Loytec LonWorks Protocol Analyzer (LPA) software installed and licensed. Activate the AS-P as an LPA interface: Access the Loytec LonWorks Protocol Analyzer (LPA) software. Locate the settings or configuration section. Enable the option to "Activate AS-P as LPA" to designate the AS-P device as the interface. Add AS-P as a remote network interface in LPA: Within the Loytec LonWorks Protocol Analyzer (LPA) software, navigate to the network interface settings. Look for the option to "Add AS-P as Remote Network Interface" and select it. Keep in mind that by using the AS-P as the LPA interface, you will only be able to capture and analyze the traffic addressed to or from the AS-P device itself. Network traffic between other devices on the LonWorks network may not be captured using this configuration.   It's important to have the Loytec LonWorks Protocol Analyzer (LPA) software installed and properly licensed to perform these steps.  

Issue The Conversion Settings guideline is not documented. Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Infinet i2 BACnet B3 Cause Lack of information on "Conversion" column in Conversion Settings for B3 and I2 Resolution The Conversion column has the highest priority in the setting. If a formula exists then the setting below will not affect the Value.   Example The ElecValue is set to 10 for the following examples. 1. The Conversion field is empty, the ElecValue = 10 which corresponds to 100 on the Engineering scale. The Input Value = 100. 2. The Conversion field is set to ElecValue, and the ElecValue = 10. The Input Value = 10. 3. The Conversion field is set to ElecValue - 7. The Input Value = 3.  

Issue These LED light sequences are not found in the documentation Solid White Flashing White Alternating Blue and Amber Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Cause Not yet added to current documentation Resolution Solid white forever is either no firmware in the controller or the controller is running UBoot and not launching the firmware. Solid white, transient, and followed by yellow/amber, is UBoot running. Perform a factory reset and attempt to upgrade the firmware to the latest revision allowed based on the version of EBO used on site Flashing white would indicate a defective board requiring RMA or a power supply problem (It was seen on one site the 24Vdc power supply had been damaged and was only supplying 12 to 14Vdc. Thus replacing the power supply solved the problem) Alternating Red/Blue happens during an up rev of the firmware. It specifically happens when the EFR32 (the Bluetooth chip) is being upgraded. Generally, power supply problems can cause various issues with RPx and MPx controllers, including partial corruption of the firmware/application. A recent case had transformer secondary circuits linked that cause Red/Blue flashing and 'untranslated BACnet errors’ following a site wide power cycle. Always ensure the RPx power supplies are within tolerance and fully compliant to Grounding and Power for Systems WebHelp has been updated to include more information see RP Controller Status LED

  Issue When attempting to add a new user to the system in EcoStruxure Building Operation, a workstation crash occurs upon selecting the Create button. The crash dialogue shows: parsing "[]" - Unterminated [] set Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The workstation crash is triggered by a misconfiguration in the password policy settings. Specifically, the Special Character field has been unintentionally deleted, resulting in it being left blank. However, the password policy still requires a minimum number of special characters to be entered (set to 1 or more). Resolution To resolve this issue, follow one of the two options below: Restore the default special characters: Access the password policy settings in the control panel. Locate the Special Character field. Click on the "Default Characters" button to add the default special characters back to the field. Disable the requirement for special characters: Access the password policy settings in the control panel. Locate the option for "Minimal number of special characters". Modify the setting to "0" (zero) to remove the requirement for special characters. By implementing either of these solutions, the workstation crash issue should be resolved when creating new users in EcoStruxure Building Operation.

Issue Deleting BACnet objects using a BACnet Operator Workstation (BOWS) can permanently remove those objects from the BACnet device.  The effected devices can be Building Operation BACnet devices, e.g. Automation Server or third party BACnet devices. Environment Building Operation Enterprise Server Building Operation Automation Server 3rd Party BACnet Controllers Cause The BACnet controller(s) in question support BACnet create and delete services on the specific objects.  Resolution Functions as Designed If the device supports create and delete services for the object it is designed to function this way. In general the BOWS should provide as much as possible a complete and accurate image of the contents of the device.  For example using the Enterprise/Automation server as a BOWS:  Creating new objects will automatically send a create-object request and attempt to create the object in the device. Deleting objects will automatically send a delete-object request and attempt to delete the object in the device. Upload and Download of object commands attempt to synchronize the database with the actual contents of the device.  Download will attempt to create any objects that are in the database (but not in the device), and also attempt to delete any objects from the device which are not in the database. Upload adds or removes objects from the BOWS database. Please see Protecting EBO/SBO BACnet objects from being deleted by 3rd party BOWS for a method of preventing BACnet points being deleted from an Enterprise/Automation Server.  Consult third party documentation to identify preventing creation/deletion.   Offline Workaround If the device supports the Device Communication Control service, and allows disable, a work around is to make changes to the database while the device is offline. For example, using the Enterprise/Automation server as a BOWS, right click the device and select Device->Communication->Disable.    Open the property grid for the device and it should take about 12 seconds before the device is reported as offline.  Any other break in communication should also work to get the device offline.  Once offline, objects can be deleted from the database without affecting the device.  But, after changing the database this way, the device's "upload" or "download" commands should not be used, as it will re-synchronize the device and database (either deleting objects from the device, or adding them back to the database).  It is important to note using this method the BOWS will not fully represent the objects in the device and also remember to re-enable the communication to the device.

Issue Is it possible to prevent a 3rd party BACnet Operator Workstation (BOWS) from deleting the BACnet objects in an Enterprise/Automation server? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause Current version of EBO/SBO puts the responsibility of creating & deleting BACnet objects to the site administrator.  The enhanced security on this issue will be added in the later version. Resolution The following video demonstrates how to protect the BACnet objects in ES/AS by utilizing shortcut objects.    

Issue Using the Function Block Program Macro Library Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The need for program examples on creating Function Block Programs Resolution To assist with creating Function Block Programs, the EBO Function Block Program Macro Block Library is included in the EBO Workstation installation. Here's how you can leverage the Macro Library: Access the Macro Library: Open the EBO Workstation. Navigate to the Function Block Program section. Locate and access the Macro Library. Incorporate the Macro Library: Once inside the Macro Library, explore the various pre-built Function Block Program macros available. Select the desired macro that aligns with the specific function you intend to program. Integrate the selected macro into your Function Block Program to enhance its functionality. Learn by example: The Macro Library also serves as an excellent resource for learning and understanding how to program specific functions. Study the structure and logic of the included macros to gain insights into effective programming practices. Utilize the examples as a starting point to develop your own customized Function Block Programs. The EBO Function Block Program Macro Block Library is designed to simplify and accelerate your programming tasks within EcoStruxure Building Operation. Leverage the library's resources and example programs to enhance your programming skills and efficiency.  

Issue Cannot change the IP address or host a SpaceLogic IP device, MP or RP controllers, or IP-IO modules in a second EBO Server. Product Line EcoStruxure Building Operation Environment IP address BACnet Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller  Building Operation IP-IO Building Commission Application Cause 1. IP settings are saved (eg in Building Commission), but the IP address of the Controller does not change. (Option to change most settings is grayed out from Building Commission for hosted SpaceLogic IP devices) 2. The Controller is already hosted by an EBO server and cannot be hosted by a second EBO server, thus data objects cannot be read. 3. Rehosting an SpaceLogic IP device to a different EBO server Resolution 1. Changing the IP address "settings" can be done with Building Commission application, formely know as eCommission Tool, in some earlier versions but if the SpaceLogic IP device, formely known as SmartX IP device, is already fully hosted by an EBO Server, then a warm start from the Building Commission is inhibited. (Option to change most settings is grayed out from Building Commission for hosted SpaceLogic IP devices) Without the hosting Server initiated warm start the new IP setting will not be used. If the SpaceLogic IP device is not hosted then the IP address can be changed from the Building Commission, using the warm start option. Notes A local warm start initiated at the SpaceLogic IP device(manually with the reset button) will not force the SpaceLogic IP device to use these new settings. See BACnet/IP Controller Commissioning Scenarios The IP address of a Hosted SpaceLogic IP device cannot be modified from eCommission Tool A factory reset will force the SpaceLogic IP device to return to AutoIP and DHCP, the BACnet Id will generally be retained see Automatic Association after a Factory Reset in a BACnet Controller or IO Module 2. When a SpaceLogic IP device is fully hosted by an EBO Server, it can be BACnet hosted by a second EBO Server, but this will only contain the standard BACnet Applications folder. This hosted BACnet Device needs to be manually created using the SpaceLogic IP device instance Id.  Below, it can be seen that the fully hosted SpaceLogic IP device and the BACnet only hosting under ASP_22   3. When a SpaceLogic IP device is configured or programmed via the hosting EBO Serving using WorkStation, some of the objects (eg. Scripts or Function Block) data is not fully contained within the SpaceLogic IP device. Thus if the hosting EBO server is changed, some of the configuration data will be lost and a simple upload to the new hosting EBO Server will not upload all the data required to recreated these objects. In such a case, an export from the original hosting EBO Server should be imported into the new hosting EBO Server to ensure no data is lost.

Issue Alarms not received at the Enterprise Server Product Line EcoStruxure Building Operation, Satchwell BAS & Sigma Environment Sigma Transition Alarms Cause Alarms are being generated by the controller but do not appear at the Enterprise Server. Resolution If any changes are made to the Sigma system using the Sigma Server, then either all, or part of the Sigma configuration must be re-imported into the Building Operation Enterprise Server.

Issue Certificate for FDA regulations in the manufacturing of pharmaceuticals, 21 CFR Part 11 "Electronic Records / Electronic Signatures." Can Building Operation incorporate a comment section to capture a reason for change made by an operator/user? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Building Operation site in need of the compliance certificate for 21 CFR Part 11 "Electronic Records / Electronic Signatures." Usually, these are pharmaceutical manufacturing sites, and the full FDA document PRT11Elect.pdf is attached to this article. Resolution EcoStruxure Building Operation 3.2 and higher Compliance Pack enables 21 CFR Part 11 compliance for regulated industries. The Compliance Pack is an add-on module to EcoStruxure Building to help regulated industries meet the compliance requirements for Electronic Signatures & Electronic Records that are in place in the region.   This feature in our EcoStruxure Building Operation software provides facility-wide accountability and traceability of the environmental conditions that can impact the quality and safety of products developed in controlled environments in line with the 21CFR Part 11 regulation.   Compliance Pack is a licensed feature and compatible with EcoStruxure Building Operation V3.2.1 and later. Part Number Description SXWSWCMPLPK001 Compliance Pack – includes TimescaleDB, Digital PDF Signing, Change Control, For one Enterprise Server or one Enterprise Central For technical documentation and sales enablement tools for the Compliance Pack, please visit The Exchange Building & Power Extranet and use the search keyword: 21cfr ebo   EcoStruxure Building Operation 3.1 and below EcoStruxure Building Operation V3.1 and below has not addressed the pharmaceutical market and there is no electronic signature feature set that meets the FDA regulations 21 CFR part 11.   For sales issues surrounding FDA regulations, please contact through your sales channel to the local Category Manager. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue One of the following error messages are displayed. Internal server error Server already part of a system Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Server Cause Cause #1 The automation server is either not the same version as the enterprise server or it is still connected to a different Enterprise Server. If the AS is still connected to another ES then it must be detached before it can be added underneath a new ES. Cause #2 In some instances, the User Permissions "System Address" is not added to the user account that is attempting to add the server.    Resolution If you are given an error that states "Domain: Internal Server Error" then you need to download the same version of firmware to the AS that is installed on the ES. Resolution #1 In order to detach the automation server, follow these steps: Log in to the Automation Server. In the system tree pane, right-click on the automation server and go to Advanced > Detach server. The Disconnect Automation Server window will open; click yes. The Automation Server is now detached and can be added to an Enterprise Server. Resolution #2 To confirm this is the issue, the simplest resolution is Check a current backup using the SBO xbk Analyzer and verify the number of servers listed under "Reports>Servers" exist or  Log on using the default admin account and see if these servers exist. Detach the server(s), as described above. If the secondary user still requires permission to add and see ALL servers go to the user and select the Permissions tab shown below: Ensure the ES path is selected Click on the "Add System" button (identified with the arrow) Enable all options to allow read/write, create etc.  Save these changes and log off and back on with this user to see the changes. This user should now be able to add/see ALL servers.

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 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.   Note: For Advanced Display v3 please see How to recover the password for Advanced Display version 3

Issue The address used to access the Generate Authentication URL up to and including PME 9.0 no longer works. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation EcoStruxure Energy Expert (formerly Power Manager) EcoStruxure Power Monitoring Expert Cause Up to and including PME 9.0 the following address could always be used to access the 'Generate Authentication URL' page which allows a user to manually create urls/hyperlinks for specific PME pages (with and without authentication) to use in EBO: http://<yourservername>/SystemDataService/Auth/GenerateAuthURL .     However with the advent of PME2020 this address is no longer valid. Resolution The address for the 'Generate Authentication URL' page has changed in PME2020 and permission to access this new address must also be activated via a Query run on the SQL database of the PME2020 install. Page 1676 of the PME 2020 System Guide  - Manual integration steps without using the Integration Utility - shows the required steps and the new address to be used.