You can get to this screen by going to the "Shell" and selecting "Settings" to bring up the EOS Configuration Utility ("ECU" in ETC Parlance). Our console had a Class A, non-routeable IP address. Of course, the computer/device you are using for control must have an IP address in the subnet of the console. Refer to Section 5.2 of this manual (Electrical Installation) for more information. There's just a couple things you need to need to establish communications. Step 2 Electrical Connections Using the labels on the back of the instrument as a guide, connect the process inputs, outputs and power supplies. The manual is very clear that, "All text will be queued up until either a carriage return (hex 0D), a “\r”, or a “#”, is encountered to show the end of the command". Cue 1 2 – run cue 2 from list 1, on the appropriate fader.The commands are detailed on page 23 of the EOS Family Show Control User Guide. (Although, implementing my "simpler is always better" design principle, for an upcoming show we will be firing old school, hardware-based MIDI Show Control out of the Ion to control Dataton Watchout).ĮTC has implemented into the Ion (and the Eos family) a simple ASCII-based "String Interface" control protocol that can be sent via a serial port or via IP. In most of the stuff I'm doing these days, I'm trying to move away from legacy protocols like MIDI, serial, and DMX and into IP everything. I'm a noob on the Ion, but I worked with my colleague Sue Brandt who can find her way around the board, and this blog assumes you know the basics of the console as well. I had a little time today (we're on winter break and don't have classes) so we set up our ETC Ion lighting console to see how to control it over the network. I've written before about controlling a GrandMA2 console, Figure 53's QLab V3, Weigl's ProCommander, and Stage Research's SFX all using ASCII commands over IP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |