EOS priority questions

Our system: EOS console (backup), EOS RPU (master), EOS RVI (client), all version 1.4.2.

Our console shows (via the [about] key) that it has a ACN priority of 101 and a Net2 priority of 9.

Our RPU has an ACN priority of 100 and a Net2 priority of 10.

On the console's ECU: Network screen , the console is set to ACN priority of 100 and Net2 priority of 10 (to match the RPU).  The option "Backup takes over at a higher priority" is checked (on).  I assume that is why the console is reporting a higher priority (via [about] key) than it is configured in the ECU.

Some questions:

What is the usefulness of having the backup take over at a higher priority? Is this option enabled by default (I know I didn't enable it explicitly)?

If the backup takes over at a Net2 priority of 9, what happens to the Unison system on the same network that is at Net2 priority of 10 and controls all of our houselights, worklights and running lights?  I remember when the system was being installed and the RPU (master) was turned off while the console (backup) was on, the console took over and turned off every light in the theater because it took over at a higher priority than the Unison.  This behavior was described to me as a bug that was going to be fixed- has it become a feature?

At least it is a feature that can be disabled :)

Todd

 

 

  • First let me say you appear to have a firm understanding of how priority works in our systems.

    You are absolutely correct that in a system that includes Unison and Eos/Ion you probably want the Eos and Unison at the same priority so they will pile on (HTP). In this type of system you should uncheck the "Backup takes over at higher priority" check box. Ideally this is done as part of the turn on.

    That said there are reasons to have the backup take over at a higher priority. Here are a few...

    • Your Primary Eos could fail, but still be outputting levels. If the backup takes over at a higher priority, levels from the primary will not keep the lights on.
    • If the backup is running at a higher priority, you can restart the primary without it sending level to the rig.

    I guess you could say this has become a feature, but I see it as a bug we fixed. We always intended this behavior to be configurable. The bug was that we did not allow access to the configuration. Now we do.

    Dennis

     

  • Dennis,

     Thanks for the information.  I will uncheck the "Backup takes.." option on our system as that is appropriate for our situation.  I can also see where the situations you describe would need to have the backup take over at a higher priority.

     Todd

     

Related