Application messaging api functions, Non volatile data api functions, Non-volatile data api functions – Echelon LonTal Stack User Manual
Page 194
182
Appendix D: LonTalk API
Function
Description
LonGetUniqueId()
Gets the unique ID (Neuron ID) value of the Echelon Smart
Transceiver or Neuron Chip.
LonGetVersion()
Gets the version number of the LonTalk API.
LonPollNv()
Requests a network variable value from the network. A
LonTalk Stack application can call LonPollNv() to request
that another L
ON
W
ORKS
device (or devices) send the latest
value (or values) for network variables that are bound to the
specified input variable. To be able to poll a network
variable, it must be declared in the model file as an input
network variable and include the polled modifier.
LonQueryNvType()
Queries the information about a network variable.
LonSendServicePin()
Broadcasts a service-pin message to the network. The
service-pin message is used during configuration,
installation, and maintenance of a L
ON
W
ORKS
device. The
LonTalk host stack automatically broadcasts service-pin
messages when needed.
Application Messaging API Functions
The following table lists the LonTalk API functions that are used for
implementing application messaging and for responding to an application
message. Application messages can be used to implement a standard interface or
a proprietary interface that does not need to interface to devices from other
manufacturers. Support for application messaging is optional.
Function
Description
LonReleaseCorrelator() Releases a request correlator for an application message
without sending a response.
LonSendMsg()
Sends an application message.
LonSendResponse()
Sends an application message response to a request message.
The LonTalk Stack application calls LonSendResponse() in
response to a LonMsgArrived() event handler function.
Non-Volatile Data API Functions
The following table lists the LonTalk API functions that are used for
implementing support for non-volatile data.