Building Automation Knowledge Base

Issue The F3 Search function in EcoStruxure Building Operation (EBO) WorkStation does not return results for Notification File objects (e.g., .xlsx, .pdf, .txt), even when using wildcards.     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WorkStation Search Cause This behavior is functioning as designed (FAD). Notification files generated using the "Write to File" option are not stored in the EBO database. Therefore, they are not indexed and cannot be retrieved using the F3 search function. Resolution Although these files are not searchable within EBO, they are saved locally in a fixed directory: ...\db\notifications To assist users in locating these files:  Create a Hyperlink Object in EBO that points to the above folder. Users can then open the folder directly within WorkStation and use the operating system’s search functionality to locate specific files. Note: The notification file path is not configurable. For more information, refer to the official documentation in WebHelp: Accessing a Notification Written to a File

Issue What is the password policy for Security Expert operators, and how can it be configured to meet specific cybersecurity requirements? Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Client Cause Some sites require customized password policies to comply with cybersecurity standards. These may include requirements such as: Enforcing regular password changes Preventing the reuse of previous passwords Setting minimum password length Requiring strong password complexity Resolution   Default Password Policy in Security Expert By default, Security Expert enforces the following password policy for operator accounts: Minimum password length: 8 characters Password change required: On first login For more information on Security Expert’s cybersecurity practices, refer to the SX-SRVR Security Expert System Hardening Reference Guide. Custom Password Policies via Active Directory Integration Security Expert does not support advanced password policy configuration directly within the client interface. However, enhanced password policies can be enforced by integrating Security Expert with Windows Active Directory. To implement this: Integrate Security Expert with Active Directory Follow the steps outlined in Option 1 of the How to Integrate Active Directory with Security Expert article or Option 2 for full Active Directory integration. See AN 288 Security Expert - Using Active Directory - Integration Guide for additional details. Configure Password Policies in Windows Domain Once integration is complete, operator accounts managed through Active Directory will adhere to the domain’s password policy. This allows you to enforce: Password expiration intervals Password history restrictions Minimum and maximum password lengths Complexity requirements (uppercase, lowercase, numbers, symbols)

Issue Confusion about the current release version of Security Expert and the limited release Security Expert for the Enterprise Download Service. Product Line EcoStruxure Security Expert Environment Security Expert Enterprise Download Service Cause Two parallel development branches now exist for Security Expert: Maintenance Builds –  version 4.3.370.15 (Released 2025-May-01 - latest stable release) Limited Release Builds –  version 4.3.386.2, intended for use with the new Enterprise Download Service. This has led to confusion because: The limited release version (4.3.386.2) has a higher version number than the current maintenance release (4.3.370.15).  The Supported Software 2025 landing page does not host the actual installation files for the limited release. Instead, it now provides a ZIP file containing instructions and a request form. Initially, version 4.3.386.2 was directly downloadable, but it has since been replaced with the ZIP package. Resolution To Access the Current Maintenance Release Visit the EcoStruxure™ Security Expert – Software and Firmware page on the Extranet. Sort the list by date to find the most recent maintenance version (currently 4.3.370.15 Released 2025-May-01).   To Access the Limited Release (Enterprise Download Service) Go to the Supported Software 2025 landing page. Select either: “2025 Enterprise Download Service (VM Bundles)”, or “Client/Server Security Expert - v.4.3.386.2”. Both links download the same ZIP file, which includes: Instructions for requesting the limited release. A site evaluation form that must be submitted  to TeamVipers@se.com who will review and provide the installation files.   If You Need to Roll Back from 4.3.386.2 to 4.3.370.15 Due to database version incompatibility, rolling back requires the following steps: Backup the current SecurityExpert and SecurityExpertEvents databases. Record the site’s license SSN. Uninstall the current Security Expert version. Important: Any configuration or event data added after the backup will be lost and must be manually re-applied. Restore the database backups from version 4.3.370.15 or earlier. Install the maintenance version (4.3.370.15).

Issue After an upgrade the SP-C-WEB is showing "NOT REGISTERED" with the option to register the controller. Attempts to register the controller fail as it is already registered. SP-C-WEB not registered When attempting to create new records their is a "License Limit Reached" message displayed and the new records are unable to be created. SP-C-WEB license limit reached Product Line EcoStruxure Security Expert Environment SP-C-WEB Cause Browser has cached settings for this controller that are interfering.  Resolution Use browser incognito mode and/or clear the browser cookies and cache.

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. 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 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 MUST BE EBO 3.1 or higher which includes ClientAPI support 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 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

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. Issue Data cannot be seen on Partner Portal for RS485 devices. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Data for the Modbus devices can be seen on third-party tools like Modscan but not on the Partner Portal. Resolution Follow the steps below if the Flex Server RS485 port is not sending any data: Ensure connections are made according to the installation instructions. Verify the correct port is configured. Double-check that the connections are not reversed. Inspect for any loose wires. Confirm the Modbus/BACnet ID is correct. Verify the baud rate configured for the end device. Check for any loose wire strands shorting on the bus or to the ground. Ensure no Modbus device is connected to the BACnet bus, or vice-versa. Confirm the number of devices in the loop matches the specifications in the installation instructions. Check if the loading of devices causes significant changes in resistance. Do not connect more than two resistors on a single bus. Ensure cables used are as per the specifications in the installation instructions.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. Issue The internet is not working at the site, so it's necessary to verify that all antenna connections are secure and the SIM card is correctly placed. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The Flex Server powers up successfully at the site, but the internet connection fails. This issue might arise if the antenna or SIM card was displaced, disconnected, or damaged during transit due to mishandling. Therefore, it's essential to verify that all connections are secure. However, the technician or engineer on-site may not be familiar with the correct slots. Resolution Carefully open the Flex Server top cover. The internal layout will appear as shown in 'Image 01' below: Image 01 Image 02 Identify the slots as follows: Slot 1: Indicates the SIM card slot. Slot 2: Located on the Compute Module marked as 'MAIN', indicates the Cellular antenna slot. Slot 3: Located on the Wi-Fi module marked as 'ANT0 WiFi', indicates the Wi-Fi antenna slot. Verify all connections and ensure they are secure. Carefully close the Flex Server cover.

Issue Can the EasyLogic range of controllers & RP-IO Modules work under Building Operation 3.2 as BACnet MS/TP third-party devices  Product Line EcoStruxure Building Operation Environment EasyLogic Controllers, EasyLogic RP-V, EasyLogic RP-C, EasyLogic MP-C EasyLogic RP-IO SpaceLogic Advanced, Pro, and Pro Plus Controllers that support native BACnet MS/TP (via a SpaceLogic RS-485 Adapters.   Standalone BACnet field controller Cause The documentation states that EasyLogic Controllers can be used as a Native BACnet MS/TP device. These devices must be configured using their respective supported Building Operation versions, such as Building Operation 2022 and above. However, there are no guidelines on whether they can be used as a third-party BACnet device, particularly in earlier versions such as Building Operation 3.2.    Resolution EasyLogic controllers can be used as BACnet MS/TP third-party devices in Building Operation 3.2 since the EasyLogic range of RP and MP controllers, and RP-IO I/O modules, natively communicate using the BACnet MS/TP protocol.  This same concept applies when using the devices as true 3rd-party devices (e.g., with Continuum and I/A systems) when older controllers fail, and these EasyLogic controllers are used as temporary replacements before a complete transition.   What MUST be understood before taking this approach is that there is no automatic conversion when migrating the site (and devices) to later Building Operation versions that support these devices natively. After the upgrade, the controller must be deleted from the database and hosted as a native EBO controller.   During this process, some programming may be lost. This risk may be mitigated by creating Custom Types for the application once engineered in Building Operation 2022 (or higher) to future-proof the site for upgrades.  Using the latest firmware for the EasyLogic range of devices is also recommended.     Furthermore, the SpaceLogic Controller Range that supports native BACnet MS/TP (via an RS-485 Adapters) can be configured in the same fashion as described for the EasyLogic range.   Refer to Hardware Overview for further details on each product line. 

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

Issue This issue is described in Tridium's internal case NCCB-71360. Users will notice that the default Nrio Device Manager view (Ux/web media) of the NrioNetwork driver in N4.14 looks identical to the previously existing workbench AX view; however, due to this defect, devices discovered and added through the web view will not function as expected.  Product Line TAC IA Series Environment I/A Series N4 Jace 9000 I/A Series N4.14 Framework Version Cause With the release of the Jace 9000, users may notice that the IO-R-16 and IO-R-34 devices will not function properly when discovery and configuration are performed through the web views. Resolution To tell if the device was added through the correct view, there are a few indicators. Malfunctioning devices will not show up with an Installed Version or a Sec version in either view: Working devices will display these values with no issue in either view: The malfunctioning devices' health section will read 'fail' even with a status of ok: Users in N4.14 should only use the Workbench AX Nrio Device Manager view to discover and add devices to a station. This use case is currently not supported in the browser for N4.14. All other use cases function in the UX Web Views, such as viewing devices, adding points, and commanding points.  

  Issue This document gives guidelines on the device constraints that effect the system capabilities or the system limitations of the Flex Server.  Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Understanding this document helps in efficiently designing architecture and Single line Diagrams. Identifying potential bottlenecks in a system allows for preemptive action. If you know a system parameter has limited device capacity, you can optimize the distribution methods or plan for upgrades before it becomes a critical issue. Understanding the limitations of system allows for the implementation of backup measures. Resolution Thes guidelines provide the recommended Flex Server design limits for common applications. These are the configurations that have been tested and supported by Schneider Electric. Environmental factors such as network traffic and radio interference may reduce the stated limits of these guidelines. Deviations from these guidelines may result in performance related issues or product failures.   Flex Server Capacity Parameter Maximum Number Number of total devices (all protocols combined) 50 Number of controlled points (all protocols combined) 500   BACnet Parameter Maximum Number Number of BACnet MSTP devices per RS485 port 32 a b e Number of BACnet MSTP networks per server 2 c Number of BACnet IP devices 50 d e   a. Maximum number of devices according to protocol specifications and guidelines. b. BACnet MS/TP adheres to RS485 rules for wiring, wire type, termination etc. c. There is one onboard RS485 port, an additional port can be added via USB. d. BACnet IP uses default UDP port 47808 (0xBAC0). e. The total number of devices across all protocols must not exceed 50   Modbus Parameter Maximum Number Number of Modbus RTU devices per RS485 port 32 a b e Number of Modbus RTU networks per server 2 c Number of Modbus TCP devices 50 d e   a. Maximum number of devices according to protocol specifications and guidelines. b. Modbus RTU adheres to RS485 rules for wiring, wire type, termination etc. c. There is one onboard RS485 port, an additional port can be added via USB. d. Modbus TCP uses default TCP port 502. e. The total number of devices across all protocols must not exceed 50   LoRa a Parameter Maximum Number Number of LoRa sensors per server 32 b c d Maximum number of messages per day (per server) 100   a. LoRa distances – LoRa is noted for its long range and deep penetration. LoRa transmissions can penetrate glass, metal and concrete found in most buildings. The radio’s antenna and installation can affect the range of LoRa sensors. You must test the transmission and signal strength, when installing wireless devices. b. Maximum number of devices according to protocol specifications and guidelines. c. Every LoRaWAN sensor manufacturer has their own decoder. d. The total number of devices across all protocols must not exceed 50   SNMP Parameter Maximum Number Number of SNMP devices 10 a Maximum number of messages per day (per server) 1024   a. The total number of devices across all protocols must not exceed 50   Object Limits Object Type Maximum Number Analog values 500 a Digital values 500 a Multi-state values 500 a Analog Input 500 a Multi-state input 500 a Analog output 500 a Digital output 500 a Multi-state output 500 a   a. The total number of combined points must not exceed 500

Issue After correctly following the process outlined in Setup External Log Storage using MSSQL., EcoStruxure Building Operation (EBO) server fails to connect to the external database, generating the following System Alarms:  Unable to connect to data source Login failed for user The system alarm specifically details an issue with the ODBC SQL Driver as below: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium (AS-P) External Log Storage [MSSQL]  Cause The system alarm details indicate an issue with the ODBC SQL Driver, specifically: "The driver doesn't support the version of ODBC behavior that the application requested..." "Invalid connection string attribute" This suggests a compatibility or configuration issue with the ODBC driver or connection string.   Resolution The following has been seen to correct the issue: Verify User Credentials Ensure that the username and password used for the ODBC connection are correct. Note: SQL Server credentials are case-sensitive, so double-check for any discrepancies in letter casing. Remove any uppercase for the username. In some cases, using only lowercase letters for the username in the ODBC connection string has resolved the issue, e.g,. Instead of "My_User" use "myuser"

Issue Cannot activate a license on an Automation Server although the entitlement works on other Automation Servers. The Device Administrator output is similar to the following:   Activate failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information: FNO server response: =V(BACK_OFFICE%DEBACK_OFFICE+]\fK%MDEVICEID|0}~;DEVICEID/jlSk\}K qq7!vi%DCH'~A%05pQWN]G|3^Jk+yaz_Kx/:Dy&w F7BWWN#`Ex|6S.d<Y^nV~@?*C.D0])"KO?[pS#GH|aMe+i|@4's9kNE\7gfocfVbRf$1VuH>sdp_JN6%4B.n|Zm$]wi9M|F8#Hrw~/L4%XU<?8o="P1S$uW6Fu5vAsAz|l>8.@XA|.'[v_ekh_P}c7 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause When an Automation Server fails in the field an RMA (Return Material Authorization) request is made, and the license is returned for re-use in the replacement Automation Server. Once this occurs the serial number of the faulty Automation Server is blacklisted to ensure that it cannot be licensed and reused. Resolution If the device was mistakenly added to the blacklist please supply the Automation Server serial number to Support. If an RMA number does not exist in the licensing system for this Automation Server, the support team can make a request to have the server removed from the blacklist.

Issue How to collect log files from the Project Configuration tool 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the PCT, log files should be provided. Resolution Collect log files through the Web interface on both Windows and Ubuntu installations: Logon to PCT server, Click Diagnostic  Click Collect logs Log starts collecting. After the log collection process is complete, the file will either be saved to the browser's default download location or a window will pop up asking where to save the ZIP file. Select the desired location then click Save   Log collector tool for PCT for Ubuntu: If the PCT web interface is unavailable, you can use the Log Collector tool to gather log files. This tool is included with the PCT installation on Ubuntu, eg. pct-2.1.1.8-log-collector-ubuntu. Give the file proper permission to be able to run as an executable either using chmod command:  chmod +x pct-2.1.1.8-log-collector-ubuntu​ or via file properties, as shown in below screenshot: Run the log collector tool. ./pct-2.1.1.8-log-collector-ubuntu​ A zip file containing the required log files will be saved in the same folder where the log collector tool is located.

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. Issue How are Elsys LoRaWAN sensors configured with a smartphone using NFC Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause All Elsys sensors are equipped with NFC for easy configuration with a smartphone. There is a requirement to configure these sensors using a Smartphone or tablet using Elsys 'Sensor Settings' application. Resolution Download the ELSYS “Sensor Settings” application from Google Play or the IOS App store and install it on a smartphone or tablet.     Ensure the mobile device supports NFC. Enable NFC on the device and start the application. Position the mobile device directly on the NFC antenna of the sensor. Ensure both devices remain close and stationary to maintain optimal connectivity. Remove the mobile device. The current settings will be displayed in the application. Set the 'Timebase' to 120 seconds using the application. Remember to revert it to 600 seconds after commissioning!    Make note of the following sensor keys: DevEUI: The unique ID of the sensor, found in the blue panel at the top. AppEUI: Application ID (8 bytes or 16 hex digits). Default is 0, can be changed if needed for the application. AppKey: Application unique key (16 bytes or 32 hex digits) that is the encryption key used for messages during every over-the-air activation. Tap the sensor's NFC antenna to transfer the new settings after making the desired changes. Ensure the application confirms the updated settings. Wait for the sensor to reboot, indicated by the LED flashing. The sensor settings should now be updated. Validate your settings by reading the NFC data after the sensor has restarted. Verify that settings have been applied by using the ‘Read’ functionality in the app and touching the sensor’s NFC antenna.    Remember to change the 'Timebase' back to 600 seconds after the commissioning is completed!

Issue How can EcoStruxure BMS server serve data to external devices or software? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Third party devices or software Cause The EcoStruxure Building Operation software supports the major communication protocols in building automation and security management. In many projects, it is required that an EcoStruxure BMS server serve data to external devices or software, E.X. HMI, SCADA or power monitoring. Resolution The following is a summary of the available options to serve EcoStruxure BMS server data to the external world: BACnet:  When you create a BACnet Interface, the system automatically creates the Application and IP network folders within the BACnet Interface folder on the System Tree. If you create a BACnet Interface for a SmartX server, you can optionally create an MS/TP network. You can create BACnet objects in BACnet application folder of EcoStruxure BMS servers and these object will be visible for external BACnet clients. More information about EBO BACnet interface: BACnet Interface   Modbus Slave network:  If you configure the Modbus Slave Network (and associate it with a serial port), you can set up any external Modbus master device to communicate with the internal Modbus Interface. In this example, a Modbus Slave Network is set up on an EcoStruxure BMS Server and the external master device is configured with the same Modbus properties as the Modbus Slave Network object. The Modbus master device can also be an HMI device. More information about Modbus serial interface: Modbus Serial Networks Modbus server network: You can create a Modbus TCP Network on an Ethernet network (TCP/IP).  You can create an internal interface which acts as the server to an external client/clients. More information about Modbus TCP interface: Client and Server Networks   MQTT: MQTT is a lightweight and flexible data transfer protocol for IoT resources. EcoStruxure Building Operation, V3.2 or higher, can be configured to send data to an MQTT broker on interval or event-driven. The below are the tested brokers: Microsoft Azure IoT Hub Amazon IoT Core IBM Watson IoT Mosquitto More information about MQTT interface: MQTT Overview LonWorks Interface: EcoStruxure BMS servers can have a local node on their networks that can act as a LonWorks node. In the local node, you can create your own NVs that can be bound to external LonWorks devices using LonWorks bindings. The NVs in your local node can then be used in EcoStruxure Building Operation bindings for applications and graphics. More information about LonWorks interface: LonWorks Engineering   SNMP: Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. The EcoStruxure BMS servers support SNMP version 3. The SmartX servers support several SNMP traps. SNMP traps enable an agent to notify the management station of significant events by way of an unsolicited SNMP message. More information about SNMP: SNMP EcoStruxure Web Service (EWS) server: EcoStruxure Web Services allows seamless sharing of operational data, including alarms and historical information, between software from different Schneider Electric Business Units. When the EcoStruxure BMS server is an EcoStruxure Web Service server, it exposes objects, such as values, to another EcoStruxure system that is an EcoStruxure Web Service client. The EcoStruxure Web Service client can read and change values on the EcoStruxure BMS depending on the configuration of the EcoStruxure BMS server. More information about EBO EWS Server: EcoStruxure Web Service Server Smart Connector: A development framework that simplifies and accelerates integrations with third-party systems or other data sources. It is an open, extensible and configurable application framework that allows developers to create innovative new capabilities, applications, and solutions which extend and enhance EcoStruxure Building solutions. Ex. SmartConnector can be used to serve EBO data in a RESTful manner, refer to: Configure SmartConnector RESTful EWS Gateway to serve EBO data   For further information watch the Smart Connector explainer video or visit the Smart Connector Developer Community on the Exchange: For developers wanting to get started using the Smart Connector framework visit: https://www.smartconnectorserver.com Smart Connector at Exchange:  EcoStruxure Building Operations SmartConnector 

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

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. Caution While removing gateway cover: Open the gateway screws and delicately remove the top cover. Take extra care during this step, as the top cover is connected to the antenna cable via a thin wire. After opening the top cover, you will be able to see the top view of the board, please insert the active SIM card in the designated slot. Once the Sim Card is properly inserted, fix the screws back and ensure that the 4G&Wi-Fi Antenna is attached properly. If the antenna cable remains disconnected from the board, then the GSM will not work.   Important Note: The SIM must not have a Username, Password, or PIN. These features are not supported. Refer to Steps to follow to unlock SIM PIN when using SIM Card under Flex server The user must ensure that no firewall is applied by the SIM provider. If a firewall exists, it may block connectivity. We recommend using SIMs without any firewall restrictions. Ensure the data plan of the SIM should not be less than 2GB per month for approximately 100-200 streams. Issue This article provides information on the SIM cards that are currently supported in EcoStruxure Building Activate and are added to the central database to support field deployment of Flex servers. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause This eliminates the need for manual support for the already validated SIM operators individually on each server. Resolution Below is the list of the Network Service Providers whose APN exists in the backend and have already been added: MCC code (Country Code) Operator APN 260 play {"generic": "internet"} 260 plus {"generic": "mbb.mobi-data.com"} 732 claro {"generic": "internet.comcel.com.co"} 454 smc hk {"generic": "Smartone"} 520 ais {"generic": "internet"} 240 tele2 se {"generic": "mbb.mobi-data.com"} 260 t-mobile {"generic": "internet"} 262 t-mobile {"generic": "internet.v6.telekom"} 505 telstra {"generic": "telstra.internet"} 204 nl kpn {"generic": "matooma.m2m"} 208 208 28 {"generic": "datapro"} 234 voda uk {"generic": "wap.vodafone.co.uk"} 901 901 40 {"generic": "internet.m2mportal.de"} 208 free {"generic": "free"} 208 bouygues telecom {"generic": "mmsbouygtel.com"} 208 sfr {"generic": "sl2sfr"} 208 orange {"generic": "orange"} 268 vodafone {"generic": "internet.vodafone.pt"} 268 nos {"generic": "umts"} 405 vi india {"iot": "IOT.ZENATIX.COM"} 404 vi india {"iot": "IOT.ZENATIX.COM"} 405 ind airtel {"iot": "iot.com"} 404 ind airtel {"iot": "iot.com"} 724 tim internet {"generic": "timbrasil.br"} 724 vivo {"iot": "smart.m2m.vivo.com.br", "generic": "zap.vivo.com.br"} 724 claro {"generic": "claro.com.br"} 310 at&t {"iot": "armstrongdynm.com.attz", "generic": "NXTGENPHONE"} 440 fl1 {"generic": "soracom.io"} 302 bell {"generic": "mnet.bell.ca.ioe"} 302 rogers {"generic": "M2Minternet.apn"} 302 at&t {"iot": "armstrongdynm.com.attz", "generic": "NXTGENPHONE"} 404 idea {"generic": "Internet"} 431 etisalat {"generic": "mnet"} 430 etisalat {"generic": "mnet"} 424 etisalat {"generic": "mnet"} 424 du {"generic": "du"} 405 404 11 {"iot": "IOT.ZENATIX.COM"} 405 vodafone {"iot": "IOT.ZENATIX.COM"} 405 airtel {"iot": "iot.com"} 404 airtel {"iot": "iot.com"} 404 vodafone {"iot": "IOT.ZENATIX.COM"} 404 404 11 {"iot": "IOT.ZENATIX.COM"} 404 jio {"generic": "jionet"} 405 jio {"generic": "jionet"} Additional Information Ensure the SIM card is active and properly inserted. Verify the antenna cable is securely connected to the board. Confirm the SIM card has no firewall restrictions and meets the data plan requirements.  

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. 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. Caution While removing gateway cover: Open the gateway screws and delicately remove the top cover. Take extra care during this step, as the top cover is connected to the antenna cable via a thin wire. After opening the top cover, you will be able to see the top view of the board, please insert the active SIM card in the designated slot. Once the Sim Card is properly inserted, fix the screws back and ensure that the 4G&Wi-Fi Antenna is attached properly. If the antenna cable remains disconnected from the board, then the GSM will not work. Issue SIM card not being detected and internet is not connecting automatically when SIM card is inserted inside the Gateway.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Some network service providers have a username, password and SIM PIN set by default when they issue the SIM to the customer. If the Gateway is using the SIM for internet, it requires any username, password and SIM PIN to be disabled before inserting the SIM inside the Gateway.  Resolution Contact the Network service provider directly to disable the username and password. The Network service provider can disable the username and password from the backend. For disabling the SIM PIN follow the below procedure: Steps to follow to unlock SIM PIN An example YouTube video on the steps detailed below can be seen at: How to unlock your SIM Card Upon receiving the SIM kit (note down the PUK number and also note down the SIM PIN if available) Insert the SIM card to a Mobile device/cellular device Type in the SIM PIN from the Step 1 and Unlock the SIM Navigate to the settings page – Network section - SIM settings - SIM PIN - Disable the SIM PIN option SIM CARD SETTINGS           SIM PIN DISABLED Reconfirm if the SIM PIN is disabled by reinserting the SIM from the SIM tray and check if it asks for PIN. If the SIM PIN is successfully disabled, it will not ask for SIM PIN at startup. If it still asks, repeat Step 4. Insert the SIM inside the Gateway SIM Slot and check for network connectivity and that the gateway goes online. After inserting the SIM card properly, power up the gateway and allow the gateway to boot up. This process may take up to 5 minutes. Once completed, the device should come online and can be provisioned through a partner portal   In case the SIM PIN is unavailable An example YouTube video on the steps detailed below can be seen at: How to Unlock Sim Card / Sim locked by Pin Code or PUK Code  Insert the SIM card into a Mobile device/cellular device Type in incorrect PIN more than 4 times till it asks to enter PUK code. Contact the Network Service Provider and perform the verification and obtain the PUK Code for the SIM from the Network provider directly Type the PUK code into the mobile device in the PUK code page Navigate to the Network settings - SIM PIN - Set a SIM PIN inside the settings Use this SIM PIN to Disable the SIM PIN lock. Reconfirm that the SIM PIN is disabled by reinserting the SIM from the SIM tray and check that it does not request a PIN.

Issue The "Change set error" occurs after trying to save a LonWorks network variable binding in SmartStruxure. Product Line> EcoStruxure Building Operation Environment Workstation LonWorks Network Cause The LonWorks bindings have become corrupt and need to be rebuilt. Resolution Rebuild LonWorks Bindings Right click on the LonWorks Network. Go to Advanced > Rebuild LonWorks Bindings. Select Yes.