• Date
    Jurgensp99
  • Date
  • Replies 6 replies
  • Subscribers 96 subscribers
  • Views 7217 views
  • Users 0 members are here

Priorities

We are working in a ballroom that has motorised screens. Some of the down lights are hitting the screen so need to be turned off.

We are achieving this by sending out UDP triggers from the Crestron to the Paradigm.

Screen goes down/Lights turn off. Screen goes up/Lights turn on.

All of this is working well except when the screen is down/lights off and someone changes to another preset, the screen lights are affected.

The question is how to we set a priority on the screen lights group/presets/channels to take precedence over other commands when the screen in down?

Parents

  • (Isn't this fun having multiple of us look at this at different times?)

    I'd add that, if there's a risk of competing control (like a DMX input for console control or anything similar), you could also use a Space or Group EZ_Set_Arbitration to take the channels to Use Internal. That would usually keep a console or any other source from driving them up.

    I'd probably use Graham's wall approach on the front end coupling with making that zero level preset higher priority. The nice thing about presets is a fade between architectural levels (sorry, I don't have a workaround to slew to console levels from arch levels).


    Rough Implementation Notes:

    Put channels that hit screen into adjacent space joined by wall.
    Create a toggle macro to fire via UDP.

    Screen On Steps:
    Close wall
    Play 2 second preset including only screen channels set to zero at priority 200.
    Space EZ set arbitration on screens space to Use Internal.

    Screen Off Steps:
    Deactivate screen channel zero preset.
    Space EZ set arbitration on screens space to HTP with Priority.
    Open wall.

Reply

  • (Isn't this fun having multiple of us look at this at different times?)

    I'd add that, if there's a risk of competing control (like a DMX input for console control or anything similar), you could also use a Space or Group EZ_Set_Arbitration to take the channels to Use Internal. That would usually keep a console or any other source from driving them up.

    I'd probably use Graham's wall approach on the front end coupling with making that zero level preset higher priority. The nice thing about presets is a fade between architectural levels (sorry, I don't have a workaround to slew to console levels from arch levels).


    Rough Implementation Notes:

    Put channels that hit screen into adjacent space joined by wall.
    Create a toggle macro to fire via UDP.

    Screen On Steps:
    Close wall
    Play 2 second preset including only screen channels set to zero at priority 200.
    Space EZ set arbitration on screens space to Use Internal.

    Screen Off Steps:
    Deactivate screen channel zero preset.
    Space EZ set arbitration on screens space to HTP with Priority.
    Open wall.

Children
No Data
Related

www.etcconnect.com