Fixture Profile Request: Futurelight CC-200

light-control.de/.../manual_FUTURELIGHT_CC200.pdf

DMX parameters in english on pages 30 and 31

official fixture profile updates through ETC only start again in the new year and have usually a turn around of 2 weeks, that might not be soon enough for you? but you might be able to create the fixture yourself, it has only 4 parameters?

How on earth did you manage to find that? Despite extensive searching, all I could ever locate was the service manual. Thanks so much for that anyway.

Whilst doing some digging, it has become apparent that this fixture is essentially a carbon copy of the Robe Beam 250XT (supposedly the two manufacturers have been linked at some point). As it happens, with Robe being a more prominent brand, there is already a profile for this model in the fixture library. Could you possibly confirm if this corresponds with the parameters and respective value ranges of the CC-200? If so, I can simply use that instead.

Thanks.

from the looks of it that should work. it's not totally complete (the dimming while focussed to a hard edge seems to be missing, i.e. parameter 4, value 0 to 192). and the colors and effects are not labelled, but seem functional.

I'm not sure what you mean. The colours are labelled when I open the ML controls display with this type of fixture selected, as are the effects.

I'm not sure what you mean. The colours are labelled when I open the ML controls display with this type of fixture selected, as are the effects.

ah, sorry. you're right of course. only looked at the personality and didn't realize that there were a color wheel and a beam fx wheel in place.

Is it possible to check the attributes of a fixture without patching it?

Why are there an extra two parameters in the fixture editor for this profile? I notice that neither have a DMX offset associated with them—is that what a virtual parameter is? If these two parameters are indeed virtual, how exactly do they know what other 'real' parameters to manipulate? Comparing the programmed value ranges in these two parameters to the ranges specified in the manual you managed to find seems that indicate that they are all wrong. For some reason, however, all editing options for the parameters themselves and their associated ranges are greyed out, meaning it is impossible to rectify this myself.

How do the ranges in the channel for colour have only generic names yet in the ML controls display each tile has a specific name and icon for each colour in the wheel? I find that rather confusing.

That confusing bit caught me as well. If you select one of those channels in patch, find the softkey Attribute, have a look at the far right end of the CIA. You will see that there is a color wheel and a beam effect wheel. Since you could change the colors in the color wheel, there needs to be a way how you could change it in patch as well... If you click either one of those wheel fields you will get to a display where you see the contents.

All the parameters in the profile without a DMX slot are virtual. Greyed out are either lamp controls or linked parameters. This linking happens in a part of the personality that doesn't have a graphical interface to change it, so it's off limits.
I didn't have a closer look, do you have an example of where you get wrong values?

Regarding the virtual parameters, I thought that must be the case as I could not understand how else they could be connected to the actual DMX channels for a particular attribute. So can only ETC themselves alter anything to do with these?

Exactly

Is there no separate software utility available to create fixture profiles as available for other consoles, or is that not publicly released and only used by ETC?

The ranges specified for the effects wheel channel correspond with the list in the manual. It is the colour wheel channel which has the wrong ranges. Unfortunately I am not at my computer so cannot take a screenshot of this in Nomad, but if you compare the values in the manual to those in the colour wheel parameter you will see none of them match.

Could you explain what the user min and user max columns modify exactly?

if a parameter has a color or an effect wheel assigned, then the values are taken from there. if you select a channel in Live and open About>Patch, you will see that the output values of the colors match perfectly.

user min and max define what values the user sees. have a look at an intens parameter. you will see min max are 0 and 255 but user min max are 0 and 100. so in reality the parameter can output between 0 and 255 but the user makes his choice between 0 and 100. the user max and the max column mean the same thing and so do min and user min. it's just that one number is the user side and the other is for the output side.

So user min and max is what enables values to be displayed as a percentage instead of the raw DMX value (0–255)?

As each of these parameters have ranges, how can I finely adjust the values selected with the buttons? Is this possible?

Can someone please advise me on these two matters?

Hi Aaron:

Yes, user min and max allows percentages to be shown instead of 00-255 if you desire, but it doesn't do the math for you as to what those percentages should be.

Ranges are the values selected by the buttons- then to move within those you would hold down shift while moving your encoder.

Thank you,

Additionally, your request has been submitted for when we start making profiles again the new year.

Thank you very much, Shasha. As I stated in my first message, strangely the CC-200 is identical to the Beam 250 XT produced by Robe. I would just use that fixture profile instead—both manuals have the exact same DMX chart—however there are a few slight problems with it anyway related to incorrect or missing ranges.

Could you possibly estimate how long it would take for the profile to be completed? How exactly are fixture profiles that have been requested by individuals such as myself released? Does EOS have some sort of facility to import individual fixture definition files?


Regarding parameter ranges, I am using Nomad in Element mode, as opposed to EOS, so I do not have encoders. Can I scroll within ranges in ML Controls somehow? I want to know how to do this for two reasons: so that, if desired, I can set the colour wheel to such a position where the beam produced is split between two adjacent colours, and for adjusting the strobe rate on the shutter channel.

When the button pertaining to each range specified for a particular parameter is selected in the ML Controls display, is the value outputted the lower bound of that range or its midpoint, or neither?

Thank you, Aaron.

As other responses have noted, the delay now is simply because of the holiday but our typical turnaround time for new profiles is two weeks. Once the holidays are over we will do our best to have a library patch released before 1/14/2017 that will include the CC-200.

Profile requests are release as Fixture Library Updates via our website. If you go to the same location as software downloads you will also find the most recent library patch. We are creating fixture definition files and then creating an installer to place them onto your console.

In ML Controls clicking the title of any parameter will give you a virtual encoder on the screen. You can use this to move within ranges.
The value output is the lower of the range when selecting buttons in ML controls.

Thank you,