Direct memory files callback handler functions, Non volatile data callback handler functions, Non-volatile data callback handler functions – Echelon LonTal Stack User Manual
Page 200
188
Appendix D: LonTalk API
Function
Description
LonGetMyNetworkInterface() Gets the name of the network interface used to open the
native LonTalk interface. This method returns the
name of the network interface, such as the serial port
name. This method has the following syntax:
const char *LonGetMyNetworkInterface(void);
Direct Memory Files Callback Handler
Functions
The LonTalk API provides the callback handler functions listed in the following
table to support the direct memory files (DMF) feature. These functions rely on
utility functions generated by the LonTalk Interface Developer utility.
Function
Description
LonMemoryRead() Indicates a request to read memory in the LonTalk Stack device’s
memory space.
LonMemoryWrite() Indicates a request to write memory in the LonTalk Stack device’s
memory space.
Non-Volatile Data Callback Handler
Functions
The following table 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, which are also listed in
the table:
• LonNvdDeserializeSegment()
• LonNvdGetApplicationSegmentSize()
• LonNvdSerializeSegment()
The remaining non-volatile data callback handler functions are implemented in
the FtxlFlashDirect.c and FtxlFlashFs.c files.
Function
Description
LonNvdClose()
Indicates a request to close a non-volatile data
segment.
LonNvdDelete()
Indicates a request to delete a non-volatile data
segment.