Echelon FTXL - Manual (Page 168)

156 FTXL LonTalk API
Function Description
LonEventReady() Indicates that a network event is ready to be processed.
The FTXL LonTalk protocol stack calls this callback handler
function to indicate that a network event is ready to be
processed, and that the main application should call the
LonEventPump() function. However, the LonEventReady()
function should not call the LonEventPump() function directly.
Typically, the LonEventReady() callback signals an operating
system event that the main application task waits upon. When
the main application task wakes up, it should call the
LonEventPump() function.
Direct Memory Files Callback Handler
Functions
The FTXL LonTalk API provides the callback handler functions listed in Table 22
to support the direct memory files (DMF) feature. These functions rely on utility
functions generated by the LonTalk Interface Developer utility.
Table 22. FTXL DMF Callback Handler Functions
Function Description
LonMemoryRead() Indicates a request to read memory in the FTXL device’s memory
space.
LonMemoryWrite() Indicates a request to write memory in the FTXL device’s memory
space.
Non-Volatile Data Callback Handler
Functions
Table 23 lists the callback handler functions that support non-volatile data. For
the functions listed in the table, the LonTalk Interface Developer utility
generates the following callback handler functions (also listed in Table 23):
• LonNvdDeserializeSegment()
• LonNvdGetApplicationSegmentSize()
• LonNvdSerializeSegment()
The remaining non-volatile data callback handler functions are implemented in
the FtxlFlashDirect.c and FtxlFlashFs.c files.
Table 23. FTXL Non-Volatile Data Callback Handler Functions
Function Description
LonNvdClose() Indicates a request to close a non-volatile data
segment.