Yes, that was intentional. There are many different valid implementations and there was not a "one size fits all" approach that worked for everyone.
If you get an ACK_TIMER and the device does not support QUEUED_MESSAGES then you would go back and query the device again after the timer has expired.
It depends on the device as to whether it needs ACK_TIMER or not. There are many implementations where there is no need for ACK_TIMER as the information is immediately available.
A controller shouldn't worry about ACK_TIMER being supported in an end-device unless it gets an ACK_TIMER response.
__________________
Scott M. Blair
RDM Protocol Forums Admin
|