|
RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard. |
|
Thread Tools | Search this Thread | Display Modes |
January 12th, 2007 | #1 |
Task Group Member
Join Date: Jun 2006
Posts: 181
|
Table 6-6 Checksum Example Error
In section 6.2.11 Table 6.6 we have an example of checksum usage.
It happens to use of a GET_COMMAND: STATUS_MESSAGES and shows in slot #24 a value of 0xFF for the paramater data STATUS_ERROR. HOWEVER the Status Type define for STATUS_ERROR is shown in Table A-4 as 0x04. How did I find this ?? A controller (by others) sent me a GET:STATUS_MESSAGES with 0xFF in the paramater data, which I rejected with a NACK: NR_DATA_OUT_OF_RANGE, since the only valid values (from Table A-4) are 0x00 thru 0x04. I suggest we review this (and other task group posts) in Dallas before making some of this knowledge public via this forum regards |
January 19th, 2007 | #2 |
Administrator
|
That example is incorrect. The correct value for STATUS_ERROR is 0x04. The correct value for SC_SUB_MESSAGE is 0x01.
With the STATUS_ERROR of 0x04 and SC_SUB_MESSAGE, the correct Checksum would be: High Byte=0x06, Low Byte=0x69.
__________________
Scott M. Blair RDM Protocol Forums Admin Last edited by sblair; January 19th, 2007 at 09:08 PM. |
Bookmarks |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
COMMS_STATUS Error reporting | prwatE120 | RDM Interpretation Questions | 0 | January 20th, 2007 08:07 AM |
ACK_TIMER Example Error | prwatE120 | RDM Interpretation Questions | 1 | December 26th, 2006 04:46 PM |
Checksum curiosa | sjackman | RDM General Implementation Discussion | 3 | October 3rd, 2006 07:24 AM |
Discovery Checksum Problem Analysis | nic123 | RDM General Implementation Discussion | 3 | September 24th, 2006 11:25 PM |
Error counters | Nigel Worsley | RDM Interpretation Questions | 1 | July 3rd, 2006 04:42 PM |