Click to download this document.
Version History
Updated | Document Version | Description |
2026-08-18 | V1.1 | Optimize image description |
2026-06-18 | V1.0 | Initial version |
Gateways & Firmware Requirement
Software | E2C Factory | E2C Field | E2C Facility |
Gateways supporting | EG3120; EG5120; EG5200 | LG3120 | LG5120 |
Firmware Requirement (RobustOS Pro Version) | EG3120 (≥ROS Pro:2.4.103); EG5120 (≥ROS Pro:2.4.105); EG5200 (≥ROS Pro:2.3.108) | LG3120 (=ROS Pro:2.4.111) | TBD |
1. Manual Description
1.1 Manual Purpose
This manual guides field technicians to quickly configure the Robustel edge computing gateway to forward collected data to higher-level systems (such as a BMS - Building Management System) using the Northbound BACnet/IP protocol.
1.2 Scope of Application
This manual is written for field implementation engineers. You do not need deep theoretical knowledge of the BACnet protocol. By following these step-by-step instructions, you can easily configure the gateway as a BACnet Server, map internal data tags to BACnet objects, and verify the data using third-party tools.
2. Basic Concepts & Network Topology
Gateway Role: From Collector to Server
In a typical IIoT project, imagine the gateway as a translator between your local sensors and the Building Management System (BMS). The data flow consists of two main stages:
- First Stage (Southbound): The local field devices (such as a Modbus TCP Sensor) are connected to the gateway. The gateway actively collects data from these devices and stores the values internally as "Tags".
- Second Stage (Northbound): The gateway operates as a BACnet IP Server on the network. It takes those internal Tags, converts them into standard BACnet objects, and exposes them so that a higher-level system, such as a BMS or a BACnet testing tool like Yabe Explorer, can continuously read the data.
Figure 2-1 BACnet northbound network topology
3. Preparations
(Note: This document uses the LG3120 gateway and E2C Field software as an example. The configuration process for other supported gateway and software combinations is very similar.)
Before starting the configuration, please ensure the following preparations are met:
3.1 Hardware Device Requirements
Device | Requirement |
Gateway | Robustel Gateway with E2C Field / E2C Factory / E2C Facility software installed. In this document, we use LG3120 with E2C Field for an example. |
Debugging PC | A PC used to log into the gateway's Web UI and run the BACnet testing software (Yabe). |
Southbound Device | A Modbus TCP Slave device (e.g., PLC or sensor simulator) to provide the initial data source. |
Ethernet Cable | Standard Ethernet cables to connect the gateway, the debugging PC, and the Modbus device. |
3.2 Environment and Network Requirements
- LAN Connectivity: The gateway, the debugging PC, and the Modbus TCP device must be connected to the same Local Area Network (LAN) (e.g., connected to the same switch or the gateway's LAN ports).
- IP Allocation: Ensure all devices have valid IP addresses in the same subnet (e.g., 192.168.0.x) and there are no IP conflicts.
- Port Accessibility: Ensure the PC's firewall allows UDP traffic on port 47808 (the standard BACnet/IP port).
- BACnet Testing Tool: Download and install Yabe (Yet Another Bacnet Explorer) on your debugging PC. It is a free, industry-standard tool used to search and verify BACnet Server devices.
4. Prerequisite: Southbound Data Collection
Before forwarding data via BACnet, the gateway must first collect data from the field devices. In this guide, we will use a Modbus TCP sensor simulator as an example to collect two tags: Temperature and Humidity.
4.1 Logging into E2C Field
- Connect your PC to the gateway's LAN port.
- Open a web browser and enter the gateway's IP address (the default is usually 192.168.0.1).
- Log in with your credentials and click Edge Computing in the gateway's Web GUI to enter the E2C Field software.
Figure 4-1 Open E2C Field from the gateway Web UI
4.2 Adding a Modbus TCP Device
(Note: This section assumes that you already have a Modbus Slave device physically connected to the gateway via an Ethernet cable.)
- On the left menu of E2C Field, go to Data Collection > Wired Device.
- Click the + Create button to add a new device.
- Select Modbus TCP as the Driver.
- Fill in the basic device parameters (refer to your sensor's manual):
Parameter | Description | Default / Example Value |
Name | A recognizable name for your Modbus device. | Sensor1 |
Driver | The communication protocol used by the device. | Modbus TCP |
IP Address | The IP address of the Modbus TCP slave device. | 192.168.0.17 |
Port Number | The TCP port number for Modbus communication. | 502 |
Slave Address | The Modbus unit identifier or device address. | 2 |
Polling Cycle | The interval (in seconds) at which the gateway reads data. | 1 |
- Click Save.
4.3 Creating Data Tags (Temperature & Humidity)
Now we need to read the specific registers from the Modbus device. Let's assume the client's Modbus Slave manual states that the Temperature data is stored in Holding Register 40001 and Humidity is stored in Holding Register 40002.
- Click on the newly created device (Sensor1) to enter its configuration page.
- In the Tag List section, click Add to create two tags. Fill in the following parameters:
Parameter | Description | Example Value |
Name | The name of the data point. | Temperature , Humidity |
Tag Type | Choose between Device Tag or Virtual Tag. | Device Tag |
Function Code | The Modbus function code for reading. | 03 |
Address | The specific register address of the data point. | 0 , 1 |
Data Type | The data format of the register. | short(int16) |
R/W Permission | Select Read Only or Read & Write. | Read Only |
- Click Save at the bottom, and then click Publish at the top right to start data collection.
- Tip: You can check the Status to verify if the Temperature and Humidity tags are successfully reading values before proceeding to the BACnet configuration.
Figure 4-2 Create Modbus TCP data tags
Figure 4-3 Verify Modbus TCP data tag status
5. Northbound Configuration: BACnet IP Server
This is the core step where we expose our internal tags to the BACnet network.
5.1 Creating the BACnet IP Server
- Go to Data Forwarding.
- Click the + Create button at the top, select BACnet IP Server, and click Save.
- You will enter the BACnet IP Server Configuration page. Enable BACnet IP Server Configuration and configure the Basic Settings:
Parameter | Description & Action |
Local network port | Select the gateway's network interface connected to the LAN (e.g., br_lan(192.168.0.1)). |
Port Number | Keep the default 47808. This is the standard UDP port for BACnet IP. |
Local Device ID | Enter a unique number for this gateway in your building network (e.g., 0). Note: This ID must not duplicate any other BACnet device on the same LAN. |
Enable BBMD | Enable this if the higher-level system (e.g., Yabe or BMS) and the gateway are on different subnets. Leave it disabled (default) if they are on the same subnet. |
Figure 5-1 Configure the BACnet IP server
5.2 Mapping Tags to BACnet Objects (Crucial Step)
The Yabe / BMS does not understand the internal tag names like "Temperature". It only understands standard BACnet Objects like "Analog Input 1 (AI:1)". You must translate them using the BACnet IP Mapping Table.
- Scroll down to the BACnet IP Mapping Table section, Click the Add button.
- In the new row, configure the mapping for your tags. Fill in the following parameters and Save:
Parameter | Description | Example Value |
Mapping Object Type | The standard BACnet object type (e.g., AI for Analog Input). | AI |
Device | Select the Southbound device from which to collect data. | Sensor1 |
Tag | Select the specific Southbound data variable to map. | Temperature (or Humidity) |
Instance number | The unique instance identifier for the BACnet object. | 1 (for Temperature) / 2 (for Humidity) |
Conversion Mode | How to handle decimal to integer conversion (Round, Ceil, Floor). Select Round for standard rounding. | Round |
- Click Add again and repeat the process to map the second tag (Humidity) using the values shown in the table above.
- Click Submit at the bottom to save the configuration.
- Very Important: Click the Publish button at the top right of the page. The configuration will only take effect on the edge gateway after publishing.
Figure 5-2 Map tags to BACnet objects
6. Verifying Configuration with Yabe
Now, let's test if our gateway is successfully working as a BACnet Server.
- Open the Yabe software on your PC.
- Click the green "+" (Add device) button under the "Devices" window.
- Select your local PC network interface and ensure the port is 47808 (Hexadecimal: BAC0, as Yabe uses hex for port numbers). Click Save.
- In the "Devices" tree on the left, you should see a node named BACnet IP Server 0
(where 0 is your Local Device ID). Click on it.
- In the "Objects" window (bottom left), you will see the mapped objects:
- AI:1 (mapped to Temperature)
- AI:2 (mapped to Humidity)
- Click on AI:1. Look at the "Properties" window on the right. Find the Present_Value property. If it shows the correct real-time temperature (e.g., 28), your BACnet data forwarding is successful.
Figure 6-1 Verify BACnet data with Yabe
7. Common Troubleshooting
Issue / Phenomenon | Possible Cause | Solution |
Yabe cannot find the gateway | PC and Gateway are not on the same network subnet. | Ping the gateway's IP from your PC to ensure network connectivity. Check if Windows Firewall is blocking UDP 47808. |
Yabe finds the gateway, but there are no AI:1 / AI:2 objects | Configuration is submitted but not published. | Go back to the E2C Web UI, ensure you have clicked both Submit and Publish. |
Object exists in Yabe, but value is 0 or frozen | The Southbound collection failed, so the tag has no data. | Go to Data Collection to verify if the Modbus device is actually online and updating values. |
BMS reports "Device ID Conflict" | Another controller on the site is using the same Device ID. | Change the Local Device ID in the BACnet IP Server configuration to a unique number (e.g., change 0 to 2001). Submit and Publish. |
8. Core Parameter Quick Reference
For quick on-site configuration, refer to these industry-standard concepts:
Parameter Name | Default/Recommended Value | Description |
Port | 47808 (UDP) | Standard BACnet/IP port. Do not change unless specified by the BMS engineer. |
Local Device ID | Unique number (e.g., 0 to 4194303) | The unique identifier of the gateway in the BACnet network. |
AI (Analog Input) | E.g., AI:1, AI:2 | Used for continuous numerical sensor data (Temperature, Pressure, Level). Mostly Read-Only. |
AO (Analog Output) | E.g., AO:1, AO:2 | Used for continuous numerical control targets (Frequency setting, Valve opening percentage). Read/Write. |
BI (Binary Input) | E.g., BI:1 | Used for digital status (Running/Stopped status, Fault alarm). Read-Only. |
BO (Binary Output) | E.g., BO:1 | Used for digital control commands (Start/Stop command). Read/Write. |