|
|
|||||||
| RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard. |
 |
|
|
Thread Tools | Search this Thread | Display Modes |
August 19th, 2011
|
#1 |
|
Junior Member
Join Date: Aug 2011
Posts: 8
|
Interpretation of ACK_TIMER
Hello,
Is it correct that a 0x0000 as an ACK_TIMER response indicates a "come back immediately for the requested and queued data"? Greetings Marc |
|
|
|
August 19th, 2011
|
#2 |
|
Task Group Member
Join Date: Aug 2008
Posts: 390
|
Yes, that is correct.
|
|
|
|
|
August 19th, 2011
|
#3 |
|
Administrator
Join Date: Feb 2006
Posts: 441
  |
I have to ask though, if you are ready immediately then why ACK_TIMER?
__________________
Scott M. Blair  RDM Protocol Forums Admin |
|
|
|
|
August 19th, 2011
|
#4 |
|
Task Group Member
Join Date: Aug 2008
Posts: 390
|
If you need a bit more time than 176us, but don't need the 100ms minimum value allowed in ACK_TIMER. The shortest possible RDM packet is around 1.3ms, so by the time the responder can send you the GET QUEUED_MESSAGE you'll have the data it requested.
|
|
|
|
|
August 21st, 2011
|
#5 |
|
Junior Member
Join Date: Aug 2011
Posts: 8
|
Hi Eric/Scott,
Yes, indeed this can serve quick turn-arounds, even a little bit more than 1.3 ms, depending on the application the ACK_TIMER reply itself (also 1.3 ms) as well as the max delay to response (2 ms) could be added together, of course depending very much on application. Greetings Marc |
|
|
|
|
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Welcome to the RDM Interpretation Discussion Forum | sblair | RDM Interpretation Questions | 0 | May 31st, 2006 10:47 PM |
Linear Mode
