Echelon OpenLDV - Manual (Page 83)

OpenLDV Programmer’s Guide 75
Message Type Message Codes (Hex)
Foreign responder offline 4F
Network diagnostic message 50 .. 5F
Network management message 60 .. 73
Router configuration message
(not used by the network interface)
74 .. 7C
Network management escape code 7D
Router far side escape code
(not used by the network interface)
7E
Service pin message 7F
Sending Messages to the Network Interface
Some messages can be sent to the network interface itself. For example, the
NM_update_domain (0x63) message can be sent to the network interface using
the niNETMGMT network interface command. This message sets the network
address (domain ID, subnet ID and node ID) used by the network interface.
Some network interfaces require authentication for local network management
commands. Thus, you should always set the auth bit of the ExpMsgHdr to 1 for
local network management commands. See ExpMsgHdr on page 63 for
information about the message header.
Receiving Messages from the Network Interface
Incoming application, foreign frame, and network variable messages are passed
unchanged to the OpenLDV application. Most network management messages
received are handled by the network interface itself. However, the network
management messages listed in Table 32 can be passed to the OpenLDV
application, which must respond appropriately. See the ISO/IEC 14908-1
protocol specification for information about these network management and
diagnostics messages.
The OpenLDV Developer Example contains an example framework for
recognizing and processing these messages.
Table 32. Network Management Messages Passed to the OpenLDV Application
Message Code Comments
Query NV Config 0x68 OpenLDV application should respond with data from the
network variable configuration table or alias table.
Update NV Config 0x6B OpenLDV application should write its own network variable
configuration or alias table, respectively.