Slow 2nd byte in zero count move for I-Cue

Hello, Click:

I am curious about your current data stream.  Are we talking hardline DMX out of the console to these units?  If so, do we have them talking through a splitter or gateway that may have settings that could impede communication?  Do you know the setting of the DMX speed at the port of the Element console?

Do you have just the one I-Cue or are do you have others?   Are other units behaving in the same way when sent the same data from the console?

Thank you

I will double-check the DMX run at the theatre tomorrow, but in the meantime could you advise how to check the DMX speed setting at the Element?

Thank you.

To check the speed settings:

1. Exit to the shell by pressing [Displays] or [Browser] and selecting {Exit}

2. Click on {Settings} when it pops up in yellow

3. Navigate to the {Local I/O} tab. Speed information for each port will be listed there, among other things.

Thanks!

Hans

The single DMX run is as follows (all hard wire):

Element-->Sensor Pack-->Wybron PSU (feeding (3) Eclipse Dowsers)-->Rosco I-Cue-->City Theatrical DMX Iris.

There is one I-Cue and one Iris.  No opto-splitter is involved.  It's a very small system.

Hans, I checked the DMX speed, and it was set to Maximum.

Hello, Click:

If you connect the I-Cue directly to the output of the console, so it is not controlled through the Sensor Pack, do you still see the same behavior?

Thank you!

Yes, I connected the I-Cue and Iris directly to the console.  Without feeding through the Sensor pack and Wybron PSU, the problem remains.  Any other suggestions?

Thanks

When you checked the dmx port speed, did you try slowing it down?