ETC Ion Xe 2K

Follow the path from the channel to the output being used.

1. Confirm fixture power and matching profile and address. Check calculated output, not just the channel intensity level.
2. For networking, check the protocol in Patch > Protocols and Setup > Device > Network, receiver interface and universe. Confirm Default Protocol or the interface assigned to that channel.
3. For local cable, check Local DMX and Setup > Device > Local Output: the port start address may have been remapped. Test a simple known path.

Licensed outputs and show channels count different things.

1. Check System Count and used addresses in About. A fixture with many attributes can occupy numerous addresses within a single channel.
2. Adding a connector or node does not add outputs. Identify unnecessary patch before editing it, saving the show first.
3. In a Primary/Backup system, check both licenses: the lower one determines the system’s System Count. Do not assume they are added together.

Check the monitor and role before reinstalling or clearing settings.

1. Connect and power an external monitor before starting Eos; for touch, also check USB.
2. Offline is not a show operating mode. In Client, local DMX output is disabled by default unless Output In Client Mode is enabled; verify the session design.
3. Record version, status and symptoms; save the show and logs if the console becomes unresponsive. Do not start troubleshooting with Deep Clear or component firmware updates.

We can assess an Ion Xe to complete your system or a prepared package. At least one external monitor must be connected to start Eos; let us know whether you also need the monitor included in the rental.

1. State available monitor connections, peripherals, fixtures, modes and how DMX reaches each area. Confirm licensed output capacity and the route through ports or nodes; extra connectors do not expand the license.
2. We can quote the console and missing accessories, show-file preparation, patch and output checks, rehearsal or operation, depending on what your production already covers. Share date, venue and setup/rehearsal schedule; we will identify the display, adapters, data distribution, programmer and operator. Availability and each service must be confirmed in the proposal.

Yes, we can begin assessment using the event program and a provisional inventory. Show file, patch and actual connections must be completed before relying on cues.

1. Share photos or an approximate list, lighting areas, moments and cue caller. If an Eos file exists, preserve the original and state its version and planned changes; opening it does not verify physical output.
2. We can assess adaptation of an existing file or programming around event needs. Profiles, capacity and rehearsal depend on confirmed equipment; compatibility and programming time are not guaranteed without reviewing scope.

We can assess operator-triggered cues or coordination through show control. Eos can receive timecode to execute programmed events; it does not recognize songs or their changes on its own.

1. Share a provisional rundown, which parts are live or recorded, who calls cues, and the audio/video playback system with versions and connections. If timecode is proposed, identify the source, format, route and interfaces; Eos receives SMPTE through a Response Show Control Gateway, which must be considered where applicable.
2. We can quote programming and operation with stage-management cues, integration of confirmed playback, or a combination by segment. Agree on and rehearse starts, pauses, running-order changes and signal-loss recovery with audio, video and lighting; define who can intervene. Do not assume that starting two devices together keeps them synchronized or that playback equipment or a gateway is included.