About network architecture

Niagara uses a consistent driver framework to represent each driver in a station database. This includes the upper-tier parent network component and one or more child device components, each with device ext (extension) child components.

Hierarchically, the component parentage is: network, device, device extensions, and points, as shown here. Using a network architecture enforces a logical structure and helps coordinate mechanisms used by the driver for communications. Exceptions to this rule are noted (as applicable) in documentation.

For drivers that use field bus communications, such as Lonworks, BACnet, and Modbus (among many others), the top-level network component corresponds directly to a physical network of devices. Often (except for BACnet), the network component matches one-to-one with a specific communication (comm) port on the host platform, such as a serial or RS-485 port, Lonworks FTT-10 port, or Ethernet port.

Figure 2. Example of a driver Device Manager view (OpcUa)

The driver network is the parent container for all device-level components. Devices list in tabular format in the default view for the network, the DeviceManager. You use the Device Manager to create and manage device components, and (if the driver provides this), use discover features.

Access these slots in the driver network’s Property Sheet.

Figure 3. Example OpcUaNetwork property sheet

Depending on the specific driver, there may be additional slots and components in the driver network. For example, if the driver supports a field bus network, there may be PollScheduler and/or CommConfig slots. Some of these may require proper configuration before driver communications occur.

NOTE: A BacnetNetwork component is unique because it supports multiple logical BACnet networks, which sometimes use different comm ports (for example, a controller with BACnet MS/TP and one or more RS-485 ports).

Other non-field-bus drivers also use a network architecture, for example the Nrio driver (Niagara Remote Input/Output) has a network (NrioNetwork) that interfaces with physical I/O points on the appropriate host controller or hardware I/O module (either directly attached or remotely connected). Database drivers use a network architecture, for example the rdbSqlServer driver includes an RdbmsNetwork. Database drivers apply only to Supervisor hosts.

Depending on the driver, other specific properties (or even component containers) may be found in the network component’s property sheet.