Document Version: V1.1
Gateways & Firmware Requirement:
| Software | E2C Factory | E2C Field | E2C Facility |
|---|---|---|---|
| Gateways supporting | EG3120 EG5120 EG5200 | LG3120 | LG5120 |
| Firmware Requirement (RobustOS Pro Version) | ≥ 2.3.103 | 2.4.110 | (TBD) |
This manual guides technicians to quickly configure the Robustel edge computing gateway to collect data from Southbound BACnet devices (BACnet/IP or BACnet MS/TP). It also covers how to forward the collected data to Northbound systems using MQTT or an OPC UA Server.
This manual is written for field implementation engineers and technicians. You do not need deep theoretical knowledge of the BACnet protocol. By following these step-by-step instructions, you can easily connect devices, read data points, and forward data.
In the BACnet network, the Robustel Gateway acts as the data forwarding machine. Its job is to actively initiate requests, read data from the underlying BACnet devices (such as HVAC controllers, chillers, or smart meters), and then translate this data into IIoT protocols (like MQTT/OPC UA).
| Device Type | Specific Requirements |
|---|---|
| Gateway | Robustel Gateway with E2C Field / E2C Factory / E2C Facility software installed. In this document, we use LG3120 with E2C Field for an example. |
| BACnet Device | BACnet/IP device or BACnet MS/TP device (must know its IP or Serial settings). |
| Wiring | Standard Ethernet cable (for IP) or 2-wire RS485 cable (for MS/TP). |
| PC | A laptop connected to the gateway's LAN port for web configuration. |
If your field device uses a network cable (Ethernet), follow this chapter. If it uses an RS485 serial port, skip to Chapter 5.
Purpose of this step: To establish basic network communication. The gateway's LAN IP must be configured so it can successfully "ping" and communicate with the target BACnet/IP device over the Ethernet network.
(Note: If crossing subnets, ensure routers are configured correctly and BBMD is properly handled for device discovery).
| Parameter Name | Configuration Description | Recommended / Example Value |
|---|---|---|
| IPv4 Address and Subnet Mask | Set the gateway's IP to be in the same subnet as the end BACnet device. | e.g., 192.168.1.1/24 (if device is 192.168.1.100) |
Purpose of this step: To define the target device in the Data Collection engine so the gateway knows exactly which IP address and port to send data requests to, and how to identify itself on the BACnet network.
First, click Edge Computing in the gateway's Web GUI to enter the E2C Field software. Then follow these steps to add a BACnet IP Device.
Method 1: Manual Configuration
| Parameter Name | Configuration Description | Recommended / Example Value |
|---|---|---|
| Device Name | Create a custom name for easy identification on the platform. | e.g., Chiller_01 |
| Driver (Protocol) | Select the protocol type for the Southbound device. | BACnet IP |
| Local Network | Select the LAN port that connects to the BACnet IP device. | e.g., br_lan(192.168.1.1) |
| Port Number | The communication port for BACnet/IP services. | Keep default 47808 unless specified otherwise. |
| Device ID | The ID of the BACnet IP device. | e.g., 1111 |
Method 2: Auto Search (Recommended)
If you are unsure of the device's specific parameters, you can use the Auto Search feature to discover BACnet/IP devices on the network.
Purpose of this step: To define which specific sensor values or registers (data points) need to be read from the added BACnet device.
Method 1: Auto Search (Highly Recommended) BACnet protocol supports network discovery. This is the fastest way to add points.
Method 2: Manually Add If Auto Search fails or is not supported by the end device, you can add points manually based on the manufacturer's Point List. Click Manually Add and configure:
| Parameter Name | Configuration Description | Recommended / Example Value |
|---|---|---|
| Collection Mode | Select Polling or Subscription Mode | e.g., Polling |
| Name | Tag name, a readable name for the data point. | e.g., DO1 |
| Tag Type | Select Device Tag or Virtual Tag. For reading data from device, select Device Tag. | e.g., Device Tag |
| Object Type | The type of the BACnet object. Refer strictly to your device's Point List. | e.g., Analog Input (AI), Binary Output (BO) |
| Instance Number | The unique register/instance number for this specific object. | e.g., 17 |
| Data Type | The data format of the point value. | Select according to the Point List. |
| R/W Permission | Select Read Only or Read & Write. | e.g., Read & Write |
If your field device uses a 2-wire RS485 serial connection, follow this chapter.
First, click Edge Computing in the gateway's Web GUI to enter the E2C Field software. Then follow these steps to add a BACnet MS/TP Device.
Purpose of this step: To align the gateway's serial port hardware settings with the field device. In RS485 communications, all devices on the daisy-chain must speak at the exact same speed and format, otherwise, no data can be read.
Warning: Ensure the RS485 wiring is correct (A to A, B to B). If communication fails later, try swapping the A and B wires.
| Parameter Name | Configuration Description | Recommended / Example Value |
|---|---|---|
| Baud Rate | The communication speed. Must exactly match the end device. | Usually 38400 or 9600 |
| Data Bit | The length of the data payload. | 8 |
| Check Bit | No Parity / Even Parity / Odd Parity | No Parity |
| Stop Bits | The end-of-byte signal length. | 1 |
| Parity | Error checking method. | None |
Purpose of this step: To tell the Data Collection engine which serial port to listen on and what the MS/TP MAC address (Station ID) of the target device is.
Method 1: Manual Configuration
| Parameter Name | Configuration Description | Recommended / Example Value |
|---|---|---|
| Device Name | Create a custom name for easy identification on the platform. | e.g., Chiller_01 |
| Driver (Protocol) | Select the protocol type for the serial device. | BACnet MSTP |
| Communication method | Select the serial port that connects to the device. | e.g., /dev/ttyCOM1 |
| Local Node Address | Set an address of the Edge Gateway itself. | e.g., 0 |
| Maximum number of frames per message | Set the maximum number of frames per message. | e.g., 5 |
| Maximum number of primary devices | Set the maximum number of primary devices. | e.g., 10 |
| Device ID | Set the ID of the BACnet MS/TP device. You can get this value from the specification document of the device usually. | e.g., 1 |
| Polling Cycle | Set the polling cycle time. | e.g., 1 |
Method 2: Auto Search (Recommended)
If you are unsure of the device's specific parameters on the serial network, you can use the Auto Search feature to discover BACnet MS/TP devices.
| Parameter Name | Configuration Description | Recommended / Example Value |
|---|---|---|
| Device Name | Create a custom name for easy identification on the platform. | e.g., Chiller_01 |
| Driver (Protocol) | Select the protocol type for the serial device. | BACnet MSTP |
| Communication method | Select the serial port that connects to the device. | e.g., /dev/ttyCOM1 |
| Local Node Address | Set an address of the Edge Gateway itself. | e.g., 1 |
| Maximum number of frames per message | Set the maximum number of frames per message. | e.g., 5 |
| Maximum number of primary devices | Set the maximum number of primary devices. | e.g., 10 |
| Polling Cycle | Set the polling cycle time. | e.g., 1 |
Purpose of this step: Let the software know which point data to read.
Method 1: Auto Search (Highly Recommended) BACnet protocol supports network discovery. This is the fastest way to add points.
Method 2: Manually Add If Auto Search fails or is not supported by the end device, you must add points manually based on the manufacturer's Point List. Click Manually Add and configure:
| Parameter Name | Configuration Description | Recommended / Example Value |
|---|---|---|
| Collection Mode | Select Polling or Subscription Mode | e.g., Polling |
| Name | Tag name, a readable name for the data point. | e.g., DO1 |
| Tag Type | Select Device Tag or Virtual Tag. For reading data from device, select Device Tag. | e.g., Device Tag |
| Object Type | The type of the BACnet object. Refer strictly to your device's Point List. | e.g., Analog Input (AI), Binary Output (BO) |
| Instance Number | The unique register/instance number for this specific object. | e.g., 17 |
| Data Type | The data format of the point value. | Select according to the Point List. |
| R/W Permission | Select Read Only or Read & Write. | e.g., Read & Write |
Once the configuration is complete, it is crucial to verify that the gateway is successfully communicating with the field devices and collecting accurate data.
Purpose of this step: To confirm if the gateway has successfully established a connection with the Southbound BACnet device.
Purpose of this step: To verify that the configured data points are successfully returning valid readings from the field device.
Purpose of this step: To send control commands back to the field device (e.g., turning on a relay or setting a new temperature setpoint).
Once the gateway successfully reads data from Southbound BACnet devices, you can forward this data to the Northbound platform.
Purpose of this step: To organize the collected BACnet data points into logical groups before sending them to the cloud or application systems. Grouping allows you to control exactly which data points are packed and uploaded together in a single payload.
(Note: You will use this created Group in the following MQTT transmission settings to define the upload payload).
This scenario is used to push data to cloud platforms (like AWS, Azure, or private IoT platforms).
This scenario is used to provide data to local factory SCADA or BMS systems. The gateway acts as an OPC UA Server, waiting for the SCADA to connect to it.
| Symptom | Possible Cause | Solution |
|---|---|---|
| BACnet/IP: Cannot search any devices or points | 1. Gateway and device are in different subnets without BBMD. 2. Target IP or Port is incorrect. | 1. Ensure the gateway IP is in the same subnet as the target, OR properly configure BBMD for cross-subnet discovery. 2. Verify the Target IP and Port (Default 47808). |
| BACnet MS/TP: No data | RS485 wiring is reversed OR Baud rate does not match. | 1. Swap the A and B wires physically. 2. Check Serial Ports Configurationto ensure Baud Rate matches the device. |
| Both: Status show red (Read Failed) | The device does not support the requested Object Type or Instance Number. | Check the manufacturer's manual. Manually add the point and ensure the Instance Number is exactly correct. |
| MQTT: Fails to connect | Gateway has no internet access or wrong broker info. | Check if the gateway's WAN/4G interface is online. Verify Broker IP and Port. |
For quick on-site configuration, refer to these industry-standard default values. Unless explicitly required by the site, do not change them:
| Parameter Name | Protocol | Default/Recommended Value | Description |
|---|---|---|---|
| Port | BACnet/IP | 47808 (UDP) | Standard BACnet/IP Port. |
| Device ID | BACnet/IP | Unique number (e.g., 200) | Must not duplicate other devices on the LAN. |
| Baud Rate | BACnet MS/TP | 38400 or 9600 | Must match the end device perfectly. |
| MAC Address | BACnet MS/TP | 1 to 127 | The Slave ID of the end device. |
| AI (Analog Input) | Point Object | Sensor values | Temperature, Pressure, Level (Read Only). |
| AO (Analog Output) | Point Object | Control values | Valve position, Fan speed (Read/Write). |
| BI (Binary Input) | Point Object | Digital status | Switch ON/OFF, Fault Alarm (Read Only). |
| BO (Binary Output) | Point Object | Digital control | Relay ON/OFF command (Read/Write). |