SC_SUB_MESSAGE values
I have recently discovered that I need to support draft V1 of the protocol in one of our products because there are systems out there with it, and the packet structure is different.
I thought SC_SUB_MESSAGE would be the way of differentiating between different draft standards, however The following values apply:
Draft1 - SC_SUB_MESSAGE = 0x01
Draft2 - SC_SUB_MESSAGE = 0x02
Draft3 - SC_SUB_MESSAGE = 0x01
So draft 1 and 3 have the same sub start code values... is/was this considered a mistake or is this how everyone's RDM packets are being structured?
I don't have the actual release yet, it should be with us today so I can't comment on that yet.
|
July 31st, 2006
Threaded Mode