Starting in AX-3.3, when learning/adding a Lon device, you can optionally specify for the device’s LonComponents to be grouped under “LonObject” containers. Each LonObject represents a LonMark object, and its child LonComponents are the set of nvs, ncis, and cps that comprise that object.
As shown in Figure 47, LonObjects are visible in the Nav tree when the Lon device is expanded. This extra level of component hierarchy may be useful in devices that have a large number of LonMark objects.
The LonObject container has only a few properties, with important properties as follows:
-
Object Id
The numerical LonMark object identifier for the object, unique in the device among all objects.
-
Object Type
The numerical LonMark object type for the object, for example “0” for the “Node object,” or “8080” for a “Unit Ventilator Controller” functional profile.
The default name for a LonObject is “Typen”, where “n” is the LonMark object type number. The property sheet is the default view for a LonObject, as seen in Figure 47. For details on globally implementing LonObjects, see Use Lon Objects notes.
You can also specify the “Use Lon Objects” option on a Lon device that already exists in the station database, when issuing either the ImportXml command or the Learn Nv action.