SLOT_INFO and 16-bit secondary slots - E1.20 RDM (Remote Device Management) Protocol Forums

tharron · December 16th, 2014

Hi folks,

I'm well into my RDM client implementation, but upon reflecting I've come to realize that I'm not sure how to handle 16-bit secondary parameters. For instance, in my fixture I have a gobo with a 16-bit rotate/index value.

The way I interpret the spec is that a secondary channel may not have a coarse and fine byte. What's the 'proper' way to handle this? The more I think about it the more I want to mark every channel as a primary/undefined :-)

December 16th, 2014	#1
tharron Junior Member Join Date: Sep 2014 Posts: 10	SLOT_INFO and 16-bit secondary slots Hi folks, I'm well into my RDM client implementation, but upon reflecting I've come to realize that I'm not sure how to handle 16-bit secondary parameters. For instance, in my fixture I have a gobo with a 16-bit rotate/index value. The way I interpret the spec is that a secondary channel may not have a coarse and fine byte. What's the 'proper' way to handle this? The more I think about it the more I want to mark every channel as a primary/undefined :-)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
SLOT_INFO	Paul-Zero88	RDM Interpretation Questions	0	September 30th, 2009 03:40 AM