Forum: RDM Marketplace Discussion
February 6th, 2013
|
Replies: 4
Views: 17,923
Tomas,
Reading the spec again, my...
Tomas,
Reading the spec again, my interpretation is that "slot" and "channel" refer to the same concept (slot offset), so the first 2 bytes of SLOT_INFO is a slot offset, and the slot# in the GET...
|
Forum: RDM Marketplace Discussion
February 6th, 2013
|
Replies: 4
Views: 17,923
Tomas,
Thanks for your responss (and to...
Tomas,
Thanks for your responss (and to Peter Willis for forwarding this to Robe). Unfortunately, I no longer have the Actor 3 here to play with.
As you advised, I use the first 16-bits of each...
|
Forum: RDM Marketplace Discussion
January 31st, 2013
|
Replies: 4
Views: 17,923
|
Forum: RDM Interpretation Questions
February 16th, 2012
|
Replies: 6
Views: 12,305
Thanks for the quick responses, gents.
...
Thanks for the quick responses, gents.
Scott, I didn't know QUEUED_MESSAGE was optional for the controller; thanks. I do try to handle both responder ACK_TIMER implementations anyway...
|
Forum: RDM Interpretation Questions
February 14th, 2012
|
Replies: 6
Views: 12,305
ACK_TIMER corner cases
Hey guys, I have two unusual ACK_TIMER response cases I'd like to think are illegal, but the RDM spec doesn't expressly forbid:
1. ACK_TIMER following ACK_OVERFLOW for the same pid
For example:...
|