Building Automation Knowledge Base

Issue How do you define the number of decimal places displayed for a point? Is it possible to change the number of decimals displayed in WorkStation / WebStation? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation  Cause The operating system's regional settings determine the default resolution for decimal places displayed. This value cannot be modified within WorkStation; however, the regional settings in WebStation can be adjusted to show the desired number of decimal places. Resolution This setting applies to all displayed values except graphics, where the graphic editor can define the number of digits displayed.   WorkStation Open Control Panel Select under Clock and Region - Change date, time, or number formats As shown in the screenshot below, select Additional Settings [1]  Then adjust the Customize Format "No. of digits after decimal to your requirements" [2]. Restart WorkStation if already opened. WebStation  From the User Account drop down Select Settings Select Regional Change the Decimals from Auto to the desired number (0-6) required in WebStation.  Click Save Log off/on to WebStation to see these changes.   

Issue How are user profiles (accounts) configured in Esmi Ultima Fire Panels? Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. FFSULH1005. Cause Access levels allow permissions to be assigned to different user types. Resolution User Accounts Maximum Accounts: Up to 63 user accounts can be created. Permissions: Access group or singular permissions as set out within each user group. Profile Configuration User Levels: The example above shows User Level 2 in Group 1. Group numbers increase as more groups are added. Session Timeout: Range from 1 to 255 seconds for the function button availability after login. Function Buttons: Selected according to users who need access to the group. Panel Permissions: Additional permissions can be set in the User Menu Options section. Event Log: Records individual user activity. User Profile Example Username: Up to 20 characters. Passcode: Should contain 5 or 6 numerical characters. User Level: Mike Allerton is the 4th user, placed in User Level 3. User options Panel Control Interface: User activates the interface and enters their passcode to unlock screen and panel permissions. Function Option Button: Provides access to the buttons as described earlier.

  Issue How to program the function buttons in Esmi Fire Panel Product Line ESMI Fire Detection Environment FFSULH1001. FFSULH1002. FFSULH1003. FFSULH1005. Cause Customer wants the specific buttons for specific actions. Resolution Up to 24 customer specific, on-screen function buttons may be configured to provide control, disablement and engineering functions. The function buttons can be configured to be either available or hidden for each log-in profile. The following procedure describes how to: Set function button attributes/properties. Allocate function buttons to user groups.  Create password specific user accounts for inclusion within a nominated user group. Setting attributes Function buttons (inputs) may be set to operate by association to output devices with the same properties e.g. a security input will activate any device that has security ticked as part its output properties, or as part of a cause-and-effect rule where the function button is the “Cause”.   With Loop Explorer open, select the Configure menu button and select System Manager to open the function button configuration page. Select the 'Details' button to open the properties section of the function button that you wish to configure. Note: Input Properties The properties page allows the user to configure the input action and associated messages, to set individual colours and either to work as a latched (cleared on user interface reset) or toggled action (press function button to operate and again to turn off). Mapping to zones is optional, and the location text is the name given to the function button when completed. Feature Groups There are 4 default user groups that can be configured with specific permissions for different users.     When configured, the function buttons will be included as selectable options in each of the feature groups. It should be noted that if a function button is allocated to the Logged-out group, then it will be present alongside the User Options button when all other user groups have been logged out. Note that at this level then the user options are limited to system information and basic panel tests such as display colour and LED function. Function buttons allocated to User level 2 and 3 may be accessed using the default login codes. If users are to be allocated unique numerical codes, then it would be advisable to change the panel default level 2 and/or 3 codes where required.

Issue Attempting to update the System Identifier to align with the newly created ID in the EBO system, is causing a 'Duplicate BMS System Data Source' error. Product Line EcoStruxure Building Advisor Environment Building Advisor Cause A duplicate ID has been identified in Building Advisor. This may correspond to an older system ID or one from a different site.   Resolution The error indicates the site where the duplicate ID is found, which usually corresponds to the site you are attempting to update. - Go to the admin menu, select the site, then choose 'Clear' on the BMS System and click 'Save'. - Click the pencil icon to add or edit the BMS System. Enter the new ID and then click 'Save'.    

Issue EcoStruxure Building Activate Flex Server fails the Wi-Fi Signal Strength test.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause If the Flex Server Gateway is configured on Wi-Fi, it must achieve a RSSI value greater than -75 or value does not go below -80 more than 3 times. If these conditions are not met, Gateway will fail the test.   Resolution Below steps should be checked/followed to check the issue: Check Network Type: Ignore this issue if gateway is using a GSM network Verify Wi-Fi Receiver: Ensure the Wi-fi receiver is properly inserted into the USB port of the gateway Optimize Placement: Make sure the Gateway is near or in line of sight with the router to improve signal strength. Restart Router: Restart the router and check with your network provider for any issues.

  Issue EcoStruxure Building Activate Flex Server doesn't pass the GSM Signal Strength test.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The Flex Server must achieve a GSM Signal Strength greater than 14 to pass the test. If the signal strength is less than 14, the test will fail.   Resolution Below are the troubleshooting steps which should be checked/followed: Ensure the Gateway is located in an area with good network coverage. If possible, reposition the Gateway to improve signal strength. Verify that the APN settings for the SIM card in the Device Management Dashboard are correct. Change the network carrier and reconfigure the APN again

Issue In Andover Continuum, the model name of a field device (i2/b3) is always obtained from the SQL database as there is no direct way to retrieve the model directly from the controller. Consequently, discrepancies between the model stored in the SQL database and the actual controller may lead to uprev errors like "This Uprev file does not match this type of controller"     In the screenshot above, note that both the device's editor as well as the command line, report the controller's model as i2800, when in fact the hardware associated with the device is an i2920.   Note: In EcoStruxure Building Operations, where a distributed database design is employed, the device's model type is always obtained from the proxy representing the device in the Automation Server. Product Line Andover Continuum Environment All i2s All b3s Cause Frequent model mismatches for i2/b3 devices in Continuum installations often result in errors when attempting to upgrade the device's firmware. Resolution To obtain the device's model (controller type) from the Continuum controller hosting the device follow the steps below: In the master controller, create an InfinityNumeric, in this example we will name it 'DevModel' In the master controller, create an InfinityProgram, in this example we will name it 'GetDeviceModel' Enter the following lines of code in the program... DevModel = <device_name> CntrlType Stop ***Replace <device_name> with your i2/b3 device's name   Note in the screen capture above, that the program reports the actual device's model to be i2920. The mismatch needs to be corrected by either installing the correct hardware or adjusting the model in the device editor in Cyberstation to align with the hardware.   IMPORTANT If the program reports the model as 0 (zero) it means the proxy representing the device in the master controller has lost the model number, you will need to reload the whole master controller to recover, make sure to select the option to reload the controller but NOT its children.

  Issue The LEDs on the Flex server indicate the status of the gateway's connection with the Internet and server. This document contains the details that will help in understanding the gateway status.   Product Line EcoStruxure Building Activate Environment ESXBFXSVR00B008 ESXBFXSVR0BC008 ESXBFXSVRBCW008 Cause The behavior of top LEDs and Bottom LEDs are different in terms of troubleshooting and understanding the Flex server state. Resolution The LED blink patterns are indicators used to check the status of the internet connection, server connection, SD card health, gateway firmware health, device connection, and data transfer. Fig 1: Side View of the Flex-Server showing LED location     Fig 2: Gateway Status LED indication   Fig 3: Network Status LED   Fig 4: Ethernet Status LED   Fig 4: Power LED indications            

  Issue While performing the verification tests, an error is displayed: 'error: There is no change in the configurations' as shown below:   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Partner Portal Cause This error occurs under the following conditions: The user made changes in the Partner Portal but later reverted to the original settings/configuration, assuming there should be some changes, and then started the verification tests again. The user chose to perform the test and verification process once post-submission, resulting in this error message. Resolution When the verification process is initiated, it goes through four checkpoints. The user can safely ignore this error message and proceed with the tests directly. Clicking on the 'Load Mapping' button will remove this error message.

Issue In earlier SLP firmware the sensor displayed the CO2 with yellow and red as shown below:                               However new sensors display CO2 differently.   Is it possible to go back to the old look?   Product Line Field Devices Environment SLP Sensor Cause When launched, the SLA/SLP PM series sensor firmware was updated to display stoplight indicators (red, green, yellow) over the CO2 and PM values. In previous firmware, the stoplight function only applied to CO2 and the full screen showed red, green or yellow, but current firmware highlights the individual CO2 or PM value in the appropriate color. Resolution Firmware of this offer is not field upgradable; it is not possible to revert to the previous functionality.  

Issue Extended Jace 9000 Commissioning Time. Product Line TAC IA Series Environment I/A Series Jace 9000 Cause With the release of the Jace 9000 using Ubuntu Core 20 Linux as it’s operating system the commissioning/upgrade times increase as compared to the previous Jace 8000. Initial commissioning times can take longer then 15 minutes to finish. There are scenarios where multiple reboots are needed after the initial commissioning is completed. Once the commissioning has been completed for the Jace 9000, boot times should be significantly lower. Resolution Users will need to reboot their Jace at least twice and will need to set more time aside for commissioning of the new Jace 9000s. Please allow for a minimum of 15 minutes for commissioning. If you continue to experience issues with bootup or commissioning on the Jace 9000,  please contact your country level product support. Please note that the JACE-9000 does not print a lot of output on the debug port when you cycle power so give it time to fully bootup.

Issue Incorrect Default Gateway setting may prevent communication with the JACE-9000 Product Line TAC IA Series Environment I/A Series Jace 8000/9000 Cause The Jace8000 and Jace9000 both have primary and secondary LAN adapters. Previously, Workbench prevented users from some invalid IP configurations, but current versions of Workbench, when connecting to a 9000 will allow invalid configuration in the default gateway. Resolution In the 9000, a user can set different default gateways for the Primary (en0) and Secondary (en1) ports. This should not be allowed on a single network device, and leads to unpredictable behavior when routing. Compare the location of the IPv4 Default Gateway in the TCP/IP Configuration of the Platform on a 9000:      And the same page as seen in the 8000: In future versions, this will be changed, but users should avoid invalid configurations in the affected versions. When configuring both LAN ports for use on a 9000, only enter a value for the default gateway field in one adapter. Leave the other intentionally blank. It does not matter which is given a default gateway and which is left blank. Note: Sometimes, when an Adapter has the Default Gateway, you cannot connect to the other Adapter (despite correctly being on that Adapter's local subnet). These symptoms can be triggered by the Ethernet "link" (active connection) toggling up or down.  The link state can change whenever: the JACE is rebooted or power-cycled; and/or the Ethernet switch ("hub")  is rebooted or power-cycled; and/or the Ethernet cable(s) are un- or re-plugged (at either end). In some cases, the symptoms can alleviated by toggling the Ethernet link state, in the ways listed above.

Issue Are stainless steel pockets suitable for use in seawater/saltwater applications? Product Line Field Devices. Environment STR Sensor. Cause Customer asking if stainless steel pockets are suitable for use in seawater/saltwater applications. Please note that the answer would need to cover both static (stationary) water and flowing water in the pipe, because seawater/saltwater has different effects on metals depending on whether it is moving or not. Resolution Highest corrosion class is Class III for stainless steel, which seems not suitable for intended application.   ISO 12944 Impact Interior Exterior C1 Very low Heated buildings with clean air, such as offices, shops, schools, hotels, etc. None C2 Low Buildings not heated, where condensation may occur, such as warehouses and sports halls. Atmosphere with low pollution. For example in the country. C3 Middle Buildings for production with high atmospheric humidity and some air pollution such as food manufacturers, breweries, dairies and laundries. Urban and industrial areas, moderate sulphur dioxide pollution. Coastal areas with low salt content. C4 High Chemical manufacturers, swimming baths and ship- and boatyards by the sea. Industrial areas and coastal areas with moderate salt impact. C5-I Very high - Industry Buildings or areas with almost permanent condensation and with high pollution. Industrial areas with high humidity and aggressive atmosphere. C5-M Very high Buildings or areas with almost permanent condensation and with high pollution. Industrial areas with high humidity and aggressive atmosphere.  

Issue A duress input is only triggering duress alarm events and not the return to normal events after the duress input is reset. The point going into alarm is seen on the Monitoring | Status page when viewing all alarms but the return to normal events are not being displayed. Product Line EcoStruxure Security Expert Environment Security Expert Cause The problem is due to how the Event Filter and Event Report are configured. Resolution Check to see that the Event Filter includes all of the Event Types that should come through as shown alarms. In the example this would be at least "Input Opened" and "Input Closed" under the "All Input Events" folder.   Event Filter: Create an Event filter and include the correct Event Types that you wish to report on.   Event Report: Add the Event Filter you configured in step 1. To show those Alarms, create/modify a Status Page under Monitoring | Setup > Status Page Editor, set the Type to Event Windows and add the Event Report from step 2 above to the Record field.

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 shop at Exchange:  https://shop.exchange.se.com/en-US/home 

Issue EBO server has receive timeout parameter for Modbus TCP gateway, and the gateways has also time for the serial line. Having both timeouts not configured properly can lead to instability issues. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause When EBO sends a request to the Modbus gateway, e.g. polling a register from a serial device, it expects the gateway to respond with a value or exception code within the configured receive timeout. The Gateway will forward the request to the serial device and wait for a response within the timeout configured in the gateway.  If the device fails to respond within the timeout period, the gateway will send an Exception code 11 to EBO (Gateway Target Device Failed to Respond).    If the timeout configured in the EBO server is less than or equal to the timeout configure in the gateway, the EBO connection to the gateway may timeout before the connection between the gateway and the Modbus device timeouts.  This can lead to frequent device offline alarms, if one or more devices are slow or offline. Resolution The receive timeout configure in the Modbus TCP Gateway Properties – Basic Tab should be higher than the serial line timeout configured in the Modbus TCP gateway. Please see Setting Message Timeout for Modbus Client and Modbus Server - EcoStruxure Panel Server User Guide for examples/recommendations.

Issue The Access Expert Bosch integration User sync stopped working whereas previously the Users and their passcodes from the Bosch Panel could be brought into Access Expert using Import Configuration. Example: In the case below, there should be 4 Users, not 2 compared to Bosch RPS.   Note: User 0 is not counted Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Bosch Panel Integration Bosch Remote Programming Software (RPS) Docker Cause There was a September 2024 update from Feenics to fix a User synchronization defect and there are pre-requisites for the User synchronization to operate normally Resolution 1. Check the version number of Access Expert that is displayed when logging in. The version should be 24.9.1.0 or greater 2. Pre-requisites for the User synchronization     a. Area Authority Assigned     b. Person assigned to the User - the person cannot be blank. This can happen if LDAP is used     c. At least 1 Area Assigned To verify: In Access Expert> Access Configuration Select Area Assighnment 1, or 2, etc. Blank Person for a User Open Bosch RPS and connect to the panel, Expand User Configuration> User Assignments 3. Check Access Expert Live Monitoring and the Docker Logs  If the Import is still not working after ensuring Access Expert client software is up to date and the pre-requisites are set, check to see if there are any entries related to the Import or Users that may help troubleshoot by using Live Monitoring in Access Expert and/or the Docker Logs. An Example of the Docker Logs: Launch Docker> Under the Bosch Service> Logs (User 2 and 4 were not coming in prior to the Sep. Update) If the above steps do not resolve the issue, please open a case with Product Support for assistance.

Issue Timestamps in Script programs are different by an amount equal to the UTC offset of the workstation's timezone settings. 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 - Standard Building Operation WorkStation Script editor Cause Take the following program as an example:   Datetime Output TimeOut, TimeOut2 TimeOut = StrToDate ("1/17/2012 15:00") TimeOut2 = StrToDate ("1/17/2012 3:00 PM") In EcoStruxure Building Operation, the values will read:  "1/17/2012 9:00:00 AM" (in this example, the UTC offset is set for -6). In servers, all time values are stored in UTC, then the offset is applied by the client.  When it receives a value from a Script program, it stores the value as UTC, then the offset for the selected timezone is applied. Resolution Write code in the Script program to adjust the time values to UTC. Check the example code below to help understand operation: Datetime Output dtOut1 Datetime Output dtOut2 String Output str1 dtOut1 = Date 'Local time, displays with added UTCOffset dtOut2 = Date - UTCOffset - DST 'Local time, adjusted by the UTCOffset and DST, displays properly Print Date to str1 'Local time String value displays properly (UTCOffset system variable is available in v2.0 or higher, DST system variable is available in EBO 2022 v4.0 or higher)

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. If Firmware 3.02.01 is installed, please upgrade to 3.02.02. SmartX is now SpaceLogic. KNOWN ISSUES with Firmware affecting RSTP: RSTP not performing as expected with Static IP addressing - Schneider Electric Community

Issue All Controllers appear offline with any associated I/O showing a status of “Unknown”. The Security Expert Event Service's memory usage builds up until it gets close to 2GB when the controllers go offline.  Restarting the Security Expert Event Service brings the controllers back online. After a period of time the issue re-occurs and controllers again appear offline. Product Line EcoStruxure Security Expert Environment Security Expert Cause A potential memory leak in the Event Service would cause the service to stop working resulting in controllers appearing offline. Resolution 1. Upgrade to Security Expert version 4.3.370.1 or greater as discussed in known issue. 2. A potential workaround to mitigate the frequency of the problem is to disable the Event service from using MSMQ. As long as there are no site integrations using MSMQ then this option can be disabled in the Event Service Config file. Go to ..\Program Files (x86)\Schneider Electric\Security Expert and edit the SecurityExpertEvtSvr.exe.config file. Search for the MSMQ key <add key="MSMQ" value="1" /> and replace it with the following. <add key="MSMQ" value="0" />