Echelon LNS - Manual (Page 25)

LNS Programmer's Guide 11
Service Device that specifies the new dynamic message tag as the monitor target. Then,
open the monitor set and use the message monitor point to send messages from the
Network Service Device to the devices bound to the message tag. Note that you can still
use message monitor points to send messages to individual application device, as
described in Chapter 9 of this document.
To help you keep track of changes related to these new dynamic interface capabilities,
the OnNodeIntfChangeEvent, which is fired each time a device’s external interface is
changed, has been modified for Turbo Edition. The OnNodeIntfChangeEvent event
now returns several new values indicating that interface changes related to these new
features have been made. For example, once an application registers for this event, it will
be fired each time a network variable is added or removed from a LonMarkObject, or
each time a LonMarkObject is added to an interface.
For a general overview of device interfaces, see Device Interfaces on page 104. For details
on how you can use the dynamic device interface features described in this section, see
Using Dynamic Device Interfaces on page 179.
Improved Monitoring Performance
As of LNS Turbo Edition, there are two separate types of MonitorSet objects:
permanent MonitorSet objects, which can be used in multiple client sessions, and
temporary MonitorSet objects, which can only be used in a single client session by the
application that created them.
If you need monitor points that will only be used in a single client session, you should use
temporary MonitorSet objects, as it takes less time and database resources to create
them. If you are creating a group of monitor points that you need to use in multiple client
sessions, you must use the permanent MonitorSet objects.
This section describes the major differences between permanent and temporary monitor
sets.
Using Permanent Monitor Sets
Each Network object contains a MyVNI property, which returns an AppDevice object
representing your client's Network Service Device on the network. You can use this
AppDevice to access all the permanent MonitorSet objects that are stored in the LNS
database for your client’s Network Service Device. Echelon recommends that you only
use the MyVni property to access MonitorSet objects when creating permanent
MonitorSet objects, or when modifying the configuration of those MonitorSet objects.
For actual monitor and control operations with permanent monitor sets, use the
CurrentMonitorSets property of the Network object.
The CurrentMonitorSets property returns a collection of all the permanent
MonitorSet objects on a network that are currently stored in your client’s Network
Service Device. This is useful if you have created monitor sets while the system
management mode is set to lcaMgmtModeDeferConfigUpdates (note that prior to
LNS Turbo Edition, this was lcaOffNet). Although those monitor sets exist in the LNS
database and can be accessed through the MyVni collection mentioned in the previous
paragraph, they will not be commissioned into the Network Service Device, and cannot
be used for monitoring operations, until the system management mode is set to