Protocol Integration

Your Systems Don't Speak the Same Language

N2, PUP, LON, Modbus, BACnet — building automation is a Tower of Babel. We're the translators that make your systems work together.

Discuss Protocol Integration

The Protocol Problem

Every BMS manufacturer developed their own communication protocol. For decades, this kept you locked into their ecosystem. Today, it's a barrier to modernization, integration, and data access.

Vendor Lock-in

Proprietary protocols mean you can only use that vendor's equipment and services.

Integration Barriers

Can't connect to analytics platforms, energy management, or other building systems.

Obsolescence Risk

Legacy protocols have shrinking support. The expertise to maintain them is disappearing.

Protocols We Integrate

From legacy proprietary buses to modern open standards — we speak them all.

B

BACnet

Open Standard

The industry standard for building automation. MS/TP, IP, and Ethernet variants. Where legacy systems need to go.

Learn about BACnet integration →
N2

N2 Bus

Johnson Controls

JCI's legacy field bus protocol. Connects DX-9100, VMA, TEC controllers. Migration to BACnet is critical.

Learn about N2 integration →
LON

LonWorks

Open (Echelon)

Peer-to-peer network protocol. Common in '90s-'00s installations. Still functional but declining support.

Learn about LON integration →
MB

Modbus

Industrial Standard

Simple, reliable protocol for equipment integration. RTU (serial) and TCP (Ethernet) variants.

Learn about Modbus integration →
PUP

PUP Protocol

American Auto-Matrix

AAM's Public Unitary Protocol. Connects SOLO controllers. Critical for AAM migrations.

See AAM services →
+

Other Protocols

Proprietary

CCN, Comm5, P1/P2, C-Bus, and other vendor-specific protocols. We've seen them all.

Ask about your protocol →

How We Bridge Protocols

Protocol integration isn't just about hardware gateways. It requires understanding both sides — the legacy system's data model and the target system's requirements.

1

Discovery

Map the existing network — devices, points, addresses, relationships.

2

Translation

Configure protocol drivers or gateways to expose legacy points.

3

Normalization

Standardize naming, units, and data formats for the target system.

4

Verification

Test bidirectional communication, command execution, and data integrity.

Integration Tools

We use the right tool for each integration challenge:

  • →
    Niagara Framework

    Extensive driver library for legacy protocols

  • →
    Protocol Gateways

    Hardware bridges for serial protocols

  • →
    BACnet Routers

    Expose legacy as BACnet objects

  • →
    Custom Development

    When off-the-shelf doesn't exist

Common Integration Scenarios

Unified Building Dashboard

Multiple BMS platforms from different eras need to report to a single interface. We integrate them all into Niagara or another supervisor.

Protocols: Any → Niagara/BACnet

Energy Analytics Platform

Your analytics platform needs BACnet or API data, but your BMS speaks N2 or LON. We expose the data in the format they need.

Protocols: Legacy → BACnet/IP or API

New Equipment Integration

New chiller or AHU has BACnet, but your existing BMS only speaks a legacy protocol. We bridge the gap without replacing everything.

Protocols: BACnet ↔ Legacy

Phased Migration

Upgrading in stages — new BACnet controllers alongside legacy devices. We keep everything talking during the transition.

Protocols: Mixed environment

Integration Services →

Learn about our full integration capabilities, process, and what to expect from a project.

Legacy Systems →

Explore our expertise in specific BMS platforms: JCI, Honeywell, Siemens, Trane, Carrier, and AAM.

What Protocol Are You Stuck With?

Tell us what you have and where you need to go. We'll figure out the translation.

Discuss Your Integration