Issue Lua calculations in an SE8000 controller return integer values instead of decimal values. Values configured with decimal precision display as whole numbers (for example, 53.0 instead of 52.6), leading to questions about why floating-point results are not retained. Product Line EcoStruxure Building Operation, Field Devices Environment SE8000 Room Controller Lua scripting Lua Parameter X (AVxx) objects Cause SE8000 "Lua Parameter X (AVxx)" objects support only integer values. Decimal values are rounded when stored in these objects. Additionally, the Room_Hum (AV103) object rounds to whole numbers and is not designed to display decimal relative humidity values. Resolution When using Lua Parameter X (AVxx) objects that require decimal precision, multiply the calculated value by 10 (or 100) before storing it and divide the value when it is used. This preserves the required decimal precision within the integer-only object. For newer TRC controllers, floating-point values can be supported by defining the increment appropriately, for example: ME.AV25_Inc = 0.1 or ME.AV25_Inc = 0.01 For humidity values displayed through Room_Hum (AV103), decimal percentages are not supported because the object rounds to whole numbers and the SE8000 display is not designed to show decimal %RH values.

Issue When configuring an AS-P-3 and adding Central I/O modules, the module ID selection allows the first module to be assigned ID 1. There is uncertainty about whether module addressing should instead start at ID 3 because the AS-P-3 itself occupies an address on the I/O bus. Product Line EcoStruxure Building Operation Environment AS-P-3 Automation Server Central I/O modules EcoStruxure Building Operation Cause The addressing behavior of the AS-P-3 and connected Central I/O modules can lead to confusion when configuring module IDs. Documentation states that the AS-P-3 automation server has address 2 on the I/O bus, while connected devices are assigned subsequent addresses. Resolution Refer to the EcoStruxure Building Operation documentation for Central I/O bus addressing. The documentation states that an AS-P-3 automation server is the leftmost device on the I/O bus and has address 2. The I/O bus assigns addresses to connected Central I/O modules, with the address increasing by one for each connected device. Verify the intended module addressing against the current product documentation when configuring modules.  

Warning Broken Links: Links are unable to be updated since transition to MySchneider because some documentation is no longer available. Issue Upgrade path from version 1.0 to the 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 the 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 EBO system was in sync with Building Advisor Portal and is now not. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment Building Operation Building Advisor Portal Building Operation Enterprise Server Building Operation Automation Server Cause System ID changed and no longer matches in Building Advisor Portal. There are several causes for this: A backup restored on different hardware Migrated to a new VM VM was upgraded Windows update on the VM Resolution Check EBO Server Trace Log for nsp.pin.Cloud records and there should be one that shows "SystemId". Here is an example: 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterface Sending notification {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterfaceReal edgeAgent_sendMessage: {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} (retCode = 0) In Building Advisor Portal, check the BMS System Identifier to ensure it is the same and update as needed.   In this case, d057cfba-9fc0-11e4-a62a-3417ebbed129 needed to be updated to 4ba3db45-0235-7146-981a-c81dc08e39bf

Issue How to obtain an EcoStruxure Building Operation (EBO) evaluation license, engineering license, demo license, temporary license, or project license? This article explains where to download licenses for EBO 7.0 and later, as well as EBO 2024 (6.0) and earlier versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 7.0 and later EcoStruxure Building Operation 2024 (6.0) and earlier Cause   Users may be searching for "demo licenses", "evaluation licenses", "temporary licenses", "project licenses", or "engineering licenses". The terminology differs depending on the EBO version being used. EBO 7.0 and later uses Engineering Licenses, while EBO 2024 (6.0) and earlier uses Evaluation Licenses: EBO 7.0 and later Introduces the Engineering license, replacing previous demo or evaluation licenses. These licenses support system operation during the project phase without requiring commercial licenses. EBO 2024 (6.0) and earlier Evaluation license files remain available and must be downloaded manually. Resolution EBO 7.0 and Later — Engineering Licenses Engineering licenses can be downloaded from the EcoStruxure Power & Building Software Companion during the project phase. When the system is ready for commissioning or handover, you can convert Engineering licenses to Commercial licenses in the portal. No re-engineering or replacement of the license is required. Engineering licenses are valid for 6 months. They can be extended for another 6 months if required. WorkStation Pro demo licenses remain available for limited-time operation. Use commercial WorkStation Pro licenses for uninterrupted use. EBO 2024 (6.0) and Earlier — Evaluation Licenses Evaluation license files are available to BMS EcoXperts and Schneider Electric employees on mySchneider. Search for “Evaluation License” after logging in. For EBO 6.x and earlier software products (EC, ES, Workstation) select the Evaluation license with .asr file extension. For SpaceLogic Servers (AS-P, AS-B) select the license titled SpaceLogic Servers.

Issue After upgrading SmartConnector, the Portal reports that no valid license is installed. The existing SmartConnector Core and CSP Add-On licenses may appear installed and valid on the Licenses page, but other Portal selections return to the Setup - Install SmartConnector License page. Product Line EcoStruxure Building Operation Environment SmartConnector versions 2.5.x and 2.6.x SmartConnector CSP Add-On SmartConnector hosted on a virtual machine Cause The installed SmartConnector Core and CSP Add-On licenses were for the earlier SmartConnector version. New commercial licenses matching the upgraded SmartConnector version were required. Resolution Delete the existing SmartConnector Core and CSP Add-On licenses. Obtain new commercial licenses for both the SmartConnector framework and CSP Add-On from SmartConnector Server Marketplace. If a purchase order, invoice, or order confirmation number is requested, enter the same number used when obtaining the previous licenses. Add both new licenses to the SmartConnector management portal. Fully restart the virtual machine or computer, including Windows, to reinitialize SmartConnector. Confirm that SmartConnector no longer reports that a valid license is unavailable.

Issue A security scan of an External Trend Log Storage Server identifies a requirement to update the .NET Framework. The customer wants to know whether updating the .NET Framework could affect the server operation. Product Line EcoStruxure Building Operation Environment External Trend Log Storage Server PostgreSQL TimescaleDB Microsoft .NET Framework Microsoft Windows Server Warning Potential for Data Loss: Ensure data is backed up before proceeding. Cause As noted in: Install self-hosted TimescaleDB | Tiger Data Docs and PostgreSQL: Documentation: 18: 17.1. Requirements, PostgreSQL and TimescaleDB do not have .NET Framework requirements. However, an External Trend Log Storage Server may contain additional software components that could have .NET Framework dependencies, requiring verification before the framework is updated. Resolution Before updating the .NET Framework, verify: Windows Server version Currently installed .NET Framework version Whether any EcoStruxure Building Operation components or other applications installed on the server depend on a specific .NET Framework version. Plan the Windows update appropriately, as a server restart may be required. As an additional precaution, back up the External Log Storage using the the documented External Log Storage Backup and Restore procedure and copy the backup to an external disk or another server before performing the update.

Issue WorkStation crashes when opening specific Schedule objects. The same schedules can be opened in WebStation without crashing. The following error may be displayed    Input string was not in a correct format.  System.FormatException: Input string was not in a correct format.   Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2024 (v6) and above  EcoStruxure Building Operation WorkStation Cause A WorkStation crash is triggered when a schedule exception name contains a space. Testing across multiple EBO versions using both WorkStation and WebStation did not reproduce the creation of exception names containing spaces, and the mechanism that created the exception names remains unknown. Manual editing of XML files from exports is not supported and should be avoided. Resolution Review the affected schedule exception names and remove any spaces from them. In WorkStation with the System Tree displayed Ensure the Show/Hide non-presentation items is deselected (clear). Locate the Schedule: Holding down the CTRL-ALT-SHIFT keys, left-click on the arrow adjacent to the schedule This exposes the associated schedules within the main schedule.    Press F2 and rename each problematic schedule to remove spaces from the exception name. Open the schedule again and verify it displays correctly.

Issue An Engineering License expired before it was renewed, and Software Companion reported that the license could not be extended. The Extend option was unavailable to project administrators, preventing the project from continuing under the existing Engineering License. The license had never been previously extended. Product Line EcoStruxure Building Operation, Software Companion Environment Software Companion EcoStruxure Building Operation Engineering License Cause Engineering Licenses have a fixed six-month validity period with one single extension permitted. Once an Engineering License has expired, the self-service extension option is no longer available. See Manage Existing Licenses Resolution An expired Engineering License cannot be extended using the self-service Extend option in Software Companion. Contact Schneider Electric Support, providing the Entitlement ID, to request an extension of the expired license. When the extension is applied by Schneider Electric Support, the new expiration date will be six months from the date the extension is processed.

Issue Understanding how to check the firmware version of the USB-485-I/NET adapter and upgrade it to the latest version. Product Line TAC I/NET, EcoStruxure Building Operation Environment Building Operation I/NET USB-485 I/F Building Operation Automation Server Building Operation Automation Server Premium Cause If the firmware version of an I/Net USB interface is at an older firmware version then it may need to be updated. Please check the Exchange website for the latest firmware version Note: If the USB adapter is not at least at firmware version 1.02 then the system may experience communication issues in which I/Net values are not updating in EcoStruxure Building Operation or Automation Servers may be dropping offline.  In some cases, the Enterprise Server can lock up due to the older firmware in the I/Net USB adapter. Resolution To download the latest "USB-485-Inet Firmware Update Utility" click here. To Verify the Current Adapter Firmware Version in EBO 2.0 and Higher Right click the I/Net Interface is the System Tree of WorkStation and choose Properties. Down towards the bottom of the Basic tab you will find the Firmware Version.   To Verify the Current Adapter Firmware Version in SBO 1.9 and Lower Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Do not hold the pushbutton in on the USB Interface. Run the firmware executable. Press Enter. It will display: "Found USB Device on COMX" and will display the hardware version, software version, and the firmware date. It will then say, "Press Enter to begin the upgrade.  Note: Pressing Enter here will only repeat the hardware and firmware versions. The process to Upgrade the Adapter Firmware Note: If the I/Net USB adapter is already plugged into the laptop from checking the firmware version as described above, then to start the upgrade process USB cable will need to be unplugged from the laptop. Then follow the steps below. While holding down the pushbutton of the I/Net USB adapter, unplug the adapter's USB cable from the AS/AS-P and plug it into your laptop. After it is plugged into the laptop, release the pushbutton.  You will see that the LEDs on the interface are not flashing. On the laptop, run the firmware executable. After the command window opens, press Enter to start the update process. It should display "Unprogrammed device located" followed by "Device programmed successfully". Next, it will say "Found USB Device on COMX" and show the hardware version, firmware version, and the firmware date. Press Esc to close the command window.  The firmware upgrade is now complete. Note: Some laptops will not recognize the USB Interface and will not assign it a Com port.  If this is the case you will still be able to upgrade the firmware.  But instead of giving the Com port the and the firmware version after the upgrade is complete, it will show "Unable to find USB Device".   Also, you would not be able to check the firmware version prior to upgrading as mentioned above.  To correct this you must install the 7801 Tap.inf driver.  Click here to download the 7801 Tap.inf drivers. To install the 7801 Tap.inf drivers: Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Go into Device Manager and find the I/Net USB Interface.  It will have an error because of no driver. Right-click on it and choose to Update Driver Software... Select Browse my computer for driver software and browse to the 7801 Tap.inf file. Then follow the instructions above.

Issue A customer wants to deploy an Edge Server on ARM64-based hardware that supports Docker containers and is requesting an ARM64 container image. The available Edge Server container images appear to support AMD64 (x86-64) architecture only. Product Line EcoStruxure Building Operation Environment Building Operation Edge Server ARM64-based hardware Cause Edge Server supports AMD64 (x86-64) CPU architecture only. ARM64 container images are not available. Resolution Edge Server container images are currently available only for AMD64 (x86-64) CPU architecture. ARM64 container images are not supported or available for download. Customers wishing to deploy Edge Server should use supported AMD64 (x86-64) hardware platforms. If ARM64 support is required, submit an enhancement request through the appropriate Schneider Electric channel or engage the local sales representative for further guidance.   Note: Running AMD64 images through emulation on ARM64 hardware may impact performance and is not supported.

How to Obtain a Software Bill of Materials (SBOM) for EcoStruxure Building Operation Issue How can a Software Bill of Materials (SBOM) be obtained for an EcoStruxure Building Operation (EBO) release? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation WorkStation Cause A Software Bill of Materials (SBOM) is a comprehensive inventory of software components used within a software product. It provides information such as component names, versions, libraries, modules, frameworks, and other software elements included in the final product. SBOMs provide transparency into the software supply chain and support: Security by helping identify and address software vulnerabilities. Compliance by assisting with software licensing and open-source usage requirements. Supply Chain Management by providing visibility into software dependencies and component origins. Support and Maintenance by identifying the software components and versions included in a release. An SBOM may include: Component inventory Licensing information Component version information Resolution Schneider Electric maintains and distributes SBOMs through a secure SBOM platform. Because software libraries and components can change between product releases, SBOMs are version-specific and may need to be generated upon request. To obtain an SBOM for a specific EcoStruxure Building Operation release: Contact your local Product Management or Account Management team and specify the exact EBO version required. Customer onboarding begins after verification of the requestor's identity and receipt of a Non-Disclosure Agreement (NDA). Access is provided through the Schneider Electric SBOM portal: https://sbom.se.comhttps://sbom.se.com After the initial sign-in, the SBOM Operations team assigns the required permissions before SBOMs can be viewed or downloaded. Additional Information If the requested SBOM is for a previous product version, generation may take up to four weeks after the request is submitted. Available download formats may include CycloneDX, SPDX, and PDF. For assistance with SBOM access or interpretation, contact sbom@se.com. Keywords SBOM, Software Bill of Materials, EcoStruxure Building Operation, EBO, software components, software supply chain, software compliance, software security, third-party components, open-source components, vulnerability management, CycloneDX, SPDX, Schneider Electric SBOM Portal

Issue Additional Certificate Authority (CA) certificates are required for certificate validation within an EBO container. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation (EBO) Container Servers Enterprise Central for Linux Enterprise Server for Linux Edge Server Cause EBO containers ship with a default CA bundle that contains Mozilla root certificates. Additional CA certificates are not automatically included in the container and must be added to a custom CA bundle when required for the deployment. Resolution The supported method is to create a single PEM-formatted CA bundle that contains: The default Mozilla root certificates Any additional CA certificates required for the deployment The default CA bundle is located at: /opt/sbo/etc/ca-bundle.crt New Container Deployment Create a combined CA bundle containing the default Mozilla root certificates and the required additional CA certificates. Start the container using the --ca-bundle parameter. Existing Container Deployment Copy the default CA bundle from the container. Append the required CA certificate(s) to the bundle. Use the updated CA bundle as required by the deployment. Before deployment, verify that the updated CA bundle contains: The original Mozilla root certificates All additional CA certificates required for certificate validation Additional Reference: GitHub - SchneiderElectricBuildings/EBO-Servers: The official EcoStruxure™ Building Operation Servers page. · GitHub

Issue BACnet/IP controllers are not configured in RSTP Mode by default, therefore must be configured during installation. Having RSTP Mode disabled by default allows one to connect BACnet/IP controllers to any switch, even with port security configured to detect BPDU packets and disable the port. Product Line EcoStruxure Building Operation, TAC IA Series Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller IP-IO I/A Series N4 Jace8000 SmartX IP Driver for Niagara Cause RSTP protocol requires that controllers, switches, and network architecture are configured to ensure the protocol will operate as expected.  Resolution Setting RSTP Mode for BACnet/IP Controllers ALL devices in the RSTP loop MUST BE IN RSTP MODE to function properly. This is not a huge issue because during startup you can unplug 2nd side of the loop and it will function properly in a daisy chain. Ensure the SmartX Controllers are configured correctly Configuring BACnet/IP Controller Device Settings A factory or network reset returns the RSTP setting to Disabled. Important: Whenever you change RSTP settings, the controller MUST be WARM START. If you fail to perform this restart, the BACnet/IP controller will continue communicating using its previous RSTP settings. 'Activate IP Changes' does not affect RSTP mode. Ensure the switch is configured correctly per Configuring RSTP on a Managed Switch for SmartX IP Controllers. If asked to review this for a case, please provide PSS screenshots from the switch configuration page(s).  Bridge Priority = 4096 Hello Time = 2 sec Max Age = 40  (40 is the maximum value allowed by the protocol. Default is 20) Forward Delay = 21 sec Bridge Priority Considerations Change Bridge Priority by adding 4096 as switches get further away from AS. (8192, 12288, 16384, 20480, 24576, 28672) DO NOT set the priority as 32768 or higher because that is the built-in Bridge Priority of BACnet/IP Controllers. First, configure the Root Bridge Switch (closest to the Automation Server) settings. Then, configure the additional Switches in order of increasing Bridge Priority. {OPTIONAL}: Troubleshooting RSTP with Wireshark Plug in 2nd side of the RSTP Loop If all devices stay online, then it is working properly. Now test line breaks or controllers that are powered off. If all devices go offline and/or the switch LED is flashing rapidly, then go to RSTP Troubleshooting. Managed Switch Troubleshooting Consult the documentation or contact the vendor or manufacturer to assist with configuration for the items below. Ensure the switch is IEEE 802.1D - 2004 capable. BACnet/IP Controller Networking Term Definitions RSTP Ring mentions the Rapid Spanning Tree Protocol is specified in IEEE 802.1D - 2004. Ensure the firmware is up-to-date by contacting the vendor or manufacturer or downloading it from its website. Ensure ports not participating in RSTP are configured as Edge Port, Admin port, or have STP disabled. Nomenclature for those settings on your specific managed switch may vary. Adding BACnet/IP controllers to site-managed switches, work with Local IT to add these devices to their network. They will need to work with their switch vendor/manufacturer/support group to ensure the configuration of those switches because it could be more complex than changing the minimum recommended four settings above. Also, since RSTP Protocol is limited to Max Age = 40 (hops including site switches and BACnet/IP controllers), each loop's size may be limited based on their site switch network configuration and architecture.  Determined the proper configuration (or disable) for the following features. DHCP snooping Dynamic ARP inspection Denial-of-service (DOS) mitigations BPDU Guard BPDU Filter Energy-saving settings. Similar to Wake-on-LAN: the switch had minimal traffic, so ports entered power-saving mode. When they reactivated, the AS-P had already timed out, triggering a comm loss alarm. RSTP Troubleshooting Check each BACnet/IP Controller -> Diagnostics -> Device Report to confirm in RSTP Mode MANUAL CHECKOUT Double-click MP - Diagnostics Files - Device Report It will open in the default text editor Review the Device Settings section near the bottom. In firmware 1.00.0x, the report should report RSTP Mode: Enable In firmware 2.00.0x or higher, RSTP: Enabled and RSTP Status: Operational If it reports disabled, then perform Setting RSTP Mode for BACnet IP Controllers Step 1 until RSTP is working properly. USE SEARCH & EVENTS EBO 2.x MP Device IP and Settings.xml for EBO 2.0 as it only includes MP controllers EBO 3.x SmartX Device IP and Settings.xml for EBO 3.x or higher Import attached search USE RSTP STATUS GRAPHIC IN WEBSTATION Run from web browser via WebStation because utilizes ClientAPI EBO 6.0 and higher: TGML HTML Version SpaceLogic RSTP Status Summary - Schneider Electric Community  EBO 3.1 and higher: TGML Script Version Frontline Fridays Episode 02 - Rapid Spanning Tree Protocol (RSTP) Date: 2022-11-11 Mike Botens posted the following in the thread: RSTP Status TGML dated 2022-11-09 PDF of the presentation Fusion Fridays - Session 07 ​​​​ Date: 2020-05-28 The start of the video shows the graphics page in use RSTP Status.zip is downloaded via the link below the video. Extract the TGML and drop it on the AS to import. The suggestion is to store TGML directly under the AS to help with navigation in Webstation. Bind the network to the BACnet/IP network with the BACnet/IP Controllers. (You may need a second TGML page if BACnet/IP controllers are on Primary and Secondary IP) Run from web browser via WebStation because utilizes ClientAPI KNOWN ISSUES Offline controllers that are scattered are NOT an RSTP issue. Check to see if there is a possible DHCP issue by verifying controllers are still at their AUTO-IP address (IP 169.254.nnn.nnnn Subnet Mask 255.255.0.0). RSTP communications issues affect the entire RSTP loop or one contiguous group of controllers. Factory Reset or controller replacement should leave one ethernet cable unplugged until configured for RSTP per these articles: Replace a BACnet/IP Controller in an RSTP Ring Network Workflow and MP Controller Reset Modes If BACnet/IP Controller Device Report OR RSTP Graphic reports RSTP Status: Changes Pending instead of RSTP Status: Operational, disable RSTP Mode, Warm Start, re-enable RSTP Mode, Warm Start, and check again. SmartX is now SpaceLogic. KNOWN ISSUES with Firmware affecting RSTP: If Firmware 3.02.01 is installed, please upgrade to 3.02.02. RSTP not performing as expected with Static IP addressing RSTP does not work well on RPC HW RPC-16-B HW revision 6

Issue Customers may encounter one or more of the following symptoms: Automation Server (AS) reports a communication alarm for the Enterprise Server (ES). Server-to-server bindings remain unresolved. ES displays an AS as online, while the AS reports communication issues with the ES. Communication issues occur after firewall changes, network segmentation, NAT implementation, cellular router deployment, or system upgrades. Communication problems are observed despite successful ping tests or apparent server connectivity. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server (ES) Automation Server Premium (AS-P) Automation Server Bundled (AS-B) HTTPS server communications TCP server communications Cause A common misconception is that server communications are functioning correctly if the Enterprise Server can communicate with an Automation Server and reports it as online.   In EcoStruxure Building Operation, server-to-server communication is inherently bidirectional. Both servers must be capable of exchanging information as part of the server communication relationship.   When firewall rules, routing policies, NAT configurations, or network infrastructure prevent one server from communicating with the other, communication alarms, unresolved bindings, and other synchronization issues may occur even while the servers appear online.   The exact communication behavior depends on the EBO version and communication protocol being used. Refer to the EBO EcoStruxure BMS Server Communication Webhelp topic for guidance on the recommended protocols for each EBO version. Resolution EBO 5.x and Earlier Prior to EBO 6.0, server communications used traditional CSP, HTTP, or HTTPS transport methods. In these versions: Enterprise Servers initiate communications to Automation Servers. Automation Servers initiate communications to Enterprise Servers. Each server acts as both a client and a server. Both servers must be directly reachable across the network. The following communication models require bidirectional network connectivity: Protocol Default Port Connectivity Requirement TCP TCP 4444 Bidirectional HTTP TCP 80 Bidirectional HTTPS TCP 443 Bidirectional Because both servers actively establish connections, firewall rules and routing policies must allow communication in both directions. EBO 6.0 and Later Beginning with EBO 6.0, server communications over HTTPS were enhanced through the introduction of WebSocket technology. This change was designed to improve communication efficiency and support architectures where direct inbound communication between servers may not be practical, including: Cloud-hosted Enterprise Servers NAT environments Segmented enterprise networks With WebSocket communication enabled through HTTPS: One EBO server establishes a WebSocket connection to the other server. The WebSocket connection remains active as a long-lived TCP session. Both servers exchange information through the established session. Application-level communication remains fully bidirectional.   Although only one TCP session may be visible, communication continues to occur in both directions through the established WebSocket connection. This allows server communications to function in network architectures where traditional bidirectional connection establishment would otherwise be difficult. Important Notes HTTPS (TCP 443) When HTTPS communication is configured, EBO uses a WebSocket-based communication model. Characteristics include: Persistent long-lived connection Bidirectional application communication Reduced connection establishment overhead Improved performance compared to repeatedly creating and closing sessions Better support for NAT and cloud-connected deployments TCP(TCP 4444) Traditional TCP communication on TCP 4444 remains available. Characteristics include: Traditional connection model Requires bidirectional reachability Both servers must be capable of establishing communication with each other Does not use WebSocket transport Organizations upgrading older systems may still have servers communicating over TCP 4444 even after upgrading EBO versions. Multi-version systems In Multi-version systems, it recommended to: use HTTPS for EBO 6.x or later servers and TCP for servers on older versions. set the protocol to HTTPS for child servers after upgrading them to EBO 6.x or later not before the upgrade, refer to Automation Servers Running EBO 3.2.4 Go Offline After Enterprise Server 7.1.2 Upgrade When Using HTTPS  Troubleshooting Guidance When investigating unresolved bindings or ES/AS communication alarms: Identify which protocol is being used between servers. Verify whether communication is configured for TCP 4444 or HTTPS 443. Confirm that firewall policies permit the required traffic. Verify routing paths between all EBO servers. Review NAT rules that may affect server communications. Check for network devices that terminate or time out long-lived connections. Perform Repair Server Communications after resolving network issues. Verify communication alarms clear and bindings return to a resolved state. You can check for possible server to server communication issues in WorkStation by  creating an Alarm view with system alarm IDs filter “Communication failed” and “Server offline”. In WebStation V5 or later, you can use Diagnostics Server Communication List in WebStation Additional Information An Automation Server communication alarm referencing the Enterprise Server is a particularly important diagnostic indicator. This alarm originates from the Automation Server and indicates that the Automation Server is experiencing difficulty communicating with the Enterprise Server. The Enterprise Server may still show the Automation Server as online because communication in one direction continues to function. This asymmetric communication condition is frequently associated with: Firewall restrictions NAT translation issues Incomplete routing Network segmentation Cellular network deployments Improperly configured server communication protocols Network design guidance Understanding the underlying server communication model is often the key to diagnosing unresolved bindings and server communication alarms in complex network environments. For recommendations on EBO network design and best practices refer to the following documents: Information Technology System Planning Guide  Guidance on Implementing a Cybersecure BMS Architecture with EcoStruxure Building Operation

Issue There are a number of ways to disable a User, a card, or access levels, depending on what is needed at the site.  Product Line EcoStruxure Security Expert Environment Security Expert Data Sync  Active Directory 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. Cause There are a number of options described in documents and Security Expert's help, but the options are not consolidated in one place for comparison. Resolution Here are the options in no particular order. Some of these options can be affected when using the Data Sync Service and Active directory or they can be set manually in Security Expert.   1. Setting User Start and Expiry Dates Each user can be assigned access for a defined period by checking the Start and/or End options (in the General tab) and setting a date and time. This allows you to issue and send out cards prior to access being enabled, such as for employees who have not started yet. You can also set credentials to automatically expire, for example when a contractor is due to finish on a set date.   2. Disabling Users or using the Delete option     a. The Disable User setting (found under the Options tab) removes access immediately while still retaining the user record and its details. This is ideal for removing access temporarily, such as when staff are away on extended leave, or removing access while still retaining the user information. This gets distributed to the controllers with priority.      b. User Disable or Delete         1. Disable period: When this option is enabled you can set an inactivity period in days, hours or minutes. If there is no user activity during this period (i.e. they do not access any doors or keypads), the user record will be disabled (using the Disable user option in the Options tab).         2. Delete period: When this option is enabled you can set an inactivity period in days, hours or minutes. If there is no user activity during this period (i.e. they do not access any doors or keypads), the user record will be deleted from the database.     User last active: Shows the date and time the user was last granted access to a door or keypad within the system (read only). This field is not updated when the user accesses a door record which represents a COP or DOP in an HLI elevator integration. See related article Users accessing elevator doors are being disabled due to inactivity for more details on this.   3. Card Disable From Security Expert Help Card disabled: This setting allows a credential to be disabled without deleting the details. The credential can be re-enabled by unchecking the box. If a user has multiple credentials, the setting may be enabled or disabled where appropriate for each credential. Inactivity period: When this option is enabled you can set an inactivity period in days, hours or minutes. If the card is not used within this set period it will automatically be disabled. When this option is enabled you can set an inactivity period in days, hours or minutes. If the credential is not used within this period it will automatically be disabled. The maximum inactivity period is 365 days. If you enter a longer period the field will reset to the default period of 30 days.   4. Credentials This section allows you to assign custom credentials to users. When a credential type has been created in Sites | Credential types it will be automatically added, or you can use the Add and Delete buttons to manage the user's available credentials. Credential type: The custom credential type that the credential is associated with (e.g. license plate, custom card format, compliance type, etc.). Disabled: Check this box to disable the credential without deleting it. Credential: The specific credential data for the user (e.g. their license plate). Start: Only applicable to compliance types. When this option is enabled the user will not be able to gain access using this compliance before the date specified. End: Only applicable to compliance types. When this option is enabled the compliance will expire after the time and date specified and the user will not be able to use it to gain access. Inactivity period: When this option is enabled you can set an inactivity period in days, hours or minutes. If the credential is not used within this period it will automatically be disabled. The maximum inactivity period is 365 days. If you enter a longer period the field will reset.   5. Access Level Expires When this option is enabled the access level will expire based on the defined start and end dates.

Issue Raw card data events displayed unexpected facility code and card number values when credentials were presented to OSDP readers. A custom credential format had been configured; however, the card data shown in Security Expert did not match the expected values programmed on the card. Read Raw Data (9999:99999) At Entry Reader On Door 'door name' (DR1) (RD 1 Port 1) Product Line EcoStruxure Security Expert Environment Security Expert OSDP readers Custom credential format Cause Third party OSDP readers require a bit more configuration than native Security Expert readers. The custom credential format was configured on the Reader Expander but was not configured on the Smart Reader. As a result, the Smart Reader continued to interpret the credential using its existing format and transmitted data that did not match the expected credential definition. Resolution Verify that the custom credential format is configured on the Smart Reader. The reader expander will need to be set to OSDP and the associated Smart reader records set with the format settings. See detailed configuration details starting at the Security Expert Programming section in the AN-254 Security Expert - Configuring OSDP Readers - Application Note.   After applying the correct custom credential configuration to the Smart Reader and downloading the updated configuration, present the credential again and review the raw card data events. The facility code and card number should then be interpreted using the intended credential format.

Issue How to get answers for project specification responses or how to get a product enhancement implemented. Product Line EcoStruxure Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause Unsure who to go to for help with specification replies or how to get a potential product enhancement added to the offer. Resolution Create an idea on the EBO Idea Exchange community for your specific Offer. The more Likes an idea floated on the Community receives, the more attention it is given by offer management for that associated product line. Even if you do not yourself have an Enhancement Request, help raise the profile of others by Liking theirs Contact your local solution category manager for the Offer as they will be able to point you in the right direction for answers to specification questions and can help escalate enhancement requests to Product Management. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com When providing your feature request make sure to include as much detail as possible about the feature as well as any specifics that might help justify the need for the new feature.

Issue The system was reported as hanging and running slowly for a period of time. Users experienced slow response, including door unlock commands taking around 30 seconds to respond. The condition self-recovered without intervention and the system remained stable afterward. Product Line EcoStruxure Security Expert Environment Security Expert Client Server Microsoft SQL Server Cause Analysis of the SQL Server Application Log, SQL ERRORLOG, and Windows System Log identified multiple storage-related warnings during the reported outage window. The following events were recorded during the period when users experienced system hangs and slow response times: Event SQL Event 833 - Long I/O detected on SecurityExpert transaction log file (SecurityExpert.ldf) SQL Event 833 - Long I/O detected on SecurityExpertEvents database file (SecurityExpertEvents.mdf) SQL Event 833 - Long I/O detected on SecurityExpert database file (SecurityExpert.mdf) SQL Event 833 - Long I/O detected on SecurityExpertEvents transaction log file (SecurityExpertEvents.ldf) SQL Event 833 - Long I/O detected on SecurityExpertEvents database file (SecurityExpertEvents.mdf) ESENT Event 508 - Storage latency warning   These events indicated that database and transaction log I/O requests for the SecurityExpert and SecurityExpertEvents databases were taking up to 30 seconds to complete. The ESENT Event 508 warning further showed that the latency was observable outside SQL Server and also affected the Windows ESENT subsystem. Review of historical SQL ERRORLOG files showed similar long-I/O warnings occurring repeatedly over several weeks. Based on the available log evidence, underlying storage latency was identified as the most probable cause of the application slowdown and system hang behavior. Resolution Review of the SQL Server Application Log, SQL ERRORLOG files, and Windows System Log confirmed that SQL Server remained online throughout the incident and did not experience a service crash, restart, database recovery, or corruption event. Long I/O warnings affecting the SecurityExpert and SecurityExpertEvents databases were identified during the outage window. Historical review of the SQL ERRORLOG showed similar long-I/O warnings occurring repeatedly over several weeks, indicating an ongoing storage performance issue rather than an isolated application fault. The findings were provided for further investigation of the SQL Server infrastructure and storage performance.

Issue Server data may be combined in Building Advisor if a server connected to Building Advisor is cloned or detached without first disabling Cloud Connectivity (Cloud Plugin) and resetting its System ID. This can result in duplicate System IDs and incorrect data associations between servers. Product Line EcoStruxure Building Advisor, EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server (ES) Enterprise Central (EC) EcoStruxure Building Advisor Cloud Connectivity (Cloud Plugin) Cause Cloud Connectivity (Cloud Plugin) was not disabled, and the System ID was not reset before the server was cloned or detached. As a result, the new server retained the original server's identification, which can lead to duplicate System IDs and combined server data in Building Advisor.   Resolution   Identifier terminology: In EcoStruxure Building Operation, the identifier is displayed as Server Id. In the tracelog, the same identifier is shown as sysID. Because the tracelog provides the most accurate and current value, this article refers to it as the System ID. The System identifier field shown in EcoStruxure Building Operation is a different value. Although it may be used when connecting a server to the Building Advisor Portal, it is not used in this cloning or detaching procedure. Do not reset or modify the System identifier field for this process. Before adding a new top server, cloning a server, or detaching a server connected to Building Advisor:   If Cloud Agent is installed on the server, review the referenced article and complete the Cloud Agent removal procedure before continuing with the server modification activities How to remove Cloud Agent Components Before Performing Server Changes  Disable Cloud Connectivity (Cloud Plugin) Reset the Server Id shown in EcoStruxure Building Operation. This is the value identified as sysID in the tracelog and is referred to as the System ID in this article. Figure 1. Reset the value labeled Server Id. Do not modify the System identifier field for this procedure. Perform the server architecture change, such as adding a new top server, cloning the server, or detaching the server.   Resetting the Server Id/System ID allows the new server to generate a unique identifier and establish its own Building Advisor registration. The System identifier field is not part of this procedure. Following this procedure helps prevent duplicate System IDs and prevents data from multiple servers from being combined in Building Advisor. This is especially important when the servers belong to different customers. If a server was cloned, detached, or a new top server was added before Cloud Connectivity was disabled and the System ID was reset, open a PSS ticket for assistance with separating the server data.