|
RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard. |
|
Thread Tools | Search this Thread | Display Modes |
July 11th, 2006 | #1 |
Junior Member
Join Date: Jul 2006
Posts: 6
|
Request in the middle of ACK_TIMER
Hey all,
Since the spec doesn't cover this in detail, I just wanted to know how what should be the outcome of this possible scenario :- Controller sends SET_CMD (LAMP_STRIKE) Responder sends back an ACK_TIMER ( wait 5 secs) . . . Controller sends a GET_CMD (any PID) . Responder sends back an ACK_TIMR (wait 2 secs) . . . . (end of 5 sec) Controller sends GET_QUEUED what happens now ? (In the Message Queue on Responder , we'll have 2 messages, which gets sent first ?) I'd assume a FIFO (is that correct ?) Hope it makes Sense Cheers EOD Last edited by endoftheworld; July 12th, 2006 at 12:04 AM. |
July 13th, 2006 | #2 |
Administrator
|
EOD,
It's up to the device. There are no requirements as to which message gets sent first. There could also be other messages pending as well, for example someone could have changed the DMX Start Address on the menu of the device so it Queued up a message to report that back to the console as well. Put another way, the controller should never make an assumption that just because it got an ACK_TIMER earlier that when it does the next GET QUEUED_MESSAGE that it would get a response back for a specific PID. Hope that helps..
__________________
Scott M. Blair RDM Protocol Forums Admin |
Bookmarks |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
ACK_TIMER Handling | ericthegeek | RDM General Implementation Discussion | 8 | January 20th, 2011 08:15 PM |
ACK_TIMER, QUEUED Messages | berntd | RDM Interpretation Questions | 1 | November 12th, 2008 10:02 PM |
ACK_TIMER Example Error | prwatE120 | RDM Interpretation Questions | 1 | December 26th, 2006 03:46 PM |