Multi Ion users

Hey Guys,

I'm a relatively new ION user in NYC. I have extensive networking experience and I'm also a expression damily programer and a MA programer.  I'm doing a install for a pair of TV shows sharing one stage space with multiple sets and two Ion desks already working together on the network.  Right now we have our booth console set up as the primary console and the floor unit working as the client.  They have different ID numbers so that they can share dimmers and save files but different command lines, pages, and cue stacks.  we currently have 7 98 touring racks sensor+2's and 2 60A out sensor 2+ racks.  Data is being run NET3 to a common dimmer room and all racks are daisy chained into a 4 port ETC gateway. 

My question is, is there any way we can have two programers one on each desk working on the same network and writing cues and subs without interfering with the other? we've thought about writing in blind only using subs for each set as a work around.  If both consoles were setup as primary but with only one as the DHCP server could the work independently? Also would Partitioning work to solve this problem if we set up partitions for each of the 20 or so set spaces ? 

Thanks for the ideas

Cheers

Derek Gross

IA 52

 

Parents
  • You could very easily set up both desks as primary, and have individual show files, and both could control all of the dimmers on an HTP basis (most likely without having to change any settings since both consoles are networked to a NET3 gateway). If you want to limit what each desk can control, you can set the range of outputs available to each Ion in the shell, or establish per address priorities in the NET3 gateway.

    The downside to this setup is if Ion B needs the information stored on Ion A. If you truly need two independent systems using the same dimmers, you're probably ready to go.
Reply
  • You could very easily set up both desks as primary, and have individual show files, and both could control all of the dimmers on an HTP basis (most likely without having to change any settings since both consoles are networked to a NET3 gateway). If you want to limit what each desk can control, you can set the range of outputs available to each Ion in the shell, or establish per address priorities in the NET3 gateway.

    The downside to this setup is if Ion B needs the information stored on Ion A. If you truly need two independent systems using the same dimmers, you're probably ready to go.
Children
No Data
Related