For an M2mIoNetwork, only one child Nrio16Module is valid. This supports the onboard IO of an “M2M JACE” (JACE-x02 Express).

Currently, all Nrio-accessed IO is represented as “Io16”, where each discovered NrioModule appears with a default name of “Io16_n”. Usually you change this name, except for the NrioModule under an M2mIoNetwork copied from the nrio palette—its default “LocalIo16” name is often acceptable. Note that any NrioModule’s child “Points” extension dynamically reflects its parent’s name.

You may also enter a Description in the Add dialog (Figure 7) when adding an NrioModule, or else do that in the Edit dialog later. Note that Address is read-only, and is “automatically” assigned by the online Discover (you cannot manually edit). For details, see NrioModule.

Offline engineering is possible (using Add Offline Hardware), and can be useful when engineering is needed before being online with the exact IO device(s). In this case, when online with the IO devices, you use the “Match” feature in the Nrio Device Manager, following the Discover.

This lets you match one-for-one a discovered NrioModule to the actual IO device. In the case of multiple external remote I/O modules (more than one), you typically use the Wink action on discovered devices before each Match, to correctly associate the software component to the right physical I/O module. For more details, see About Nrio offline engineering, including About Nrio Wink and About Nrio Device Match.