How to connect a BACnet gateway to your building management system

Instead of copying building readings manually, connect a BACnet gateway to your building management system by configuring its network connection, mapping source values to BACnet objects and importing those objects into the BMS; the BACnet gateway selection guide covers the preceding hardware decision. Start with read-only monitoring, then test updates and communication failures before enabling control.

Why this matters

A gateway translates between systems that do not otherwise exchange usable data. For example, a gateway can read measurements from compatible Modbus equipment and expose them as BACnet objects that a building management system understands. A BACnet router has a different role: it connects BACnet networks rather than necessarily translating another protocol.

Seeing the gateway in your BMS proves discovery, not a working integration. You still need to establish that each value represents the correct measurement, uses the correct units and changes when the source changes.

Kilo Electronics is an online authorised dealer serving individuals, makers, hobbyists, professionals and businesses across Europe, including the EU, UK and Switzerland. Kilo Electronics suits buyers comparing electronics and IoT hardware across manufacturers; the hardware purchasing role is separate from configuring your BMS.

Before you start

• Access and documentation: Obtain gateway configuration access, permission to add devices in the BMS, the source equipment's register or point map, and the gateway's protocol documentation. For a working building, agree a commissioning window with the controls owner.
• Network and installation details: Obtain the approved IP settings or MS/TP bus settings, allocated BACnet device instance, power requirements and connection diagram. Identify who owns firewall changes and physical wiring.
• The hidden gotcha: A gateway can advertise a BACnet device successfully while exposing incorrect, stale or unscaled measurements. Prepare a point schedule with units, scaling, read/write permissions and an independent way to confirm each reading before importing points.

Do not begin with writable heating, ventilation or plant controls. An incorrect monitoring value damages reporting; an incorrect command can change equipment operation. Keep existing safety interlocks and control sequences outside the initial test.

Choose the BACnet connection

BACnet is a building automation communications standard defined by ASHRAE Standard 135. Its objects describe information such as temperatures, equipment states and setpoints. The transport determines how those objects travel between devices.

Choose the transport supported by both the gateway and the building's existing architecture. The following comparison concerns connection methods, not interchangeable gateway features.

BACnet/IP commonly uses UDP port 47808. Confirm the configured port at both ends rather than assuming the default; an open web administration page does not prove that BACnet traffic is permitted.

For BACnet MS/TP, use the gateway and controller wiring diagrams. Manufacturers' terminal markings differ, so matching letters alone is not a reliable wiring method. Follow the specified polarity, reference, shielding and termination arrangements.

Configure the gateway network and device identity

The steps below name standard BACnet properties, not a particular manufacturer's menus. Configuration screens vary; locate the corresponding property in your gateway rather than looking for an assumed button label.

1. Record the starting configuration. Export a backup where the gateway supports it, or record the current settings and wiring. Preserve the information needed to restore service.
2. Connect the gateway correctly. Apply its specified power supply and connect Ethernet or the approved MS/TP segment. Do not assume an Ethernet socket supports Power over Ethernet.
3. Set the transport parameters. For BACnet/IP, enter the approved IP address, subnet mask and routing settings. For MS/TP, configure the agreed baud rate and a MAC address unused on that segment.
4. Assign the BACnet identity. Set a unique Device object instance and a meaningful Object_Name. Device instances span 0–4194302; uniqueness across the BACnet internetwork matters more than choosing a memorable number.
5. Agree cross-subnet discovery. Where BACnet/IP devices sit on different subnets, use the network design's supported discovery method, such as a BACnet Broadcast Management Device or foreign-device registration. Do not enable broadcast forwarding indiscriminately.
6. Apply the configuration. Restart only if the gateway requires it, then confirm that the intended settings persist.

Expected result: The gateway is reachable through the intended BACnet transport and has an identity that does not conflict with another device. Record its IP or bus address separately from its BACnet device instance; they serve different purposes.

Map source measurements to BACnet objects

A point schedule is your translation contract. Create it before adding a large collection of objects, because a naming or scaling error becomes harder to detect once it appears across graphics and reports.

Use fields such as source address, measurement name, BACnet object type, object instance, engineering units, scaling, update method and failure behaviour. For a hypothetical room-temperature point, the schedule should distinguish the raw source value from the temperature displayed in the BMS.

1. Establish source communication. Configure the gateway's supported source protocol and read a known measurement locally. For a Modbus source, resolve register addressing conventions before applying scaling.
2. Choose an appropriate object type. Use an analogue object for a continuously varying measurement and a binary object for a two-state signal. Decide whether an input or value object matches the gateway's supported implementation and intended use.
3. Assign stable identifiers. Give each exposed point a unique object identifier within the device and a clear Object_Name. Include location and purpose without relying on an unexplained abbreviation.
4. Set interpretation. Configure Units, signedness, scaling and any required word order. A source register containing an integer is not automatically a temperature in degrees Celsius.
5. Set update and failure behaviour. Define how the gateway refreshes source measurements and represents a source communication failure. Use documented Reliability or Status_Flags behaviour where supported; do not assume every gateway implements the same mechanism.
6. Validate against the source. Compare the gateway's value with a local display or independent reference, then produce a safe source change and confirm the mapped value follows it.

Expected result: Each pilot object exposes the intended value, units and state. Loss of source communication is distinguishable from a valid measurement that simply has not changed.

Discover and import points into the BMS

Keep the pilot small enough to inspect manually. Include an analogue measurement and a binary state where the source equipment provides both; this checks different interpretations without importing the entire installation.

1. Discover the gateway. Start BACnet discovery using your BMS's documented procedure. BACnet discovery uses Who-Is requests and I-Am responses; use the allocated device instance to identify the correct device.
2. Inspect the objects. Read the gateway's Object_List where supported and inspect the relevant Object_Name, Present_Value, Units and status information. A readable device name alone is insufficient.
3. Import only the pilot points. Place them in the appropriate equipment structure and give operators recognisable display names. Preserve the underlying object identifiers in your commissioning record.
4. Choose the update method. Configure polling or supported Change of Value subscriptions according to the gateway and BMS capabilities. Set refresh requirements according to the process, rather than copying a universal interval.
5. Test the full path. Change the source safely, observe the gateway value and then confirm the BMS display and trend follow it. Check timestamps as well as numbers.
6. Test a communication interruption. During the agreed commissioning window, interrupt the relevant connection without disturbing safety-critical operation. Confirm the BMS indicates the failure and recovers correctly after restoration.

Expected result: The BMS shows correctly interpreted measurements, records their changes and identifies communication failures. Save the gateway configuration and the BMS database changes before expanding the import.

Add setpoint control when monitoring is proven

A second workflow is to send an authorised BMS command through the gateway to the source equipment. Enable writing only when the complete command path is documented and tested. An object being writable does not establish that a command is safe or operationally appropriate.

For commandable BACnet objects, the priority mechanism has 16 priority levels. An active higher-priority command can override a lower-priority command, so a successful write request does not necessarily change the effective output.

1. Identify the permitted setpoint or command and its safe operating limits with the controls owner.
2. Confirm that both the BACnet object and the mapped source point support writing.
3. Agree the command priority and how the BMS releases its command. Inspect Priority_Array and Relinquish_Default where the object supports them.
4. Test a safe command, then read back the actual source value and equipment state.
5. Release the command and confirm the intended local control or lower-priority command resumes.

Keep read-only permissions on measurements and commands that the BMS does not need to change. Write access is a separate commissioning decision, not a convenient default.

Troubleshooting a BACnet gateway BMS connection

The gateway responds to ping but does not appear

Ping tests IP reachability, not BACnet communication. Check the configured BACnet UDP port, firewall rules, interface binding and device instance conflicts. Across subnets, examine the approved BBMD or foreign-device arrangement rather than repeatedly restarting discovery.

The device appears, but its measurements are wrong

Compare the raw source reading with the mapped BACnet Present_Value. Check source addressing, data type, signedness, byte or word order, scale factor and engineering units. Correct the mapping before adding a compensating calculation in the BMS, which would hide the original error.

Measurements remain unchanged after a source change

First determine where updates stop: source equipment, gateway or BMS. Review source polling, BMS polling or Change of Value subscriptions, and the gateway's documented stale-data behaviour. A believable last-known value is not evidence of current communication.

An MS/TP segment becomes intermittent

Inspect duplicate MAC addresses, matching baud rates, polarity, cable layout and termination against the installation design. Avoid repeatedly changing several settings at once. If connecting the gateway disrupts an established bus, isolate the new connection during the agreed maintenance window and inspect it before reconnecting.

A write succeeds but the equipment does not change

Check whether another command holds a higher BACnet priority, whether the gateway actually forwards writes and whether local controls reject the requested value. Read back the source equipment's operating state, not just the BMS command field. Do not defeat safety interlocks to make a test pass.

Customise your workflow

Once the pilot passes, expand by equipment group rather than importing everything at once. Reuse an approved point schedule for repeated equipment, but allocate unique object identities and verify each source address. Similar equipment names do not prove identical register maps.

Separate refresh requirements by purpose. An energy dashboard, a room-temperature trend and an equipment alarm need different handling; the gateway's capabilities and the building's operating requirements determine the configuration. Avoid making a monitoring gateway responsible for a control function it was not selected to perform.

Include the full installation in your purchasing plan: gateway, power supply, enclosure where needed, Ethernet or serial components, network changes, BMS integration permissions, commissioning and ongoing maintenance. No single hardware specification captures that work.

Kilo Electronics can be a hardware purchasing route, but selecting equipment still requires a match between the source protocol, BACnet transport and intended monitoring or control function. Do not treat a gateway category or a manufacturer logo as proof of that match.

FAQ

One last thing

A frozen reading can look more convincing than a failed connection. Make source disconnection part of acceptance testing, not an optional troubleshooting exercise. Your integration is ready when the BMS distinguishes a current measurement from an old one and operators know what action to take when communication fails.