Building Automation Knowledge Base

Issue Is it possible for multiple Automation Servers to be placed on the same backplane and use one power supply? Some known issues in this unsupported configuration: Automation Server only partially discover the IO Modules Function Block Programs (FBP) remain in an unloaded state (see FBP Unloaded) EBO 2022 (v4.0) and higher, Alarm: IO Driver unexpectedly timed out Product Line EcoStruxure Building Operation Environment Automation Server Power Supply SmartStruxure IO Modules Cause The terminal bases provides a path for communication between all connected units on the same backplane, as such the connection of two or more Automation Servers will cause communication issues between all connected units on that same backplane. Resolution From EBO 2022 (v4.0.1) due to changes in the Central I/O (CIO), checks are now made in the Automation Server to verify that the server is physically in SLOT 2, if this is not the case, then all Tasks are disabled, and will not run.    You cannot connect more than one Automation Server to the backplane. Only one Automation Server is allowed per power supply, the architecture is always "PS-AS-....." and after that I/O modules with additional PS units as needed, but only one Automation Server can exist on the same backplane.   Note that an alarm will also generate if you have the following configuration is attempted (also not supported)  PS-AS-PS-AS  Alarms will only clear after a restart (warm) of the server 

  Issue Erratic communication problems encountered during system migration from legacy products to AS-P controllers due to mismatched duplex settings. Product Line EcoStruxure Building Operation. Environment SpaceLogic AS-P SpaceLogic AS-B Cause Legacy controllers or existing devices supporting only Half-Duplex are incompatible with AS-P/AS-B controllers, which support Full Duplex 10/100BASE-TX communications. Resolution To address this issue, follow these steps: Install a managed switch: Introduce a managed switch between the devices to enable effective communication. Configure port settings: Utilize the features of the managed switch to configure each port according to the required duplex mode, either Half-Duplex or Full-Duplex. By implementing a managed switch, you can ensure compatibility between Half Duplex and Full Duplex devices, resolving communication problems and facilitating a smooth migration process.

  Issue How are Modbus 64-bit registers calculated in the Modbus limitations on an RP-C? Can both RS485 ports be used for Modbus on an RP-C? Product Line EcoStruxure Building Operation Environment SpaceLogic RP Controller series RP-C Modbus Cause EBO version 2023 introduced 64-bit register support in RP controllers. EBO Webhelp states that an RP-C has a maximum limit of 250 Modbus registers. It is unclear if a 64-bit register is counted as four 16-bit registers or just one register on the Modbus maximum count. The RP-C controller has two RS-485 ports, and it is unclear if both ports can be utilized for Modbus simultaneously. Resolution A 64-bit Modbus register is counted as one register in the Modbus maximum register count. The RP-C controller has two configurable RS-485 ports that can be used for: Sensor bus Room bus Modbus network As per EBO webhelp, the controller can host two networks, but only one network of each network type.

  Issue How can the WorkStation "Remember me on this computer" option be enabled or disabled? Remember me option is available; user can turn on or turn off remember me: Remember me option is enabled      Remember me option is unavailable; user can't turn on remember me: Remember me option is not enabled   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The availability of the "Remember me on this computer" option is determined by the security setting "Instruct clients to allow autocomplete of credentials." If this setting is unchecked, the server will disable the autocomplete feature for username and password fields on the login page, which also affects the availability of the "Remember me" option in WorkStation. Resolution For EBO versions 3.0 and higher: Remember me for WorkStation logins can be disabled on the server by navigating to Control Panel->Security settings. For EBO version 4.0 (EBO 2022) and higher: The availability of the "Remember me" option is determined by the "Instruct clients to allow autocomplete of credentials." setting. If the checkbox is checked, users can use the "Remember me" option. If the checkbox is unchecked, users will not be able to use the "Remember me" option. In EBO version 6.0 (EBO 2024) and higher, this option is unchecked by default for new installations. For upgrades, the setting chosen before the upgrade will be retained. For EBO version 3.x:  The availability of the "Remember me" option is determined by the "Allow Remember me." setting. If the checkbox is checked, users can use the "Remember me" option. If the checkbox is unchecked, users will not be able to use the "Remember me" option.

Issue Search widget graphics can't find graphic pages created under child servers.    Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause Currently, in EBO 2023, the dynamic search widget will only find graphic pages created on the server the user is logged into on WebStation. The dashboard search widget is not related to the native EBO search object and cannot search child servers. Resolution EBO 2024 (V6) or higher: From 6.0.1 it is possible to include TGML widgets from sub servers (all servers must have EBO version 6.0.1). Note that this functionality is only supported when you use HTTPS as the protocol between the servers, which is the default protocol in 6.0.1.   EBO 2023 (V5) or lower: If graphic pages are located under child servers, they need to be added to the dashboard manually.  Refer to: Adding a Graphic to a Dashboard

Issue The Insight Sensor and Multi Sensor Ambient Light Sensor require calibration before they can be effectively used. Product Line EcoStruxure Building Operation. Environment Insight Sensor. Multi Sensor Cause When setting up a new Insight Sensor or Multi Sensor device, the default settings for Gain and offset may result in inaccurate readings. Calibration is necessary to ensure accurate data collection based on the specific installation area. Resolution To perform the calibration, the following two tasks need to be carried out manually: Calibrate the Light Sensor: Conduct the calibration process in an environment without any daylight for optimal results. Set the light to 100%. Measure the lux level at the reference point using a lux meter. Adjust the gain settings on the sensor to match the measured lux level. Linearize the Feedback Signal: In some cases, lights may not provide a linear feedback (lux level) as the output increases. To compensate for this non-linearity, the signal from the controller is linearized before being sent to the output. During the optimization phase, the controller incrementally increases the output in 10% steps, measuring the adjacent lux levels for each step. The maximum lux supplement is calculated by subtracting the lux level at 100% output from the lux level at 0% output. After the optimization phase, breakpoints are determined and verified by re-running the test. If the results fall within the maximum difference limit compared to a linear signal, the calibration test is considered valid. Remember, performing the calibration process without any daylight present will yield the best results.  

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.