lonworks-DeviceData
In general, it is recommended that you leave slot values under a device’s DeviceData container at default settings. Largely, these are data structures that contain address and state information administered by the network management functions of the station.
Figure 17. Device Data property sheet
To access this view, expand the Local lon Device component in the Nav tree, and right-click .
| Property | Value | Description |
|---|---|---|
| Neuron Id | hexadecimal number |
Maps the device in the station database to a different physical device (or no device, if the address is not available). While
most DeviceData properties should be left at default values, this is one property you may routinely edit.
|
| Program Id | hexadecimal number | Identifies the interface to a dynamic device (network node). Different external interfaces should be associated with unique Program Ids. Some vendors support multiple device types in the same hardware platform. Refer to AppDownload. |
| Node State | drop-down list |
CAUTION: Do not set this property for any hosted Lon node (or the
Local Lon Device) to Applicationless or the device will become irretrievably non-functional. Instead, use the Lon Device Manager view of the Lon network to make changes to Lon devices.
|
| Subnet Node Id | read-only |
Reports the assigned Lonworks subnet/node address. Node must be unique for this device on the channel.
|
| Location | text | Provides the location of the device. |
| Authenticate | true or false (default) [used once]
|
Turns authentication on and off. |
| Channel Id | read-only or a number (defaults to zero (0) ) | Reports or defines the ID of the channel to which the device is connected. |
| Binding I I | read-only | Reports if this type of binding is enabled (true) or disabled (false).
|
| Hosted | read-only | |
| Two Domains | read-only | Reports is the device belongs to two domains. |
| Msg Tag Count | read-only | Reports the number of tag messages associated with the device. |
| Address Count | read-only | Reports the number of addresses associated with the device. |
| Address Table | list | All properties are marked as “Not In Use.” |
| Priority Slot | read-only | Reports the device’s priority setting. |
| Alias Table | additional property | Associates a network variable selector with a network variable index. These identifiers associate a network variable update
message with a network variable within the receiving application.
Refer to a subtopic in this guide. |
| Self Doc | string of text (defaults to: &3.0@;Niagara Server Node) This property requires External Config to be set to true |
Defines a text string for the host node’s self documentation up to 1024 bytes. A single asterisk (*) omits self documentation.
NOTE: When using self documentation, always retain the leading header portion (&3.0@) along with an additional zero (0), plus other characters.
|
| Has Node Object | true or false (default)
|
Determines if the node includes an object (true) or not (false).
|
| Freeze Channel Priorities | true or false (default)
|
Enables (true) and disables (false) the ability to change channel priorities.
|
| Facets | additional properties |
Determine how values are formatted for display depending on the context and the type of data. Examples include engineering
units and decimal precision for numeric types, and descriptive value (state) text for boolean and enum types.
With the exception of proxy points (with possible defined device facets), point facets do not affect how the framework processes the point’s value. Besides control points, various other components have facets too. For example, many kitControl and schedule components have facets. Details about point facets apply to these components too, unless especially noted. You access facets by clicking an Edit button or a chevron >>. Both open an Edit Facets window. |