![]() |
|
RDM Interpretation Questions Discussion and questions relating to interpreting and understanding the E1.20 RDM Standard. |
![]() |
|
Thread Tools | Search this Thread | Display Modes |
![]() |
#1 |
Junior Member
Join Date: Sep 2014
Posts: 10
|
![]()
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 :-) |
![]() |
![]() |
![]() |
#2 | |
Administrator
|
![]()
I hear ya! It takes a bit to wrap your head around at first. Here is how I've implemented Gobo wheels in the past. This covers a rotating gobo wheel with control channels and 16-bit rotation.
Quote:
__________________
Scott M. Blair ![]() RDM Protocol Forums Admin |
|
![]() |
![]() |
![]() |
#3 | |
Junior Member
Join Date: Sep 2014
Posts: 10
|
![]()
Thanks, Scott! This is an interesting approach. I didn't think to place a secondary dependency.
I'm curious as to why you labeled the Gobo Rotate Function (Control) as a dependency on the Rotate High instead of the Wheel? Quote:
|
|
![]() |
![]() |
![]() |
Bookmarks |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
SLOT_INFO | Paul-Zero88 | RDM Interpretation Questions | 0 | September 30th, 2009 03:40 AM |