Local Nv Manager
Figure 63. Default sort of local nvs, ncis, is by NvIndex
To access this view right-click node in the Nav tree, and select .
While defining local nvs and ncis, the Local Nv Manager lists items with a sort order of NvIndex. However, you can click on any column header needed to resort entries.
In a typical operation, the station acts as the LonNetwork manager—you do not use this view (or method) to share data among other Lon devices. Instead, you create Lon proxy points under Lon devices, and then link the proxy points into station logic.
However, if you configure the station as only another Lon node, this view lets you create custom Lonworks network variables (nvis, nvos, ncis) available externally to other Lonworks devices. The station appears as a peer Lonworks device. In this scenario, Lonworks network management is not handled by the station.
Columns
| Column | Description |
|---|---|
| Name | Displays the name of the component that represents this device. |
| Summary | Summarizes the component configuration. |
| NvIndex | Displays the index value for the network variable. |
| Direction | Indicates the direction the message traveled. |
| Send Type | Data columns provide the current information about each link and binding. By default, this table is sorted by selector. |
| SnvtType | Displays the standard network variable type. |
| Selfdoc | Displays information for the component. Lon components are self-documenting. |
| Lnml File | Supports use of manufacturer-defined user nvs, or UNVTs (vs. SNVTs) by specifying an lnml file for a device that implements |
| Type | Works in conjunction with the Lnml File property, where once you specify an lnml file, Type provides a list of UNVTs from which you can choose for this nv. |
Button
- New creates a new device record in the database.
- Edit opens the device’s database record for updating.
- TagIt associates metadata, such as location or unique configuration with the object.