![]() |
|
|||||||
| RDM General Implementation Discussion General Discussion and questions relating to implementing RDM in a product. |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#2 |
|
Task Group Member
Join Date: Jun 2006
Posts: 181
|
As support for Queued Messages is not mandated, you possibly have to decide based on whether your reponder supports that PID.
I think we need to propose a scheme whereby requests that are initially met by an ACK_TIMER can be serviced by a subsequent request within a known "time to live" period. You ask for something not immediately available - and are are given an ACK_TIMER xxx. If you ask again within (say) 10 xxx you are handed the requested data. If you ask after that time it is deemed to be stale and yiu get another ACK_TIMER. And yes, if your responder supports QUEUED_MESSAGES, it can get added to the list of pending messages. mroe discussion needed ... Peter Willis |
|
|
|
| Bookmarks |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| 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 |
| Request in the middle of ACK_TIMER | endoftheworld | RDM Interpretation Questions | 1 | July 13th, 2006 10:53 PM |