Echelon i.LON SmartServer 2.0 - Manual (Page 230)

i.LON SmartServer 2.0 Programmer’s Reference 14-30
14.3.3.2 Issuing Debugging Commands
You can use the InvokeCmd function to issue debugging commands on L ON W ORKS devices. The
debugging commands consist of QueryStatus, ClearStatus, and SendServicePin. You can use the
QueryStatus debugging command to test the performance of a device and diagnose any problems. You
can use the ClearStatus debugging command to clear the device statistics returned by the QueryStatus
command. You can use the SendServicePin command to send a service pin message from one of the
16 internal devices stored on the SmartServer.
The input parameters you supply to this function will include one or more elements with a
LON_Device_Command_Invoke type and an attribute specifying the debugging command to be
performed on the device. Each element will include the of the device upon
which a debugging command is to be issued.
QueryStatus
You can use the QueryStatus debugging command to test the performance of a device. The following
example demonstrates how to query a device:
Request
Net/LON/iLON App
Response
0
xsi:type="LON_Device_StatusData_InvokeResponse">
Net/LON/DIO-1
0
2008-03-28T15:35:24.070-07:00
00a145791500
0
0
0
0
0
LonFormat="UCPTresetCause">DRC_SOFTWARE_RESET
100
LonFormat="UCPTerrorLog">DELT_NO_ERROR
LonFormat="UCPTneuronModel">MN_NEURON_3150
LonFormat="UCPTonlineStatus">DST_CONFIGURED_ONLINE
The QueryStatus command returns the following device statistics:
The name of the device in the following format:
<network>/<channel>/<device>
The Neuron ID of the device as a 12-digit hex string. The
Neuron ID is a unique 48-bit number burnt into the device’s
Neuron chip.
Transmission errors typically indicate cyclical redundancy check
(CRC) errors. CRC errors are commonly caused by
electromagnetic interference (EMI) on the channel.