HelvarNet Errors/Diagnostics |
|||
The routers are capable of providing useful diagnostic information for all possible Ethernet I/O messages received from a 3rd party device . The diagnostic response can provide information concerning whether a message was successful, was invalid or was not appropriate for a specified address.
Successful queries will simply be replied with the answer.
However, if the query is invalid or does not contain the correct parameters then an error diagnostic will be returned, instead of the expected answer, with the original query.
For lighting or configuration commands diagnostic information is available on demand and is achieved by specifying that you want this information returned using the Ethernet I/O 'Acknowledgment' feature.
In the ASCII format this will mean attaching the parameter ID 'A' with a parameter value of 1 or in the RAW format by switching the 'Acknowledgment' flag on in the command word.
The following table shows you the raw value and ASCII description for each error message:
Raw Value |
ASCII Description |
0 |
Success |
1 |
Error - Invalid group index parameter |
2 |
Error - Invalid cluster parameter |
3 |
Error - Invalid router parameter |
4 |
Error - Invalid subnet parameter |
5 |
Error - Invalid device parameter |
6 |
Error - Invalid sub device parameter |
7 |
Error - Invalid block parameter |
8 |
Error - Invalid scene parameter |
9 |
Error - Cluster does not exist |
10 |
Error - Router does not exist |
11 |
Error - Device does not exist |
12 |
Error - Property does not exist |
13 |
Error - Invalid RAW message size |
14 |
Error - Invalid messages type |
15 |
Error - Invalid message command |
16 |
Error - Missing ASCII terminator |
17 |
Error - Missing ASCII parameter |
18 |
Error - Incompatible version |
The error message contains the command data which was sent, followed by the data concerning the erroneous command. See below for an example error message in ASCII and raw formats.
If you send the following Query Device type command:
>V:1,C:104,@:2.2.1.1#
If the device does not exist, then the reply will be:
!V:1,C:104,@:2.2.1.1=11#
If you send the following Query Device type command:
0x00010068 0x00020002 0x00010001 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
If the device does not exist, then the reply will be:
0x02010068 0x00020002 0x00010001 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x0000000B