Skip to content
NimrodBuilding operations, connected.
All articles

Connectivity

Different networks. Consistent Points.

How Nimrod’s polling agents bring BACnet, Modbus, LonWorks, and web sources into the operating model.

A portfolio rarely comes with one network protocol. Building controllers, electrical meters, older field networks, and web services each expose information differently. Operators still need to use the resulting measurements together.

Nimrod’s polling agents perform the protocol-specific reads and map the results into Points. Those Points can then support equipment views, dashboards, alarms, reports, and recorded history.

Connect building automation networks.

BACnet/IP provides a path to BACnet devices, objects, and properties over an IP network. MS/TP devices can be reached through an appropriate BACnet router. Host configuration and network reachability determine which systems the agent can access.

BACnet/SC uses secure WebSocket connections and mutual TLS. A Nimrod connection joins a configured SC hub to reach devices and routed BACnet networks. The hub is a connection endpoint with its own enrollment and certificate requirements.

[ 10 / NETWORK PROTOCOLS ]

Your networks.
Connected.

Bring building controllers, meters, field networks, and web APIs into the same operational model. Nimrod’s polling agents handle the protocol-specific reads.

Connected at the sourceField networks → Polling agents → Points
Connection / BACnet/SC

From the source.

Join a BACnet/SC hub over secure WebSockets to reach devices and routed BACnet networks.

SC hubDeviceObjectProperty
Explore BACnet/SC
nimrod / Polling agent
01Schedule reads02Map values to Points03Record trend history
One collection layer
PointShared data structure

CHW supply temperature

Value
44.0°F
Status
Normal
Value · Time · Status · History
Different sources. Consistent Points.EquipmentDashboardsAlarmsReports

Read values through configured hosts and resources, then use the resulting Points throughout Nimrod. Select a protocol to explore an illustrative data path.

Explore networking

Select a protocol to inspect its collection path. The example values illustrate a common Point representation; this is not a live network connection.

Bring meters and field networks into the model.

Modbus TCP is useful for meters and industrial equipment that expose coils, discrete inputs, or input and holding registers. The device’s register map is essential: an address alone does not establish the units, scaling, or meaning of a measurement.

LonWorks collection uses CN/IP through an IP-852 channel. The commissioned model can be discovered through supported EES or i.LON paths, giving the agent access to the relevant function blocks and network variables.

Use structured web responses too.

HTTP and HTTPS hosts poll REST-style endpoints and map values from JSON or XML responses into Points. This extends collection to reachable web services with a response structure that the configured resource can interpret.

As with a controller integration, the work includes identifying the correct value, its units, and the expected update behavior. A web endpoint becomes useful operational data through an explicit mapping.

Keep the operational representation consistent.

After collection, the Point supplies a common place for the value, time, status, and associated history. Equipment bindings add meaning by assigning those Points to defined roles in the facility model.

Supporting a protocol is one part of an integration. Routing, credentials or certificates, source configuration, and the collection schedule still need to suit the site. Start with the documented host and resource workflow for the source you are connecting.

That separation lets the agent handle communication details while the operating model provides a consistent representation for the people using the data.

Keep exploringFind your deployment