Application messaging event handler functions, Non volatile data event handler functions, Non-volatile data event handler functions – Echelon LonTal Stack User Manual
Page 198
186
Appendix D: LonTalk API
Function
Description
LonNvAdded()
Indicates that a dynamic network variable has been added.
LonNvDeleted()
Indicates that a dynamic network variable has been deleted.
LonNvTypeChanged()
Indicates that one or more attributes of a dynamic network
variable have changed.
Application Messaging Event Handler
Functions
The following table lists the event handler functions that are called by the
LonTalk API for application messaging transactions. Customize these functions
if you use application messaging in your LonTalk Stack device. Application
messaging is optional.
If you choose not to support application messaging, you do not need to customize
these functions.
Function
Description
LonMsgArrived()
Indicates that an application message has arrived from the
network to be processed. This function performs any
application-specific processing required for the message. If the
message is a request message, the function must deliver a
response using the LonSendMsgResponse() function.
Application messages are always delivered to the application,
regardless of whether the message passed authentication. The
application decides whether authentication is required for a
message.
LonMsgCompleted()
Indicates that message delivery, initiated by a LonSendMsg()
call, was completed.
If a request message has been sent, this event handler is called
only after all responses have been reported by the
LonResponseArrived() event handler.
LonResponseArrived() Indicates that an application message response has arrived
from the network. This function performs any
application-specific processing required for the message.
Non-Volatile Data Event Handler Functions
The LonTalk API provides the event handler function listed in the following table
to support non-volatile data.