Using and Ion to backup an Eos

An Ion can back up an Eos up to the Ion's Capabilities.  So yes after 2048 address the Ion would not be able to output DMX.  You will also loose the ability to recall snapshots, loose tab browsing, and mostly the Poe switch on the back of the desk.

P

An Ion can back up an Eos up to the Ion's Capabilities.  So yes after 2048 address the Ion would not be able to output DMX.  You will also loose the ability to recall snapshots, loose tab browsing, and mostly the Poe switch on the back of the desk.

P

just to add what P said, just in case you didn't already know... when the Ion is attached to the EOS as a Tracking Backup, it will go online as an Eos client, so it will have tabs, and full access to all address's above the 2048.  If the Eos were to go offline, the Ion would take over as master, but as a master Ion, not a master Eos, so you would lose those Eos features that the Ion doesn't support.

So, in other words, the Ion will not act as a proper backup for anything above the 2048 should the Eos fail, but it will be able to help out on the network as long as the Eos is happy.

Or at least this is my understanding from the last time I used an Eos and Ion in a similar environment to what you have described. In the end, we ended up using and Eos RPU as the Master, an Eos desk as the Tracking Backup, and an Ion as a client to the RPU. So if the RPU went down, the Eos desk took over the show, and then we just switched the Ion to look for the Eos desk instead of the RPU.

HTH,