Echelon OpenLNS User Manual
Page 502
OpenLNS Programmer's Reference
465
use in multiple client sessions or that you intend to use multiple times, you should use the
permanent MonitorSet objects described earlier in this section. However, if you do not need
to re-use a monitor set, you should use temporary monitor sets, as it takes less time and
network resources to create them.
The properties and methods that can be used on a temporary MonitorSet object and its
monitor points it contains are generally the same as those that can be used on permanent
MonitorSet object and its monitor points. However, if you have been using MonitorSet objects
with OpenLNS versions prior to LNS Release 3.20, you should note the following exceptions
to this rule:
1.
Temporary MonitorSet objects cannot be created or used while in independent mode. And
the Open and Close methods have no effect on temporary MonitorSet objects, because
temporary MonitorSet objects are opened as soon as they are created, and closed as soon
as the client session in which they were created ends. You should also note that
temporary monitor sets are not enabled as they are opened. You must explicitly enable
temporary monitor sets and temporary monitor points with your application using the
applicable Enable method.
2. In addition, the DefaultOptions properties stored in MsgMonitorPoint and
NvMonitorPoint objects in temporary monitor sets are not accessible. The values applied
to these properties are taken from the temporary monitor set’s MsgOptions or NvOptions
properties. For more information, see the DefaultOptions property.
3.
Monitor points in temporary monitor sets do not support the use of connection
description templates to set certain monitoring options, as monitor points in permanent
monitor sets do. As a result, you must set the connDesc element to NULL when you add
a monitor point to a temporary monitor set. See the online help for the Add method for
the MsgMonitorPoints and NvMonitorPoints collections for more information on this.
4. Network variable monitor points in temporary monitor sets cannot be automatically
bound to the monitoring node. This means that the
temporary monitor sets and monitor points should be set to False. For more information
on this, see the online help for the
The following table summarizes the
MonitorSet
object.
Description
A set of network variable and message tag monitor points.
Added to API
Prior to LNS Release 3.0.
Accessed Through
object.
Default Property
Name.
Methods
•
•
•
•
Properties
•
•
•
•
•
•
•
•
•