This blog discusses Niagara LonNetwork database requirements to properly configure an Ax Station to be managed by an LNS database.
For a Niagara station to properly function in an LNS database the proper self-documentation must be setup in the station database. The device "Self Doc" string property on the LocalLonDevice must be setup to include all LonMark objects that will be used in the station. If you wish to omit the device self-documentation string you can just type an asterisk into the "Self Doc" property. If self-documentation is supplied it must comply with the format described in The LonMark Interoperability Guidelines.
The syntax for the device self-documentation:
|
&3.0@0NodeObjectName,FunctionalBlock;selfDocText
|
| |
|
The ampersand ("&") prefix denotes an interoperable device.
|
|
3.0 identifies the major and minor version the station device implements.
|
|
An at-symbol ("@") is used as a seperator.
|
|
The functional profile numbers are listed in order of the corresponding functional-block index 0, 1, 2, etc.
|
|
The node object must be the first of the indices (0).
|
|
NodeObjectName is the description of the node object (0).
|
|
FunctionalBlock includes any other LonMark or non-LonMark functional profiles that you wish to add to the station database.
|
|
selfDocText is any text that you might want to add that describes the functional profiles.
|
Example:
&3.0@0NodeObject;Niagara Server Node
The node object (0) has two mandatory network variables, SNVT_obj_request and SNVT_obj_status. Network variables are created on the LocalLonDevice "Local Nv Manager" view.
Select new from the "Local Nv Manager" and add the following network variables:
|
The ampersand ("&") prefix denotes an interoperable device.
|
| Name | Direction | SnvtType |
| nviRequest | Input | Snvt Obj Request |
| nvoStatus | Output | Snvt Obj Status |
Now that you have created the two mandatory network variables for the node functional block you must setup the network variable self-documentation. From the properties of each newly created network variable assign the "Self Doc" string per The LonMark Interoperability Guidelines. If you wish to omit the network variable self-documentation string you can just type an asterisk into the "Self Doc" property.
The syntax for the network variable self-documentation:
| @fbIndex|memberNum;[text] |
| |
| "@" is used to denote the start of NV self-documentation. |
| fbIndex is the functional block index. |
| "|" is the functional profile seperator. |
| memberNum is the member number within the functional block. |
| text is optional for describing the NV. |
Example:
@0|1;nviRequest
@0|2;nvoStatus
Ok added a point nviTemp to the LonWatcher and it went in fine. Adding a second point after the initial commisioning is LNS crash waiting to happen. I get a ton of different error dealing with self documentation.
Is there an easy fix in syntax. Does 100% of the point need to be configured, then commission? Only 1 point seem to take up all of the resources.
I have the error log available to look at?