Issue
How can EcoStruxure BMS server serve data to external devices or software?
Product Line
EcoStruxure Building Operation
Environment
EcoStruxure Building Operation
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.
