Under any Lon device, all of its available nvs (nvis and nvos), ncis, and cps (SCPTs) are represented in the station by LonComponents, viewable on the device’s property sheet (see Figure 34). In turn, each LonComponent contains “LonData” plus or one or more container slots, including a “Props” structure needed by the station’s network management to access or create links to that data.

As shown in Figure 46, you can expand any LonComponent in the property sheet of the device.

A Lon device’s collection of LonComponents is determined by its referenced Lon xml (.lnml) file. The .lnml file is automatically determined in a “Quik Learn” (see Quik Learn) or following a Discover in the Lon Device Manager. Or, you can manually specify the .lnml file in the Add or Edit dialog for a Lon device, then use the right-click device command “Import Xml”.In the case of a DynamicDevice that does not have a referenced lnml, its network variables can be “learned” from a Learn Nv action (when the device is online with the station).

See the following sections for more details: