Is it a software or a hardware problem with the Colorsource 20?

1 If a fader is left on when the console is put into hibernation mode the light will stay on.

2 When the power is disconnected and the console restarts and all the faders are down a light will come on in the rig and follow the colour changes on the console as it starts up.

Parents
  • These are features of the fixture, not the console.

    When the console is hibernating, it stops sending any DMX and gently biases the DMX line "positive" as required by the RDM standard.
    This ensures there's no flicker, and allows any inline controllers (eg architectural button stations) to send their own DMX and/or other proprietary protocols down the wire. We have had a few reports of devices that appear not to detect DMX properly so don't treat this as "no data", despite what the standards say Disappointed

    1) Most DMX fixtures do one of the following "some time after" after DMX stops:

    • Turn off
    • Hold-last-look forever
      • The fixture keeps doing whatever it was doing when DMX stopped, until DMX starts again.
    • Play an internal Preset or Sequence
      • Sometimes they also send data along the DMX line to synchronise with other fixtures

    Many fixtures allow you to configure which of the above to do.
    Some even allow you to configure how long they will wait before turning off or playing the internal preset/sequence.

    For example, you can configure the ColorSource Par to play a Preset or Sequence when DMX is lost.
    With no DMX, use the buttons on the back to play the Preset/Sequence you want (or off!).

    It will then return to that same internal Preset/Sequence every time DMX is lost.

    2) The console will send the Home values for all patched fixtures when it loads the showfile.
    If that's not "all-zero-dmx", then the fixture will probably move or change internal colour.

    Fixtures that have 'non-standard' Intensity functions such that DMX@0 is not "off", are likely to produce some light while Homing.
    In most cases you'll never see that oddity when actually using the lights as ColorSource tries very hard to make everything work in almost the same way.

Reply
  • These are features of the fixture, not the console.

    When the console is hibernating, it stops sending any DMX and gently biases the DMX line "positive" as required by the RDM standard.
    This ensures there's no flicker, and allows any inline controllers (eg architectural button stations) to send their own DMX and/or other proprietary protocols down the wire. We have had a few reports of devices that appear not to detect DMX properly so don't treat this as "no data", despite what the standards say Disappointed

    1) Most DMX fixtures do one of the following "some time after" after DMX stops:

    • Turn off
    • Hold-last-look forever
      • The fixture keeps doing whatever it was doing when DMX stopped, until DMX starts again.
    • Play an internal Preset or Sequence
      • Sometimes they also send data along the DMX line to synchronise with other fixtures

    Many fixtures allow you to configure which of the above to do.
    Some even allow you to configure how long they will wait before turning off or playing the internal preset/sequence.

    For example, you can configure the ColorSource Par to play a Preset or Sequence when DMX is lost.
    With no DMX, use the buttons on the back to play the Preset/Sequence you want (or off!).

    It will then return to that same internal Preset/Sequence every time DMX is lost.

    2) The console will send the Home values for all patched fixtures when it loads the showfile.
    If that's not "all-zero-dmx", then the fixture will probably move or change internal colour.

    Fixtures that have 'non-standard' Intensity functions such that DMX@0 is not "off", are likely to produce some light while Homing.
    In most cases you'll never see that oddity when actually using the lights as ColorSource tries very hard to make everything work in almost the same way.

Children
No Data
Related