E1.20 RDM (Remote Device Management) Protocol Forums

E1.20 RDM (Remote Device Management) Protocol Forums (http://www.rdmprotocol.org/forums/index.php)
-   RDM Interpretation Questions (http://www.rdmprotocol.org/forums/forumdisplay.php?f=5)
-   -   Interpretation of ACK_TIMER (http://www.rdmprotocol.org/forums/showthread.php?t=1106)

eldoMS August 19th, 2011 04:50 AM

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

ericthegeek August 19th, 2011 11:12 AM

Yes, that is correct.

sblair August 19th, 2011 12:31 PM

I have to ask though, if you are ready immediately then why ACK_TIMER?

ericthegeek August 19th, 2011 01:08 PM

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.

eldoMS August 21st, 2011 03:39 AM

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


All times are GMT -6. The time now is 05:44 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.