Figure 13.   NrioModule (Nrio16Module) property sheet

A controller with integral (onboard) Nrio-connected I/O, for example an M2M JACE, is represented by only one NrioModule (Nrio16Module), under its M2mIoNetwork (a specialized type of NrioNetwork). For a controller with external I/O module(s) connected via RS-485, each RS-485 port with connected I/O modules requires its own associated NrioNetwork. Under such a network, one NrioModule represents each physical I/O device (one-to-one).

Under any Nrio network, each Nrio16Module, must have a unique Address property value from 1–16.

Similarly (in Niagara 4.3 and later), each Nrio34Module will require two of the available 16 address slots (1–16). This is because the Io34 is actually two controllers on one pc board. One is referred to as the primary controller, the other as the secondary. When an Io34 is viewed in the Nrio Device Manager the Address column shows the address of the primary controller, and the SecAddr column shows the address of the secondary controller.

For any type of NrioModule, the address value is automatically derived during an online Discover, and is a read-only value. Also during Discover, each I/O device’s globally-unique “Uid” (Universal Identifier) property value is retrieved.

Apart from the Enabled and Description properties, the wink-related properties are writable (Wink Output, Wink Duration), as well as the Output Default Values properties ( Niagara 4.3 and later). All other NrioModule properties are read-only types.

Each NrioModule has a single important device extension: Points - The container for all its Nrio proxy points. Each proxy point represents a specific I/O terminal address, serviced by that board’s I/O processor(s).