Overview of ETC Ion
ETC Ion is a versatile lighting control platform that integrates hardware and software for advanced cue management. The Ion Operations Manual, available at www.etcconnect.com, details setup, network devices, and out‑of‑sequence cue handling. It supports Eos, Gio, and Ion Xe systems. It supports live shows
Hardware and Software Components
ETC Ion’s architecture centers on a modular RPU (Remote Processing Unit) that runs the Ion software suite. The RPU hosts a dual‑core ARM processor, 512 MB DDR4 RAM, and 4 GB eMMC storage, providing ample headroom for real‑time cue execution and network communication. A 10‑GbE Ethernet port, optional Wi‑Fi 6, and a serial RS‑232 interface enable flexible connectivity to lighting fixtures, DMX‑512 consoles, and other control devices. The Ion console itself incorporates a 10‑inch capacitive touchscreen, a dedicated control surface, and a high‑resolution 4K display for previewing cue lists and fixture data. On the software side, the Ion Operations Manual describes the Ion software installed on the RPU, which includes the core lighting engine, cue list editor, and network stack. The software supports DMX‑512, Art‑Net, sACN, and OSC protocols, allowing seamless integration with a wide range of fixtures and third‑party devices. Firmware updates are delivered via the Ion web interface, ensuring the system remains current with the latest performance enhancements and bug fixes. Together, the hardware and software components form a cohesive platform that delivers reliable, low‑latency control for complex lighting productions.
The Ion console’s firmware is modular, allowing users to load custom extensions via the RPU’s USB port. Each extension can expose new DMX channels or control protocols, expanding the system’s capabilities without firmware upgrades. This design supports future‑proofing and simplifies maintenance across large venues 24/7 support

Supported Control Systems
The ETC Ion platform is engineered to work seamlessly with a broad spectrum of ETC lighting consoles and remote processing units. The Ion Operations Manual explicitly lists the following systems as fully supported: the Eos Titanium, the standard Eos console, the Gio and Gio 5 models, the Ion Xe and Ion Xe 20 units, the Element 2, the Eos RPU, the Ion Xe RPU, and the portable ETCnomad Puck. Each of these devices can be connected to the Ion RPU via the 10‑GbE Ethernet interface or, where available, through Wi‑Fi 6 for wireless links. The manual also notes that the “About System” feature will display all network devices currently linked to Ion, allowing operators to verify connectivity to any of the listed consoles. In addition to the core consoles, the Ion software supports a variety of fixture protocols—including DMX‑512, Art‑Net, sACN, and OSC—ensuring that fixtures controlled by the listed consoles will respond correctly to cue changes, link instructions, and out‑of‑sequence cues. The compatibility list is maintained and updated through firmware releases available on the ETC website, ensuring that new console models or firmware revisions remain integrated with the Ion ecosystem. This extensive support framework enables lighting designers to incorporate Ion into existing rig setups without significant reconfiguration, providing a unified control environment across multiple ETC hardware platforms.

Ion’s cue architecture lets designers build nested lists that run in or sequence, a flexibility!

System Requirements and Compatibility
Ion requires a 10‑GbE RPU, 2 GB RAM, 64‑bit OS, and firmware 5.0+. Supported consoles: Eos Titanium, Gio, Ion Xe, Element 2. Network must be 802.11ac or Ethernet. Firmware updates via ETCconnect.com. All updates via ETCconnect ensure secure installs
Minimum and Recommended Hardware

Minimum hardware for ETC Ion includes a 2 GHz dual‑core processor, 2 GB RAM, 20 GB SSD, and a 10‑GbE network port. Recommended configuration upgrades to a 3.5 GHz quad‑core, 4 GB RAM, 50 GB NVMe SSD, and dual 10‑GbE ports for redundancy. The RPU should run Windows 10/11 Pro or a supported Linux distribution with the latest firmware. A dedicated graphics card is not required, but a 128‑bit GPU can accelerate visual previews. Power supplies must provide 12 V/5 A per port, with an additional 30 % headroom for peak loads. All hardware must comply with IEC 60335 and UL 60950 safety standards. For large‑scale productions, consider clustering multiple RPUs behind a load‑balanced switch. The Ion console supports up to 512 DMX universes via 10‑GbE, with optional 1000‑Mbps Ethernet for legacy DMX‑512. Ensure that the network switch supports VLAN tagging and IGMP snooping to prevent broadcast storms. The firmware version 5.0.3 or newer is mandatory to access the latest cue‑linking features, and the RPU must be updated through ETCconnect.com. Compatibility with older consoles (Eos, Gio, Ion Xe) is maintained via the Ion Bridge software, which translates DMX and OSC protocols. For troubleshooting, refer to the Ion Operations Manual, downloadable from the ETC website. This manual provides detailed schematics, pinouts, and troubleshooting steps for each hardware component. Following these guidelines ensures reliable performance and scalability for live events, theater productions, and broadcast environments.

For advanced rigs, pair the Ion RPU with Ion Xe modules that add DMX outputs and audio processing. These modules need a separate 12 V/10 A supply and a 10‑GbE uplink. The Ion Xe 30 supports 1024 universes and includes a 1 GbE port for remote control. Synchronize the RPU clock via NTP or PTP to keep cue timing accurate. Use a Layer 3 switch with QoS to prioritize OSC traffic.
All components should reside in a climate‑controlled rack, maintaining 20 °C–25 °C. The Ion RPU chassis is IP20 rated; for high‑humidity sites, use an IP54 enclosure. Ensure compliance with local codes and standards.
Operating System and Firmware Versions
ETC Ion’s software stack is designed for stability and performance on modern operating systems. The RPU runs a hardened Windows 10/11 Pro edition or a certified Linux distribution (Ubuntu 22.04 LTS or CentOS Stream 9). Firmware version 5.0.3 or newer is required for full OSC support, DMX‑512 over Ethernet, and the latest cue‑linking algorithms. Firmware updates are delivered via the ETCconnect portal; the RPU automatically checks for updates at boot and can be forced to update through the Ion Operations Manual interface. Compatibility tables in the manual list supported OS builds, kernel versions, and required patches. For Windows, the Ion software requires the .NET 6 runtime and the Microsoft Visual C++ Redistributable 2022. Linux builds depend on libuv and libssl libraries; the Ion package includes a script that verifies library versions before installation. The firmware itself is a monolithic binary flashed over the serial console or via the web UI. All firmware releases include a cryptographic signature; the RPU verifies the signature during boot to prevent tampering. The manual details the procedure for manual flashing, including the use of the “ionflash” utility and checksum validation. The manual’s troubleshooting section covers common OS issues such as driver conflicts, firewall rules that block OSC, and the need to disable power‑saving modes on the network interface. Users are advised to keep the OS and firmware up to date to benefit from security patches, bug fixes, and new features such as the expanded cue‑linking interface. The Ion Operations Manual provides a step‑by‑step guide for upgrading the OS, installing the necessary dependencies, and firmware updates, and verifying the firmware integrity after each update.
Network and Connectivity Options
ETC Ion supports a wide range of network protocols and connection methods to integrate seamlessly into modern lighting setups. The RPU’s Ethernet port is a 1 GbE RJ45 interface that can be configured for static IP, DHCP, or PPPoE. For environments that require redundancy, dual‑port Ethernet is available; the firmware automatically fails over to the secondary port if the primary link drops. Ion also supports Wi‑Fi through an optional USB adapter; the adapter is recognized by the RPU and can be managed via the web UI. The console can act as an OSC server or client, exposing a 5719 UDP port for OSC messages. DMX‑512 over Ethernet (E1.31) is fully supported; the RPU can receive or transmit E1.31 streams on any of its network interfaces. For DMX‑512 over USB, the Ion software includes a virtual DMX interface that maps to the RPU’s USB‑to‑DMX adapter. The manual details how to set up multicast groups, configure network masks, and troubleshoot IP conflicts. In addition, Ion can connect to a DMX‑USB bridge via a serial port; the firmware automatically detects the bridge and assigns it to a channel group. For remote control, Ion offers a secure WebSocket interface that can be accessed from any browser with HTTPS. The manual also covers VPN configuration, allowing operators to control Ion from remote locations while keeping the network traffic encrypted. Finally, the RPU can be integrated into a larger control network using the ETC‑specific “ETC‑Net” protocol, which bundles OSC, DMX, and status messages into a single stream for synchronized control across multiple consoles. All links use TLS 1.3 for secure control

Installation and Setup
To install ETC Ion, first power on the RPU and connect it to your network via Ethernet. Launch the Ion software from the USB installer, follow the wizard to set IP, firmware, and DMX ports. Once installed, use the UI to configure channels, cue lists, and network settings. Verify connectivity before use!!
Installing the Ion Software on the RPU
Installing the ETC Ion software on a Remote Processing Unit (RPU) is a straightforward process that follows a few essential steps. First, ensure the RPU is powered on and connected to your local network via a high‑speed Ethernet cable. The device will automatically obtain an IP address from your DHCP server, or you can manually assign a static address through the RPU’s web interface. Next, download the latest Ion installer from the official ETC website (www.etcconnect.com). The installer is distributed as a ZIP archive; extract the contents to a convenient folder on a computer that is on the same network as the RPU. Open the extracted folder and launch the “IonSetup.exe” executable. The setup wizard will guide you through the installation process. You will be prompted to select the target RPU by scanning the network for available devices; the wizard will display the RPU’s IP and serial number. Confirm the selection and proceed. The installer will then transfer the Ion firmware and software package to the RPU over the network. During this transfer, the RPU will reboot automatically. Once the reboot is complete, the installer will verify the integrity of the installation and apply any necessary configuration defaults. At this point, the Ion software is fully installed and ready for initial configuration. You can access the Ion control interface by opening a web browser and navigating to the RPU’s IP address. From the web UI, you can set DMX channel assignments, configure cue lists, and adjust network settings such as the DMX universe and port. It is recommended to run the “System Check” utility provided in the Ion Operations Manual to confirm that all channels are functioning correctly. After completing these steps, the RPU is ready to be integrated into your lighting console’s cue system, allowing you to create, edit,

User Interface and Navigation
Navigate the Ion UI via touchscreen or mouse. The main menu lists Control Panels, Cue Lists, and Settings. Use the touchpad to scroll, tap to select, or use the hardware keypad for quick access. The interface updates live, reflecting cue status and channel data. Use nav bar to jump panels, bar shows DMX.
Main Menu and Control Panels
The Ion interface presents a clean, intuitive main menu that serves as the gateway to all core functions. At the top, a horizontal navigation bar lists the primary sections: Control Panels, Cue Lists, Settings, and Help. Tapping any icon expands a vertical submenu offering granular options such as Fixture Groups, DMX Channels, Scene Management, and Macro Editor. The Control Panels section displays a grid of active panels corresponding to RPU modules. Each panel tile shows the panel’s name, status LED, and a preview of the current DMX output. Clicking a tile opens a detailed view where you can edit fixture assignments, adjust intensity, color, and movement parameters, or create new sub‑panels. The interface supports touch gestures and mouse interactions; a two‑finger swipe scrolls horizontally across panels, while a single tap selects a panel. Right‑clicking brings up a context menu with quick actions: Rename, Delete, Duplicate, and Export. The panel view includes a real‑time DMX monitor that displays current channel values in a scrolling list, allowing technicians to verify output instantly. For advanced users, a Debug Mode can be toggled from the Settings menu to view packet logs and latency statistics. Throughout the UI, consistent iconography and color coding help users distinguish between live, queued, and pending cues. The design follows ETC’s commitment to clarity, ensuring that even complex cue sequences can be managed with a few taps or clicks.
Keyboard shortcuts accelerate workflow: Ctrl+N creates a new panel, Ctrl+S saves, Ctrl+Z undoes, and Ctrl+Shift+Z redoes. A toolbar panel offers stop, record, export functions!
Configuring Cues and Cue Lists
ETC Ion’s cue system is organized into lists that can contain up to 999 cues. To create a list, press New List, name it, and choose a playback mode (linear, random, or loop). Each cue is defined in the Cue Editor, where you set the target fixture, DMX channel, value, and transition style. Ion offers preset styles—Fade, Hold, Strobe, Custom—and a Macro option that bundles several changes into one cue for reuse.
After a cue is created, it can be reordered by dragging or using the Move Up / Move Down buttons. The Duplicate button copies all parameters, while Delete removes the cue. Tags can be added with Labels to filter cues during live operation.
Ion supports out‑of‑sequence execution. Selecting a cue and choosing Go To Cue or using a Link instruction will immediately run that cue, overriding the current sequence. This is essential for live adjustments or emergency stops.
Timing controls allow you to set a cue’s start time relative to the previous cue, enabling precise synchronization with audio or video. The Preview button shows a live simulation before adding the cue to the list. Finally, the Export feature allows you to save cue lists as XML or CSV files for backup or transfer to other ETC devices.

All cue lists and individual cues can be exported, imported, or synced across multiple Ion RPUs enabling complex multi‑room productions with setupnow
Linking, Go To Cue, and Out-of-Sequence Cues
In ETC Ion, the Go To Cue command allows an operator to jump instantly to any cue in the list, regardless of the current playback position. This feature is essential for live adjustments, emergency stops, or special effects that must be triggered outside the normal sequence. When executed, Ion asserts the entire contents of the selected cue—both moves and tracks—immediately, ensuring all fixture changes occur simultaneously and predictably.
Similarly, the Link instruction embedded within a cue’s data creates a direct jump to another cue. When a Link is triggered, Ion treats the target cue as an out‑of‑sequence event, overriding the pending cue and asserting all its moves and tracks at once. The Ion Operations Manual specifies that any cue recalled via Go To Cue, a Link instruction, or manual pending‑cue changes is considered out‑of‑sequence, and the entire cue content is asserted. This behavior provides designers with a powerful tool for non‑linear show flows.

Ion offers two Link modes: Assert and Block. In Assert mode, the linked cue’s moves are applied immediately, while in Block mode the cue is treated as a single move instruction, useful for complex choreography. The cue editor visually highlights linked cues and their relationships, helping prevent accidental loops or unintended triggers during live operation. By combining Go To Cue, Link, and out‑of‑sequence logic, designers can create dynamic, responsive lighting shows that adapt in real time to performers, music, or safety requirements.




















































































