Lighting
High End Systems Full Boar 4 troubleshooting
The High End Systems Full Boar 4 problems live-event techs bring to Ask Roadie most (also called FB4, Full Boar, Hog Full Boar). Pick your symptom, or describe your own in plain words, and get the likeliest fix first, with the manual page when there is one.
Common Full Boar 4 errors & problems
What techs run into most, and what's usually behind it. The step-by-step fix for your exact unit is in Ask Roadie.
- Step-by-step fixGet the fix →
Art-Net / sACN input into the console failing (e.g. from a media server or timecode/DMX-in source)
Likely cause: Network DMX only reaches the console when addressing and multicast handling line up; managed switches without proper IGMP config drop sACN multicast traffic.
- Step-by-step fixGet the fix →
Console power-down / avoiding show-file corruption and safe mains handling
Likely cause: The OS writes the show database continuously; an orderly shutdown flushes it.
- Step-by-step fixGet the fix →
Expanding output beyond the 4 onboard universes / adding a DP8000 DMX Processor
Likely cause: The console processes 6,144 channels but only has 4 physical DMX ports; DP8000s add physical outputs and offload processing while staying addressed over the show network.
- Step-by-step fixGet the fix →
Firmware/OS update process and current latest version
Likely cause: A full install (not just an app update) is what reliably refreshes the OS image on Hog consoles and is required to clear the licensing/boot bugs; v4.2.1 is the newest confirmed build for the Hog 4 platform.
- Step-by-step fixGet the fix →
Full install stuck (e.g. on "Detect and mount CD-ROM") or driver/certificate errors after install
Likely cause: The installer mounts the image like a CD; a flaky USB stalls that step.
- Step-by-step fixGet the fix →
How to output Art-Net or sACN (E1.31) instead of/in addition to onboard 5-pin DMX
Likely cause: Hog 4 OS sends network DMX only out FixtureNet; an incompatible IP means nodes never receive data, and each universe must be explicitly mapped to a protocol and destination.
- Step-by-step fixGet the fix →
Internal DMX widget not detected in System Info / Control Panel
Likely cause: The internal widget is the onboard DMX interface; wrong dip-switch config or a loose PSU harness stops it from enumerating, and non-solid LEDs indicate a hardware fault rather than a config issue.
- Step-by-step fixGet the fix →
No DMX output from an onboard universe even though the widget is detected
Likely cause: Detected hardware still needs an explicit universe mapping to output; a stale/corrupt mapping is cleared by remapping, and host firewalls silently drop the widget traffic on PC.
- Step-by-step fixGet the fix →
Output licensing lost at startup (console shows reduced/no output rights) on Full Boar 4 built after 2020
Likely cause: The bug was in how newer console hardware validated its output license at boot; the fixed OS builds correct the license detection so full output is restored.
- Step-by-step fixGet the fix →
Touchscreen unresponsive on one or both built-in displays
Likely cause: Most touch failures are a seated-cable or grounding fault; matching display types is required because the console driver expects identical panels.
Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.
How Ask Roadie helps with the Full Boar 4
- 1. Pick the High End Systems Full Boar 4. It's already in the list.
- 2. Describe what you're seeing. In your own words, or the error code off the screen.
- 3. Get the likeliest fix first. Steps in order, the manual page when there is one, and a note when other techs have confirmed it.
- 4. Still broken? Tap 👎 and it keeps going from where you left off.
Free trial
Get your Full Boar 4 back up before doors.
Try it free. No card required.
Start free trial →