Building Automation Knowledge Base

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 How to change the IP address of the Automation Server and ensure proper communication. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Building Operation Device Administrator Building Operation Workstation Cause At times the IP address information for an Automation Server must be changed after being added to an Enterprise Server to accommodate changes in IP network design, correction of incorrect data, or any other reason. Changing the IP address needs to be done in the proper method to avoid artifacts and confusion after the change. Resolution To avoid complications, follow this process to modify the IP address of an Automation Server that is already communicating with an Enterprise Server. In the Building Operation Device Administrator connect the AS controller via USB or IP.  WebHelp Topic Connect to SmartX Servers Right-click on the AS and select Network Settings Modify the IP address settings to the new values Additionally, this can be changed through PuTTY with the "setip" command. Power Cycle the Automation Server (If a power cycle is not completed the AS will still have invalid data for network settings despite the physical network interface running with the new settings) Start Building Operation Workstation and log in to the Enterprise Server Select the Enterprise Server and open the Communication Tab Highlight the Automation Server that needs to be changed and modify the address field for the IP address of the device. (The Communications settings tab is enabled by selecting the Show/Hide tick icon). Click the Save button The Enterprise Server should now automatically establish communication with the AS, but if you want to speed this process you can right-click the Enterprise Server and select the "Advanced\Repair Server Communication" option. IMPORTANT: As of 1.41 if the IP address is changed on a server that is configured with a BACnet interface, the IP address and possibly the broadcast address of the IP Network under the BACnet interface must be updated manually. (see below)

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 How many objects, users, devices, etc. per device with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server WorkStation 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  and on WebHelp Topic for the version being used

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

  Issue TAC Xenta I/O modules working as LonWorks device, indicates offline, flashes fast after power restore. Product Line TAC Vista, EcoStruxure Building Operation Environment XENTA421A XENTA451A Cause When the TAC Xenta I/O modules are used as Lonworks devices, this is indicated by the LED that flash once every tenth second. After a power failure, the device will indicate offline by 5 flashes per second.   The device will indicate offline until it gets an update to any nvi or nci variable. Resolution As soon as the device gets an update on any nvi or nci, it will again start to flash once every tenth second. This means, that if you only read variables from the device, that is, only uses its inputs, it may indicate offline until the next time the configuration is changed.   A workaround for this issue could be to just use a dummy output, that is updated regularly.  

Issue SE7000/SE8000 controllers are randomly going offline or are undiscoverable on BACnet network. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE7000 SSL SE8000 Cause Improper terminations of the BACnet MS/TP communication cable.   Resolution The REF (reference) Terminal is a BACnet Reference which is a voltage reference required by BACnet testing lab (BTL) and it is rarely used in the industry. If not used as a reference, The Ref terminal should be left empty. It is not a terminal to land a shield nor a ground.    At each thermostat (Cable Junction) : Connect the (+) and the (-) wires Twist the shields together Tape around the cable to prevent short-circuit. Ground the shield at one end only (usually on the BAS side) and leave the REF terminal empty Ensure that the shield wire is not connected to the REF (Reference) terminal.

Issue SE7000s (all) and old hardware SE8000 (firmware <= 1.7.4) won't support EBO Zigbee. Product Line EcoStruxure Building Operation Environment SSL SE7000 SSL SE8000 Cause EBO Zigbee has Standard and High-Security levels. The SE7000s and old hardware SE8000 (firmware <= 1.7.4) only supports Zigbee Low Security. Resolution Replace the SE7000s and SE8000s old hardware using SE8000 with the current hardware that supports firmware 2.0.0 and newer.

Issue What does that controller/device look like Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Site with TAC or Schneider Electric Controller(s) Cause Questions concerning what a controller looks like, or if there are no labels on the controller which help identify. Are photographs or drawings available? (This is an article in progress. Have one that is not listed? Please help by taking a good picture(s) and including or send to Product Support) Resolution I/NET: 7728 7728 Left side 7728 Right side  7790 7790 side 7790 older model  7790 older model side  7798C Top 7716 7920 7920 side  MR-AHU MR-AHU left side MR-AHU right side P8UI8DO Expansion board  SCU1284 SCU1284 side Continuum: ACX5720 ACX5720 Open CX9702  b4920 b4920 Open BCX1 BCX1 open i2-600 Series i2.600 Series Open  i2_850 i2_850_Open i2_887_L_115  i2_920 i2_920_open CX9400 with three 32s and two 16s in 8 card rack CX9400 CPU front CAD Drawings for the Continuum controllers are also available on The Exchange Download Center: Link Here.

Issue When EcoStruxure Building Operation (EBO) is installed after TAC Vista on the same PC, changes to the national character set in the OP Configuration Tool in Menta cause an error preventing the generation of the MTA file. The error appears when the Generate command is selected in Menta. Depending on the combination of versions of EBO and TAC Vista, the error message is: "National character set not selected" "Cannot open file: struxureware path\ national.dec" (where struxureware path is the location of the Schneider Electric StruxureWare\ Building Operation 1.x installation folder) "ERROR! Failed to create OLE dispatcher: GraphOP.Application.320, GraphOP.Application.NSP" Product Line TAC Vista, EcoStruxure Building Operation   Environment Building Operation Workstation Vista Workstation Cause The installation of EBO overwrites settings in Menta regarding character sets. When Menta is opened with normal user rights, changes to character sets in the OP Configuration Tool are not saved due to the OS user security settings. Resolution Right-click on Menta in the program list and select "run as administrator". Then select your required character set in the OP Configuration Tool ("Formats | Character set file"). The changes can now be saved and Menta will generate successfully. This procedure is only required the first time you run Menta after installing EcoStruxure Building Operation. Normal user rights can be used for subsequent editing sessions.