• State Suggested Answer
  • Date
    Salazar
  • Date
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 184 subscribers
  • Views 1089 views
  • Users 0 members are here

RPU as Primary, console as Tracking Backup

I'm looking for info on what is normal practice when adding a Tracking Backup to a system, specifically where the additional components need to be to be usable mid-show if either the Primary or Backup go down.
We're looking at setting up a Tracking Backup by purchasing an Ion Xe RPU and running the RPU as Primary Master, and our Eos Ion Xe Console as a Tracking Backup.  The console will stay in the Tech Booth for shows and we will run the show from the console under normal circumstances.
This is the part I'm not clear on.  If the Console (Tracking Backup) goes down, the RPU (Primary) will have to be in the booth to be accessed? ...and will have to have at minimum a keyboard (for the spacebar for "GO" commands, etc.), a screen to see what is happening, preferably a touch screen, and perhaps a mouse, so the show can be run from the RPU if the console goes down (unlikely, if the console is the Tracking Backup, but still possible).
If the RPU Primary goes down then the console takes over (once we acknowledge the change by pushing the button that appears on the Backup's screen).
Also, when it comes down to it, is there much price difference between an Ion Xe Console, and an Ion Xe RPU?  Perhaps we should just purchase a second console?
  • 0

    Hi Salazar.

    Salazar said:
    If the Console (Tracking Backup) goes down, the RPU (Primary) will have to be in the booth to be accessed?

    You're correct that if you are sending commands (programming, firing cues, etc.) with your console (acting as Tracking Backup) and it were to go offline for any reason, you would need some other way of communicating with the Primary. This could mean that you have your RPU (Primary) setup next to your IonXE in the booth. Another option, if available, is to have the RPU setup somewhere else in your space and have a Client in your booth that can send commands to the Primary in the event of your Backup going offline. 

    Of course, there are other options to setup a Backup as there are many factors to consider (hardware failure, crashes, network switch failure, etc.) 

    Salazar said:
    If the RPU Primary goes down then the console takes over (once we acknowledge the change by pushing the button that appears on the Backup's screen).

    If you wanted, you can have the Backup automatically take control. You may not want it to do that, but wanted to make sure you knew it was an option. Since 3.2, you can enable this within Eos in Setup->System->Session and toggle "Backup Auto Take Control" to your preferred setting. Additionally, you can have the Backup take a higher sACN priority upon takeover (regardless of auto take over). This is setup in Patch->Protocols->sACN and toggling "Backup Uses Higher Priority". This would ensure that if the Primary does come back and starts outputting (which it shouldn't), any sACN receiver would ignore sACN levels being sent by it. If you're running a version prior to 3.2, these are configured in shell settings. 

    For pricing, I would contact your local ETC rep.

    A RPU is more flexible in terms of where you can set it up within your system. Since it can be rack mounted, you could add it to an equipment rack closer to the backbone of your network infrastructure. Obviously, with the console, you'll get an additional face panel, and as such you can have two people programming at once (of course you can always with a keyboard on the RPU). It all depends on what you think would be best for your workflow and team. 

    I hope this helps answer some of your questions. I'm sure others on here will have more ideas and suggestions.

  • 0 in reply to bill nowlin

    Hello Bill

    So we've run the last two Tech Rehearsals with a Nomad Setup on a Laptop as Primary, and the IonXe as Tracking Backup, both in the booth so both accessible to the operator.  We ran the cues from the Ion's control surface.

    Before last evening's rehearsal I made the changes in Setup and Patch you mentioned to have the Ion take over automatically, and also to have the Nomad NOT take back control when it came back online until authorised to do so.

    We tested it a few times to see how it all worked if the Primary, or the Backup went down (by pulling the corresponding network cables), and except for a blink in the conventionals when the Primary goes down and the Backup takes control, it all seem seamless.

    We'll play with it a bit more before we decide which way we want to go.  Thank you for you answers and suggestions.

  • 0

    One thing to add:

    If you're using local input/outputs on your backup console, takeover will be less complete. This seems obvious but gets overlooked sometimes.

    If your using local DMX outputs from the console and the console goes down, or if you're using a USB-MIDI adapter to trigger stuff this will be lost. Products to consider in that case would be networked products like ethernet DMX gateways and ETC's Response MIDI gateway.

    Finally: the multi-console connection is network-based. If you currently don't have a network switch close-by consider adding one.

Related

www.etcconnect.com