In this typical application of the lonworks driver, you use Workbench to “model” all other Lon devices in the station’s database (under the LonNetwork). The lonworks driver provides online “learning” capabilities to simplify this. Then (as needed), you also model data in each device using Lon proxy points.
The various manager views on the LonNetwork provide your interface to all network management operations performed by the station. This includes all engineering, maintenance, and troubleshooting of the Lonworks network (including all bind operations). In addition, you can establish links directly between Lon nodes, typically by using the wire sheet view of the LonNetwork.
Depending on the installation scenario, you may need to perform a learn of a network of Lon devices that are already configured (previously managed), or, on a previously-unmanaged (new) network. Both learn types are supported, however, engineering considerations apply.
See the following sections:
On an unmanaged network, Lonworks devices are often unconfigured (not addressed, or operating with identical addresses), and Lon bindings between devices do not exist. There is no existing Lon network management to learn (only to establish for the first time).
On a previously managed network, Lonworks devices are uniquely addressed and configured, often with existing Lon bindings in use between devices. In this case, you usually want to learn all existing network management.
At this point forward, the station (Niagara) must become the only Lonworks network manager. Otherwise, proper network management cannot be successfully maintained.