Issue Some BACnet devices advertise support for services such as RPM, COV, etc but malfunction when the service is used. An example of such a device is the Johnson Controls TEC2627VVT, which advertises support for RPM but fails to upload its objects when SBO uses RPM to get the object list. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause Some BACnet devices with inconsistent protocol implementations cannot process BACnet services such as RPM, COV, etc. Resolution GLOBAL Rules are implemented in versions where the first patches are applied, but then are deprecated when surfaced via Workstation, which is targeted for the next Major.Minor revision Feature Supported in Version Available in Workstation (deprecated) <ignore-unhosted-devices/> 3.2.3.9005 and higher (*) /BACnet Interface <disable-force-polling/>   <enable-force-polling/>   <restrict-backup-service/>   <evaluate-alarms-on-startup/>   <enable-execute-time-sync/>   /System/Interface Manager/BACnet <disable-mstp-fast-offline-detection/>   MSTP Network under BACnet Interface   Vendor/Model Rules For particular BACnet devices, the 'Vendor Identifier' and 'Model Name' are specified and must match exactly as shown in that device's Properties - Advanced Tab. Feature Supported in Version <no-rpm/> 1.8.1 and higher <no-cov/> 1.8.1.23701 and higher <no-get-event-information/>   <no-broadcast-who-is/>     Users can create a rule in the BACnet interface to configure the BACnet Plug-in to avoid using the service. Some rules are global, while others can be for specific BACnet devices.    Ensure you have installed the version that supports the feature you want to change. Setup file using the no-rpm rule. Use a text editor like 'Notepad' to create a text file or download the same file below. Enter the device's vendor ID (5)  and model name (TEC2627VVT) followed by the rule (no-rpm) using the format seen in the screenshot below. Save the file to the desired location on the PC with a name aiding later identification. Under the BACnet interface, create a new 'Document' object in the 'Application' folder. NOTE: The object MUST be named 'service_blacklist' in all lowercase. Click 'Next,' import the text file created in step 1, and save the 'Document' object. Restart the Server  Once the device is on the block list, SBO will not send 'readPropertyMultiple' requests to the device using only individual 'readProperty' requests. Add the service_blacklist to the EBO Server. Add the no-cov tag if you would like to block that service for this device:  Extended for multiple devices from different vendors simultaneously using this example for reference.   One can add a global rule using this syntax to ignore unhosted devices. * NOTE: It is recommended to remove <ignore-unhosted-devices/> after upgrading to EBO 4.0/2022 and higher because this feature is supported in the BACnet Interface Properties and BACnet Device Discovery view. Device Discovery for BACnet Controllers and IO Modules (se.com)  Once the Server has restarted, check the trace.log file and search for service_blacklist, there should be entries similar to this. It will also list a warning for Global Rules that have been deprecated because they are now available in Workstation.

Issue Clarification is required on whether BACnet/IP communication for MP-C, AS-P, and EcoStruxure Building Operation can use TCP instead of UDP, and which devices must be whitelisted in firewall configurations. There may also be uncertainty regarding BACnet/SC support and communication paths for BACnet/IP Controllers, such as the MP-C, RP-C range of devices, and third-party devices. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation (EBO) 3.2 or later Automation Servers BACnet/IP, BACnet/SC, BACnet MS/TP SpaceLogic MP‑C / MP‑C Pro / MP‑V SpaceLogic RP‑C / RP‑C Pro / RP‑V Cause BACnet/IP communication runs over UDP and does not support TCP. BACnet/SC is a separate communication method that uses TCP-based secure connections. Additionally, standard EcoStruxure Building Operation communication routes MP-C traffic through the AS-P rather than directly to the Enterprise Server. Resolution BACnet/IP must remain UDP-based and cannot be changed to operate over TCP. If TCP-based communication is required, BACnet/SC must be used as it provides TLS-encrypted WebSocket communication over TCP and requires certificate-based trust between devices. For firewall configuration: For BACnet/SC: All devices that need to communicate with the BACnet/SC hub must be allowed through the firewall, as communication uses a hub-and-spoke architecture with outbound connections to the hub. For standard EcoStruxure Building Operation communication (non-BACnet/SC), MP-C devices communicate via the AS-P, so only the AS-P needs to be whitelisted on the Enterprise Server firewall. If a third-party device does not support BACnet/SC, it cannot participate in BACnet/SC communication.   Other considerations:  Before recommending firewall rules or BACnet/SC adoption, ensure the customer's complete network and security requirements are understood. Requests for "whitelisting" or replacing UDP with TCP can sometimes indicate a broader network segmentation or security requirement rather than a BACnet protocol limitation. Consider gathering additional information regarding: The overall system architecture and communication paths. The specific security or compliance requirement driving the request. Whether network segmentation, isolation, or traffic restriction is the primary objective. Alternative approaches that may satisfy the requirement include: Network switch-based access controls, such as MAC address filtering, port security, or other switch-level whitelisting mechanisms. VLAN segmentation to isolate BACnet/IP networks, including secondary or site-specific BACnet networks. Deploying edge servers with multiple network interfaces, where a secondary BACnet network can be connected through a dedicated interface or VLAN. Isolating the Building Management System (BMS) / Operational Technology (OT) network within the network infrastructure rather than relying solely on host-based firewall restrictions. Understanding the customer's full architectural requirements helps ensure the most appropriate network design is recommended rather than focusing only on protocol-level configuration options.

Issue An Operator Display connected to an AS-P or AS-B is not discovered in EcoStruxure Building Operation and cannot be added to the system. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS-B, AS-P) SpaceLogic Operator Display (HMIST6400SL) Cause Adding an Operator Display to AS-B or AS-P Resolution Connect to the AS-B or AS-P with EBO Device Administrator version 3.0.1 or later. In the AS-B/AS-P configuration, navigate to Ethernet 2 Configuration and configure: Ethernet 2 Mode: Dual IP DHCP Mode: Server Verify that the default IP address for Ethernet 2 is 10.110.210.1.   Apply and save the configuration changes. Connect the Operator Display to Ethernet Port 2 on the AS-B or AS-P. Verify that the Operator Display establishes communication with the server by confirming that the three red Offline indicators at the top of the display are no longer shown. Connect an Building Operation WorkStation to the AS-B or AS-P. Create a BACnet Interface. Create a second IP Network beneath the BACnet Interface. Select the server in the System Tree and open the Device Discovery tab. Device Discovery and locate the Operator Display in the discovered devices list. Drag and drop the Operator Display onto the second IP Network. Validation The Operator Display appears in Device Discovery. The Operator Display can be added to the second IP Network. The display is online and communicating with the AS-B or AS-P.

Issue Insight Sensors were not counting people as expected, even though the sensors were online and other sensor functions such as PIR operation appeared to be working. Troubleshooting, resets, firmware upgrades, and recommissioning did not resolve the issue. Product Line EcoStruxure Building Operation Environment Insight Sensor Cause After troubleshooting with the Insight Sensor Engineering Tool, removing masks for testing, and verifying that other sensor functions were operating correctly, the affected sensors were determined to be faulty. Resolution Use the Insight Sensor Engineering Tool to verify configuration and test the sensor with no masking applied. If the sensor remains online, other sensor functions like PIR operate correctly, and people counting still does not function, replace the affected sensor. In this case, replacing the sensor resolved the people-counting issue, which ruled out any configuration issues.

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 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 After upgrading an MP/RP controller to firmware 7.0x.xx, Bluetooth commissioning from Building Commission (EBC), on phone and PC versions, fails. The PIN can be entered and the controller appears in the paired Bluetooth devices list, but the connection does not progress further. Product Line EcoStruxure Building Operation Environment Building Commission MP/RP Controller  Cause The External Application Whitelist was enabled. When Bluetooth is enabled while the whitelist is active, the Bluetooth connection is secured for the Engage mobile application and is not available for commissioning through the commissioning tool. Resolution Disable the External Application Whitelist on the controller and reconnect using Bluetooth. After the whitelist was disabled, the Bluetooth connection is established and the controller can be commissioned through EBC. If needed, assign a new Bluetooth PIN and remove the controller from the paired devices list before attempting to reconnect. Refer to: RP Controller Settings Properties - Basic Tab

Issue How to configure the EcoStruxure BMS External Log Storage feature using PI System. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need EBO to send selected trend logs and the event log to AVEVA PI System directly without the need for intermediate storage or specialized PI System connectors. Resolution The following video will illustrate how to: Install and configure AVEVA PI system (PI Server and PI Web API) for testing. Configure PI system settings in EBO. Configure trend logs to be written to PI system. View and organized the data in PI system Explorer. Things you need: EBO 2023 (V5.0.3) or higher with valid AVEVA PI System connection license or demo license (Enterprise Server, AS-P, AS-B or Edge Server). AVEVA PI server and PI web API with valid license (Check EBO Information Technology System Planning Guide for tested versions). For more information about PI system recommended architectures, system requirements and installation instructions, please check AVEVA documentation, PI System™ | AVEVA, OSIsoft - PI System and YouTube video published by AVEVA for detailed instructions about installing and setting up PI system Setting up a PI System Development Environment From Scratch - YouTube Note: In EBO V7.0.1 or higher, values can also be read and hosted from an AVEVA PI System, refer to: Hosting Points from AVEVA PI System Note: Starting with EBO version 7.1.2 and later, disabling the "EnableCSRFDefense" setting on the AVEVA side is neither required nor recommended. Hotfixes are available for EBO 6.0.4 and EBO 7.0.3. Please contact Technical Support to obtain the appropriate hotfix. Refer to: EBO cannot connect to AVEVA PI when EnableCSRFDefense is enabled - Schneider Electric Community

Issue Extended Logs have stopped updating on the Enterprise Server. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server Automation Server Trend Logs (TL) Extended Trend Logs (ETL) Architecture Note In typical deployments, Trend Logs reside on Automation Servers, while Extended Trend Logs are hosted on the Enterprise Server. Data is transferred from TL to ETL using a subscription-based mechanism driven by sequence numbers. Any inconsistency in this synchronization can result in ETL not updating even when TL continues logging. Cause Extended Trend logs have been configured on-site and have been operating reliably over an extended period. A subset or all of the Extended Trend Logs has stopped updating. The issue can occur after a Server backup is restored.  Trend logs and Extended Trend logs are allocated sequence numbers, and if the sequence numbers do not follow the correct sequence, the Extended Trend log may not update. How to verify the issue: Trend Log: Navigate to the corresponding Trend log and open it in a "Trend Log List" view. Add an additional column to show the Sequence number. Note the highest sequence number used. Extended Trend Log: Navigate to the Extended Trend log that is referencing the above Trend Log. Open the Extended Trend Log properties. Press and hold down the "ALT" key and click where the dot is indicated on the screen shot below, (just below the Basic tab).      This will show some more properties for the Extended Trend Log, the one you are interested in is “Last transferred sequence number”.   If the last transferred sequence number on the Extended Trend Log is higher than the Trend log’s highest sequence number, then that is why the Extended Trend Log has stopped. Resolution Option 1 - When Historical Data is Required Increase the sample interval by reducing the interval time of the Trend log until it has caught up with Extended Trend Log's Sequence Number. The Extended Trend Log will only fetch new records that has a sequence number higher than the last transferred sequence number. Until the sequence of Trend Log has caught up with the sequence of Extended Trend Log, you will not see any new records in the Extended Trend Log. The Log records that are created after you have caught up in sequence numbers will only be fetched to Extended Trend Log.   Option 2 - When Historical Trend and Extended Trend Data Are Not Required Create a new Extended Trend Log and associate the corresponding Trend Log. The new Extended Trend Log will fetch every record that the Trend log has and continue from there, but you will lose the records of the old Extended Trend Log had that the Trend log does not have anymore.   Option 3 - When Historical Trend Data Is Not Required but Extended Trend Data Must Be Retained Backup & restore the AS on the same AS. The Trend log will be cleared but the Extended Trend Log will start fetching new records.   Important Note - Extended Trend Log:  The extended trend log cannot log a variable. The extended trend log gets the initial value of the connected trend log. Do not connect more than one extended trend log to a trend log or another extended trend log. If a trend log is connected to two or more extended trend logs, critical conflicts can occur. The extended trend log must have the same unit as the monitored trend log to correctly display values.

Issue A user wants to configure a static IP address on a SpaceLogic Twisted Pair Adapter (SXWTPAE10001). After installing the Twisted Pair Adapter Engineering Tool, no option is available to modify the adapter IP configuration or change it from DHCP to a fixed IP address. Product Line EcoStruxure Building Operation Environment SpaceLogic Twisted Pair Adapter (SXWTPAE10001) Twisted Pair Adapter Engineering Tool Ethernet infrastructure over existing twisted-pair cabling Cause No mechanism is available to modify the adapter's maintenance IP address or configure the adapter for DHCP or a user-defined static IP address. The adapter uses a fixed maintenance IP address (192.168.0.249) for engineering access and operates as a Layer 2 Ethernet bridge/switch rather than a configurable Layer 3 network device, and this is the key reason why configurable IP addressing is not relevant to its normal operation. Resolution Configuring the SXWTPAE10001 with a user-defined static IP address is not supported. The maintenance IP address (192.168.0.249) is fixed and intended only for engineering access through the Twisted Pair Adapter Engineering Tool. During normal operation, the adapter transparently forwards Layer 2 Ethernet traffic while connected devices retain their own operational IP addresses. If engineering access is required, configure a secondary IP address on the engineering workstation within the 192.168.0.x/24 subnet and connect using the Twisted Pair Adapter Engineering Tool as noted in the Twisted Pair Adapter Engineering Tool v1.0.0 Release Notes. This maintenance IP is not used for normal runtime communications. How the Twisted Pair Adapter operates The TPA is a Layer 2 device and it's role is simply to transport Ethernet frames across the existing twisted-pair infrastructure. From the perspective of the connected IP devices, the adapter is largely transparent. To put this into context: Layer 2 (Data Link Layer) works with Ethernet frames and MAC addresses. Layer 3 (Network Layer) works with IP addresses. Routers operate at Layer 3 and make forwarding decisions based on IP addresses. Switches and bridges operate at Layer 2 and make forwarding decisions based on MAC addresses. A useful analogy is a standard Ethernet switch. When you connect an AS-P or RP-C to an Ethernet switch, the switch itself does not participate in the BACnet/IP communications. The switch simply learns which MAC addresses are connected to each port and forwards Ethernet frames accordingly. The BACnet/IP communication occurs through the switch, not with the switch. The Twisted Pair Adapter performs a similar function. The AS-P, RP-C, and other IP devices retain their own operational IP addresses and communicate normally using BACnet/IP or BACnet/SC.   

Issue Currently, a procedure exists to do conversion of i2 to b3 and vice versa using Continuum Cyberstation and NetControllers.   However, it is much simpler to do the conversion using the RoamIO and the Infinet/BACnet Service Tools. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) 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. 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 This article describes an alternate and simplified conversion method to the original procedure published to convert i2 to b3. Before using this procedure, read the Conversion of Continuum devices from i2 to b3 and vice-versa in the field Knowledge Base article in its entirety for important information about converting i2/b3 controllers in the field.  Resolution IMPORTANT NOTE If the device you are converting is of model i2/b3 865/866/885 STOP First confirm that the device is NOT a -V device, this is accomplished by inspecting its version number, -V devices have a "1" embedded in the second part (after the ".") of the version number   A -v device will show the version number as follows... 3.501027 A non -v device will show the version number as follows... 3.500027   Before starting the procedure, you need the following items: The device to be converted. The serial number of the device to be converted. A RoamIO2 configured to communicate with your PC via Bluetooth and the Infinet and BACnet Service Tools A special, firmware application upgrade file for the appropriate device model as provided by Product Support A bootloader file for the appropriate device model, provided by Product Support To convert i2 field devices into b3 BACnet using RoamIO2 Contact Product Support and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (e.g. i2920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd) for each model you are converting. Connect the RoamIO2 directly to the i2 device (make sure device is disconnected from field bus) Launch the InfinetServiceToolPC.exe (attached) and click on the connect icon Once the device shows up on the tree, right click on it then select 'Uprev firmware...' Send the conversion application file provided by Product Support Once the uprev operation is complete, click the connect icon to disconnect the Infinet Service Tool from the i2 device then close the InfinetServiceTool app. Cycle power to the RoamIO2 then start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from i2 to a b3 causes the device to default to baud 38400 and an invalid BACnet master MAC id, so upon connection the following error will be shown... Click 'Yes' to continue From the 'Tools' menu select 'Set b3 baud rate' and set it to Baud38400  From the 'Tools' menu select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC id then click on 'Apply' If the baud and MAC id have been set successfully, the device will automatically pop up in the tree but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right click on the device then select 'Update OS', send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, select the device and click on 'Cold start device' After the device re-start, click on the device in the tree and select 'Switch view', confirm the firmware and boot loader versions are correct. (you may need to do a refresh from the 'Tools' menu)

Issue The EcoStruxure Building Operation demo environment can be accessed online or downloaded as a backup file for local demonstration. There may be confusion regarding availability of demo versions, usernames and passwords, differences between online and offline demos, and the support scope for demo databases. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation demonstration database Cause Users may experience confusion when accessing the EcoStruxure Building Operation demo environment because multiple delivery methods (hosted online and local offline databases) are available, each with different access methods, behaviour, and support expectations. This can lead to inconsistent experiences such as shared changes in the online environment, differences in login credentials, and uncertainty about what is supported, particularly when users assume the demo behaves like a standard, single-user or production system. Resolution Two demo options are available: Online demo (hosted environment) Accessible via Schneider Electric hosted demo platform. Multiple users may be logged in simultaneously, and actions performed by other users may be visible and impact the demonstration experience. Offline demo (local installation) A backup copy of the demo database can be downloaded from mySchneider and installed locally to ensure exclusive access and a controlled demonstration environment. The database can be reinstalled at any time to restore the original state. Access to supporting materials: Login credentials and user guides are available via mySchneider Support expectations: The Demo Database is provided "as is" and is not supported by Product Support Product Support may assist with installation of core software components such as License Administrator or Enterprise Server Product Support does not support demo database content, features, or behavior

Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) 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 With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution IMPORTANT NOTES: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    If the device you are converting is of model i2/b3 865/866/885 STOP First confirm that the device is NOT a -V device, this is accomplished by editing the device and inspecting its version number, -V devices have a "1" embedded in the second part (after the ".") of the version number   A non -v device will show the above version number as follow,,, 3.500027   To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After: NOTE 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device. Make sure to use the V2 version of the b3 to i2 conversion files as it was found the original set of b3 to i2 conversion files did not work in some cases. Please note that once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

Issue Users are unclear about how to complete the offline registration process in EcoStruxure Building Operation, particularly regarding the location and use of the System ID and Registration Code. Product Line EcoStruxure Building Operation Environment EBO Systems requiring offline activation Cause This confusion arises due to: Misinterpretation of the registration email: Users expect both the System ID and Registration Code to be included, but only the System ID is provided. Limited visibility of the registration code: The code is only shown in the browser on the online machine used for registration. Manual transfer requirement: Users may not realize that the registration code must be manually copied to the offline machine. Uncertainty around System ID resets: Users may not know how or when to reset the System ID, especially after hardware changes or reinstallation. Resolution System ID Visibility: The registration email contains only the System ID. The registration code is not included in the email. Where to Find the registration Code: The registration code is displayed in the web browser on the online machine during the registration process. This code must be manually copied and entered into the offline machine to complete activation. Resetting the System ID: If a reset is required, refer to the official guide: 🔗 Reset System ID – EcoStruxure Building Help Offline registration Instructions: 🔗 Offline Registration Guide 🔗 Registering Your System Offline Dialog Box

Issue An Engineering license obtained from Software Companion appears under the Demo license section in Workstation. This creates confusion about whether the license is behaving correctly or if it may impact system or configuration license validation.   Product Line EcoStruxure Building Operation Environment Building Operation 7.x Top server  Cause Both demo licenses and engineering licenses are currently tracked under the DemoLicense category. This is the expected behavior as confirmed by the product team. Resolution This behavior is expected and does not indicate a defect. To verify installed licenses: Check licensingmetadata to view installed licenses Demo licenses are listed under clientmetadata Engineering licenses are listed under servermetadata   The appearance of engineering licenses under the demo license icon does not impact system functionality or license validation.

Issue Direct bindings between Automation Server (AS-P) and Infinet (I2) controllers in EcoStruxure Building Operation (EBO) generate excessive Infinet traffic due to polling behavior. As the number of bound points increases, this can lead to network slowdowns and communication issues. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation AS-P (Automation Server) Infinet network I2 controllers Cause Direct bindings configured through the EBO binding window or reference tab rely on polling mechanisms. For certain data flows (such as I2 to AS-P and I2 to I2 on the same network), values are polled at the configured interval (default 10 seconds), increasing network traffic. These bindings do not utilize the Continuum Import/Export (IE) system, resulting in inefficient, polling-based communication rather than event-driven updates. Note that for data flow from the AS-P to the I2 device, a direct binding maybe used because the AS-P will ensure data will be transferred only when the value changes. When doing DIRECT bindings via the binding window in EBO to/from I2 devices here is a summary of how the transfer is done for the different data paths ASP to I2 (Irrespective of whether the value resides under the Infinet interface or not) The value is transferred only when it changes I2 to AS-P Value is polled per the binding interval I2 to i2 on same Infinet network Value is polled per the binding interval I2 to I2 on the second Infinet network of the parent AS-P The value is transferred only when it changes I2 on Infinet of AS-P to I2 on Infinet of second (remote) AS-P No support for Continuum IE system, value is transferred by AS-P only when it changes.  Resolution For data paths that result in polling, use script program-based bindings to transfer data between controllers. This approach leverages the Continuum Import/Export system, where values are transferred only when they change, eliminating continuous polling and significantly reducing Infinet traffic. For optimal performance: Use script programs for I2 to AS-P and I2 to I2 data transfers. For data paths that result in polling, direct bindings may be used for a small number of points where traffic impact is minimal. When using the Import/Export system via Scripts, for values that do not change frequently (such as occupancy schedules), implement a periodic refresh or forced export in the script program to ensure updates are re-transmitted in case for whatever reason an update failed to reach one or more devices. This approach ensures efficient, event-driven communication and helps maintain stable Infinet network performance.

Issue When attempting to upgrade TimescaleDB from version 2.27.0 to 2.28.0 (or 2.28.1) on PostgreSQL 18.0, the upgrade process fails with the following error: ERROR: could not load link library "C:/Program Files/PostgreSQL/18/lib/timscaledb-2.28.0.dll".The specified procedure could not be found. CONTEXT: SQL statement:"SET LOCAL search_path TO pg_catalog,pg_temp" link script file"timescaledb--2.27.0--2.28.0.sql",near line 6​ Product Line EcoStruxure Building Operation Environment External Log Storage using PostgreSQL v 18.0 Cause The failure occurs due to a binary incompatibility between PostgreSQL 18.0 and the TimescaleDB 2.28.x extension build. The extension was compiled against a newer PostgreSQL version, resulting in missing or incompatible library procedures when loaded on PostgreSQL 18.0. This leads to the “could not load link library” error during the upgrade. Resolution Upgrade PostgreSQL from version 18.0 to 18.4 to ensure compatibility with the TimescaleDB 2.28.x extension. PostgreSQL 18.4 includes the required library compatibility for the extension, allowing the upgrade process to complete successfully. Steps: Upgrade the PostgreSQL installation from version 18.0 to 18.4. Restart the PostgreSQL service after the upgrade. Re-run the TimescaleDB extension upgrade to version 2.28.x. Validation: Confirm the extension upgrade completes without errors. Check that External Log Storage is functioning and logs are being written correctly.

Issue External Log Storage in EcoStruxure Building Operation is not reporting a fully healthy state following restoration of connectivity. “Ready for reads” remains False after Enterprise Server restart, and synching-related counters remain high. Trend logs are visible and accessible in WorkStation, indicating partial functionality. Product Line EcoStruxure Building Operation Environment Enterprise Server with External Log Storage configured External Log Storage using Microsoft SQL Server External Log Storage using PostgreSQL Server Cause The observed behaviour is due to a large backlog of pending log writes that accumulated while the External Log Storage Server was unreachable. Resolution Following a period of database disconnection, a significant backlog of log data is expected to accumulate. Once connectivity is restored, the system gradually processes and writes this backlog, which may take an extended amount of time (hours or days) depending on the volume of accumulated data. The “Synching logs count” visible from System > Modules > LogStorageManager > ExternalStorage represents the number of pending log entries that have not yet been written to the database. Monitor the Synching logs count over time. If the value is decreasing, the system is operating correctly and progressing through the backlog. The status “Ready for reads = False” will persist until the backlog has been sufficiently processed and the Synching logs count is zero. 

Issue A large number of “Duplicate Network Identifier” alarms are generated when a BACnet network is shared between Schneider Electric and Third-party systems. Device discovery does not show duplicate device instance IDs or overlapping network IDs, and the alarms appear to originate from a BACnet gateway. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation ES / AS Site with Schneider Electric and Third-party managed BACnet networks Cause Packet analysis shows multiple devices responding to “Who-Is-Router-To-Network” with “I-Am-Router-To-Network” messages. This indicates that multiple devices are advertising the same BACnet network numbers at the network layer (NPDU). As a result, multiple routing paths to the same network are exposed, which is not permitted by the BACnet standard and leads to routing ambiguity and duplicate network identifier alarms. Resolution Identify all devices that respond with “I-Am-Router-To-Network” on the shared BACnet internetwork and reduce routing to a single designated gateway or router per network path. To identify devices broadcasting the duplicate network IDs Capture BACnet traffic (e.g. Wireshark) on the relevant network Apply display filter such as bacnet.npdu.network_layer_message == 0x00 || bacnet.npdu.network_layer_message == 0x01 Identify the trigger request Who-Is-Router-To-Network   Inspect all corresponding responses I-Am-Router-To-Network from multiple devices Compare the advertised network numbers (Network List) in each response If multiple devices advertise the same network number, this confirms duplicate network identifiers Align BACnet network configuration between Schneider Electric and Third-party systems to ensure that network numbers are unique and not advertised by multiple routers.

Issue Poor communication is experienced between an Automation Server Premium (AS-P) and Deep Sea Electronics (DSE) generator or switchgear Modbus RTU slave devices. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Deep Sea Electronics (DSE) Modbus RTU slave devices Cause When upgrading from an Automation Server (AS) to an Automation Server Premium (AS-P), Modbus communication performance may degrade. Communication that was stable with the AS may become unreliable or poor when using the AS-P. Resolution Ensure the AS-P is running version v3.2.3.8000 to improve Modbus RTU polling performance. If the issue persists, or if upgrading is not possible: Access the DSE Modbus slave configuration using the DSE software tool Locate the Inter-Frame delay parameter Change the value from 0 ms to 1 ms

Issue The Loytec NIC-852 interface remains offline after upgrading from EcoStruxure Building Operation (EBO) 3.2 to EBO 6.0 or later. The interface shows as offline within EBO Testing via the Loytec plugin indicates no issues System logs display the error: NSP.Pin.lon.orion OrionInit returned error code [1] Reverting back to EBO 3.2 restores normal operation, and the NIC-852 comes online without errors Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Loytec NIC-852 Loytec software Cause   The Loytec NIC-852 driver is outdated and not compatible with EBO 6.0 and later versions.   Resolution   Update the Loytec NIC-852 driver: Download the latest driver from the Loytec website: https://www.loytec.com/support/download?view=docman/NIC852-SW Create and log in to a Loytec user account to access the download Install the updated driver for the NIC-852 Once updated, the NIC-852 will come online in EBO 6.0 and later versions