lonworks-LonNetwork

This component is the base container for all Lonworks (Lon) components in the station. As with other driver networks, it resides under the station’s Drivers container.

If the host has multiple Lon ports, you need a separate LonNetwork for each physical port.

The default view of the LonNetwork is the Lon Device Manager.

In addition to being the network container for LonDevices and their child data objects (Lon proxy points), the LonNetwork includes a LocalLonDevice, which configures the station’s representation as a Lonworks device.

Figure 7. LonNetwork properties

To access this view, expand Config > Drivers, right-click the LonNetwork component in the Nav tree, and click Views > AX Property Sheet.

Property	Value	Description
Status	read-only	Reports the condition of the entity or process at last polling. `{ok}` indicates that the component is licensed and polling successfully. `{down}` indicates that the last check was unsuccessful, perhaps because of an incorrect property, or possibly loss of network connection. `{disabled}` indicates that the `Enable` property is set to `false`. `{fault}` indicates another problem. Refer to `Fault Cause` for more information.
Enabled	`true` or `false`	Activates (`true`) and deactivates (`false`) use of the object (network, device, point, component, table, schedule, descriptor, etc.).
Fault Cause	read-only	Indicates the reason why a system object (network, device, component, extension, etc.) is not working (in fault). This property is empty unless a fault exists.
Health	read-only	Reports the status of the network, device or component. This advisory information, including a time stamp, can help you recognize and troubleshoot problems but it provides no direct management controls. The Niagara Drivers Guide documents the these properties.
Alarm Source Info	additional properties	Contains a set of properties for configuring and routing alarms when this component is the alarm source. For property descriptions, refer to the Niagara Alarms Guide
Monitor	Ping Monitor	Configures a network's ping mechanism, which verifies network health. This includes verifying the health of all connected objects (typically, devices) by pinging each device at a repeated interval. The Niagara Drivers Guide documents these properties.
Lon Comm Config	additional properties	Configures the communication stack for a single Lonworks connection including specifying the port’s `Device Name` For specific properties, refer to a separate topic in this guide.
Poll Service	additional properties	Configures the frequency with which the driver polls points and devices. “Poll Service properties” in the Niagara Drivers Guide documents these properties.
Tuning Policies	additional properties	Configures network rules for evaluating both write requests to writable proxy points as well as the acceptable freshness of read requests. For more information, refer to the Niagara Drivers Guide.
Lon Netmgmt	additional properties	Serves as the container for Lon network management functions provided by the station. For specific properties, refer to a separate topic in this guide.
Local Lon Device	additional properties	Configures the local interface to the Lonworks fieldbus. For specific properties, refer to a separate topic in this guide.

Lon Comm Config

Figure 8. Lon Comm Config properties

In addition to the standard polling properties documented in the Niagara Drivers Guide, these properties are unique to Lon Comm Config.

Property	Value	Description
Device Name	string	Identifies the host’s LONn port used in a Lon network. For example, Device Name = Mnlrr2. For a LonTunnel copied from the palette, this defaults to LON1. Defice names must match the name string in the LonNetwork Lon Comm Config container.
Link Debug	`true` or `false` (default) [used once]	Controls the display of messages from and to the Neuron. `false` limits the message display. `true` shows the raw byte data for messages from and to the Neuron. To use this feature you must also enable link debug using the spy page in the station. Refer to the Troubleshooting chapter.
Repeat Timer	drop-down list of millisecond values (defaults to 384 milliseconds) [used once]	Applies to all outgoing network management messages, all poll messages, and unbound nv update messages from the station.
Receive Timer	drop-down list of millisecond values (defaults to 96 milliseconds) [used once]	Applies to all outgoing network management messages, all poll messages, and unbound nv update messages from the station.
Transmit Timer	drop-down list of millisecond values (defaults to 96 milliseconds)	Applies to all outgoing network management messages, all poll messages, and unbound nv update messages from the station.
Retry Count	number (defaults to 3)	Applies to all outgoing network management messages, all poll messages, and unbound nv update messages from the station.

Actions

Figure 9. Lon Network actions menu

To access these actions, right-click the LonNetwork and click Actions.

Action	Description
Ping	Attempts communication with the device. If successful, the device status reports {ok}. If this fails, the system sets device status to {down}
Upload	Reads transient (nvs) and persistent (ncis and cps) data from the device and writes them to the station database (Lon device). An Upload window selects the type of data.
Download	Writes persistent data (ncis and cps) to the device from values in the station database (Lon device). A Download window selects recursive writes.
Make Nvs Non Critical	Changes the network variable.