E1.20 RDM (Remote Device Management) Protocol Forums  

Go Back   E1.20 RDM (Remote Device Management) Protocol Forums > RDM Developer Forums > RDM General Implementation Discussion
Register FAQ Community Calendar Today's Posts Search

RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product.

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
Old October 19th, 2009   #7
sblair
Administrator
 
Join Date: Feb 2006
Posts: 441
Send a message via AIM to sblair Send a message via MSN to sblair
Default

The ACK_TIMER is supposed to indicate to the controller to "bugger off and leave me alone". Now that only applies to the specific PID. So if you ACK_TIMER me on GET DMX_START_ADDRESS, that doesn't mean I can't still ask you for other PID's, which you may ACK_TIMER as well.

ACK_TIMER is really only a partial solution as it requires the controller to remember all the questions it has asked and come back and ask them again later and hope for a reply. QUEUED_MESSAGES does a great job at closing the loop at providing the information to the controller when it becomes available.

I have not done a lot of experimentation with controllers and ACK_TIMER to see if they really do wait the amount of time that is included in the ACK_TIMER response before asking (if they ask again at all). All my implementations have used QUEUED Messages so that it negates that.
__________________
Scott M. Blair
RDM Protocol Forums Admin
sblair is offline   Reply With Quote
 

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 02:53 AM.


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