To create Lon proxy points

Once you learn a LonDevice, or create it offline and assign it a specific Lon Xml File, you can add Lon proxy points under its Points extension. Use the following procedure:

To create Lon proxy points in a device:

1. In the Lon Device Manager, in the Exts column, double-click the Points icon   in the row representing the device you wish to explore.

   This brings up the Lon Point Manager.

2. Click Discover    to make sure the view is in split-pane (learn mode).

   The device’s network variables (nvis, nvos, and ncis) are listed in the top pane of the view, in the “Discovered” table. Initially, each network variable (nv) occupies one row. Often, an nv is implemented with a structured SNVT (multiple data fields), and so is listed with a “+” you can expand to see other data fields. (By default, the “first” data field in the SNVT structure appears on top.) Each row in the Discovered table represents one Lon proxy point candidate.

   See Lon Point Manager tips and Lon proxy point type selection for more details.

3. Click to select the data items you wish to proxy. Often, for an nv implemented as a structure, you may need one or more secondary data fields instead of (or in addition to) the first “top” data field.

4. You can map selected items in the station in a number of ways:

   • Drag from the Discovered pane to Database pane (brings up an Add dialog).

   • Double-click an item in the Discovered pane (also brings up an Add dialog).

   • Click to select in Discovered, then press “a”. (“Quick Add”, meaning no Add dialog).

   This works the same as in other driver’s Point Manager views.

5. When the Add dialog appears, you can edit the configuration of each proxy point’s LonProxyExt before it is added in the Niagara station. Initial property values are determined by Niagara, based upon how the nv or nci was implemented in the device.

   Note the following about entries in the Add dialog:

   • Name is the “nvi, nvo, or nci name”, and if part of a data structure, a trailing “_elementName” to ensure a unique point name. For example: “nciTempSetPts_occupiedCool”

     This is the Niagara point name only—change if needed (does not affect Lonworks node).

   • Type is the Niagara control point type to use for the proxy point. For nvis and ncis, the default selection is a “writable” control point; whereas nvos can be “read-only” points only.

     Unlike other editable entries in the Add dialog, you cannot edit Type later.

   • Target is the LonComponent represented by the proxy point, for example “nvoStatus.”

   • Element is the data element if a structure, or the SNVT type if an unstructured item

   • Facets represent the parent Niagara proxy point’s facets, for how the value should be displayed in Niagara.

   • Conversion specifies the conversion to use between the “read value” (in Device Facets) and the parent point’s facets, where “Default” is typically used.

   • Link Type specifies the Lon service type to use when binding to this item.

6. When you have Lon proxy point(s) configured properly for your usage, click OK.

   The proxy points are added to the station, and appear listed in the Database pane.

   • If online with the LonNetwork, points will poll for current values.

   • If programming offline, all proxy points appear down (yellow).