Echo Inspire Station > Echo Integration Interface > EOS UDP triggering?

Hi all,

I'm working on a system that originally just controlled lights in a studio space with an ETC Nomad Puck. A change order happened where they also want an Echo Inspire 2-button station to turn on some lights without having to go over to the Puck to turn lights on, since it's in a separate booth.

So the hardware of the system is currently: Echo Inspire 2-button station, Echo Integration Interface (both going to an Echo Station Bus), and ETC Puck through a Netgear network switch. The EII is also plugged into the same network the ETC Puck is.

So, how do I make it so that a button press on the Inspire station fires a Macro on the ETC Nomad? My current guess is using UDP strings, but I don't know how to capture an Inspire button press/button state into UDP and then have the Echo Integration Interface send that along/be heard by ETC Nomad, to then take the appropriate action.

I have set up in the Show Control tab in Eos an Event list with Network Type enabled. And I made sure the System Settings > Show Control > UDP Strings tab has the right port numbers and are enabled, too.

I'm also using StringTheory to monitor UDP commands and responses.

Any insights on how to make this happen? Thanks!

Parents
  • +1

    Hello, unfortunately this is not possible without some additional intermediary.  

    The strings which the Echo Integration Interface outputs are hard-coded to start with E$  However, Eos needs "arbitrary" UDP for Show Control events to start with "SC", followed by the arbitrary string.  So, you would need some device or software in the middle that could receive the string from the EII, then either add the prefix SC to it or create a new string (or OSC message, etc) to tell the Eos software what to do.  

    You would also need some kind of Echo "host" device such as a SmartSpace Controller or Echo Output Interface because in an Echo system, the button stations are relatively "dumb" devices which don't track the state of the system (that is, if zones or presets are active) - that is managed by the host(s).

    A different ETC-based solution would be to use an Analog I/O Gateway to take in the contact from a simple switch and have it send commands to Eos.  You may also be able to source other devices that take contacts from a push-button and send out programmable UDP messages.  I suspect it may be possible with an Arduino as well, but cannot give guidance on how to do so.

Reply
  • +1

    Hello, unfortunately this is not possible without some additional intermediary.  

    The strings which the Echo Integration Interface outputs are hard-coded to start with E$  However, Eos needs "arbitrary" UDP for Show Control events to start with "SC", followed by the arbitrary string.  So, you would need some device or software in the middle that could receive the string from the EII, then either add the prefix SC to it or create a new string (or OSC message, etc) to tell the Eos software what to do.  

    You would also need some kind of Echo "host" device such as a SmartSpace Controller or Echo Output Interface because in an Echo system, the button stations are relatively "dumb" devices which don't track the state of the system (that is, if zones or presets are active) - that is managed by the host(s).

    A different ETC-based solution would be to use an Analog I/O Gateway to take in the contact from a simple switch and have it send commands to Eos.  You may also be able to source other devices that take contacts from a push-button and send out programmable UDP messages.  I suspect it may be possible with an Arduino as well, but cannot give guidance on how to do so.

Children
Related

www.etcconnect.com