Building Automation Knowledge Base

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 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 How many objects, users, devices, etc. per device with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation WorkStation Building Operation WebStation Cause How many objects per device and what are the limits of EcoStruxure Building Operation? Resolution The primary source of these details should be the Architectural Guidelines on WebHelp Topic for the version being used

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE EcoStruxure Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

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 When doing a conversion from TAC Vista with LNS Network, to EcoStruxure Building Operation, what system should handle the addressing of the devices? What does the Network property “Shared LNS and SBO network” mean? Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista Conversion Tool Cause In a TAC Vista system, running as LNS system, the network is marked as Protected in TAC Vista. This means that all addressing is handled via the LNS system. Resolution After a conversion from TAC Vista with LNS network, to EcoStruxure Building Operation, a flag is set in the Network properties, named “Shared LNS and SBO network” which means that the LonWorks network is shared between LNS and EcoStruxure BMS. LNS is used for network management, such as handling addresses and Lon bindings. LNS has the ownership of the network. EcoStruxure Building Operation is used for downloading application and configuration to the controllers. It does not write in the address table of the Lon device.  This flag should not be set manually.

Issue How do you use iLon600 in an EBO Project Product Line EcoStruxure Building Operation Environment EcoStruxure Enterprise Server Echelon iLon600 Cause When to use iLon600 in EBO Resolution There are no support for iLon 600. EcoStruxure only supports Loytec network interfaces. See datasheets for exact models. If you are engineering a new system you should get Loytec products. The Loytec NIC has support for iLon600 so you should be able to add a NIC852 and one L-IP (to use as a config server) and use the iLon600 as router. This have not been tested but should work. Only supported interfaces are listed in the datasheet.  

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

Issue Confusion over the thermistor type selection for an EBO Temperature Input object Product Line EcoStruxure Building Operation Environment Building Operation I/O Module Building Operation Automation Server Bundled Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Building Operation IP-IO Cause The Thermistor type selection lists sensor "Types" I through V     This is confusing since, for example, the Continuum sensor is listed as 10k Type I but in manufacturers literature and temperature vs resistance tables is often referred to as 10k Type 3 Resolution The reference to Thermistor 10k Type in the selection list is an internal reference and not intended to refer to the types listed in manufacturers literature and temperature vs resistance tables. For reference the selections refer to the following sensor types:   Thermistor 10k Type I (Continuum) – Thermistor 10K4A1 also referred to as 10K Type 3 - SpaceLogic Sensors (as SLASXXX, SLAWXXX and SLABXXX), STx5xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type II (I/NET) – Thermistor 10K2A1 Dale/Vishay - STx20x Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type III (Satchwell) – Thermistor 10K3A1 (No Longer Applicable for Satchwell sensors) Thermistor 10k Linearized (Satchwell DxT - Type T) - STx6xx Sensors (see HVAC Sensor catalog for details) Thermistor 10k Type IV (FD) – Thermistor 10K4A1 type ‘G’ (U.S. Sensor) Thermistor 10k Type V (FD w/ 11k shunt ) – Thermistor 10K type ‘G’ (U.S. Sensor) with external 11k ohm shunt resistor installed Thermistor 1.8k (Xenta) – Thermistor type 1.8KA1 - STx1xx Sensors (see HVAC Sensor catalog for details) Thermistor 1k (Balco) – (not a thermistor) RTD, 1000 ohm Balco Thermistor 20k (Honeywell) – Thermistor 20K6A1 type H Thermistor 2.2k (Johnson Controls) – 2.2K3A1   Refer to the Temperature Sensor Resistance Charts Knowledge Base article for temperature vs resistance charts for these sensor types and others.

Issue EcoStruxure Building Operation WorkPlace Tech Editor Supported Microsoft Visio Versions The following error context is encountered when trying to run WorkPlace Tech Editor to edit a program: WorkPlace Tech Editor returned errorClass not registered 0x80040154 REGDB_E_CLASSNOTREG Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation WorkPlace Tech Editor I/A Series MNL, MNB Controllers (MNB - from SBO v1.8.1 and newer) Cause Only the 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. The error is seen when a 64-bit version of Microsoft Visio 2010 is installed. Resolution Currently, only 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. SBO 1.5, 1.6, 1.7 Microsoft Office Visio 2010 SP1, 2007 SP2, 2003 SBO 1.8 Microsoft Office Visio 2010 SP1 (32-bit), 2007 SP2, 2003 SBO 1.9, EBO 2.x, 3.x Microsoft Office Visio 2016 (32-bit), 2013 (32-bit), 2010 SP1 (32-bit) EBO 2022 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit) EBO 2023 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit) EBO 2024 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit)

Issue As soon as a user logs in to Workstation, there is a bandwidth usage above 50%. When logged out, it goes down to 10%. When logged in to Webstation, there are no changes to the bandwidth usage; it stay at 10%. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are a lot of signals in the Watch Window. The system continuously asks for the watched values as long as the user is logged in. The system stops asking for the watched values when the user is logged out. Resolution Remove values from the Watch Window when they are no longer needed.

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

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. Issue Need to move PCT storage file to another location Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The hard drive where the storage file resides may be full, or the space may be allocated for another purpose Resolution It's suggested to create a backup before proceeding, follow How to backup PCT 2.0 data to create a backup.   Open Hyper-V Manager Select "pct" under Virtual Machines then click "Move..." from the right-hand side menu Move "pct" Wizard Window will pop-out, click Next Select "Move all of the virtual machine's data to a single location" then click Next Select the NEW location for PCT then click Next. Check if the location is correct, then click Finish. Hyper-V will initial the process Once the Status shows the progress finishes. Click "Shut Down" from the right-hand side menu for "pct" image   Click "Stop Service" from the right hand side menu to stop Hyper-V as we need to modify the file location for PCT settings file   Open Windows Explorer and go to C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool Open the "settings" file Replace the old folder location with the new one then Save the file (I changed the folder from 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool' folder to 'D:\PSS\PCT 2 storage' Before modification After modification Go back to Hyper-V then click Start Service   Select "pct" then Click Start   Wait for a couple of minutes for the VM to start Go to https://192.168.10.2/ in a browser and PCT will start with all the existing projects

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. Issue Need to create PCT backup Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause Users need to backup all PCT data to prevent data loss or corruption. Resolution Since PCT 2.0 virtual machine resides in Hyper-V., the process is the same as backup any VM in Hyper-V Manager. Open Hyper-V Manager: Launch the Hyper-V Manager application on your server. Select the VM: Navigate to the virtual machine you want to back up in the left pane. Right-click and choose "Export": Right-click on the VM and select "Export" from the context menu. Choose a destination: Select the folder where you want to save the exported VM files. Start the export process: Click "Export" to begin the backup process. The "Export" process will create a "pct" folder from the folder in step 4. The 3 folders under "pct" folder are the backup for PCT 2.0 with projects and server packages installed.      

Issue There is currently no summary KB article for all the data collection available in EBO systems. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Building Operation Webstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Identified the need to review data from EBO to analyze performance or issues. Resolution Purposes for Data Collection Provide visual information about the issue Screenshots (from Windows Snip & Sketch or other tools) Video Capture or Mobile Device Video Device LEDs, provide any information about them and when they change. Provide information about your configuration/installation Network devices, including routers, switches, and any configuration you can provide BMS Routers Site Topology, including all devices included in the communications path Provide server (EC/ES/AS) XBK backup Configuration only is smaller and useful when investigating configuration, bindings, and/or programming All Data is larger and recommended when need to see trends or events to help investigate the issue's timeline. Provide any information to replicate the issue. Provide as specific as possible steps used to create that outcome Provide VERSIONS of ALL software, hardware, and protocols involved If submit any captures or logs, perform the following: Provide any steps performed in EBO during the capture or log with the date & time, so these events can be matched.   Servers (EC/ES/AS) Collect logs from an Automation Server Collect logs from the Enterprise Server and Enterprise Central Backing Up EcoStruxure BMS Servers Manually  (Configuration Only or All Data) Server Fieldbus Protocols Infinet: Gathering Trace Log information for the Infinet bus in EBO Lon: (Video included) Analyze Lon communication using trace log in EBO Modbus: Capture a Modbus trace log in EBO/SBO   Software EBO Webstation Collect EBO Webstation browser logs EBO Workstation Collect EBO Workstation logs EBO Project Configuration Tool (PCT) Collect log files from Project Configuration Tool (PCT) Windows Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Wireshark For extended period capturing, use this article to set up a Ring Buffer in Wireshark. Wireshark capture ring buffer for continuous capturing Hardware b3/Infinet Controller Collect log from a b3 or Infinet controller BACnet/IP Controller Workstation method - BACnet/IP Controller Diagnostics Building Commission method - Viewing and Exporting Diagnostic Files (WebHelp) or Viewing Diagnostic Files (YouTube)   Protocols & Electrical Interfaces Ethernet Capture any ethernet traffic, including IP: Using WireShark to analyse communications on an Ethernet network Capture Loopback (127.0.0.1) traffic between applications and/or servers running on the same host OS: How to capture localhost traffic with Wireshark to help troubleshoot EWS communication issues Lon Using Loytec LPA with SpaceLogic Server AS-P RS-485 Fieldbuses include BACnet MS/TP, I/Net, Infinet, Modbus RTU BACnet MSTP Capture Application - Communities (se.com) aka mstpcap.exe BACnet - PicoScope Basics Picoscope Configuration for Modbus RTU capturing and decoding

Issue Getting error "Failed to run: import-VM" when trying to install PCTv2 Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Could install PCTv2 fine but the issue started when going back and forward between PCTv1 and PCTv2 so that might have caused the issue. Resolution Uninstall Hyper V in Windows Programs and Features and restart computer Delete everything in ProgramData\Microsoft\Windows\HyperV Install PCTv2 version 2.0.2.13 or later

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. Issue Project Configuration Tool generates a 'failed get matching version' error when attempting to start an existing server Product Line EcoStruxure Building Operation Environment Project Configuration Tool (PCT) Cause The associated PCT server package files are not installed, cannot be accessed or are corrupt Resolution The "get matching version error" can occur when the associated server package files are not installed, cannot be accessed or are corrupt.  Try the following steps:   Check the associated PCT server package is installed, click manage packages (1) and check the Manage packages window (2)   Install the package if it is missing and then attempt to start the server If still unsuccessful, reinstall the server package and then attempt to start the server When installing the package if the error below occurs navigate to 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\logs' and open the ConfigurePCT.log file to try and identify the problem                                                                                                  In the case the server package config file is corrupt navigate to the server packages folder at 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\cfg' and delete the associated *.cfg file.      Reinstall the server package and then attempt to start the server Additionally consult PCT error installing EBO package for further suggestions

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. Issue How to uninstall PCT 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause The uninstalling instruction isn't documented. Resolution Launch Hyper-V. Shut Down PCT VM. After the VM is shut down, select Delete from the bottom right window. Select Delete if the confirmation window prompts. It may take some time depending on the VM size.   Go to the VM location selected during the PCT installation The default installation path is  "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool 2.0"     Right-click on the pct folder then select Delete (This action will delete all the data in PCT including projects and servers created)