Model and documentation reference
Reference model: new-generation Tour Hog 6111A1001 in Rev F September 2026 sheet, distinct from Tour Wing and Eos consoles. Hog OS 5.3.0 b557 manual and October 2026 notes are consulted; installed OS and firmware remain unconfirmed. Sheet and manual document 64-universe capacity and four local DMX outputs, which are different concepts.
Tour Hog 6111A1001 · sheet Rev F 2026-09
Event application
For a theater, presentation or show in Argentina, record rundown, zones, fixture models/modes, console and intended processors. Separate immediate operator access from network/DMX routes to each receiver. Agree on cue names and holds with the caller. Another-version file or similar-looking peripheral establishes no show-ready system.
Hog OS 5.3.0 Rev A 2026-Oct · selected network/session pages
Minimum records for the intended Tour Hog
| Part | Verified reference | Missing actual-system data |
|---|---|---|
| Console | Tour Hog 6111A1001; four local DMX outputs | Label, version, peripherals and port mapping |
| Distribution | Documented 64 universes; FixtureNet for Art-Net/sACN | Processor, universe and receiver for each path |
| File and components | Hog 5.3.0 b557; specific compatibility notes | Show origin, library and each section firmware |
| Session | HogNet and session partitions have distinct rules | Data authority, copies and recovery owner |
Hog OS 5.3.0 Rev A 2026-Oct · selected network/session pages
Follow processor, universe and receiver
The manual distinguishes HogNet for Hog-system communication from FixtureNet carrying Art-Net or E1.31/sACN to compatible receivers. Record both by function instead of treating connectors as an undifferentiated switch. Physical outputs use processor mappings; four connectors establish neither the total capacity limit nor delivery of a particular universe. Preserve initial map and node inputs before proposing changes.
Hog OS 5.3.0 Rev A 2026-Oct · selected network/session pages
Preserve the original before adaptation or maintenance
The 5.3.0 notes say files created or edited in that version are not backwards compatible with previous versions. They also require a console full install and programmer-section firmware 1.0.1.27 on Tour Hog for this release; this is no instruction to install during an event. Programmer and playback firmware are independent. Record OS/build and each section FW, then agree on review without assuming one update updates everything.
Hog OS 5.3.0 b557 notes · effective 2026-Oct-19 · ETC · Hog versions · compatibility table · ETC · independent front-panel firmware · applicability only
Prepare rehearsal and a defined return
- Identify Tour Hog 6111A1001, components, documented OS/build and per-section FW. Preserve original show, source version and agreed working copy without opening/converting files here.
- Build a zone row with model/mode, universe, processor, local output or FixtureNet, node and receiver input. Separate HogNet from lighting-data distribution.
- Define sample looks and rundown holds. Agree on observing controls, active cue, receiver data and light outside event operation.
- Record who preserves authoritative data if a session partitions. The manual says restored connectivity does not automatically merge partition changes; promise no transparent return.
- Agree on window, owner and recovery evidence before maintenance. This package installs nothing, downloads no firmware, restarts/logs off no devices and performs no rehearsal.
Hog OS 5.3.0 Rev A 2026-Oct · selected network/session pages
Frequently asked questions
Are Tour Wing and Tour Hog the same device?
No. The sheet separates the Tour Hog console from the Tour Wing peripheral. Identify each component before assigning capacity or connections.
Do four DMX outputs mean four total universes?
No. Capacity and local connectors differ. Record how each universe maps to a processor and reaches its receiver.
Can I edit in 5.3 and return to earlier software without an original?
The notes mark files created/edited in 5.3.0 as not backwards compatible. Preserve the original and agree on delivery version before adaptation.
Do OS and both panel firmware versions always match?
They are distinct components, with independent programmer and playback firmware. Verify release requirements and recorded state without diagnosing a fault from different numbers alone.
Does reconnecting the network resolve a split session?
The manual does not automatically merge partition changes. Preserve data and determine show authority; this guide performs no logoffs or resets.
Follow the lighting control path
Official edition-specific documentation
Tour Hog Rev F 2026-09 sheet: all three pages consulted. Hog OS 5.3.0 Rev A 2026-Oct manual: selected PDF positions recorded; pp. 73–74, 82–83, 86–87 and 89–90 support networks/session; PDF 87, printed 84, visually inspected. 5.3.0 b557 notes: PDF 1, 6, 10 and 11 read, p. 6 inspected. Three existing originals SHA verified without new copies or a tested local reader.
