Element Classic and Ion Classic interaction

A local college theatre has an Ion in the booth and an Element on stage, both on a Net3 network. The installer told them there was no way to use the two boards at the same time and one of them had to be shut down in order for the other to control the rig. They have experimented and not been able to get around the restriction. Is there anything that they could change or add to the system to allow ether client, mirror, backup or remote shutdown/startup to avoid this situation?

Parents
  • an element can only connect to other element consoles or to nomad instances running in element mode. it is however not correct that you can have only one of them at the same time. depending on use-case it sensible to only have one of them running. technically speaking you can have both of them online and outputting, but each of them as an independent instance (not linked, so Go on one console wouldn't do anything on the other console). to avoid confusion it would probably be helpful if the ion and the element didn't control the same addresses (although it's technically possible).

Reply
  • an element can only connect to other element consoles or to nomad instances running in element mode. it is however not correct that you can have only one of them at the same time. depending on use-case it sensible to only have one of them running. technically speaking you can have both of them online and outputting, but each of them as an independent instance (not linked, so Go on one console wouldn't do anything on the other console). to avoid confusion it would probably be helpful if the ion and the element didn't control the same addresses (although it's technically possible).

Children
Related