Lighting and control
ETC Gio @5
Check the console role, physical port assignment and network protocol settings before changing the show patch or expecting more outputs.
Ask GLMedia about renting ETC Gio @5 for your event. Availability and configuration are subject to confirmation.
Model and purpose
- Manufacturer
- ETC
- Model
- ETC Gio @5
- Model / menu scope
- Gio @5; Eos online manual 3.3.10
- Console output options
- 4096 base or 24576 unlocked; verify the actual device
- Connections
- 4 DMX/RDM 5-pin ports; 2 Gigabit Ethernet; 2 DisplayPort
- Power / environment
- 100–240 VAC, 50/60 Hz; 0–35 °C; typical weight 23.59 kg
An Eos console for programming and operating lighting cues, moving fixtures and integrated show control. Its compact surface combines a built-in touchscreen with physical playback controls. It is the Gio @5, with its own hardware layout and output options; do not transfer specifications from Gio or Apex models.
Prepare your rental inquiry
- Date, city, venue and setup, event and pickup schedule.
- Intended use, area dimensions and equipment already supplied by the venue or production.
- Show platform and version, fixture profiles, universe count and required outputs.
- Operator, connections, backup and replacement equipment to be considered.
Specify equipment only or whether setup, programming, operation and strike are also needed. Scope is confirmed in the proposal.
You do not need a final equipment list: tell us the result you want and the part you need help with. Availability and scope are confirmed in the proposal.
Features and connections
The surface includes 5 configurable motorized 60 mm faders, a dedicated main playback pair and 4 haptic encoders. The articulating internal screen is 18.5 inches; external displays and optional touch USB connections require compatible hardware and adapters.
Local DMX connectors and Ethernet lighting output are separate routes. Suitable sACN/Art-Net receivers can accept network control directly; a gateway is needed when the receiving fixture requires physical DMX. A node does not by itself prove additional licensed capacity.
Prepare the exact fixture profiles/modes, DMX and IP plans, a separate show backup and a tested recovery arrangement. USB ports are for data peripherals rather than device charging. Check the actual hardware revision and accessories before assuming a port inventory.
Prepare the system
- Record hardware revision, installed Eos version, output entitlement and the intended Primary, Backup or Client role. Offline does not output. The menu names here follow 3.3.10; compare them with the installed system before editing.
- Use the locking IEC cable and protective earth with stable support, clear ventilation and room for the screen movement. Save an independent show copy and external recovery copy before patch, protocol or role changes.
- Agree on which station and port supplies each receiver. Test on one isolated fixture or agreed low-level circuit. Avoid connecting both console network interfaces to the same network/subnet; plan any restart prompted by a setting outside active operation.
Questions and troubleshooting
The show responds on screen but the rear DMX port is silent: what should I inspect?
Confirm the station role and local port assignment separately from the fixture patch. A connected Client does not necessarily supply local DMX.
- Check whether the console is Primary, Backup, Client or Offline, and identify the intended active source. Do not change a live session’s roles merely to see whether a fixture responds.
- Open Setup > Device > Local Output and identify the connected hardware/port. Compare its starting Address with the patched output address; check port settings and any restart warning.
- If this is an intentional Client output, review Output In Client Mode, which defaults to disabled. Coordinate the change with the system operator and rehearse the intended route. With a verified cable, test the same fixture before changing its profile or start address.
A network receiver sees no useful sACN or Art-Net: which settings must agree?
An online network interface proves a usable connection, not a complete lighting-control route or receiver configuration.
- In Setup > Device > Network, inspect the actual connected interface, IP/subnet and protocol enable. Trace the cable and compare the receiver’s input settings with the agreed network plan.
- Also inspect Patch > Protocols. Confirm Enabled Protocol, intended default protocol, Start Universe and relevant per-universe overrides. An offset can send a correct patch to a different receiving universe.
- For sACN, compare priorities and multicast/unicast destination choices with the receiving system. Observe data at the receiver, not just a console indicator. If data is present but the device ignores it, investigate its own input/mapping settings; do not copy another model’s IP workaround.
Why does System Count differ from channel count, and do two consoles add capacity?
Output count concerns patched addresses. A multiparameter fixture can occupy several addresses while remaining a single control channel.
- With an empty command line, open About and compare System Count, Patched Addresses and Allowed Output Addresses. A high universe number alone is not proof that the total address allowance is exceeded.
- In a conventional Primary/Backup arrangement without expansion processing, the lower output count sets the system allowance; the two console counts do not add. Check both proposed host devices before relying on failover.
- About while networked may show the session allowance rather than that individual desk’s programmed capacity. Verify each device separately during a planned isolated inspection, never by unplugging an active console. If capacity or allowed address ranges are insufficient, preserve the show and resolve the system design before rehearsal.
Quick reference
| Layer | Record |
|---|---|
| Local DMX | Station role, local port and starting output address |
| Network | Interface, protocol enable, universe offset and receiver mapping |
| Capacity | Individual entitlement, session System Count and patched addresses |
Precautions
- Use dry, ventilated support within the stated environment. Shut down through the software/power control before disconnecting mains; internal service requires isolation and qualified personnel.
- Legacy Net2 and AVAB UDP are not supported in Eos 3.2.0 or later and on Windows 10 consoles. Do not assume an older network protocol remains usable after a system change.
- A backup, an online interface or a motorized fader does not establish successful recovery. Rehearse output loss and restoration with the actual receiving system before the show.
Terms on this page
- DMX
- A data protocol controlling lighting functions; each model defines what its channels mean.
- RDM
- Management communication for querying or configuring compatible equipment over a compatible path.
- Patch
- Assignment of fixture, profile, address and universe in the control system.
Documentation and sources
- Gio @5 product
- Gio @5 datasheet — G
- Gio @5 overview — Eos 3.3.10
- Local Output — Eos 3.3.10
- Device Network — Eos 3.3.10
- Patch Protocols — Eos 3.3.10
- Console output counts
- Addresses and parameters
Consulted October 22, 2026. Model data follows official Gio @5 documents; menu checks use Eos 3.3.10 online help. Individual license, installed software, adapters and receiving devices remain system-specific. Public forum cases suggested questions;