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 During or immediately after a firmware upgrade, the RP-C controller may experience corruption of the STM32 processor's flash memory. This results in the controller misreporting its model type and becoming non-functional. Affected RP-C controllers may exhibit the following: Incorrect controller model appears during BACnet discovery or in the device report. Controller defaults to RP-C-16A-F-230V when STM32 is unresponsive. No communication between STM32 and main processor (LCES). Controller reset button has no effect (no LED blink sequence). Even if the actual model is RP-C-16A-F-230V, it will not operate correctly if STM32 is corrupted. Lack of response to the reset button is a key indicator of STM32 corruption. Product Line EcoStruxure Building Operation Environment  Room Controller (RPC) Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause STM32 flash corruption is caused by interruptions during firmware activation, such as: Power cycling the controller before activation completes. Network disruptions during upgrade. Premature assumption that upgrade is complete based on “100%” progress bar. Resolution To prevent the issue, perform the following: Do not disturb controller operation during firmware activation. Ensure the following indicators are met before removing power: Firmware revision is updated in the “Firmware revision” column. “Upgrade status” shows Operational. Controller is Online (not just showing 100% progress). If STM32 corruption has occurred, follow these steps to restore the RP-C controller: Ensure prerequisites for your laptop: Enterprise Server with Demo License running 5.0.2.109 or higher EBO Workstation compatible with Enterprise Server version instructions are for DHCP network that laptop and controller are connected. Adapt for direct connection using Auto IP, if needed. Multiple SpaceLogic firmwares, as needed to use one different from the version the controller is currently running Launch EBO Workstation and log into Enterprise Server. Connect RPC to network via Ethernet. Apply 24VAC power to RPC. Open Device Discovery and initiate BACnet discovery using Discover All button. If RPC is not discovered, cycle power and retry discovery. Once discovered (likely as RP-C-16A-F-230V), host it to the ES IP network. Ensure ES has a different firmware version than the one currently on RPC. Go to Firmware Upgrade screen: Select a different firmware version. Choose Activate Immediately. Click OK to start upgrade. Wait for the status to change: “Download firmware in progress” → “Activate firmware scheduled” → “Activate firmware in progress”. RPC will go offline in 1–3 minutes. Wait 1 minute, then power cycle RPC (off for 5 seconds, then on). Wait another minute, then repeat power cycle. Within 10–30 seconds, Status LED flashes Red & Green (STM32 reprogramming is being performed). After ~1:15 minutes, LED flashes White & Green, then toggles Red & Blue (Bluetooth FW upgrade is being performed). There is an expected white and green flash of LED where the final LED state is Solid Green. Rediscover RPC in EBO. The controller should now report the correct model and be fully operational.

Issue Need to perform a diagnostic verification as a preventative measure during routine maintenance or reactively in response to cabling that is causing RSTP issues. Product Line EcoStruxure Building Operation Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller (RPC) IP-IO Cause Issues can be caused by cabling or cabling terminations between controllers in the RSTP Loop. Resolution Reference RSTP Troubleshooting for BACnet/IP Controllers - Schneider Electric Community to ensure that: the managed switch is appropriately configured for RSTP all SpaceLogic controllers, on the RSTP loop, report RSTP Status = Operational Leave one side connected to the managed switch Plug the other end into a laptop running Wireshark Evaluate based on the information below Ensure both ends are not plugged into the managed switch at the same time by: Unplug the end from the managed switch Unplug the end from the laptop and plug it into the manage switch Take the free end and plug it into the laptop Evaluate based on the information below If it fails either evaluation, check the cables based on Message Age using a cable tester. It is optional but highly recommended to use a cable tester that displays cable length, as they tend to be more accurate, pointing out failures that other testers may report as passing. If it passes the evaluation on both ends, then one can plug in both ends into the managed switch Evaluation This capture shows a topology change (TC + Root) in RSTP, then settles out to a consistent Root Bridge Priority and Message Age. Your capture should only show a topology change when Wireshark is capturing on one end and the other end is connecting/disconnecting from the managed switch. Review the following fields: Root Bridge Priority - should be consistent and show the Priority of the Root Bridge. The root bridge can be the switch to which the RSTP loop is connected or a managed switch upstream. If it shows 32768, then another SpaceLogic controller assumed the root because it is not communicating properly back to the root bridge. (See Message Age Note) Message Age - should be consistent and show the expected number of controllers away from the root bridge. When Root Bridge Priority is 32768, you can use Message Age to determine how many controllers away the issue is occurring, checking the cabling connected to or close to that controller.

Issue Maintaining device uptime and ensuring data integrity is critical. This article explains the Device Firmware Upgrade (DFU) process, the meaning of “nosync”, and how we’re enhancing system reliability. Product Line EcoStruxure Building Operation Environment EBO version 5.0, 6. and later Cause What Is “nosync”? Introduced in SBO 1.5, the term “nosync” indicates an incomplete shutdown, which may result in data inconsistency. Devices in this state can be recovered using the DFU process. What Is the DFU Process? The Device Firmware Upgrade (DFU) process is a standardized recovery method that restores devices even when system data is corrupted—essentially reviving a “bricked” or “nosync” device. Instead of booting from internal firmware, DFU allows the system to boot using data sent via USB. Common use cases: Downgrading to an earlier software version. Recovering from failed shutdowns to restore functionality. How Our Devices Store Data—and Why Proper Shutdowns Matter? Unlike traditional computers, Automation Servers use eMMC memory for continuous data logging. The smallest writable unit is a 4096-byte block. To reduce wear, we use write caches that temporarily store data before writing it permanently. A proper shutdown ensures all cached data is safely written. Interruptions can cause data loss due to: Power Failure: If power is lost before the backup capacitor completes the write process. Linux Kernel Crash: Prevents proper data management and shutdown. Resolution Improving System Reliability with EBO 7.0 In EBO 7.0 and later includes a major reliability enhancement. The Automation Server will now perform a smart check of its last shutdown status. If an improper shutdown is detected, the system automatically runs the Linux fsck (file system consistency check). This helps determine whether a “nosync” state is truly warranted, reducing false reports and improving reliability.   This enhancement has also been included in EBO versions 5.x and 6.x via hotfixes:  EBO Hotfix 5.0.3.17009 (CP16) EBO v6.0.4.10001 (CP8)

Issue Need to download the XIF and NXE files for a SVEA Lon I/O Module DR-N-3D1M (0-10V) module, but having difficulty locating these files on the Extranet. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment SVEA XIF NXE Cause The difficulty in locating these files, is due to them being identified by their article number, in this case DR-N 3DIM. This number was used when these were classified as the SVEA devices. The Schneider version is now known as MTN881001, and not DR-N 3DIM. Resolution The Schneider Electric (MTN881001) files are located on The Exchange Download Center Download the XIF / NXE files for the SE MN881001 Download the XIF / NXE files for the SVEA DR-N 3DIM Note: It appears that although these devices are both classified as Lon I/O Module 1-10V, the XIF / NXE files are different.

Issue Which models of the SE7300 series room controllers can be used with the SC3000 series relay packs? Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SE7300 series Room Controllers Cause The SC3000 series relay packs allows existing line voltage wiring between the fan coil unit and temperature controller to be re-used. Only certain models of the SE7000 series room controllers can be used with the relay packs.  Resolution The SER7300 is used with the SC3000. Refer to F-27797 SER7300 and SC3000 Series datasheet. Refer to the F-27777 SC3000 Series datasheet to select the appropriate relay pack for your application.  SE7000 series Room Controllers documentation can be found on The Exchange Download Center.   

Issue Where is the information on LVIS Display/Screen Environment Lon Bacnet Loytec LVIS L-VIS L-VIS Touch Panel for BACnet networks   Cause Information on Loytec L-VIS Resolution The L-VIS from Loytec uses bacnet MSTP or LON. See Product Announcement - LonWorks and BACnet Touch Panels release for more information. All support for this product is via Loytec

Issue  Where do I find our BACnet controllers BACnet PICS? (Protocol Implementation Conformance Statement) Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment All BACnet controllers Cause Alternative locations to find BACnet PICS for our controllers. Resolution PICS documentation can be found on The Exchange Download Center and BACnet International website.

Issue Example graphics components required Product Line EcoStruxure Building Operation Environment TGML - Building Operation Graphics Editor Cause No standard graphics or components are supplied within the product. Resolution A Standard graphic component library can be downloaded from the Buildings Download Center. This consists of a number of Component Libraries that can be installed on a Workstation by double clicking on each one. In your TGML Editor, Right click in the Components window and select "Categories" you can then select the categories you require to see in your components section. There are also a lot of standard Snippets that have been developed by users around the world, these are available to download from the EcoStruxure Building Operation Forum - Graphics Exchange.

Issue What is the contact rating for a digital output (DO) within the StruxureWare Building Operation I/O modules? Environment Automation Server I/O Module Cause Information required for correct installation. Resolution Contact rating - 250 VAC, 30 VDC, 3 A  Click here to be linked to the DO-FC-8 and DO-FC-8-H - SmartX Controller Specification Sheet   Click here to be linked to the DO-FA-12 and DO-FA-12-H - SmartX Controller Specification Sheet

Issue What is the unit load (UL) of the SpaceLogic SP90 PIBCV Actuators that will help me to calculate how many SP90 PIBCV Actuators can be added on ComA and ComB of a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic SP90 PIBCV Actuator SmartX Server Cause Require the Unit Load (UL) of the SpaceLogic SP90 PIBCV Actuator to calculate the number of actuators allowed on the RS-485 network.  Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SpaceLogic SP90 PIBCV Actuator range uses the SN65HVD1780DR transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/10 UL. In addition, there are no local bias resistors and therefore the 1/10 UL of the transceiver would be the total UL presented to the bus by the SpaceLogic SLP Room Unit. Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus SN65HVD1780DR 0.1 Yes None None 0.1 No Based on the above the total number of devices can be calculated as 32/0.1 = 320. The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore a SmartX Server is limited to 127 devices per com port (254 total per Server) so this should effectively be the limiting factor. However, the documentation recommends using only up to 64 devices with the same RS-485 transceiver, or 32 devices with different RS-485 transceivers.   Since the SpaceLogic SP90 PIBCV Actuator does not have an isolated RS-485 interface it conforms to Generic RS-485 Network Device Configuration 1 in EBO Webhelp.  A network consisting of only SpaceLogic SP90 PIBCV Actuators should only require a 120-ohm termination resistor at each end of the bus and not require any bias resistors. Also, check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

   

Issue What is the unit load of SE8300 that will help me to count how many SE8300 controllers that can be added on AS ComA and ComB Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SER8300 room controller SE8300 room controller Automation Server Cause Documentation does not state the unit load of the SE8000 range Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SE8000 range use the ADM4850A transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/8 UL load. In addition the 100K local bias resistors have been eliminated and therefore the 1/8 UL of the transceiver would be the total UL presented to the bus by the SE8000.   Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus ADM 4850A0 0.125 Yes None None 0.125 Yes** ** Unlike the normally recommended interconnection of the communication common/reference (ground) terminal on all bus devices such as documented in the generic application note for the isolated RS485 bus interfaces, the Viconics bus should be operated with the communications REF (reference) terminal open on each SE8000 and not connected to the bus shield wire, or to any other circuit. Based on the above the total number of devices can be calculated as 32/0.125 = 256 The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore an Automation Server is limited to 127 devices per com port (254 total per AS) so this should effectively be the limiting factor.   Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue Is a certain version of Technician Tool Mobile Application compatible with all versions of StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool Automation Server Enterprise Server Cause The Technician Tool will always be backwards compatible, meaning that the latest version of the tool will work with any version of SBO. Older versions of the Technician Tool may not work with a newer version of SBO. Resolution Please note: Mobile experience to be replaced with EcoStruxure™ Building Operation v2.0 WebStation. For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool Always use the latest version of Technician Tool Mobile Application when possible, as that will work with all SBO versions.

Issue SmartStruxure with BACnet interface, points from BACnet devices are displayed in a graphic, list view etc, initially everything works fine and the point's value updates normally but after sometime of operation (days or weeks) the value stops updating. Value maybe shown as 0.00 or ... or with a green circle or red X that indicates a bad variable. Environment Automation Server Enterprise Server BACnet interface B3 Third party BACnet devices Cause Software defect in version 1.3 (including SP1) and below. Resolution Please note that if 1.3 SP1 has not been applied it MUST be applied before installing the hot fix. Contact Technical Support to obtain hot fix 1.3.0.11403 Provide site details Apply the hotfix

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

Issue Upgrading an AS results in an empty database. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 StruxureWare Building Operation 1.1.0.362 to 1.2.0.767  Cause When upgrading the database, the Enterprise Server (ES) upgrades without error, but when upgrading the AS, the result is an empty database. Resolution StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 The problem is caused by the initial engineering of the system being carried out on an old AS that was not LON or BACnet specific, copying into new hardware at R1.0 then when upgraded to R1.1 the upgrade fails due to the wrong type of AS being used (LON or BACnet). This practice is not common place and rather rare. When the trace log is examined, they find that the upgrade fails due to the fact that an illegal object type is attempted to be created – a BACnet interface. This is not legal in an AS-L. The reason that this occurs is that the backup file is from an AS-L that had been restored from a 1.0 AS-B backup file. Check New Release or Upgrade StruxureWare Building Operation Site Software. The issue you face could possibly be a procedural one and this article clearly defines the steps. StruxureWare Building Operation 1.1.0.362 to 1.2.0.767 The solution is identifying problems with a period, space, or other character in names. Placing a period at the end of a name or accidentally having a space at the end is suggesting something is following or further action. If using BACnet, please see the note below. Problems with bindings which were still in tact when values were removed also are a potential issue and not properly removed.    Work Around: Backup AS Upgrade PC to 1.2 Open Device Administrator Upgrade AS to 1.2 DO NOT close Device Administrator Open StruxureWare Workstation Log into AS If Database is Blank go back to Web Browser Connect to AS Log in In the top right hand corner of the screen select Setting>Device Configuration Select the Server Log tab Click “Get all log files” Once downloaded, open “trace” using Notepad Click Edit>Find Type the word “nsp.csc.UpgradeManager ERROR:” The error lines run from date stamp to date stamp so isolate the line beginning with the year and ending with the next instance of the year. Here is an example: 2012-08-29 16:39:32.990 [32] nsp.csc.UpgradeManager ERROR:    Error Parsing Dump Objects:  RecoverableException: source/Path.cppy) ) Error: Invalid_Path (0x10001), module Coml(11), moduleCode 0, dispString "Heatsink Temp.", techString "Path& Path::Append(const UTF8String& name)"  The “dispString “_______”” section of this line will give you the object name that contains an illegal character. Downgrade the AS back to 1.1 Locate the dispString object and change the name so that it does not contain any illegal characters. This is typically a name ending in a period. NOTE: when the rename dialogue pops up, it will indicate that an illegal character is present to confirm you are modifying the right object. Backup the AS Re-Upgrade the AS to 1.2 If the upgrade fails, repeat steps 9-20 or call product support. Be prepared to provide a Db backup at 1.1 as well as the trace file from the 1.2 failed upgrade. BACnet Note: A BACnet device including an object name "East Duct Max." is no longer valid because of the illegal character at the end of the name. Before upgrading the ES from 1.1 to 1.2, remove any full stops/periods from any object names. "East Duct Max." is changed to "East Duct Max"  Other illegal characters include *°?|/"<> or ~ and an object cannot begin or end with a white space or period. Select TPA-SBO-12-0008.00 - ES upgraded from 1.1 to 1.2 loses database to review this TPA.

Issue Upgrading Reports Server from 1.4.1 to 1.5 Environment StruxureWare Building Operation 1.5.0 Windows Server 2008 R2 Reports Server WebReports Enterprise Server Warning Cause Failure to follow upgrade guides may result in data loss. The most likely point of failure seems to be running the Reporting Agent Service on the Reports Server while upgrading the Enterprise Server. The Upgrade will error out if SQL2008 R2 is not upgraded to SP2 or .NET framework is not upgraded to 4.5 at the indicated points. Resolution This resolution process was developed from the System Upgrade Reference Guide and tested on a single PC. Windows Server 2008 R2 at StruxureWare Building Operation 1.4.1 running SQL2008 R2 SP1 and .NET 4.0 upgraded to StruxureWare Building Operation 1.5.0 SQL2008 R2 SP2 and .NET 4.5.  You can find and download all 1.5.0 released software and documentation by searching the Building Download Center for the tag "relsbov1.5" Backup Enterpriser Server, All Automation Servers and Report Server. Store backups on external media. If desired, create a Windows snapshot for a quick return point. Download all StruxureWare Building Operation 1.5 Installation files, SQL2008 R2 Upgrade files and .NET 4.5 installer. Close all StruxureWare applications In the Windows Server Manager, Expand Configuration and Select Services Browse to “StruxureWare Reporting Agent”, right click on it and select stop Open Software Administrator and stop the ES service. Close Software Administrator In the Windows Server Manager - Services section, stop the service “Building Operation 1.4 License Server” Run the .NET 4.5 installer. If prompted to restart, select Restart Later. If the PC restarts on its own, verify that all services listed above are stopped before moving forward. (repeat on all PCs) Run the License Administrator 1.5.0 installer Run the Enterprise Server 1.5.0 installer; select the Upgrade current version option. Note the ports used. Port 80 should not be used for http communication when the ES is installed on the Same PC as the Report Server. If desired install the Project Configuration Server.  Be sure that the HTTP port is not the same as what is used for the Enterprise Server and not port 80 Open Software Administrator and verify that both the Enterprise Server and PCS are running and using different ports Install Workstation. If you are upgrading from 1.4.1 to 1.5 and planning to delay the upgrade of the Automation Servers, you should install Workstation in parallel instead of upgrading Install Device Administrator. If you are upgrading from 1.4.1 to 1.5 and planning to delay the upgrade of the Automation Servers, you should install Workstation in parallel instead of upgrading At this time, upgrade any required Automation Servers. If upgrading from 1.4.0, all AS must be upgraded together. Install any required language packs If required, download and install the SQL2008 R2 upgrade to SP2 : http://www.microsoft.com/en-us/download/details.aspx?id=30437The default file name for the upgrade installer is SQLServer2008R2SP2-KB2630458-x64-ENU.exe In Windows Control Panel, go to Programs and Features Uninstall the “Building Operation Reports Installation” application only. This is the installer application for 1.4 Web Reports Run the Reports Server 1.5.0 installer Browse to C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation Reports Installer Right Click on SE.SBO.WebReports.Installer and select “Run as Administrator” For Setup Type, select “Upgrade both software and database” Fill in site specific information as instructed. For Reporting Agent, be sure to specify the exact Enterprise Server Address and port used. Follow the remaining prompts to install WebReports On completion, log into the StruxureWare WebReports interface and run a few test reports.

Issue When upgrading EcoStruxure Building Operation to version 2.0 or newer, the existing Power Manager software should also be upgraded to EcoStruxure Energy Expert to maintain compatibility Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Power Monitoring Expert (PME) Power Manager Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause The proper procedure is required when upgrading from older versions of Power Manager to the latest Energy Expert version. Guidance and best practices are needed for upgrading a PME server from PME 7.2 to PME 9.0. Resolution A Power Manager 1.0 site should be taken to 1.1 first, then upgraded to Energy Expert 2.0 Below are the recommendations for a side-by-side upgrade from PME 7.2 to PME 9.0: On the old server: Run the PME_8.2.iso file to do an in-place upgrade from PME 7.2.3 to PME 8.2 After completing that upgrade, the system will default to using a PME 8.2 trial license Install and run the PME 8.2 CM 2.1.0 Tool which will perform necessary actions for the side-by-side upgrade; we will use it to create a .zip file containing configuration components such as reports, dashboards, diagrams, users, devices, etc. Transfer this .zip file from the CM Tool to the new server On the new server: Run the PME_8.2.iso file to install PME 8.2 (this can be done while the above steps are performed on the old server) After transferring the .zip file from the old server, install and run the PME 8.2 CM 2.1.0 Tool on the new server and have it load the archived data from the .zip file into the program, and then write it to the system (essentially performing a PME 8.2 server to server migration) After that finishes, we can run the PME_9.0.iso file to upgrade from PME 8.2 to PME 9.0 After PME 9.0 is installed, we can activate the PME 9.0 license(s) in the Floating License Manager using the activation ID(s) that were already acquired, then remove the PME 9.0 trial license using License Manager (different from Floating License Manager) Running into issues with the install? Receiving error messages related to PME? Check out the Technical FAQ for a solution to your problem.  Links to relevant documentation and files: Where can I find documentation for Power Monitoring Expert 8.2 (PME 8.2)? Where can I download Power Monitoring Expert 8.2 installation files? Where can I find documentation for Power Monitoring Expert 9.0 (PME 9.0)? Where can I download Power Monitoring Expert 9 installation file? PME 8.2 CM Tool Exchange Community post  PME 9.0 CM Tool Exchange Community link  

Issue Upgrade path from version 1.0 to a current version Product Line EcoStruxure Building Operation Environment SmartStruxure Building Operation versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9 EcoStruxure Building Operation versions 2.0, 3.0, 3.1, 3.2, 3.3 (limited), 4.0, 5.0, 6.0 Cause Upgrade path from version 1.0 to current - version Important - The upgrade process is sequential, for example, 1.1 to 1.2 to 1.3 to 1.4 From v1.9, non-sequential upgrades are possible  The primary released versions were, Release Note Dates (approximate) 1.0.0.161   1.1.0.362 Dec 2011 1.2.0.767 July 2012 1.3.0.938 Nov 2012 1.3.0.10100 SP1   1.3.0.20011 SP2   1.4.0.4020 Sept 2013 1.4.1.68-73 Oct 2013 1.5.0.532 July 2014 1.6.0.250 (RC) Dec 2014 1.6.1.5000 Feb 2015 1.6.2.27 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.7.0.255 (RC) July 2015 1.7.1.89 Oct 2015 1.7.2.29 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.8.0.244 (RC) Mar 2016 1.8.1.79-87 Jun 2016  1.9.1.95 Apr 2017   1.9.2.45 Maintenance Release Oct 2017  - See release note 1.9.3.24 Maintenance Release April 2018  - See release note 1.9.4.29 Maintenance Release April 2019  - See release note 2.0.1.130 & 135 June 2018 (130(License, WS, Reports Server) 135 - Server (AS, ES, EC)) - See release note 2.0.2.67 Maintenance Release Sep 2018  - See release note 2.0.3.45 Maintenance Release Dec 2018  - See release note 2.0.4.83 Maintenance Release June 2019  - See release note 3.0.1.104 May 2019  - See release note 3.0.2.33 Maintenance Release July 2019  - See release note 3.0.3.11 Maintenance Release Aug 2019  - See release note 3.0.4.43 Maintenance Release Dec 2019  - See release note 3.1.1.312 Dec 2019  - See release note 3.1.2.29 Maintenance Release Mar 2020  - See release note 3.2.1.630 Aug 2020  - See release note 3.2.2.61 Maintenance Release Nov 2020  - See release note 3.2.3.59 Maintenance Release Mar 2021  - See release note 3.3.1.59L Limited distribution release Feb 2021 - intended for specific feature compatibility with some hardware or applications - See release note EBO 2022 (4.0.1.86) Dec 2021 - This version follows v3.x, and reflects a new naming convention focused on release year for clarity - See release note EBO 2022 (4.0.2.559 & 562) Maintenance Release Apr 2022 - WorkStation Hotfix and License Admin 4.0.2.562, others 4.0.2.559, see revised release note EBO 2022 (4.0.3.176) Maintenance Release Jul 2022 - See release note EBO 2023 (5.0.1.86) Dec 2022 - See release note EBO 2024 (6.0.1.93) Mar 2024 - See release note Resolution It is most important to read the Release Notes and System Upgrade Reference Guide for each version you are upgrading to, as there are some special notes that only apply to some installation types. Click Here for Release Notes Click Here for Upgrade documentation The Minimum upgrade path would be as below (See Release Notes for any special instruction) 1.0.0.161 1.1.0.362 See StruxureWare Building Operation v1.0 to v1.1 upgrade issues Appendix A 1.1.0.1225 See Appendix A 1.2.0.767 See Appendix A This version can be avoided by using 1.2.0.1412 if possible 1.2.0.2207 (Hotfix) Available from PSS See also Appendix A 1.3.0.938 See also Appendix A 1.3.0.10100 (SP1) (needed if runtime compatibility is required during upgrade) 1.4.0.4020 or 1.4.1.68 (Only needed if runtime compatibility is required during upgrade) See Upgrading Automation Servers from 1.3 to 1.4 1.5.0.532 1.6.1.5000 See Upgrade to 1.5.0 or 1.6.0 fails 1.7.1.89 1.8.1.87 See Product Announcement 00471 Pre-Upgrade LON Add-On 1.7.1 to 1.8.x 1.9.1.95 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions Option to 1.9.2.45 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.3.24 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.4.29 Upgrade options more limited with this version, only from v1.7.2, see the release note 2.0.1.130/135 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions. NOTE the new License structure for v2.0. 3.0.1.104 Possible to upgrade directly from v1.8, see the table in "System Upgrade Reference Guide" (3.0.1 System Upgrade Overview), but carefully study the release notes and upgrade instructions. NOTE the new Licenses for v3.0. 3.1.1.312 Possible to upgrade directly from v1.8 See Release notes and upgrade documents for full details 3.2.1.630 AS Classic not supported, Win 7 and Win server 2008 not supported 3.3.1.59L Limited distribution release - intended for specific feature compatibility with some hardware or applications, see release note for details. If you do not require the specific features outlined in this Release Notes, it is recommend installing EcoStruxure Building Operation 3.2.x instead EBO 2022 (4.0.1.86 and later) The following protocols, objects, and devices are not supported in EcoStruxure Building Operation 4.0 or higher: I/NET, Sigma, MicroNet, NETWORK 8000 ASD and LCM. A multi-version system supports I/NET, MicroNet, NETWORK 8000 ASD and LCM on automation servers and Sigma on an enterprise server, running an earlier version than 4.0. Report Server/WebReports is not supported in EcoStruxure Building Operation 4.0 or higher. See release notes for details. EBO 2023 (5.0.1.128 and later) New SpaceLogic and Easylogic Controller support, External Storage support for MS SQL, Some support for IPv6, BACnet protocol rev.16, Virtualized Automation Server - Edge Server added,   See release notes for details. EBO 2024 (6.0.1.93 and later) Added New Software Assurnace, Sustainability Pack, EBO Enterprise Server and Enterprise Central for Linux, OPC UA Client Support, Modbus2 Support, Visual Programming for Function Block, XLSX Report, and Touch Room Controller Support. See release notes for details. Appendix A - Upgrading from Specific 1.x Builds Upgrade from V1.0.0.XXXX to V1.3 (via V1.1 and V1.2) Upgrade from 1.0.0.XXXX to 1.1.0.1225 Upgrade from 1.1.0.1225 to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.1.0.XXXX to V1.3 (via V1.2) Upgrade from 1.1.0.XXXX to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.2.0.767 to V1.3 Apply hotfix 1.2.0.2207 Upgrade from 1.2.0.2207 to 1.3 NOTE: These hotfix builds are not available for download from the Extranet site, you will need to contact Product Support and request them