Echelon OpenLNS - Manual (Page 678)

OpenLNS Programmer's Reference 641
Added to API LNS Release 3.0.
UseAsyncSend
Summary Determines whether OpenLNS will wait for a completion
code to return after updating the value of a monitor point
before sending its next update message .
When sending the values of network variable and message
monitor points prior to LNS 3.20, LNS would wait for the
completion code for each message sent to be returned before
returning to the user, regardless of the messaging service
type being used. You can use this property to determine
whether OpenLNS should wait for the completion code.
Note: The UseAsyncSend property can be used to confirm
when the values of the monitor points on your network have
been successfully sent, as described earlier. However, you can
also use the OnMsgMonitorPointErrorEvent and
OnNvMonitorPointErrorEvent events to determine when
values are not successfully sent. These events are generated
whenever there is a write failure on a monitor point.
See the Monitor and Control chapter in the OpenLNS
Programmer’s Guide for more information.
Availability Local, full, lightweight, and independent clients. Note that
temporary MonitorSet objects and temporary monitor points
are not available on Independent clients.
Syntax monOptsObject.UseAsyncSend = asyncFlag
Element Description
monOptsObject The NvMonitorOptions object being
acted upon.
asyncFlag A Boolean value indicating whether
OpenLNS waits for a completion code
to return after updating the value of
the monitor point before sending its
next update message.
TRUE. OpenLNS does not wait for
the completion code to return
after sending the values of
the monitor points before
returning to the user.
In this case, OpenLNS will
generate an
OnMsgMonitorPointEvent or
OnNvMonitorPointEvent
event as soon as the
completion code has been
returned, and the value of
the monitor point has been
updated. You can use these