Building Automation Knowledge Base

Issue Support for UI16A CIO with FW 2.016 and HW C How is CIO FW 2.016 distributed? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation I/O Module 16 Ch UI Cause Due to component changes in the UI16A CIO module, a new HW version C has been created. Consequently, a new firmware (FW) file has been created specifically for that new HW version, 2.016. Resolution This FW version will be installed already at delivery from the factory for the new version of UI16A modules. For this new UI16A model, one cannot install older 2.015 firmware as it is not compatible. All the older modules can remain at the latest published CIO release 2.015. The HW version which is printed on the product label is changed from B to C on the new UI16A version. The Hardware version can also be viewed in the module object through EBO. For all other modules, the HW version will stay at B.

Issue Need to place the ADv3 Display remote from any AS-P.  Requires USB connection, as WIFI is not allowed. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Advanced Display Cause The standard for USB 2.0 provides a maximum cable length of 5 meters (16 ft 5 in). The standard for USB 3.0 provides a practical maximum cable length of 3 meters (9 ft 10 in). Resolution Schneider Electric has only tested with standard cables. It may be possible to find third-party solutions like Active USB cables or bridges. These solutions are not tested, nor supported by Schneider Electric.

Issue When saving or importing a MTA (Menta) file in SmartStruxure Workstation, and error is shown indicating that there are more than one occurrence of one or more file types in the MTA file. Product Line EcoStruxure Building Operation Environment Workstation Menta Function Block Cause A MTA file contains various files that together forms the complete program. In some cases (e.g. when using a . in the MTA file name) various occurrences of the same file types will be placed in the MTA file. Resolution Open the MTA file in with the Menta editor Mark everything and export as an AUT file Create a new MTA file Insert the AUT file created in step 2 Save the MTA file only using standard characters Import the the MTA file Generate the MTA file to ensure you have no errors and all the public constants have been updated.

Issue When a Modbus device comes back online after being offline a message is sent from the Building Operation Server to the Modbus device which looks similar to: WriteData TX on /dev/tac_comporta: 01 2B 0E 01 00 70 77 ReadData RX on /dev/tac_comporta: 01 AB 01 9E F0 This message can cause the Modbus device to restart or stop responding, is it possible to disable it? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 1.5.xand above Modbus Device Socomec Power Meters Crompton Integra 1221 Power Meter Cause A feature was added in release 1.5 that is intended to read the device's identification (0x2B). It works by polling this function code (FC). If the Building Operation server does not get a valid reply to this message, it assumes it is not supported by the device and will not request this again. This is usually not a problem but some Modbus devices, such as those listed in the Environment above, are unable to handle this message and will stop communicating with the AS or ES. Resolution In Building Operation 2.0.4 and above the option to enable or disable the device identification request (Function code 2B) has been introduced, allowing the poll interval (and online detection) to be set. Some devices will stop responding to poll requests if the device identification is enabled. Once disabled the AS or ES and the device may need to be restarted to enable normal polling without any device identification request being sent and stopping the normal responses from the device.   In previous versions this message cannot be disabled, however, if device polling is disabled the device identification request won't be requested, which can be used as a work-around. To turn off the device polling: Open Properties Set "Poll interval" to "Inhibit" The trade-off with this workaround is that the online detection for the device is turned off, so the device will never go offline in Building Operation. In some instances, the third-party Modbus device will need to be restarted to allow communication to resume.

Issue Enterprise Server IP address does not match the IP address of the Local PC. SmartX Server is showing online but there is a "Communication failed" alarm showing for this server(s). Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause The IP address of the Windows system has been changed. This can be from a DHCP renewal or a manual change of IP address. This also may be an issue if an Enterprise Server backup is restored and the backup was from another PC with a different IP address. Resolution Update the Enterprise Server IP address from the Enterprise Server communications Tab and then the properties windows.  Refer to the video below for details on how to do this.     It is also possible to specify the Network Interface used by the Enterprise Central/Server.  Refer to the following WebHelp topic Configuring Network Interface Card for an Enterprise Server or for an Enterprise Central   

Issue WebStation connection is unreliable when using a 4G (cellular) connection Auto logoff times are not obeyed  Product Line EcoStruxure Building Operation Environment Building Operation WebStation 3.x Broadband Cellular Networks Cause WebStation creates a subscription with the Building Operation server, so it will attempt to connect every 10 seconds.  If this connection is removed/interrupted/ or no longer required for a period of 60 seconds, WebStation will force itself to log out.  This setting is currently fixed and cannot be adjusted.    Currently, there have been instances where this connectivity issue is seen when using, as shown below, a device with a broadband cellular connection attempting to connect to a Building Operation server that also connected to the same/similar cellular network this is the most common scenario where this issue is seen. Resolution It is recommended not to use these cellular network connections to permanently display Building Operation Server information, especially from mobile devices connecting to the cellular network.  This type of connection should be used sparingly and for quick access to view/check information as necessary.  Connection loss can be expected if you move away from the webpage for more than 60 seconds.  Any lengthy connections to the Building Operation Server are recommended to use a more permanent network connection.     Issues have not been seen when using broadband Internet or a similar connection as shown below to a remote cellular Building Operation Server.  This meaning that the EcoStruxure Building Operation system has remote Internet access via a broadband cellular connection. To troubleshoot this further, capture a HAR file using the details provided here How to collect a network trace | Microsoft Docs and reproduce the issue while this debugging window is open within your browser.  Note: This capture must be done at the source; that is where WebStation is running.  This may not be easy to do using a mobile device.   Send this saved HAR file and the Internet browser version and EBO version used along with connection types to your local support channel. 

Issue Existing SIM-MTECH communicates with a McQuay OPM (Open Protocol Master) and McQuay controllers under it. Can an AS-P replace the SIM-MTECH? Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series NW8000 GCM/SIM-MTECH (McQuay OPM) Building Operation Automation Server Premium Cause Replacing obsolete NW8000 GCM/SIM-MTECH with currently supported EBO AS-P Resolution The GCM/SIM-MTECH data base can be converted as a normal GCM through the Transition Tool on the Schenider Electric Exchange TAC I/A Series Transition Portal.  The blocks specifically associated with the OPM integration will not be converted. A third-party hardware device can be used that will allow the AS-P to communicate through the OPM to the McQuay controllers. This will be accomplished by BACNet or Modbus protocol to the AS-P depending on the third parties device selected.  Refer to these 2 documents and websites.  NOTE: These are third party devices and have not been tested or approved by Schneider Electric Product Support. FS-8700-80 McQuay MicroTech Open Protocol Mcquay Gateways

Issue What will happen with the EBO license when used with cloned Virtual Machines in a fail-over scenario to another host? Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server Cause Even if the Virtual Machines are "cloned" the licensing will show as "Damaged" Since Virtual Machines don't have unique hardware and the software images can be identical, another identifier called UMN3 (Unique Machine Number 3) is provided by the Virtual Machine. This is, as the name indicates, unique for each Virtual Machine. Without this feature, it could be possible to cheat the licensing system and run many instances of software without a license being purchased for each instance.   See the following technical description of the virtual machine image identifier (VMID) that provides the UMN3   A hash of the universally unique ID (UUID or SMBIOS3) that the hypervisor issues whenever a virtual machine is created or cloned. SMBIOS is commonly virtualized by hypervisor providers such as VMware and Microsoft. In addition, virtualization management systems such as VMware’s VMotion ensure that all virtual machines being managed have a unique SMBIOS value. Resolution If Virtual machines are being utilized to provide a fail-over or "hot swap" of the EBO Server then licenses need to be purchased for each Virtual Machine, just as if two physical computers were used. Each Virtual Machine will require its own License Server installation and have the required licenses activated.

Issue The SmartX server has a "?" under the server name field and shows the error "SSL certificate validation failed!" as the server state in Device Administrator. In some instances, this may cause a failure to upgrade of the SmartX Server displaying these symptoms.  Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Cause The SmartX Server is added into Device Administrator over HTTPS 443 but does not have a valid SSL certificate installed. Resolution Change the connection from HTTPS 443 to HTTP 80 This can be done by clicking into the server settings (click on the "?") Select "Edit Connection"   Change the EBO Server Protocol from HTTPS to HTTP  Create a trusted chain between Device Administrator and the problem SmartX Server using a self-signed certificate by following this workflow

Issue Would like to monitor and control points and alarms from an ESMI Fire Detection Panel in EBO. Product Line EcoStruxure Buildning Operation Environment Building Operation Automation Server Premium (AS-P) ESMI Fire Detection Panel Cause The integration between ESMI Fire Detection Panel and EBO enables the user to visualize and operate ESMI Fire detection systems effectively from graphics in EBO. Resolution The interface between the ESMI Fire panels and EcoStruxure Building Operation (EBO) is handled by the AS EN54 FIRE SmartDriver. The event and command information is sent/received by the Fire panel using RS-485 communication to/from the AS-P using the SmartDriver.   This resolution is in three steps: Enable communication via RS485 (INFO protocol in Fire panel) Use the AS EN 54 Fire Configurator to create the layout for EBO Install/configure the SmartDriver and create the Fire graphics in the AS-P   Step 1 - Enable communication via RS485 (INFO protocol in Fire panel) This video shows how to enable communication from an ESMI Fire panel and an AS-P over RS485. This is a prerequisite for using the Fire SmartDriver in the AS-P.     Step 2 - Use the AS EN 54 Fire Configurator to create the layout for EBO This video will give you a quick introduction to the AS EN54 Fire Configurator. The AS EN54 Fire Configurator is a Windows application that imports floor plans and configuration files to create the EBO interface, devices, points, alarms and graphics.     Step 3 - Install/configure the SmartDriver and create the Fire graphics in the AS-P This video shows how to connect an EBO SmartX Server to an Esmi Sense Fire detection panel (FDP). And how to create and edit the Fire graphics in the EBO SmartX Server, The fire graphics provide the user interface to visualize and operate Esmi Fire detection systems.  

Issue Could not start the TAC Xenta 102-AX LonWorks PlugIn, due to an Error message. Product Line EcoStruxure Building Operation. Environment EcoStruxure Building Operation Workstation. TAC Xenta 102 AX Cause EcoStruxure Building Operation does not support online PlugIns, as LNS is running in the background, without any communication port.. If selecting to Synchronize (Upload or Download) you will get an error message. Resolution Select "Skip" synchronize.

Issue In EBO there is no build in way to view b3 array element value. In Continuum there is a command line that allows printing array elements by specifying the array index. Product Line EcoStruxure Building Operation Environment Building Operation ASP, ASB, AS b3 BACnet devices Infinet i2 device Cause The Infinet i2 device object array values can be viewed as WebHelp. This option is not available with b3 BACnet controllers. Resolution A workaround is to use a Script program to expose the array element value. See Sample Script Program to expose b3 array element value.

Issue Poor communications between AS-P and Deep Sea Electronics (DSE) generator and switchgear modbus RTU slaves. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause When upgrading from an AS to AS-P, poor Modbus communication is seen between the AS-P and DSE slave device. The communications when using the AS was seen to be good. Using an AS-P, poor communication is seen between the AS-P and the DSE slave device. Resolution Firstly, on the AS-P, ensure the release is v3.2.3.8000 to improve the modbus RTU polling. Then if the issue still persists, make the adjustments to the DSE device as below. If the AS-P cannot be taken to v3.2.3.8000 then continue with the adjustments to the DSE device.   On the DSE Modbus slave, there are additional parameters as well as the baud rate, parity and stop bits. Access to these parameters is by using the DSE software tool. The additional parameter is the Inter-Frame delay. Change the Inter-Frame delay from 0ms to 1ms.

Issue It is not possible to select a "Trend 10K3A1" Thermistor when configuring a central or onboard IO input point. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Automation Server (AS-P) Central IO Building operation Automation Server Bundled (AS-B) Onboard IO Cause The specific thermistor type is not available to be selected. Resolution Configure an input as a resistive Input with reliability level, electrical scale and engineering scale set to: Upper/Top: 0 Lower/Bottom: 587628 Then use a Function Block 10K3A1-Ohm-To-C sample program or Script program to convert from resistance to °C. NOTE Satchwell and Trend both use 10k3A1 Thermistors but the shunt resistance used within it will vary.

Issue BBMD and BBDT Enterprise Server or Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server and Automation Server BBMD (BACnet Broadcast Management Device) IP subnet, IP router  Cause Clarification for both BACnet Broadcast Management Device (BBMD) and BACnet Broadcast Device Table (BBDT) when used within Building Operation servers. Resolution A BBMD is needed when communicating to BACnet devices on another IP segment/subnet (across IP routers). One BBMD is required per subnet; this is because IP routers block broadcast packets and BACnet uses broadcast packets to initiate and maintain communications.  Continuum CyberStation (below) or bCX4 can act as a BBMD.     A BBMD can be created in a Building Operation Enterprise Server or Automation Server.    The BBMD on the other subnet should be as below   Now all the BACnet devices should be visible on both subnets Notes No more than a single BBMD should be created on each subnet for each IP port used. Additional information about BBMDs is available on WebHelp The Teach and Learn commands are useful for larger networks with multiple BBMDs  

Issue SpaceLogic SLA CO2 units prior to date code 2138 cannot be field calibrated and ABC (Auto Baseline Calibration) is not set to ON by default. Product Line Field Devices Environment Veris Models – Cost Down version: CWE2, CWE2C, CWE2D, CWE2H, CWE2K, CWE2M, CWE2N, CWV2 Firmware prior to REV1.05.23 Prior to 2138 DC   Schneider Electric + Veris Models: CW2LA2A, CW2LA2AV, CW2LAXA, CW2LAXAV SLABLC2, SLABLCV2, SLABLCVX, SLABLCX, SLASLC2, SLASLCV2, SLASLCVX, SLASLCX, SLAWLC2, SLAWLCV2, SLAWLCVX, SLAWLCX Firmware prior to REV2.08.41 Prior to 2138 DC Cause The CO2 sensors are calibrated during manufacture, but can develop an offset during shipment or storage. Units cannot be field calibrated other than by the Auto Baseline Calibration (ABC) algorithm.  The offsets can be greater than 200PPM.  The ABC only calibrates at 30PPM a week.  That would require wait times of greater than 6 weeks. Resolution Replace with a unit with a date code of 2138 or higher or make sure ABC is enabled and wait the necessary time for ABC to correct.

Issue What TAC Xenta I/O modules could act as a Stand-Alone LonWorks device? Product Line EcoStruxure Buildings Operation, TAC Vista Environment EcoStruxure Building Operation  LonWorks TP/FT-10 Network TAC Xenta 420A TAC Xenta 421A TAC Xenta 422A TAC Xenta 450A TAC Xenta 451A TAC Xenta 452A Cause It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. Resolution It is only TAC Xenta 421A, 422A, 451A, and 452A that can act as Stand-Alone LonWorks devices. TAC Xenta 400 I/O modules without -A, will not work as Stand Alone LonWorks devices. Once communication has been established with the Xenta I/O module the green status led will flash on for 1 second every 10 seconds indicating it is in Stand-Alone mode.   In Building Operation, the Lonworks devices list will show devices without an "A" after it. This may lead to the wrong conclusion that these devices can be added as stand-alone devices, but that is not the case. These devices are listed so that they can be added manually to a programmable Xenta device as an IO module.

Issue Problem with Override control of BACnet Binary Output (BO) on IA Series BACnet Unitary, VAV and Zone controllers with firmware version 1.420 or earlier. When a BO override is released the value will not reflect the correct null state and may appear to still be in the previous state. After relinquishing the priority from the point, the actual Priority status shows up correctly as "Null". However, this is not reflected in the Building Operation Workstation "Watch" window. (Click on image below for larger view) Product Line TAC IA Series, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 Automation Server BACnet Interface with MNB 1000 with MNB 300, MNB-Vx, or MNB-70. Cause When requesting the complete "Priority Array" for an output object, the values returned match their actual values, i.e. 0, 1 or "null". When requesting individual "priority array indexes" index numbers that are "null" will incorrectly return a 0 or a 1. Resolution MNB series V1.424 firmware for the VAV, Unitary, and Zone controllers resolves this issue. When an individual "priority array index" is requested, the priority input value of 0, 1, or “null” is returned. The issue only applies to the MNB-V1, MNB-V2, MNB-70, and MNB-300. The MNB-1000 does not have the "Priority Array" problem. The MNB series V1.424 firmware files are placed in the WorkPlace Tech firmware folder during the installation of WorkPlace Tech 5.8.2.

Issue Is it possible to rename an ES after an AS has been created? Product Line EcoStruxure Building Operation Environment StruxureWare/EcoStruxure Building Operation 1.9 and lower Enterprise Server Automation Server Cause Not possible to rename the Enterprise Server or Automation Servers once attached as a multi-server system Resolution It is not possible in the earlier revisions 1.9 and lower to rename an ES or an AS once created under an ES. From EcoStruxure 2.0 and above this is possible;  Refer to WebHelp for additional details: Server Rename