Building Automation Knowledge Base

Issue Availability of IPSEC on older controllers which request higher security constraints on networksLAN sites which have Andover controllers and workstations on a "flat network" but want to merge the devices into the corporate network which has IPSEC enabled. Environment Network of IP level controllers communicating with Cyberstation Cause Higher Security constraints on networksLAN sites which has Andover controllers and workstations on a "flat network" but want to merge the devices into the corporate network which have IPSEC enabled. Resolution Older versions of Andover Continuum controllers do not support network security such as IPSEC. However, the new versions of CyberStation and the new controllers, such as NetController II 9680 and ACX57x0, can be configured to communicate with controllers that do not support network security.   Another point to take note of is whether or not your site has purchased the network security option for this NetController II 9680 or ACX 57x0 controller.   IPsec is an end-to-end security scheme operating in the Internet Layer of the Internet Protocol Suite. It can be used in protecting data flows between a pair of hosts (host-to-host), between a pair of security gateways (network-to-network), or between a security gateway and a host (network-to-host).   Network Security Configuration Guide (zip)

Issue Requirements / specifications on cables used in a LonWorks network Environment LonWorks Cable Wire Guide LonMark Cause There are special requirements on cables used for LonWorks networks between Lon devices. Resolution LonMark organisation is recommending cables according to their specification. An example of this is the Belden LonWorks cable guide. Also, Echelon has a Wiring Guideline and Users Guide.

Issue Example programs for the xP Display and LD-1 Product Line Andover Continuum Environment XP Display LD-1, LD1, LD 1 ACSM Cause Need example code for these displays to act as a starting point for programming  Resolution example programs for the xP Display.  example programs for the LD-1.  Note: These applications were developed by a UK branch and should be used as a starting point for your specific application. Further information on the programming of these displays is available in The Exchange Download Center for the specific devices. xP-Display Installation and User Guide LD-1 Installation and User Guide

Issue Satchwell MZF 3-Port Flanged Valve Body requires replacement. Product Line Field Devices Environment Satchwell 3-Port Plug and Seat Flanged Valve Body MZF MZF3729 MZF3779 MZF3854 MZF3904 MZF3958 Cause Obsolescence of Satchwell MZF 3-Port Flanged Valve Body Resolution A number of alternative Schneider Electric 3-Port Flanged Valve Bodies are available to replace existing Satchwell MZF 3-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell MZF 3-Port Flanged Valve Body with S-E VG311F 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MZF 3-Port Flanged Valve Body may be retained for installation on replacement Schneider Electric 3-Port Flanged Valve Body. In such instances a Schneider Electric L9TVG Linkage Kit will additionally be required. Alternatively an Actuator from the Schneider Electric range of Actuators may be installed on the VG311F 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell MZF 3-Port Flanged Valve Body with S-E V321 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MZF 3-Port Flanged Valve Body may be retained for installation on replacement Schneider Electric 3-Port Flanged Valve Body. In such instances a Schneider Electric L8TV Linkage Kit will additionally be required. Alternatively an Actuator from the Schneider Electric range of Actuators may be installed on the V321 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the Schneider Electric VG311F and V321 3-Port Flanged Valve Bodies differ to that of the Satchwell MZF 3-Port Flanged Valve Body Similarly, the centre line to bottom of third port dimensions both of the Schneider Electric VG311F and V321 3-Port Flanged Valve Bodies differ to that of the Satchwell MZF 3-Port Flanged Valve Body As a result alterations to the pipework connected to the MZF 3-Port Flanged Valve Body will be required. Details of the Satchwell MZF 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric VG311F 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric V321 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric L9TVG Linkage Kit may be viewed here. Details of the Schneider Electric L8TV Linkage Kit may be viewed here. 

Issue Troubleshooting controllers can be aided by observing the CPU light Product Line Andover Continuum Environment Continuum controllers Cause A video created to show the differences between Normal, Error and Bootloader modes Resolution This will not show specifically what mode the controller is in, but it can offered to try to help to determine the mode. The speed of the CPU light on some of the controllers may vary, but this gives a general idea. Normal Mode is on the left, Error Mode is in the middle and Bootloader Mode is on the right. Note if the CPU LED is constant on or off see the KB article - Continuum controller CPU light solid or not illuminated

Issue To assist locating data sheets if you do not have access to the Schneider Electric BBE and other company storage areas. Product Line Satchwell MicroNet 100 series Environment MicroNet 100 series Controllers, Touchscreens, LCD, Mi and Slink data sheets. Cause To assist customers that do not have access to our internet or partner websites Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Links below to download: MLi and data sheets for MicroNet LCD Displays MLi and data sheets for MicroNet Touch Screens User Guide for MicroNet Touch Screen User Guide MLi and data sheets for S-Link Sensors Data sheets for MicroNet Manager Interfaces Mli for MN Trunking kits (MN-TK) MLi for MN Wall Mounting Kits (MN-DK) MLis for Plug-In Cards MLi and data sheets for Satchwell MicroNet MN300 Controllers MLi and data sheets for Satchwell MicroNet MN440 Controllers MLi and data sheets for Satchwell MicroNet MN500 Controllers MLi and data sheets for Satchwell MicroNet MN620 Controllers Download all of the above (file size 10.50 MB) The data sheets for MicroNet 50 series controllers ETC. can be downloaded from MicroNet 50 series controller MLi's and Data sheets.

Issue Can Value Transfer Settings be used to control the frequency at which a value is transferred over the Infinet bus? Product Line EcoStruxure Building Operation, Andover Continuum Environment Continuum i2 Controller Cause There is a need to control the frequency at which a value is transferred from one Infinet controller to another. Resolution Whether or not the Value Transfer Settings determine the value transfer rate depends on the type of reference used. When the Continuum to EBO transition process was developed, features and functionality were added to the Automation Server so that it would accommodate an existing controller protocol. Neither the Infinet controllers nor the Infinet protocol was substantially redesigned in order to work with Automation Servers. Infinet controllers have never had a Value Transfer Setting capability and it was not added when the Continuum Transition process was developed. The primary method of value transfer in Infinet controllers is the Import/Export tables. In order to enter a point into the Import Export table of a controller, the point has to be bound to an Infinet Script program or to an Infinity Alarm notification. You can find more information on the I/E functionality in the following Knowledge base article. Details on Continuum Import/Export (IE) System The Import/Export system is a highly efficient means of value transfer that is base value change. If you chose to bypass the Import/Export capability, the only method available to you to control the frequency at which values are transferred over the Infinet bus is to read these values via a program that incorporates some form of throttling to slow down the polling rate.

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server  Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Within the Automation Server logs are many records that are logged as a part of normal operations and unexpected events. Resolution Automation Server: Automation Server error logs can be retrieved using Workstation, Device Administrator, or WebStation. Device Administrator can be used in case of crash information is required, ex. dump files, or if the Automation Server is not accessible via WebStation or WorkStation. Workstation: Connect to EBO system with EBO WorkStation. Select the target Server  Expand the System folder Expand the Modules folder Expand the Trace folder and see Trace Settings For EBO 3.1 or higher, Double-click both Trace Log and System Log to open separately  For EBO 3.0 and lower, including SBO 1.x Right-click in Trace Settings Select Trace Settings in the menu Select Get System Log Repeat to select Get Trace Log  Device Administrator: Follow this WebHelp article: Getting Automation Server Debug Information If requested to retrieve a core dump, use this method to retrieve the Device Administrator Debug Information zip file. Then perform the following to make sure the zip file contains a core dump with a relevant timestamp for the event being investigated. Open Zip Open the folder containing the server name and IP address Open Server folder One should see file(s) with filename in this format core_dump_<Serial Number>_nsp_servers_<Timestamp>.tgz WebStation: EBO 4.0 (2022) and higher NOTE: You may have to enter Private Browsing mode to disable extensions, as you may see a blank page when viewing logs. Ensure credentials used are for a local 'admin' user or have access to the ~/System folder of the EBO Server you are connected. Click the 3-bar menu to navigate Select System, then Modules, then Trace One will see System Log and Trace Log in the menu, and clicking on System Log or Trace Log will open them in a new tab. NOTE: Please be patient as it may take some time to transfer the file. Once you see text in the tab, right-click on a blank area and select Save Page As... (Firefox) or Save As... (Chromium-based browser). It should recommend saving as SystemLog.txt or TraceLog.txt automatically; however, to be helpful, please add the EBO Server Name and Date to the filename. EBO 3.2 and earlier See the Webhelp Topic on collecting these logs from Automation Servers: Viewing and Downloading Automation Server Log Files. This process is now similar to that described above for WorkStation.   Credentials used to log in must be a member of a group that allows the policy of Web Configuration: Allow members to access Automation Server Web Configuration. Launch a web browser that is compatible with the installed EBO version as mentioned Webstation Specification Sheet. Type the IP address of the automation server to open the Webstation. Log into the Automation Server.                   Once logged into the Automation server, go to the Settings menu in the top right corner and click on Device Configuration. Click on the Server Log tab to view the automation server's log files. To save a copy of the log to your PC, click on the Get all log files link. The log files are compressed into a zip file and exported to downloads folder. Enterprise Server and Enterprise Central: For more information, check this article: Error logs from the Enterprise Server and Enterprise Central - Communities  

Issue Supplemental Documentation on the Menta SEQ (sequence) block Environment Menta Cause The document is intended to clarify the inputs and configuration parameters of the Menta SEQ block and when/how to use them. Resolution Click here to download a copy of this document in PDF format Click here to download the example Menta macro   Supplemental Documentation: Menta SEQ   A Brief Overview of Sequence Block The Sequence block is used to start N of M stages based on a percentage input. Each stage is represented by a single bit in the output of the block which requires calculation to determine if each stage is off or on. The Sequence block also provides the ability to rotate the stages, specify a delay between multiple stages activating, and a hysteresis to adjust the activation or deactivation of stages. The Sequence block is ideal for rotating operating stages that have high frequency of change. It is not the proper block to use for run time balancing between multiple stages. Input of the SEQ Block The input expects a 0-100 value where a 0 represents zero stages active and 100 represents all stages are active. Configuration Parameters of the SEQ Block Stages The number of stages to activate at 100% input. Rotate Rotation Flag. If Rotate is set to 0 then the first stage will always be active if 1 stage is required. If Rotate is set to 1 then the first stage to activate will be the first stage to deactivate. Period Time delay(ms) between multiple stages activating. Hysteresis Hysteresis is used to offset the activation or deactivation % for each stage. If the Hysteresis is positive then it will shift the activation % higher by that amount. If the Hysteresis is negative then it will shift the deactivation % lower by that amount. Normal Operation of 4 Stages:    Stage 1 Activation Stage 2 Activation Stage 3 Activation Stage 4 Activation Input 20% 40% 60% 80%  Hysteresis of 10%    Stage 1 Activation Stage 2 Activation Stage 3 Activation Stage 4 Activation Input 30% 50% 70% 90%  Hysteresis of -15%    Stage 1 Deactivation Stage 2 Deactivation Stage 3 Deactivation Stage 4 Deactivation Input 5% 25% 45% 65% Output of the SEQ Block The number of stages active is based on the following formula: Active Stages = ((Maximum Stages +1) * Input) / 100 The number of active stages is then encoded into an Integer as the output of the SEQ block where each bit represents whether each stage is active or inactive. Since this is a single value it must be decoded using expression blocks to detect if each bit is active.

Issue Require a Lua script for using DIM modules Environment SmartStruxure Lite Cause Using a Digital Input Module and Lua script is required to view the Inputs. Resolution For Sontay's DIM4 module download the script here. For Sontay's DIM6 module download the script here. For AXIO's DIM module download the script here. For a generic DIM module download the script here. The voltage received at the AI may need tuning. Copy and paste the text into a Lua program and create the Binary Values (BV).

Issue Modbus Register Groups feature can overcome some Modbus communication problems. It has been seen before where the Modbus controller falls offline for a few seconds then comes back online. This cycle will repeat every few seconds. When register groups are not used, there may also be issues with the amount of time it takes for a Modbus points to update. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause In a normal Modbus network, a Modbus polling device obtains data from a polled device by sending a query message to the device and then waiting for the response message that contains the requested value from the selected register. If data from another register is required, the polling device sends out a new query message and awaits the response message. This process is repeated until all subscribed points values have been read. The Modbus Register Groups are a batch read function to poll Modbus devices. Instead of reading each register individually, the batch read function reads registers in manually created groups. When all registers in a group have been read, the response message returns subscribed register values for the whole group. Register grouping provides a dramatic saving in the time taken to poll your devices. For more guidance and tips on this topic, see Section "Batch Read Function" in the EcoStruxure Building Operation Technical Reference Guide.  Note: When viewing a graphic containing Modbus values, those values will update at the same interval as their Modbus register group. Resolution When grouping Modbus points, it is important to keep in mind some of the following points. Try to ensure that as many Modbus points as possible are contained in as few groups as possible. This will reduce the overall time it takes the Enterprise Server or Automation Server to read all the subscribed points in each Modbus device. Network performance can be enhanced by choosing the method of grouping that is most suitable for each device in the Modbus network.  Network performance can be enhanced by selecting a different default poll time for each register group. Network performance can also be enhanced by grouping points that have the same or similar polls. Start with higher group poll times to ensure a stable system before reducing the poll time. Make sure to delete Modbus points out of a register group individually before deleting the group. If this is not done, it can cause system delays. See article Modbus Batch Read Multiple Registers Groups Creating a Modbus Register Group In Workstation, in the System Tree pane, right-click on a Modbus device and select New Object (1).  In the create object window select Modbus Register Group (2), provide a name and select Create (3). Now that the group has been created, existing Modbus points can be dragged and dropped into the group. New Modbus points can also be created in the group.  Right-click on the Modbus Register Group and select New Object (1).  In the create object window expand Modbus Point (2), select a point type (3), provide a name and select Create (4).

Issue Modbus TCP Device (Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus TCP Network Modbus TCP Gateway Cause Modbus TCP Device (Slave) address 248 is reserved and cannot be used. (Modbus TCP Network or Gateway) SmartStruxure supports up to address 247, as per StruxureWare Building Operation - Technical Reference Guide (up to v1.6.1). There was a defect within v1.5.0 and earlier that caused address 250 to be used if the Device address is set to "Invalid." This defect was corrected in v1.6.1. Resolution From v1.9 this is corrected, so it is possible to define addresses for Modbus TCP devices from 1-247 and 249-254 Device addresses 0 and 248 are reserved. Device address 255 is used as the Default address.   For Modbus RTU RS485 master/slave networks, slave device addressing is different, see KB article Modbus RTU slave address.   Further information about Modbus can be found in the KB article Modbus basics.

Issue How to add Basic Authentication header to SendWebRequest function in Script RESTful Web Services 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 Cause A 3rd party web service requires basic authentication for HTTP requests to ensure that data is requested securely, otherwise, the request will be rejected with an "Authorization Error".   Resolution Basic Authentication is a type of Authorization Request Headers, which transmits credentials as user-id/ password pairs, encoded using Base64, as defined in RFC 7617 - The 'Basic' HTTP Authentication Scheme (ietf.org).  Follow the below steps to create a Basic Authentication header in Script RESTful Web Services: Combine the User ID and the Password with a colon ex. "aladdin:opensesame". Encode the resulting string in base64 using script function to base64 encode a string posted in the Community or using the online encoder as Base64 Encode and Decode - Online, ex.  "aladdin:opensesame" will be "YWxhZGRpbjpvcGVuc2VzYW1l" after Base64 encoding. Construct SendWebRequest header in the following format:  Authorization: Basic <credentials>, as below example:  Headers= "Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l"'User ID=alaadin Password=opensesame Resultstring= SendWebRequest(BaseUrl,Method,ContentType,Headers,Message) Note: Basic Authentication is not a secure method of user authentication unless used in conjunction with HTTPS/TLS, as the user ID and password are transmitted as clear text. User ID and Password are Base64 encoded but Base64 can be easily decoded.  For more information refer to Script RESTful Web Services WebHelp and Authorization - HTTP | MDN (mozilla.org)

Issue Define I/A Series AX/G3/N4 software compatible with a specific version of Windows Product Line TAC IA Series Environment I/A Series (Niagara) AX/G3/N4 software Windows 32-bit and 64-bit operating systems Cause Only specific releases of the I/A Series AX/G3/N4 software have been certified compliant with specific versions of the Microsoft Windows software.  Resolution The following chart details the version compatibility between the releases of the I/A Series G3/N4 software and various versions of the Microsoft Windows Operating System software.   Refer to Supported Operating Systems for Niagara 3.7 and earlier (June 2016) Refer to Supported Operating Systems for Niagara 3.8 (July 2020) Refer to Supported Operating Systems for Niagara 4.1, 4.2, and 4.3 (September 2019) Refer to  Supported Operating Systems for Niagara 4.4 and higher (March 2025)   For the larger Schneider Electric BMS offering please refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation

Issue TAC EM 5 Actuator requires replacement. Product Line Field Devices Environment EM 5 EM5C EM5 Actuator Cause TAC EM 5 Actuator requires replacement Resolution The TAC EM5 Actuator is totally obsolete and no direct replacement is currently available. Details of the TAC EM5 Actuator can be found in EM5 OBSOLETE.tmp.pdf. The TAC EM5 Actuator was capable of use in control systems having alternative electrical wiring connections.   Alternative 1 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA DC positioning signal. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. Details of the S-E MD10A-24 Actuator may be viewed in MD10A S-E.pdf. N.B. The S-E MD10A-24 should be checked for electrical compatibility with other control system devices that it is to be integrated with. It is unlikely that it will be mechanically compatible with the other control system devices such as the Control Valve Body. Arrangements may therefore need to be made for the design and manufacture of a suitable Linkage Kit.   Alternative 2 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA positioning signal with 16 Vdc output. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. It should be noted however that no 16 Vdc output is available from the S-E MD10A-24 and none can be connected. A 16 Vdc power supply should therefore be installed to provide power to any external Controllers or Auxiliary Units.

Issue For EBO Active Directory (Windows Domain) integration, do EBO support usage of "nested groups"?. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause EBO are using Windows API and ask if the user is a member of a certain group.  Resolution Windows API should respond “yes” if the user is part of a group that is part of another group, which is configured in EBO. So this is up to how the Windows AD responds to the Windows API and not on the EBO side.   For more information, please see Integrating Windows Active Directory user accounts with EcoStruxure

Issue Software download location. Where can I download "MicroNet View's Monitor Tool" dongleless software as advised in: PA-00145 - Satchwell MicroNet Range Rationalisation Product Line Satchwell MicroNet Environment MicroNet View Monitor Tool   Cause The MicroNet View dongleless Monitor Tool, software can no longer be ordered, it is available as a free download. Resolution Download the software from The Exchange or Click here to be linked to the Monitor tool. (This link will open a new page) Click here to be linked to the SNP I/O server. (This link will open a new page) Click here to be linked to the NCP/ARCnet I/O server. (This link will open a new page). Click here  to be linked to the USB dongle driver for MicroNet View, that may be required with faster PC's (This link will open a new page).  

Issue ISO 9001 certificate for Schneider Electric Buildings Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices,Other, TAC INET, TAC Vista Environment Management Certification Certificate for the Design and Manufacture of Building Management System Controllers, Devices and Electronic Systems Cause ISO9001 certificates are sometimes requested for different projects. Resolution Download the ISO 9001:2015 certificate here.

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 MNL-V1RVx, MNL-V2RVx and MNL-V1RVx-2, MNL-V2RVx-2 differences Environment I/A Series Micronet LON VAV controllers Cause Part number MNL-V1RVx has been replaced with MNL-V1RVx-2 and part number MNL-V2RVx has been replaced with MNL-V2RVx-2.  The datasheet F-26365 indicates the parts as MNL-V1RVx and MNL-V2RVx.  Resolution The MNL-VxRVx and the MNL-VxRVx-2 are functionally the same. The '-2' was added to the part number to indicate an enhancement to the VAV actuator assembly to reduce the operation noise level of the actuator.