Elation SixPar 300 dimming issue after console update to 2.5

If you patch an example fixture as regular dimmers and fade those up and down, do you see the same fade performance? Try cues of various timings (as you have been doing) to see if it makes a difference.

From the manual, it looks like this fixture only does 8-bit RGBWAU with an optional intensity parameter (with strobe/macros in the larger profile). Which profile are you currently using?

To answer your question - there isn't a setting I can think of that would affect this on the console. Patching as dimmers will work around any potential issues in the color mixing code. Let us know what you find!

Hi Hans
I have tried both the 8 bit and the 16 bit profiles but there is no change in the dim.
The lights were behaving fine with a great dim before the update to 2.5.1. We were running 2.3.2.

The lights dim properly when used on a Chamsys MQ40 so its leading us to think it is in the software.
I have a message out to Elation to look for a firmware update but from what I can tell the fixtures are current.

Hi Hans
I have tried both the 8 bit and the 16 bit profiles but there is no change in the dim.
The lights were behaving fine with a great dim before the update to 2.5.1. We were running 2.3.2.

The lights dim properly when used on a Chamsys MQ40 so its leading us to think it is in the software.
I have a message out to Elation to look for a firmware update but from what I can tell the fixtures are current.

Did you check to see if the dmx card in the ion needed an update? Not sure if there was any change 2.3>2.5 on the Ion DMX side.

Building on this - can you check the DMX speed in the shell for the port that you're using (Exit -> Settings -> Local I/O)? Try Fast or Medium if currently set to Max.
The "patch as dimmers" test would be really great to try out, as it helps us isolate possible issues on the console side.
Is the DMX line terminated?

Will check this out on Monday and document what we find. Ill be back!