Although not a “manager” view, whenever the station is configured as the Lonworks network manager (typical), the wire sheet view of the LonNetwork (and any child LonDeviceFolder containing Lon devices) is an important view. Here, bindings between Lon devices appear as graphical links (wires), and you can add or delete bindings between devices as needed. Figure 32 shows a link being pulled from an nvo of one device to another device, using the wire sheet of the LonNetwork.
Using the wire sheet is not a strict requirement. For example, you can also perform the same operations using right-click
commands (on Lon devices) in the Nav tree, such as “Link Mark” and “Link from <LonDeviceName>”. However, the wire sheet graphically shows you existing bindings as wires or “nubs.”
However you specify a link between Lon devices, the popup Link editor (Figure 33) provides nv (e.g. SNVT) verification to allow only legitimate links. When you click , a “new link” is added. See the next section, New link to binding notes.
When you graphically add a new link between Lon devices, say in the LonNetwork’s wire sheet (Figure 32) and resulting Link editor (Figure 33), at this point it is still a “station dependent” link. In other words, until you perform a “Bind” or “Selective Bind” operation from the Lon Link Manager, the station is required for data exchange. See linkStatus.
As this “new link” state is counter to the Lonworks principle of “peer-to-peer” bindings (via nv updates), and is also inefficient in comparison, after adding links between devices you should bind them, using the Lon Link Manager. There, you can also set service types on bindings, if needed.
In the Lon Link Manager, a link/binding between two Lon devices appears as an entry row without “LocalDev” as the value of either “srcDevice” or “targetDevice” (whereas, any entry row with a “LocalDev” value represents a Lon proxy point in the station).