Colour definition on moving head unit

Good morning,

When you say

Quote from Heptagon

This almost works except that the colours come out in the reverse order, and Magenta (Position 2) doesn't happen - only 7 colours and white come out.

it sounds for me like there is a mistake in the manual itself. The best way to find out, which functions are available in for device, you check the channel with the channel overview. After you select the specific channel, you can send dmx values manually.

From the direct view on your xml code, it looks fine so far. But maybe you can also upload the manual for the device. It's easier to check with the originally written dmx chart.

Greetings, Stefan.

How did you try to stop the colourwheel rotation? When I double click on the fader in the device control, which will be shown, when you click on the drop-down button, then the rotation will be stopped right according to the channel overview. If you will set directly a static colour, then the rotation don't stop - that's true. So you need to stop the rotation first as explained before. In the moment, I don't know, if this is a right behaviour of the software itself. I need to think about and asking the team.

By the way: very funny to know in detail know, which device you are talking about. In Germany, this device is sold as Futurelight DMH-200. So I know the specs of it a bit. If you like to try to implement the definition for the Extended Mode, you can take a look to the DDF for the Futurelight DMH-160. This is quiet similar to your device.

It's true. So far, the Colorwheelrotation and also Gobowheelrotation are not stopped, in case a fixed Color / Gobo is set. This is currently the intended behavior, so there is nothing wrong with the DDF. Nevertheless, we can discuss whether this behavior is the right one. As Stefan mentioned, we can have the discussion in the Team.

You are welcome. Glad to hear, that you could work with the DDF of the Futurelight DMH-160. For implement the prism rotation, please take a look in the documentation in our wiki: in the german article Prisma (DDF-Syntax) DMXC3 you find an example at the point "

Prismenrotation auf gleichem DMX-Kanal" (prism rotation on the same dmx channel). I guess, you will understand the example - otherwise please ask again.

Hi,

Quote from Heptagon

Bye the way: what is the significance of 'mindmx = "191" maxdmx ="128"' in the example - with mindmx > maxdmx?

back then in the beginning of DMXControl 3, we defined that maxval is always greater than minval, because both parameter define the minimum and maximum possible value in a device function block. We also defined that Mindmx and maxdmx describe the position of minval and maxval. Therefore, if mindmx is greater than maxdmx you get a ramp down from maxval to minval while increasing the dmx value from mindmx to maxdmx. This behavior is designed for device functions like wheel rotation where the higher rotation speed is at the lower end of the device function block.

Regards

JP

<prism dmxchannel="17">
  <prismrotation />
  <step type="open" mindmx="0" maxdmx="3" caption="Open" />
  <step type="prism" mindmx="4" maxdmx="255" caption="3-facets radial prism">
    <step type="stop" handler="prismrotation" mindmx="128" maxdmx="132" />
    <range type="cw" handler="prismrotation" mindmx="4" maxdmx="127" minval="0.1" maxval="3" />
    <range type="ccw" handler="prismrotation" mindmx="133" maxdmx="255" minval="0.1" maxval="3" />
   </step>
</prism>

Hmm. I adapted the example from the Wiki to your needed values. Maybe you can check this in between. I will able to verify the code not until the evening in German time.

In your two tests / examples I just only can see three things, where I am not sure, how the software will react:

1. There is a crossing between the steps open and prism included. As you can see in my example, the range for the step open ends at dmx value 3 and the step prism included needs to start at dmx value 4. You wrote 3 for both values.
2. In both example, you wrote in the line for stopping the included prism prism rotation instead prismrotation for the handler value.
3. There were much more spaces in the code in general as I have seen this before, for example in front and behind of the =.

Also this three points I will try to check later. The rest of your code looks okay so far.

Good evening!

As I promised I checked now your DDF, which you attached in your post this morning. The only problem, which I could figure out, is, that due to the space in prism rotation the step for stop doesn't work. This you need to remove. All the rest works so far according to, when I take a look into the channel overview of DMXControl 3. The 18th channel reacts according to your noted responses.

I hope, it will work now. If not, please don't hesitate to ask again.

Regards, Stefan.