Building Automation Knowledge Base

Issue When a SED-TRH-G-5045 sensor is positioned outside the range of the main EBO Zigbee wireless mesh, what is the recommended method or product to extend the wireless coverage? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause The SED-TRH-G-5045 is a Zigbee pro sleepy end device. Resolution Any Zigbee router within the system can function as a repeater to extend the radio communication. The router should be positioned within the radio range of the sensor and within the range of the RPx or another router. If a Zigbee device is powered by mains, it typically operates as a router. While there are currently no SE products designed solely with "repeater capability," several SE products possess router capabilities in addition to other capabilities, SE8000 SpaceLogic room controller Wiser plug CCTFR6500 Wiser Power Micromodule CCTFR6730 Wiser Room Thermostat with display CCTFR6400 or CCTFR6401. We have not officially tested any 3rd party Zigbee routers, however the IKEA TRÅDFRI repeater is known to work effectively.

Issue The first batch of White TRCs (produced in 24H1) could appear too bright in some low-light level situations. All future batches (post 24H1) do not have the issue. See the precise list of affected serial numbers in the appendix section below. Product Line EcoStruxure Building Operation Environment SpaceLogic Touchscreen Room Controller Cause The housing color is set in the device’s manufacturing configuration to tell it what color the screen bezel is (black or white). White TRCs produced with an incorrect housing color will read a higher value for light level. This has a direct impact on the backlight dimming levels, and the only effect will be the screen staying brighter in dark rooms. Resolution Customers experiencing brightness issues may simply adjust the backlight brightness parameters to a lower value, which are configurable in the TRC configuration screens and via BACnet/Modbus. This would reduce the overall brightness of the devices immediately, without fixing the housing color. We recommend going with a permanent fix, by setting the housing color via the USB port. The steps to fix this permanently would be: Connect USB-C cable to TRC Log in as an administrator into the TRC’s configuration screens (to enable USB connection) Open a terminal app like hyperterm or putty, with settings: Speed (baud): 115200bps Data bits: 8 Stop bits: 1 Parity: None Paste in the command: #001000061009FE00009C! Device responds: #000E00071009FE0051! To confirm or test, paste in the command: #000C00001009FEE8! Device responds: White housing: #001200011009FE000000F9! Black housing: #001200011009FE000001FA! Examples Below is an example of 4 white TRCs: The two (2) outermost devices are too bright (leftmost and rightmost white TRCs). The two (2) devices in the middle have been corrected to show adequate brightness. Appendix Since the Touch Room Controller’s serial number includes the date code, knowing whether a unit is impacted is very straightforward. Follow these instructions to determine if the unit of interest is impacted: Retrieve the serial number from the unit you suspect has the incorrect housing color. Example: FL24075TRC00002 Examine the serial number date code, wrapped between the “FL” and “TRC” substrings. Example: 24075 Decrypt the date code, using this logic: 24: year 2024 07: week 07 of 2024 5: day 5 of week 7 of 2024 If the date code is between the values 24074 and 24285, the product is impacted. Products outside of this date code range are not impacted, and no fix to housing color will be needed.

Issue Required a VPAT (Voluntary Product Accessibility Template) or statement of accessibility for EcoStruxure Building Operation. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause The Voluntary Product Accessibility Template (VPAT) is a document that evaluates how accessible a particular product is according to the Section 508 Standards. It is a self-disclosing document produced by the vendor which details each aspect of the Section 508 requirements and how the product supports each criterion. VPATs are used by buyers to determine how accessible a product is and where any potential deficiencies are. They are required by some buyers before a purchase is made. More Information can be found from the below public links: Section 508 of the Rehabilitation Act of 1973 Voluntary Product Accessibility Template (VPAT) Overview of Technologies and Formats WHAT IS A VPAT AND HOW IS IT USED? Resolution Schneider Electric does not have a VPAT document for EcoStruxure Building Operation.

Issue Define what Network 8000 devices that can be integrated with EcoStruxure Building Operation. Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation Automation Server version 1.2 until and including 3.2 Network 8000 Cause Need to know the supported devices for a Network 8000 to EcoStruxure Building Operation upgrade.  Resolution EcoStruxure Building Operation supports the following Network 8000 LCM devices: LCM EcoStruxure Building Operation supports the following Network 8000 ASD devices: Microzone II MicroFlo II LIM PEM  The following Micronet 2000 products are supported: MN-FLO MN-FLO3T MN-HPFC MN-ASDI  The following Network 8000 products are not supported in EcoStruxure Building Operation: CCL GCM LNC SIM GCM PLC Note: EcoStruxure Building Operation version 4.0 (EBO 2022) and higher are not supported

Issue How to remove an unknown Embedded Demo License Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Device Administrator v4.0.5 (EBO 2022) and below Cause The Embedded Demo Licenses are handled from the Device Administrator software. However, if the installed Embedded Demo License in the SpaceLogic servers does not comply with the file in the Device Administrator, the installed Demo License could not be removed. Resolution Instructions shown in the video below are for EBO 2022 (v4.0.5) and below. In the later releases EBO 2023 (v5.x) and above, a feature now allows the Demo licenses to be returned from selected servers.  See WebHelp topic Returning All Demo Licenses from the Selected SpaceLogic Automation Servers  For any License activations/returns to occur, there must be a trusted state (Certificate State) between the server and Device Administrator. Ensure that this is in place before attempting either resolution. For more info, see Certificates Managed using Device Administrator   If this function does not work, you can attempt the manual file name manipulation described below.    To check the name of the installed Embedded Demo License, log in to the SpaceLogic servers from Workstation. Navigate to System, LicenseManager, LicensingMetadata, ClientMetadata, Product 0. In ProductID, you will see the filename of the actual file.   Rename a Demo license file and import it into Device Manager to uncheck the selected Demo License file.   At the end of this session, you will be able to: Remove Unknown Demo License in SpaceLogic servers        

Issue How can I troubleshoot a communication issue with the Modbus protocol Is there a log available within the AS or ES that shows the Modbus communication between Modbus devices Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Enterprise Server Cause When troubleshooting Modbus issues in an AS or ES it can be helpful to see the communication between devices to help identify this issue. The trace log within both server types is available and is configured as described below in the resolution. Resolution Open Workstation and navigate to [AS/ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin. Right-click "nsp.pin.modbus" and choose Properties. Under Level, change from "Information" to "Trace", then click ok. Let it run a few minutes. If there are some user input needed to recreate the Modbus issue, then perform these steps now. Retrieve the log by right-clicking [AS/ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log.  Save the log file. A useful tool available on the Community, the Modbus decoder can be used to assist in viewing/debugging the Modbus trace log file information saved in the previous step. Once debugging is complete remember to change log level back to "Information" (reverse of step 3). Note: If the ES or AS is reset, i.e. cold started or warm started, the log level will return to 'Information', so if further increased logging is required, the procedure will need to be repeated. Note2: From v6 (2024), adding the trace below can be helpful for Modbus RTU /[ASName]/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.sport/nsp.pin.sport.DeviceRS485   Here is a video showing the above process. 

Issue Multiple MP-Vs have SpaceLogic Sensors (formerly SmartX Sensors) connected, all with identical configurations.  Some are missing the Properties, Scene Configurations, Button and Scene Configuration tabs. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Building Operation Room Controller (RPC)  Building Operation RP-V VAV Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Cause Delete the sensor and add it back, which takes a long time to execute for all sensors Resolution In WorkStation, in the System Tree pane, expand the BACnet Interface and the IP network. Click the BACnet/IP controller device. In the Actions menu, point to Device, Advanced, and then click Restore optional properties. In the Actions menu, point to Device and click Download all objects 

Issue A large room has multiple SpaceLogic Sensors SXWS (formerly SmartX sensor) and the temperature setpoint is changed in one of them. Is it possible for the temperature setpoint to be changed in the other sensors?  Product Line EcoStruxure Building Operation Environment Building Operation SpaceLogic Sensor Building Operation Room Controller (RPC) Building Operation RP-V VAV Cause In EBO (EcoStruxure Building Operation) version 3.1 a functionality called HMI references is introduced which can be used in this case. This new functionality makes it possible to have bi-directional bindings for the following value types in the RP series controller Blind position: analog value Occupancy override: digital value Fan speed: multistate value HVAC mode: multistate value Light level: analog value Selected scene: analog value Blind slat angle: analog value Temperature setpoint: analog value Resolution This is done by creating a value of the value types supporting the HMI reference functionality in the Application folder of the RP IP controller which the SpaceLogic Sensors are connected to. Then bind that value to the Display properties of each SpaceLogic Sensor       For example an Analog value is created in the Application folder of the RP-C and then bound to the Display Temperature Setpoint property of each connected SpaceLogic sensor. If then changing the Temperature setpoint from the RP-C that will be distributed to all SpaceLogic Sensors. But also if changing the Temperature setpoint in any of the SpaceLogic Sensors that value will be distributed to the other SpaceLogic Sensors and the RP-C.   To see an example on how this can be done please see video:  

Issue There is a performance issue affecting EBO Workstation and Product Support has requested logs. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Product Support has requested logs from EBO Workstation. Resolution The WorkStation logs and crash dumps are stored in the application data folder. The full path depends on the software installed:   EcoStruxure: %appdata%\Schneider Electric EcoStruxure\Building Operation\WorkStation\Logs %appdata%\Schneider Electric EcoStruxure\Building Operation\WorkStation\Crashes   StruxureWare: %appdata%\Schneider Electric StruxureWare\Building Operation\WorkStation\Logs %appdata%\Schneider Electric StruxureWare\Building Operation\WorkStation\Crashes     All files from the Logs folder starting with CoreLog or CrashLog must be included. All files from the Crashes folder must be included.   Perform the following to quickly access the appropriate folder above: Select link Paste into Windows Explorer Address Bar  If you can replicate an issue, perform this process to Temporarily Raise the Log Level before running the test and collecting the logs. Log in to WorkStation Click the Tools menu Click Options Hold down the left SHIFT key on the keyboard Click Apply Release the left SHIFT key on the keyboard and click OK to close the dialog The WorkStation log level is now set to INFO until WorkStation is closed.

Issue Upgrade path from version 1.0 to a current version Product Line EcoStruxure Building Operation Environment SmartStruxure Building Operation versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9 EcoStruxure Building Operation versions 2.0, 3.0, 3.1, 3.2, 3.3 (limited), 4.0, 5.0, 6.0 Cause Upgrade path from version 1.0 to current - version Important - The upgrade process is sequential, for example, 1.1 to 1.2 to 1.3 to 1.4 From v1.9, non-sequential upgrades are possible  The primary released versions were, Release Note Dates (approximate) 1.0.0.161   1.1.0.362 Dec 2011 1.2.0.767 July 2012 1.3.0.938 Nov 2012 1.3.0.10100 SP1   1.3.0.20011 SP2   1.4.0.4020 Sept 2013 1.4.1.68-73 Oct 2013 1.5.0.532 July 2014 1.6.0.250 (RC) Dec 2014 1.6.1.5000 Feb 2015 1.6.2.27 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.7.0.255 (RC) July 2015 1.7.1.89 Oct 2015 1.7.2.29 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.8.0.244 (RC) Mar 2016 1.8.1.79-87 Jun 2016  1.9.1.95 Apr 2017   1.9.2.45 Maintenance Release Oct 2017  - See release note 1.9.3.24 Maintenance Release April 2018  - See release note 1.9.4.29 Maintenance Release April 2019  - See release note 2.0.1.130 & 135 June 2018 (130(License, WS, Reports Server) 135 - Server (AS, ES, EC)) - See release note 2.0.2.67 Maintenance Release Sep 2018  - See release note 2.0.3.45 Maintenance Release Dec 2018  - See release note 2.0.4.83 Maintenance Release June 2019  - See release note 3.0.1.104 May 2019  - See release note 3.0.2.33 Maintenance Release July 2019  - See release note 3.0.3.11 Maintenance Release Aug 2019  - See release note 3.0.4.43 Maintenance Release Dec 2019  - See release note 3.1.1.312 Dec 2019  - See release note 3.1.2.29 Maintenance Release Mar 2020  - See release note 3.2.1.630 Aug 2020  - See release note 3.2.2.61 Maintenance Release Nov 2020  - See release note 3.2.3.59 Maintenance Release Mar 2021  - See release note 3.3.1.59L Limited distribution release Feb 2021 - intended for specific feature compatibility with some hardware or applications - See release note EBO 2022 (4.0.1.86) Dec 2021 - This version follows v3.x, and reflects a new naming convention focused on release year for clarity - See release note EBO 2022 (4.0.2.559 & 562) Maintenance Release Apr 2022 - WorkStation Hotfix and License Admin 4.0.2.562, others 4.0.2.559, see revised release note EBO 2022 (4.0.3.176) Maintenance Release Jul 2022 - See release note EBO 2023 (5.0.1.86) Dec 2022 - See release note EBO 2024 (6.0.1.93) Mar 2024 - See release note Resolution It is most important to read the Release Notes and System Upgrade Reference Guide for each version you are upgrading to, as there are some special notes that only apply to some installation types. Click Here for Release Notes Click Here for Upgrade documentation The Minimum upgrade path would be as below (See Release Notes for any special instruction) 1.0.0.161 1.1.0.362 See StruxureWare Building Operation v1.0 to v1.1 upgrade issues Appendix A 1.1.0.1225 See Appendix A 1.2.0.767 See Appendix A This version can be avoided by using 1.2.0.1412 if possible 1.2.0.2207 (Hotfix) Available from PSS See also Appendix A 1.3.0.938 See also Appendix A 1.3.0.10100 (SP1) (needed if runtime compatibility is required during upgrade) 1.4.0.4020 or 1.4.1.68 (Only needed if runtime compatibility is required during upgrade) See Upgrading Automation Servers from 1.3 to 1.4 1.5.0.532 1.6.1.5000 See Upgrade to 1.5.0 or 1.6.0 fails 1.7.1.89 1.8.1.87 See Product Announcement 00471 Pre-Upgrade LON Add-On 1.7.1 to 1.8.x 1.9.1.95 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions Option to 1.9.2.45 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.3.24 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.4.29 Upgrade options more limited with this version, only from v1.7.2, see the release note 2.0.1.130/135 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions. NOTE the new License structure for v2.0. 3.0.1.104 Possible to upgrade directly from v1.8, see the table in "System Upgrade Reference Guide" (3.0.1 System Upgrade Overview), but carefully study the release notes and upgrade instructions. NOTE the new Licenses for v3.0. 3.1.1.312 Possible to upgrade directly from v1.8 See Release notes and upgrade documents for full details 3.2.1.630 AS Classic not supported, Win 7 and Win server 2008 not supported 3.3.1.59L Limited distribution release - intended for specific feature compatibility with some hardware or applications, see release note for details. If you do not require the specific features outlined in this Release Notes, it is recommend installing EcoStruxure Building Operation 3.2.x instead EBO 2022 (4.0.1.86 and later) The following protocols, objects, and devices are not supported in EcoStruxure Building Operation 4.0 or higher: I/NET, Sigma, MicroNet, NETWORK 8000 ASD and LCM. A multi-version system supports I/NET, MicroNet, NETWORK 8000 ASD and LCM on automation servers and Sigma on an enterprise server, running an earlier version than 4.0. Report Server/WebReports is not supported in EcoStruxure Building Operation 4.0 or higher. See release notes for details. EBO 2023 (5.0.1.128 and later) New SpaceLogic and Easylogic Controller support, External Storage support for MS SQL, Some support for IPv6, BACnet protocol rev.16, Virtualized Automation Server - Edge Server added,   See release notes for details. EBO 2024 (6.0.1.93 and later) Added New Software Assurnace, Sustainability Pack, EBO Enterprise Server and Enterprise Central for Linux, OPC UA Client Support, Modbus2 Support, Visual Programming for Function Block, XLSX Report, and Touch Room Controller Support. See release notes for details. Appendix A - Upgrading from Specific 1.x Builds Upgrade from V1.0.0.XXXX to V1.3 (via V1.1 and V1.2) Upgrade from 1.0.0.XXXX to 1.1.0.1225 Upgrade from 1.1.0.1225 to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.1.0.XXXX to V1.3 (via V1.2) Upgrade from 1.1.0.XXXX to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.2.0.767 to V1.3 Apply hotfix 1.2.0.2207 Upgrade from 1.2.0.2207 to 1.3 NOTE: These hotfix builds are not available for download from the Extranet site, you will need to contact Product Support and request them

Issue Do all StruxureWare I/O modules use the same base? Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Cause Want to select the correct I/O module base Resolution Yes all Building Operation I/O modules use the same SXWTBIOW110001 terminal base.

Issue When trying to run an EBO virtual server in PCT2 the following error message is received: Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information. Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The maximum number of running servers in PCT 2 has been exceeded. Resolution PCT 2 supports a maximum of 250 running servers. If this limit is reached with 250 servers already operational, no additional servers can be started.

Issue What can be used to get the Device Log (aka Error Log) from a b3 or Infinet connected to an Automation Server (AS)? Product Line EcoStruxure Building Operation Environment Building Operation Server Bacnet Infinet Cause Need to get the Device Log (aka Error Log) from a b3 and/or Infinet connected to an AS. Resolution A tool called Building Operation Device Log Viewer (SE.SBO.Device.Log.Viewer.exe), starting with v1.9 now contains a dropdown used to choose BACnet (b3) or Infinet.  Prior to v1.9, it was limited to only obtaining b3 error logs.   64-bit Windows OS Default Location: "C:\Program Files (x86)\Schneider Electric [EcoStruxure|Struxureware]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   32-bit Windows OS Default Location: "C:\Program Files\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   Note: Based on the EBO system version you are connecting, use either [EcoStruxure|StruxureWare] and version [n.n] that matches. Note: Before v1.6 it was called Building Operation b3 Device Log Viewer and had a similarly named EXE file.   The Log Viewer tries to connect to the AS-P via UDP port 33487 when BACnet is selected and UDP port 33488 when Infinet is selected.

Issue How to configure PCT memory in Hyper-V. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Hyper-V Cause There is more memory available but PCT 2.0 can't start more servers. Example: Users with over 8 GB of memory can't start more than 36 servers.  Resolution This is because the default memory is set to 8GB, approximately 36 servers. (8GB - 2GB)/.170 GB = 36 server. Open the Hyper-V Manager In the left panel, right-click on "pct" and select Settings. The Setting dialog box opens. In the left pane, under Hardware, select the Memory item. The memory settings open in the right panel. The RAM shows 8192 MB(8 GB * 1024 = 8192 MB), the "Enable Dynamic Memory box" is checked, the Minimum RAM is 8192 MB and the Maximum RAM is 262144 MB(256GB *1024 = 262144 MB).    Enter the amount of memory assigned to PCT, 10240 MB(10 GB) in the example. If the "Enable Dynamic Memory" box is unchecked, the memory assigned to PCT will be 10240 MB. If the "Enable Dynamic Memory" box is checked, the memory assigned to PCT will be between 8 GB and 10 GB(not 256 GB or other amount because the limitation is set at 10 GB from the RAM setting above). R&D recommends not using "Enable Dynamic Memory".   Helpful Link: PCT 2.0 memory usage calculation

Issue When a very long path is included in a request to the SmartConnector RESTful EWS gateway, such as when attempting to acknowledge an alarm with a long path, the gateway returns the error "HTTP Error 400: The request URL is invalid."   <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>Bad Request</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD> <BODY><h2>Bad Request - Invalid URL</h2> <hr><p>HTTP Error 400. The request URL is invalid.</p> </BODY></HTML> Product Line EcoStruxure Building Operation Environment SmartConnector Cause In Windows, the default maximum number of characters in a URL path segment (the area between the slashes in the URL) is 260 characters. When the object path, after double URL encoding, exceeds 260 characters, it triggers error 400. Resolution   To resolve this issue, follow these steps: Add a registry key "UrlSegmentMaxLength" to the following path in the SmartConnector PC registry: Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters Name: UrlSegmentMaxLength Type: DWORD Value: 0 - 32,766 (e.g., set the value to 1000) After adding the registry key, restart the HTTP services or restart the PC. Detailed instructions for this process can be found in the "Http.sys registry settings for Windows" guide on the Microsoft Learn website. Http.sys registry settings for Windows - Internet Information Services | Microsoft Learn

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue SmartX SpaceLogic/EasyLogic device is offline, inspection of the device's status LED reveals a solid red pattern instead of the normal solid green.   Product Line EcoStruxure Building Operation Environment SmartX SpaceLogic Controller SmartX EasyLogic Controller Cause A solid red status LED indicates the application can't be launched, typically there could be two reasons as the root cause of this situation: The application has become corrupted, this happens very rarely. Application keeps crashing on startup. To prevent an infinite startup->crash->startup loop, the firmware in the SmartX SpaceLogic/EasyLogic devices implement a feature known as the application startup retry counter, if the application has crashed multiple times, never running for longer than an internally defined time (typically 10 minutes), the boot applet will stop all attempts to launch the application. Resolution We can attempt to recover the device by performing the following steps: Cycle power to the device. Cold start the device by holding down the reset button for more than 5 seconds but less than 9 If the controller starts up and shows a normal status LED (solid green), immediately start  a device upgrade firmware operation, the goal is to get the uprev operation going before the application crashes again.

Issue Using a VPN, the Building Commissioning Tool is unable to recognize the network adapter Product Line EcoStruxure Building Operation Environment Building Operation Building Commissioning Tool Cause VPNs have not been specifically tested and therefore are not supported Resolution Though VPNs have not been tested and are not supported, some sites have found that this is possible. If the VPN adapter IP is available then it may work, if you have a VPN adapter that does not show up, please enter an enhancement request If the above isn't available, run the tool after turning off the VPN application or Global Protect.

Issue Licenses required to upgrade SBO/EBO to EBO 2022 v4.0.x Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium - Secure boot Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Clarifying licensing upgrade requirements for EBO 2022 v4.0.x Resolution Example: Upgrading a site SBO 1.x or EBO 2.x to EBO 2022 v4.0.x or later directly. Site has an Enterprise Server (ES) the ES has 7x Automation servers AS-Ps and 2x AS-Bs attached. One AS-P has a Modbus interface, and 1 AS-B has a Modbus interface. Adding 1 additional AS-P classic (non-secure boot), 1x AS-P-S secure boot and 1 AS-B scalable. The SBO 1.x or EBO 2.x licenses need to be upgraded to EBO 3.x first. Upgrade ES licensing from SBO 1.x license to EBO 3.x.  These licenses need to be activated using License Administrator.   1 x SXWSWESUP13010 ES Upgrade from 1.X to 3.0 with 10 or less AS    The following additional licenses are required for each AS-x when upgrading a site from SBO 1.x to EBO 3.x or upgrading a site from EBO 2.x that was originally installed at SBO 1.x and upgraded to EBO 2.x. These are not required if the site was originally installed at EBO 2.0 and upgrading to EBO 3.x. These licenses need to be activated using License Administrator.   7 x SXWSWASUP00001 license will be required one for each AS-P. 2 x SXWSWASUP00001 licenses will be required one for each AS-B.   Note: If the site has more than 24 AS-xs then part number SXWSWASUP00099 provides 999 licenses. EBO 3.2.x architectural guidelines allows a maximum of 250 AS-xs per ES.   Upgrade ES license from EBO 3 to EBO 4 This license needs to be activated using License Administrator.   1 x SXWSWESUP30010 ES Upgrade from 3.X to EBO 2022 or later (i.e. to the current EBO version) with 10 or less AS Upgrade AS-P/B licensing from EBO 3 to EBO 4 or later These licenses need to be activated using Device Administrator.   For each AS-P (non secure boot AS-P and AS-P-NL), one of the following bundles would be required for each AS-P.   SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full SXWSWASPUP30BP Full Bulk pack for upgrading AS-P-XX from EBO 3.x to EBO 2022 or later, contains 125 pieces of SXWSWASPUP30FU. For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   Note: Once an AS-P license is upgraded, there is no differentiation between AS-P Secure Boot and AS-P Non-Secure Boot (Classic):   If the “SXWSWASPUP30SD Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard” license was purchased for an AS-P classic, and later it requires an enhanced or full license.   SXWSWXUP00SDEN ASP Bundle upgrade - Standard to Enhanced SXWSWXUP00SDFU ASP Bundle upgrade - Standard to Full Would need to be purchased.   If the “SXWSWASPUP30EN Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Enhanced” license was purchased for an AS-P classic, and later it requires an  full license. SXWSWXUP00ENFU ASP Bundle upgrade - Enhanced to Full Would need to be purchased.   For the AS-Bs (AS-B-24, AS-B-24H, AS-B-36, and AS-B-36H), one of the following bundles would be required for each AS-B. These licenses need to be activated using Device Administrator.   SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs Note: Once an AS-B license is upgraded, there is no differentiation between AS-B Scalable and AS-B (L) Non-Scalable (Classic): If the “SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 AS-B Bundle – Standard” license was purchased for an AS-B (L) classic, and later it requires a full license.   SXWSWXBBUPSDFU ASB Bundle upgrade - Standard to Full, would need to be purchased.   To upgrade the AS-B-L (classic) type, the SXWSWASBUP30SD ASB Upgrade – Standard license is all that is required.   For the additional AS-P classic one of the following licenses would be required. SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   For the additional AS-P secure boot one of the following licenses would be required. SXWSWXBU0000SA ASP Bundle - Standalone  SXWSWXBU0000SD ASP Bundle – Standard  SXWSWXBU0000EN ASP Bundle – Enhanced  SXWSWXBU0000FU ASP Bundle - Full  For the AS-P secure boot if a Modbus interface is to be used the SXWSWX000MBRTU Modbus license would be required. For the additional AS-B Scalable one of the following licenses would be required. SXWSWXBBU010SD ASB Bundle – Standard SXWSWXBBU050FU ASB Bundle – Full A SXWSWX000MBRTU Modbus license is not needed with AS-B scalable. If an additional AS-B classic was added one of the following licenses would be required. SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs     Addition: If the site had an Enterprise Central (EC) at EBO 2.0 and was upgrading to EBO 2022 v4.0.x or later, one of the following licenses would be required to upgrade to EBO 3.x first:   SXWSWECUP23005 EC Upgrade with 5 or less ES SXWSWECUP23010 EC Upgrade with 10 or less ES Then one of the following licenses would be require to upgrade from EBO 3.x to EBO 2022 v4.0.x or later:   SXWSWECUP30005 EC Upgrade from 3.x - with 5 or less ES SXWSWECUP30010 EC Upgrade from 3.x - with 10 or less ES   For more information on the bundles, search for 'software bundles" in the  “Part Numbers and Hardware/Software User Matrix – EBO 2024”   For information on software and features that require licenses  

Issue When attempting to attach an Enterprise Server to a parent Enterprise Central, the error "Server name not unique" is encountered, despite the Enterprise Server having a unique name. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The error may arise due to either the server's name not being unique or one of its child servers' names not being unique. Resolution To resolve this issue, ensure that the server's name is indeed unique, and also verify that the names of the its child servers are also unique. For example, if an Enterprise server "ES1" has a child Edge server named "Edge_1" attached to Enterprise Central "EC", and another Enterprise server "ES2" also has a child Edge server named "Edge_1", it cannot be attached to "EC" until the child Edge Server is renamed to ensure uniqueness.

Issue The SUM Alarm does not generate an alarm when an Automation Server goes offline Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The online status of the Automation Servers needs to be monitored so that an alarm can be generated if any of them go offline. Using the following configuration does not work. 1. Create a sum alarm 2. Add Source and set to AS path (e.g /SWXnetwork/servers/AS1). Replacing AS1 with a * makes no difference 3. Add System alarm ID and set to "Server Offline" 4. Add Alarm State and set to "Selection as required" Resolution Options that do work Option 1 System Alarm ID = Server offline Alarm Text = */Servers/* Alarm State = Alarm and Alarm Acknowledge - (Select as required). Option 2 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source Name = AS1 or AS*   Option 3 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source = /SWXnetwork/System/Server Communication/To/AS* - (As the alarm is in the ES, the path comes from the ES).