Echelon OpenLNS User Manual

Page 546

Advertising
background image

OpenLNS Programmer's Reference

509

able to use the MsgMonitorPoint to send messages to all

the devices that the MessageTag object is bound to at

once. You will not be able to use the MsgMonitorPoint to

receive messages from those devices. The dynamic

MessageTag object must exist on the Network Service

Device containing the monitor set you are adding the

message point to.

When you are adding MsgMonitorPoint objects to temporary

monitor sets, you can only specify an AppDevice object as the

targetDevice element. You will be able to use the new

MsgMonitorPoint object to send messages to that device, or to

receive messages from the device.
As with permanent monitor sets, you cannot specify the

Network Service Device containing the monitor set as the

targetDevice element.
If you are adding a MsgMonitorPoint object to a temporary

monitor set, and specify a MessageTag object as the

targetDevice element, the LCA, #161

lcaErrNotAllowedOnTemporaryObject exception will be

thrown.
Note: If you create a MsgMonitorPoint object and specify an

AppDevice

as the targetDevice element, and that device is

removed, then the MsgMonitorPoint object will be deleted as

well.
The FilterBySource property of the MsgMonitorOptions object

must be set to True to restrict the MsgMonitorPoint object to

monitoring messages from the device set specified by the

targetDevice element.
You should use transactions when creating large numbers of

message monitor points in permanent monitor sets, as this

will reduce the overall time required to create them. For

more information on using transactions with LNS, see

Chapter 4, Programming an OpenLNS application, of the

OpenLNS Programmer’s Guide.
Monitor points in permanent monitor sets are not

automatically removed when the application shuts down. If a

monitor point is not going to be used again, you can remove it

with the Remove method before closing your application. This

does not apply to monitor points in temporary monitor sets,

as temporary monitor sets are deleted as soon as the

application that created them shuts down. As a result, you

should use temporary monitor points for monitor points you

will only need to use once.
For more information on creating and using message monitor

points, see the Adding Message Monitor Points to a Monitor

Set section in Chapter 9 of the OpenLNS Programmer’s

Guide.

Availability

Local, full, lightweight, and independent clients. Note that

temporary

MonitorSet

objects, and temporary monitor points,

Advertising