Building Automation Knowledge Base

Issue After successfully logging in, the controllers' web page is only partially displayed, showing broken image links and incorrectly formatted text. Resetting the controller does not resolve the problem. SP-C Configuration Web Page Product Line EcoStruxure Security Expert Environment Security Expert SP-C SP-AC1 SP-ACX Cause Incorrect controller web page files have been cached in the browser. This may occur if different controller firmware versions are viewed/commissioned on the same PC.  Resolution Clear the web browser's cache and try again.  Connect directly to the controllers' configuration page. For a controller with default settings, browse to 192.168.1.2/config.asp.

Issue How to configure the Security Expert system to use multiple Custom Credentials on the same door Product Line EcoStruxure Security Expert Environment Custom Credentials Cause The older inbuilt Card Formats used Primary and Secondary Reader Formats to allow two Card Formats to be used on the same Door.  But how is this functionality achieved with Custom Credentials? Resolution It is possible to add two or more Custom Credentials to a single Door.  However, when you do this it is instructing the system to request the First Credential AND the Second Credential before granting access to that Door (perhaps even in sequence) If in fact the system is required to request EITHER the First Credential OR the Second Credential before granting access, then the Fallback Credential feature is used. This allows for as many Custom Credentials on a single door as needed.   Please see demo video below:

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 When several Floor Plans or Status Pages are open at the same time the Security Expert Client slows down and eventually closes to desktop with a “Security Expert User Interface has stopped working” error message shown. Error Message Product Line EcoStruxure Security Expert Environment Security Expert Client Cause Security Expert Client is gradually using up system RAM. As the Security Expert Client reaches or exceeds, the windows 32-bit application memory limit, the Client crashes.   The reason for this excessive memory usage was due to the user photo sizes which were found to be very large (approx. 10MP with 5.9MB file size each). The sheer number of User Events displaying these images in multiple windows at the same time eventually overloads the application. Resolution Reduce the size of the User images to a much smaller size. The default, which is a good starting point is 300x400 pixels. One method of doing this would be to export, batch resize then import the photos back into the database. *** Backup the Security Expert database first *** User photos can be exported out of Security Expert by using the inbuilt feature under Global | Sites | User Photos Export. You set a directory, choose a format, and use the Export User Photos Now button to export all the photos when you're ready. User Photos Export Next, use a batch image resizing application to resize and crop the images in one step. There are lots of applications that can do this such as Photoshop or Microsoft's free Photo Resizer app. Once the images are resized you can use the Data Sync Service to then import those images back into Security Expert. Find details on how this is done in AN 266 Security Expert - Mass Importing Photos into - Integration Guide. Using two Security Clients running on the same machine can also provide a bit more headroom before the memory limits are hit as the load is spread out over two applications instead of just the one. This would be an additional safeguard if multiple Floor Plans and Status Pages open at the same time was a requirement. Reducing the User image file sizes is what will have the most impact on stability and responsiveness.

Issue The License server cannot be seen by either the Workstation or Enterprise Server Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation Workstation Building Operation Enterprise Server Cause When attempting to log onto a system using Workstation, or start an Enterprise Server, the license is not seen on a remote License Server. Resolution Make sure your firewall setting is not blocking the license system. For more information read SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96) The system consisted of a PC running the Building Operation License Server. The license on the PC had been generated from an entitlement for an Enterprise Server, Workstation and program editing tools. A second PC was running the Workstation and Enterprise Server programs. Confirming that the correct licenses are available on the License server. On the License Server, select Internet Explorer and enter http://localhost:8888 in the address bar. Select the "Concurrent View" Below shows the page displayed, confirm that the expected licenses are shown. Check that the License administrator has the correct address of the license server. Open the license administrator and select the "License Server Address" tab. NOTE: the @ symbol before the IP Address must be used.

  Issue PIBCV valves, stem up or stem down for valve open. Product Line Field Devices Environment PIBCV Valves VP220, VP221, VP222, VP228 Cause Further information required as to whether stem up or stem down for valve open position. Resolution When the stem is up (retracted into the actuator) the valve is open.   Example:

Issue The MNB-1000-15 status light is solid red.   Environment WorplaceTech, MNB-1000, MNB-1000-15 Cause The MNB-100-15 (Remote IO) was not added in the MNB-1000's application. Resolution The Remote I/O module must be configured in the MNB-1000’s application. Also at least one of its inputs (R1U10x) or outputs (R1UO0x), must be connected to an input or output in the MNB-1000’s application. If a MNB-1000-15 input/output object is placed in the MNB-1000 application unconnected, it will not be recognized by the MNB-1000 and the MNB-1000-15 status led will be solid red.  

Issue A new feature in EBO 3.2.X where the value is grayed out when the binding on the priority of a BACnet object matches the BACnet Default priority level Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Missing Release note documentation about the new feature added to EBO 3.2.X. Resolution In EBO versions prior to 3.2.X, when a bind in Priority matches the Default BACnet Write Priority, the values can be changed without forcing. From EBO 3.2.X, users need to force the value, let it change, and then un-force it. The following screenshots show this feature in more detail. The following image shows the Default BACnet write priority has been set to 16. Now, for example, if a program output is bound to Priority 16 of an analog value: The value property would be greyed out and has to be forced if changes are needed.   This is a new feature in EBO 3.2.X which is not mentioned in the Release Notes documentation.   Hint: A defect # 45570 has been documented in Release Notes 3.2.X about “Webstation - BACnet analog value's value property is not greyed out when there is a bind to the default priority.”. This issue has been fixed in EBO 4.0.X.   

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 at Exchange:  EcoStruxure Building Operations SmartConnector 

Issue Are there replacement part numbers for the MNL-V1RV3 and MNL-V2RV3 circuit board and base actuator assembly? Environment MNL-V1RV3 and MNL-V2RV3 Cause Replacement of circuit board and / or base actuator assembly required. Resolution MNL-V1RV3 circuit board assembly is MNL-V1RV3-500 MNL-V2RV3 circuit board assembly is MNL-V2RV3-500 Actuator base assembly is MN-FLO-701

Issue Controller is unresponsive and does not respond to a hard reset or power cycle with the battery disconnected..  CPU light remains on constantly. Product Line Andover Continuum Environment InfinityController, b3 Controller NetController II, CX9680 ACX57 bCX Cause Controller stopped functioning after power cycled. Resolution Test controller with a known working PS power supply and/or test the supply voltage is correct If the controller still does not respond to a hard reset then return for repair. See the appropriate manual for reset instructions

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 Where can I find Plain English Drivers and documentation for them. Environment Plain English Drivers Cause Schneider Electric Product Support Services does not supply Plain English Xdrivers, nor are they supported. Resolution Schneider Electric does not provide support for Plain English Drivers and no longer provides support for them There are, however, two xdriver manuals available on The Exchange Download Center. Carrier CCN Dataport Manual (32MP, 30GN, 30GB, 30HX, 30GT, 23XL, 19XR, 19EF) Mammoth DDC Manual

Issue Unit Conversion Exceptions Unit selection of 'bar' defaults to N/m 2 unit Units are not displaying unit as selected in the properties Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 and above Cause Building Operation supports both the SI metric system and the US Customary System for units of measurement. The operating system regional settings on which WorkStation is installed determine whether SI units or US Imperial units are displayed. The conversion between the two measurement systems is managed automatically. For example, the temperature 42,82 °C is stored in Building Operation. A WorkStation on an operating system with the US Customary System converts the temperature and displays it as 109.08 °F. To display the original unit of a value in WorkStation, open the Properties pane for the value and go to the Unit selection dialog box. As part of this process some units selected, default to a default display unit, and not what was originally selected.  For example, selecting the pressure unit 'bar' when configured in a SI regional setting will display by default the unit 'N/m 2 ' and not 'bar' as selected.  This functionality is as per design but can be altered by using the Unit Conversion Exceptions feature. Resolution First reference Adding a Unit Conversion Exception on the Building Management WebHelp site.    In the release version 1.2 and above there is a feature that allows the operator to create unit exceptions, called Unit Conversion Exceptions.  This is located under the Domain folder and allows various conversions for different domains.  The steps below indicate how this is achieved. Locate the Unit Conversion Exceptions under the required Domain The Unit Conversion exceptions are now displayed in the Workspace.  The Add remove buttons are located at the bottom of this workspace Add the Configured unit, which is the selected unit for the variable you wish to be converted Then change the SI Display Unit and / or US Display Unit to the desired unit you wish the configured unit to be displayed / converted too Save these changes and confirm that it is now displayed in the desired unit.  In some cases you may need to log out and then back in for the changes to be applied. Online Web Help is also available here: If your system is based in US region then you can default you measurement system to US as per Metric vs. English (Imperial) Operating System.

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 is the purpose of modbus registers 35 and 36 in the TC900. Product Line Field Devices Environment TC900 Cause Further detail required for registers 35 and 36 and how they interact.   Resolution The TC900 allows either the onboard sensor or an external sensor or a value e.g. a temperature value binded to a modbus (16bit unsigned) value be written to the TC900 and be used.   Register 24 determines if the in-built sensor (00) or the external sensor (01) is displayed on the screen If register 35 = 00, then the sensor set in register 24 is displayed.   Register 36 has the ability to be the binded sensor and be written to (FC06) with a value x10. e.g 23.5 should be writte as 235. If register 35 = 01, then the value in register 36 is displayed on the screen.   However, if register 23 = 01, then the setpoint is displayed on the screen.   Note, in the TC900, registers start at 0000, therefore in EBO add '1'.  

Issue How does the import/export (IE) system work in the Continuum controllers? Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller. The principle is that the value of a controller point that is referenced by other controllers on the network only needs to be sent out when it changes, much like the BACnet COV which stands for Change Of Value. The two parties involved in the IE transaction are the controller that owns the point (the owner) and the controller(s) referencing the point's value (the subscribers), a second CX controller may also be involved and acting as a router when a value is imported/exported from/to a remote field device under a remote CX. Resolution Read more in the attached document, Understanding Continuum IE System.  See how to correct Import Export tables KBA

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Proper configuration of supervised inputs, Mercury IO modules (i.e MR52) versus Continuum IO modules (AC1/AC1Plus) for transitioned Continuum sites. Product Line EcoStruxure Access Expert Environment Access Expert Controller Access Expert Reader Interface Access Expert Premise Software Access Expert Hosted Software Continuum AC-1 IO Module Cause Guidance is needed on the proper configuration of Access Expert custom EOL resistor tables in order to achieve full supervision of inputs associated with readers/doors. Full supervision in this context means not only being able to detect normal input operation (activation/deactivation) but also detection of attempts to tamper with the input's circuit (short circuit, open circuit, grounding, the introduction of foreign voltages, etc.) Please note that not all resistor configurations can detect all the various circuit issues, for example, a NO Series resistor configuration can't detect a cut in the wire given that the open circuit is the normal state for the Deactivated value of the input. The resistor configuration that provides the most supervision is the Series/Parallel configuration, using 2 resistors is possible to detect both short and open circuits. Resolution Continuum supported a fixed 10K Ohms resistance for supervised inputs, furthermore, Continuum IO modules (AC1/AC1Plus) transitioned to Access Expert under an AX-SSC controller continue to operate with Continuum firmware, this means that they do not support the custom EOL tables in Access Expert, the only configuration that is possible for AC1/AC1Plus modules is the mode of connection of the resistor (parallel, series or both).   Also, when using 2 resistor configuration, the placement of the resistor is different in Continuum compared to Mercury hardware   CONTINUUM When the switch is open only the resistor on the left is seen by the input. When the switch is closed, the two resistors are presented to the input in parallel with each other resulting in the input reading half the sum of the total resistance value.   SECURITY EXPERT       When the switch is open, the two resistors will be presented to the input in series with each other resulting in the input reading the sum of the two resistors value.  When the switch is closed only one resistor is presented to the input   For the above reasons, Continuum transitions sites where the AC1/AC1Plus has been replaced with Mercury hardware like the MR52 for example, need to configure one or more custom EOL table(s) for 10K resistors.   *** The sample tables provided below contain resistance values calculated to take into account wide variations in total supervised loop resistance due to wire distance, gauge etc., supervised loops should be installed in accordance to distance and gauge guidelines for wires as well as recommended resistor tolerance. It may be necessary to make adjustments to the resistance values in the tables on a site by site basis.   See below sample tables for all six possible 10K resistor configurations   Normally Open Parallel (10K-NO-P) Normally Closed Parallel (10K-NC-P) Normally Open Series (10K-NO-S) Normally Closed Series (10K-NC-S) Normally Open Series/Parallel (10K-NO-SP) Normally Closed Series/Parallel (10K-NC-SP)+ 1. Normally Open Parallel (10K-NO-P) 2. Normally Closed Parallel (10K-NC-P) 3. Normally Open Series (10K-NO-S) 4. Normally Closed Series (10K-NC-S) 5. Normally Open Series/Parallel (10K-NO-SP) 6. Normally Closed Series/Parallel (10K-NC-SP)+

Issue Is it possible to use existing in-built Custom Formats and the new Custom Credentials in Security Expert on the same reader at the same time. Product Line EcoStruxure Security Expert Environment Card Formats Custom Credentials Cause A library of inbuilt Card Formats has been in Security Expert for some time. Primary and Secondary Reader Formats allow 2 different inbuilt Card Formats to be used on the same Reader. What happens when a user tries to introduce the newer Custom Credential? Resolution Primary and Secondary Reader Formats can still be used in on the same Reader in Security Expert when using inbuilt Card Formats.  However once using newer Custom Credentials a Reader can either use an inbuilt Card Format OR a Custom Credential BUT NOT BOTH.  

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 Some of the fieldbus controller Output values presented on the Infinity controller's webpage do not agree with those values when viewed from Cyberstation and WebStation.  Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Cause Some controller outputs configuration are limited to specific output types.  On the b3920 for example outputs 9 through 16 cannot be configured as digital outputs.   The ElecType (the outputs electrical type) stored in the Continuum database should match the output configuration in the controller's database.  But this is not always the case.  This can happen when the output configuration was imported from a text file.      Controller output configuration viewed while the workstation is in Online mode   Controller output configuration viewed while the workstation is in Offline mode     When the controller webpage is displayed in a browser, the parent controller (cx9900, cx9680, bcx4040, bcx9640) makes a call for the point value to the fieldbus controller.  If the ElecType for the output which is stored in the Continuum database is incompatible with the controller's output type, the parent controllers' call for the output value will fail. Resolution Switch CyberStation to Offline mode Correct the outputs ElecValue to an appropriate type for the controller output Return CyberStation to Online mode Reload the fieldbus controller