Issue When trying to open WorkPlace Tech Editor the following error is shown in a pop-up window.   The following error occurred while trying to launch the WorkPlace Tech Ribbon Bar: The add-in could not be installed. Product Line EcoStruxure Building Operation, TAC IA Series Environment Building Operation Workstation (Workplace Tech Editor) I/A Series WorkPlace Tech Cause An installation of the Visio Ribbon has not closed correctly from previous use of WorkPlace Tech Editor or standalone WorkPlace Tech. Resolution Open the Add and Remove function in Windows Select "Program and Feature" Look for an instance of the SE.WorkStation.IA.VisioRibbon when no WorkPlace Tech Editor is running. Right-click and uninstall. Open Workstation and launch WorkPlace Tech Editor  There are other conditions that can cause the ribbon not to run as well.  They are detailed in other articles Similar Error Message Regarding Ribbon Bar  Unable to Load Ribbon 

Issue Technical support contact information for Design 360 and Studio 360 Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Design 360 Studio 360 Cause Design 360 or Studio 360 has issues requiring technical support assistance which is not provided by PSS. Resolution Schneider Electric Employees should contact PSS who will provide you with your Branch Administrator and Technical Expert contact information. Partners may contact Smartware directly for any support of the tool at: Email: techsupport@smartwaretech.com Phone: (716) 213-2222

Issue Replacement for defective controller is unable to be brought online in Security Expert. The online status is offline and last download shows as failed. controller status A review of the event server diagnostic window shows it is full of "Unencrypted event packet received" messages. event server diagnostics window Product Line EcoStruxure Security Expert Environment Security Expert Client Security Expert controller (SP-C, SP-AC1, SP-ACX) Cause The previous failed controller had been setup for encrypted communications with the Security Expert server. Since the newly installed replacement controller did not have the encryption keys to be able to decode the packets from the server it was not able to be brought online. Resolution On the controllers Configuration tab press the Disable controller encryption, then Yes to confirm. Wait for communications to be established with the controller, review the controller health status and update any modules that require it. To re-initialize encrypted communications with the controller press the Initialize controller encryption button to establish a new encryption key with the new controller. controller encryption buttons

Issue Is there an I/A Series G3 Modbus object that converts a PM820 three register date and time format value? Environment I/A Series G3 - all versions Cause The Schneider Electric (Square D) PM820 Power Meter provides date and time in a 3 register (6 byte) compressed format. The three registers provide a single timestamp consisting of month, day, year, hour, minute, second.  For example, if the date was 01/25/00 at 11:06:59, the Hex values would be 0119, 640B, 063B. Hexadecimal High Byte  Low Byte 0119 01 = month 19 = day 640B 64 = year  0B = hour 063B 06 = minute 3B = seconds Note: Date format is a 3 register (6 byte) compressed format.  Year 2001 is represented as 101 for the year value. Resolution Program object PM_ConvertDateTime.bog decodes and converts the register values to date and time.  The object will split the bytes and decode to individual outputs as well as provide a dateTime output.  Connect the three sequential registers to in, in1, and in2. Download object: PM_ConvertDateTime.bog  

Issue An Enterprise Server or Automation Server is unsuccessful at sending email notifications to a Gmail recipient.  Email messages from ES are marked as spam by Gmail SMTP service. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS-P, AS-B or AS) Building Operation Workstation Gmail Cause Unable to successfully configure the ES to send an Alarm Notification to a Gmail recipient. Resolution The following describes how the ES can be set up to use Gmail for Email delivery. 1. Log into the ES; designate the Sender E-mail address and E-mail Host properties. 2. Create a notification on the ES; set the destination E-mail address and type of alarms to be included. 3. Log into destination E-mail account; notice there don’t appear to be any E-mails received. Select the “More” dropdown. 4. Select the “SPAM” folder. 5. Navigate to the E-mail Selection Tab and choose all E-mails from the correct sender. 6. Select the “Not Spam” button and from now on all email notifications will be sent to your inbox! 1. Log into the ES; designate the Sender E-mail address and E-mail Host properties. 2. Create a notification on the ES; set the destination E-mail address and type of alarms to be included. 3. Log into destination E-mail account; notice there don’t appear to be any E-mails received. Select the “More” dropdown. 4. Select the “SPAM” folder. 5. Navigate to the E-mail Selection Tab and choose all E-mails from the correct sender (SxW). 6. Select the “Not Spam” button and from now on all email notifications will be sent to your inbox!

Issue Need to connect MicroNet system to EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Automation server Enterprise Server MicroNet interface Cause MN-Mi interfaces are obsolete, need to find another way to connect to EcoStruxure Building Operation system. Resolution A MicroNet system uses one of two communications protocols, Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet). If the protocol being used is NCP, the MicroNet LAN can be connected directly to the AS-P/ES, A MicroNet interface can be added and configured. If the protocol adopted is ARCnet, this does require the MN-Mi, to convert from RS 232 to ARCnet, the MN-Mi would be connected to the AS/ES using an RS232-485 converter. If the MicroNet controllers are the older 100 series version, it may be possible to remove the auxiliary ARCnet cards, and reconfigure the MicroNet controllers and LAN to use NCP protocol. If the MicroNet controllers are the 50 series type the cannot be re-confirmed as the communications components are on the main board. PA-00246 provides more information on the possible connections.

Issue Attempting to log in with WorkStation and receive the following license error: No license available. Error -83: Version of vendor daemon is too old The following error is seen in System Log / Trace log:  Error Code: -83 Error message: Version of vendor daemon is too old Building Operation Software Administrator Product Line EcoStruxure Building Operation. Environment Building Operation License Administrator Building Operation License Server Cause The most common cause is that the License Server is older than the current release of Building Operation software.  This occurs during upgrades and if the License Server used for the product has not been upgraded.  Ensure both components of the License Administrator are selected (as shown below) when performing the upgrade/installation.     Resolution To confirm the issue open the Windows Services and check that the version shown in the services is valid for the products installed.  The version shown should be at the same version or higher than the other Building Operation software installed.     To resolve the issue, upgrade the License Server component of the License Administrator installation software. 

Issue When opening a dashboard graphic, the system operates very slowly.  Navigation to other links with the Dashboard displayed, and clicking on a linked graphic does not display immediately.  Product Line EcoStruxure Building Operation Environment Building Operation 3.2.3 and higher Building Operation Automation Server Bundles (AS-B) Building Operation WebStation  Cause Typically when a large number of stored values (100,000 per trend log) is needed to be displayed within the Dashboard widget (e.g., Period Chart) with a significant number of trend logs to be displayed (five or more) in the Dashboard, this will put excessive load on the AS-B and hence stops any or all navigation thereafter.   Dashboard widgets typically continue to read data required to be displayed after closing (or navigating away). This is to keep those logs cached for a few minutes after the dashboard is closed, so if the same logs are loaded again, then the data is available. Any calculations are always done on the client, regardless of whether a chart, dashboard, or trend list is shown. The same is also true for WorkStation. Resolution Below are some considerations to look at improving the overall performance when dealing with this issue: Reducing the number of storage records from 100,000 to something more reasonable for the dashboard to display (5,000 - 8,000) Having these logs stored on the Enterprise Server and Dashboard operated from the Enterprise Server.    If large storage is necessary, then create or use different logs for display within the Dashboards widgets.  If the intention is always to show calculated values, use log processor trend logs. Log Processing Trend Log. These can be pre-calculated and thus contain only a fraction of the full source log's data amount. Upgrade to the later version (EBO 2023) as many optimizations have been made for Dashboards since 3.2.        

Issue Communication issues caused by improper grounding of the BACnet MS/TP shield connections to the B-LINK-AC repeater.   Environment BACnet MS/TP installation with B-LINK-AC repeaters. Cause The shield connection on port 1, labeled "(Input)", of the B-LINK-AC repeater is internally wired differently than the four other ports. Resolution Due to the differences in how the shield terminals are wired, the following techniques must be followed when wiring the B-LINK-AC BACnet MS/TP repeater. Port 1, marked (Input), must have its MS/TP bus shield connected to the SHLD terminal, which is isolated from Earth Ground. The incoming MS/TP shield must be grounded at only one point, at a location other than the repeater. Typically this is at the opposite end of the bus, or where the MNB-1000, UNC, ENC or other BACnet parent controller resides. All four of the other repeater ports, # 2 - 5, have their SHLD terminals tied together, and tied to Earth Ground internally, through the power supply's Earth Ground connection. For each MS/TP bus cable connected these ports, the single point of ground for the shield is at the repeater and, therefore, the shield must not be grounded at any other point on the bus. None of the five MS/TP ports on the repeater have internal termination resistors.  If a MS/TP trunk ends at the repeater, a 120 ohm terminating resistor must be connected between the MSTP+ and MSTP- terminals on that port of the repeater.  Likewise, the far end of each MS/TP trunk must also be terminated with a 120 ohm resistor between the MSTP+ and MSTP- terminals of that last controller. None of the five MS/TP ports on the repeater have internal bias resistors.  Standard practices, regarding the biasing of the MS/TP trunks, should be applied, as described in the I/A Series MicroNet BACnet Best Practices Guide, F-27360. Additional information on the use of these repeaters can be found in the "Approved MS/TP Repeaters" section of Chapter 5 of the I/A Series MicroNet BACnet Smoke Control Systems manual, F-27419.

Issue In an environment where the Security Expert database is installed on a remote SQL server (i.e. not on the same machine as the one where Security Expert Server is installed), can I use SQL Authentication for the connection between SX and SQL Server? Product Line EcoStruxure Security Expert Environment Security Expert Server Cause SQL Server supports two authentication methods: Windows Authentication and SQL Authentication. Security Expert supports Windows Authentication only. Resolution No, Security Expert does not support SQL Authentication. You must use Windows Authentication, i.e. a domain user account must be setup with permissions both to the machine where SX Server is installed and the one where the SX databases are installed. Please refer to the SX-SRVR Security Expert - Client Server - Installation Guide for more information on the installation pre-requisites. See also KB article Security Expert Multiple Machine Installation for Windows Authentication with Active Directory for further information on how to setup SQL Server and SX on different machines.

Issue BACnet/IP port supported with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Which BACnet/IP ports are supported with EcoStruxure Building Operation, and can there be more than one port? Resolution By default, the BACnet/IP network uses UDP port 47808 (0xBAC0), this is adjustable higher or lower. The BACnet/IP network supports a single BACnet UDP port, Additional IP networks can be created in the BACnet system as long as each network has a unique identifier (network Id and name) and UDP/IP port number. Refer to: Creating an Additional BACnet IP Network (se.com) and Best Practices When Configuring BACnet IP Networks and BBMDs for EcoStruxure BMS Servers Please note that BACnet/IP uses UDP as its transmission protocol. For more information read the BACnet/IP basic design criteria.

Issue What are the proper configurations in the network Poll Service to balance the BACnet packet traffic for better data handling? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series ENC and Jace 8000 Cause Improperly defined poll rates, and poll groups in the Poll Service. Resolution This video demonstrates the Poll Service configurations in a Jace (MS/TP and IP) and an Enterprise Server (IP)   About Polling  Polling Statistics  Polling Rate Tuning  About Polling Components   

Issue Backup and Restore assures that Building Operation server data can be restored after a hardware failure or data loss. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Enterprise Server Automation Server Workstation 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 Services for assistance. Cause Restore is the process of restoring data to an original or former state. Using restore, you can revert back to a previous snapshot of the server data despite any configuration changes made since the last backup. In Building Operation, restore is designed to be a manual rather than an automatic process to avoid the accidental overwriting of current server data. For convenience, Building Operation displays only the backup files that apply to the selected server.  For more information on making a backup, see Backup of StruxureWare/EcoStruxure Building Operation AS and ES. Resolution Restore an Enterprise Server Backup Set If restoring to a previous snapshot of the database that is currently running, start with step 6. If restoring a database that is different from the one currently running, start with step 1. Launch StruxureWare Software Administrator; Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare Software Administrator. Click the Stop Service button and then click OK. Go to the Enterprise server database folders; C:\ProgramData\Schneider Electric\StruxureWare X.X\Enterprise Server Change the name of the current database folder to something that identifies it with the project's name (Example outlined in red: db changed to Old_db). Make a duplicate of the "db - Copy" folder (Example outlined in orange). It is important to always maintain a clean database folder by making copies. After first installing StruxureWare, a copy should be made of the original "db" folder. Copies of this folder should be made before restoring databases or creating new ones from then on. Change the name of the "db - Copy" folder to "db" (Example outlined in blue: db - Copy changed to db). Launch StruxureWare Software Administrator again, click Start Service, and then OK. Launch StruxureWare WorkStation and log into the enterprise server;  Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare WorkStation. Select the enterprise server and go to the Main Menu > Actions > Restore. In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Note: If a backup set is seen in red it means that the backup is not compatible with the current version of the server. The backup has to be the exact same version as the server including any hotfixes or service packs.   Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available. Note: The server name is part of the restore data. Therefore, if you rename a server after a backup, a restore process will revert back to the previous server name.       Replace an Automation Server with a Restore Note: The automation server restore should be done by logging directly into the automation server. Launch StruxureWare WorkStation and log into the enterprise server or the automation server;  Start > All Programs > Schneider Electric > StruxureWare X.X > StruxureWare WorkStation. Select the automation server and go to the Main Menu > Actions > Restore. In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available.

Issue What process do the bCX and b3 controllers use to automatically establish their communication bus speed. Product Line Andover Continuum Environment bCX b3 Auto Baud MSTP Cause Having issues with b3 controllers selecting the wrong bus speed. Resolution The process by which the b3 controllers establish their communication speed is as follows. When the b3 controllers power up, they listen to the network for 2.5 seconds If they hear communication at their last known Baud rate, they start talking when they hear the poll for master. If they hear no communication after 2.5 seconds, they start their own poll for master at their last known Baud Rate. If they hear garbled communication during the 2.5 second listen mode, they begin hunting different Baud Rates while listening until they have synced to the Baud Rate they are listening to. Then they join the token passing when they receive the Poll for Master. Note:  There was a issue with the autobaud process in earlier versions of the b3 and BCX40xx controllers which would cause them to set the communication speed incorrectly.  This issue was corrected in the following firmware versions. BCX40xx ==> 4.500053 b3xxx      ==> 4.500064 b-3xxx-V ==> 4.501064

Issue When starting Continuum version 1.94 (64-bit OS), the main screen is blank.   Product Line Andover Continuum   Environment CyberStation 1.94 (64-bit OS) WebClient 1.94 (64-bit OS) Cause When Continuum is installed on a 64-bit OS, the Main.bmp file is stored in: C:\Program Files (x86)\Continuum\UserProfile  However the application is looking for the file in C:\Program Files\Continuum\UserProfile.   Resolution Configure the Main Menu to search for the Main.bmp file in the correct directory: In the "blank" Main menu, right-click in the white space, and select Edit Right click in the white space again, and select Page Properties In the Background File field, press the "..." button.  In the "Open" window, navigate to the  C:\Program Files (x86)\Continuum\UserProfile directory Select the Main.bmp file.  Press Open Click OK on the Page Edit window In the Edit window, press the Run Page button (looks like a Lightning Bolt) to close the Edit window Re-start Continuum (if necessary)

Issue Automation Server -Trend does not record at time interval when it is stopped and restarted by AS power cycle or reboot. Trend log cycle is thrown off when the trend is stopped and started again due to an AS power cycle or reboot. For example, an Interval Trend Log set up to log ever 15 minutes with an activation time right on the hour (1:00, 1:15, 1:30 etc.) that lost power for a while would start logging as soon as the power was restored (this might be 2:07, 2:22, 2:37 etc. for example). UPDATE: This issue has been corrected in SBO version 1.5, any SBO version 1.5 or grater will synchronize the interval log to the clock. Product Line EcoStruxure Building Operation Environment Automation Server Struxureware Workstation Cause This is how Interval Trends behave. For interval trending based on the time a different approach must be taken. UPDATE: This issue has been corrected in SBO version 1.5, any SBO version 1.5 or grater will synchronize the interval log to the clock. Resolution Rather than using Interval Trend Logs use Variable Triggered Trend Logs and trigger them using the following method: Create a new binary value and a new function block program. The value will serve to trigger the Variable Triggered Trend Logs. The program will set the trigger variable based on a certain time interval (for example on the hour, 15 minutes, 30 minutes and 45 minutes). Edit the program and configure it as seen in the image below. This include an integer input, an expression that will evaluate the minutes attribute of the AS and a binary output. You can also download an export of the program and value here. Bind the input of the program to the minutes attribute of the Automation Server and the output to the trigger value that you created. Note that you should also bind the Task to Task 1 (100 ms) for best performance. Create your Variable Triggered Trend Logs on the points that you want to trend. Do this by right-clicking the point to trend and selecting New > Trend and then in the dialog select Variable Triggered Trend Log. Click Next and then set the Trigger Variable to the value that you created. Make sure Trigger when is set to Change to true. Note that this example will create a log at 0, 15, 30 and 45 minutes past the hour. You can modify the program to trigger only every hour, every half hour or however you want.

Issue What are the locations where Controller configuration data is saved? Environment Continuum Cyberstation Continuum Controllers Cause Unsure as to where controller configuration information is stored and how to clear/reset this information if required. Resolution There are a number of different locations that a controllers database (configuration information) is stored - there are four locations for a BACnet controllers database and three for an Infinity controller. 1. Continuum SQL Database - Infinet tree In Continuum Explorer, this is where the controller is originally created as a Device object under a Network Folder and commissioned into the Database. This is the location where objects (inputs, outputs, programs, etc...) are created. When creating a new object, it is created in both the SQL Database and also sent out to the controllers database at the same time. The controllers information stored in the SQL Database can be sent out to the controller at any time by performing a reload of that controller (right-click Device object, Send to controller). This information can be removed from the database and the controller by deleting individual objects or by deleting the entire Device object. If the Workstation where this delete was performed is online to the field devices then the same object(s) will be removed from the live controller in the field as well as from the SQL Database. If the Workstation is offline to the field controllers  (Workstations can be taken offline for offline editing) then this delete is only applied to the objects in the SQL Database – the objects will still be located in the controllers though, creating a mismatch between the two until the controller is reloaded. 2. Controller RAM This is the active location of memory on the controller where the running database resides. On most controllers there is a backup battery that keeps this RAM alive with a trickle current when there is no power to the controller. When the controller is powered up it first tries to load its active database from RAM - this is the most current backup. The database in controller RAM can be cleared by pressing the Reset button on the Runtime tab of the controllers Device object in Continuum Explorer. 3. Controller FLASH This is the backup location of where the controllers configuration database resides. At any time the active RAM database can be saved to backup Flash by selecting "save to flash" from the controllers Device object in Continuum Explorer. This then makes an exact copy of the database in RAM (excluding point values) that can be restored at a later date either manually or automatically if the controller reboots and their is no valid database in RAM. For Netcontrollers and bCX's, this database saved to Flash can be deleted from the controllers configuration page (configuration webpage) select Clear Database Backup and then commit changes to controller. If the controllers webpage cannot be accessed, pushing and holding down the controller's reset IP switch for 30 seconds clears any backup in flash in addition to resetting the IP address and ACC node id to default. Another way to clear a controllers flash is to save a blank controller database to flash. Create a new controller Device object and then save that to flash. 4. Continuum SQL Database - BACnet tree The information stored in the BACnet tree is the BACnet side of our configured Infinet objects. This is the BACnet objects as seen in the controller and as third-party BACnet Devices will see them. When performing a "send to database" on the BACnet side, the Workstation goes out to the controller in the field, grabs all the BACnet objects and exposes them in the BACnet tree so that they can be used within Continuum. These can be deleted from the BACnet tree without harming those objects configuration in the controller or the Infinet tree. To recap:   To Create and save objects to the controller requires a two step process. Step 1: Create Database objects using Continuum Cyberstation. Objects are added to both the active RAM of the Controller and the SQL Database. Step 2: Save to Flash on the Controller. The objects in active RAM are backed up to the Flash RAM. If unsure, the only way to know that the Database in the RAM and Flash is the same as that in the SQL Database is to perform a reload of the Controller and then backup to Flash. Step 3: Send to Controller to reload configuration information from SQL Database to Controller RAM. After reload, redo Step 2 to backup to Flash. To completely wipe configuration information from a controller in the field you will need to clear its active RAM and its backed up Flash. If you want to clear all information of the controller from the field and the SQL Database then you will need to clear the RAM and Flash and delete the Device object from both the BACnet and Infinet sides of the tree. If you want to remove specific configured points from the controller but retain it in the tree, you will need to first delete the BACnet side of the controller from the BACnet tree, then you can delete individual objects (or make changes) from the Infinet tree.  

Issue EM42 is obsolete and is no longer available when replacement is needed Environment VTRA linkage kit 8600990000 EM9 180° 8601110000 VTRA valve EM42 Cause Replacement of obsolete actuator on old style valve Resolution The replacement actuator for EM42 on a VTRA valve is  EM9 180°, 8601110000, together with linkage kit 8600990000. The linkage kit originally included with the EM9 package should NOT be used.

Issue BACnet/IP controllers are not configured in RSTP Mode by default, therefore must be configured during installation. Having RSTP Mode disabled by default allows one to connect BACnet/IP controllers to any switch, even with port security configured to detect BPDU packets and disable the port. Product Line EcoStruxure Building Operation, TAC IA Series Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller IP-IO I/A Series N4 Jace8000 SmartX IP Driver for Niagara Cause RSTP protocol requires that controllers, switches, and network architecture are configured to ensure the protocol will operate as expected.  Resolution Setting RSTP Mode for BACnet/IP Controllers ALL devices in the RSTP loop MUST BE IN RSTP MODE to function properly. This is not a huge issue because during startup you can unplug 2nd side of the loop and it will function properly in a daisy chain. Ensure the SmartX Controllers are configured correctly Configuring BACnet/IP Controller Device Settings A factory or network reset returns the RSTP setting to Disabled. Important: Whenever you change RSTP settings, the controller MUST be WARM START. If you fail to perform this restart, the BACnet/IP controller will continue communicating using its previous RSTP settings. 'Activate IP Changes' does not affect RSTP mode. Ensure the switch is configured correctly per Configuring RSTP on a Managed Switch for SmartX IP Controllers. If asked to review this for a case, please provide PSS screenshots from the switch configuration page(s).  Bridge Priority = 4096 Hello Time = 2 sec Max Age = 40  (40 is the maximum value allowed by the protocol. Default is 20) Forward Delay = 21 sec Bridge Priority Considerations Change Bridge Priority by adding 4096 as switches get further away from AS. (8192, 12288, 16384, 20480, 24576, 28672) DO NOT set the priority as 32768 or higher because that is the built-in Bridge Priority of BACnet/IP Controllers. First, configure the Root Bridge Switch (closest to the Automation Server) settings. Then, configure the additional Switches in order of increasing Bridge Priority. {OPTIONAL}: Troubleshooting RSTP with Wireshark Plug in 2nd side of the RSTP Loop If all devices stay online, then it is working properly. Now test line breaks or controllers that are powered off. If all devices go offline and/or the switch LED is flashing rapidly, then go to RSTP Troubleshooting. Managed Switch Troubleshooting Consult the documentation or contact the vendor or manufacturer to assist with configuration for the items below. Ensure the switch is IEEE 802.1D - 2004 capable. BACnet/IP Controller Networking Term Definitions RSTP Ring mentions the Rapid Spanning Tree Protocol is specified in IEEE 802.1D - 2004. Ensure the firmware is up-to-date by contacting the vendor or manufacturer or downloading it from its website. Ensure ports not participating in RSTP are configured as Edge Port, Admin port, or have STP disabled. Nomenclature for those settings on your specific managed switch may vary. Adding BACnet/IP controllers to site-managed switches, work with Local IT to add these devices to their network. They will need to work with their switch vendor/manufacturer/support group to ensure the configuration of those switches because it could be more complex than changing the minimum recommended four settings above. Also, since RSTP Protocol is limited to Max Age = 40 (hops including site switches and BACnet/IP controllers), each loop's size may be limited based on their site switch network configuration and architecture.  Determined the proper configuration (or disable) for the following features. DHCP snooping Dynamic ARP inspection Denial-of-service (DOS) mitigations BPDU Guard BPDU Filter Energy-saving settings. Similar to Wake-on-LAN: the switch had minimal traffic, so ports entered power-saving mode. When they reactivated, the AS-P had already timed out, triggering a comm loss alarm. RSTP Troubleshooting Check each BACnet/IP Controller -> Diagnostics -> Device Report to confirm in RSTP Mode MANUAL CHECKOUT Double-click MP - Diagnostics Files - Device Report It will open in the default text editor Review the Device Settings section near the bottom. In firmware 1.00.0x, the report should report RSTP Mode: Enable In firmware 2.00.0x or higher, RSTP: Enabled and RSTP Status: Operational If it reports disabled, then perform Setting RSTP Mode for BACnet IP Controllers Step 1 until RSTP is working properly. USE SEARCH & EVENTS EBO 2.x MP Device IP and Settings.xml for EBO 2.0 as it only includes MP controllers EBO 3.x SmartX Device IP and Settings.xml for EBO 3.x or higher Import attached search USE RSTP STATUS GRAPHIC IN WEBSTATION 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

Issue Some actuators manufactured by Belimo are also available from Schneider Electric Environment Various Belimo Actuators: AF 230 AF 230-S AF 24 AF 24-S AF 24-SR LF 230 LF 24 LM 230 A LM 230 A-S LM 24 A LM 24 A-S LM 24 A-SR NM 230A NM 24A NM 24A-SR SM 230A SM 24A SM 24A-SR Various Schneider electric actuators, part no: 875-0000-010 875-0010-010 874-0000-010 874-0010-010 877-0000-010 875-0003-000 874-0003-000 875-1001-000 875-1003-000 875-1005-000 875-1007-000 875-1009-000 875-1011-000 875-1015-000 875-1019-000 875-1021-000 875-1025-000 875-1029-000   Cause Cross reference between various actuators of Belimo and Schneider Electric Resolution A cross reference table for these actuators can be found here (.xls).