Dynamic network variable event handler functions, Application messaging event handler functions – Echelon FTXL User Manual

Page 166

Advertising
background image

154

FTXL LonTalk API

Dynamic Network Variable Event Handler
Functions

Table 18 lists the event handler functions that are called by the FTXL LonTalk

API to process dynamic network variables. See

Handling Dynamic Network

Variables

on page 92 for more information about using these functions.

Table 18. Dynamic Network Variable Event Handler Functions

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

Table 19 lists the event handler functions that are called by the FTXL LonTalk
API for application messaging transactions. Customize these functions if you use

application messaging in your FTXL device. Application messaging is optional
and only recommended for implementing the L

ON

W

ORKS

file transfer protocol

and for proprietary interfaces.
If you choose not to support application messaging, you do not need to customize
these functions.

Table 19. Application Messaging Event Handler 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.

Advertising