2 issuing debugging commands – Echelon i.LON SmartServer 2.0 User Manual

Page 230

Advertising
background image

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 <Item> elements with a
LON_Device_Command_Invoke type and an attribute specifying the debugging command to be
performed on the device. Each <Item> element will include the <UCPTname> 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

<InvokeCmd xmlns="http://wsdl.echelon.com/web_services_ns/ilon100/v4.0/message/">
<iLonItem>

<Item xsi:type="LON_Device_Command_Invoke" Command="QueryStatus">

<UCPTname>Net/LON/iLON

App</UCPTname>

</Item>

</iLonItem>
</InvokeCmd>

Response

<InvokeCmd xmlns="http://wsdl.echelon.com/web_services_ns/ilon100/v4.0/message/">

<iLonItem>
<UCPTfaultCount>0</UCPTfaultCount>
<Item

xsi:type="LON_Device_StatusData_InvokeResponse">

<UCPTname>Net/LON/DIO-1</UCPTname>
<UCPThidden>0</UCPThidden>
<UCPTlastUpdate>2008-03-28T15:35:24.070-07:00</UCPTlastUpdate>
<UCPTuniqueId>00a145791500</UCPTuniqueId>
<UCPTtransmitErrors>0</UCPTtransmitErrors>
<UCPTtransactionTimeouts>0</UCPTtransactionTimeouts>
<UCPTrcvTransactionFull>0</UCPTrcvTransactionFull>
<UCPTlostMessages>0</UCPTlostMessages>
<UCPTmissedMessages>0</UCPTmissedMessages>
<UCPTresetCause

LonFormat="UCPTresetCause">DRC_SOFTWARE_RESET</UCPTresetCause>

<UCPTversionNumber>100</UCPTversionNumber>
<UCPTerrorLog

LonFormat="UCPTerrorLog">DELT_NO_ERROR</UCPTerrorLog>

<UCPTneuronModel

LonFormat="UCPTneuronModel">MN_NEURON_3150</UCPTneuronModel>

<UCPTonlineStatus

LonFormat="UCPTonlineStatus">DST_CONFIGURED_ONLINE</UCPTonlineStatus>

</Item>
</iLonItem>
</InvokeCmd>

The QueryStatus command returns the following device statistics:

<UCPTname>

The name of the device in the following format:
<network>/<channel>/<device>

<UCPTuniqueId>

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.

<UCPTtransmitErrors>

Transmission errors typically indicate cyclical redundancy check
(CRC) errors. CRC errors are commonly caused by
electromagnetic interference (EMI) on the channel.

Advertising