502 Hog 4 Operations Manual
32.1 Console Won't Startup
If a software update has failed the console can get into a state where it either fails to start
properly, or it goes immediately to the shutdown screen. A full re-install will be necessary;
see Console Software Full Install.
32.2 No DMX Output from Console's built-in DMX Outputs
1. Open the control panel (setup, control panel) and select the system info tab. Ensure the
serial number of the internal DMX Widget is being reported. (For HedgeHog 4 consoles
two DMX Widgets should be reported). If the widget serial is listed then move to step 2
and continue troubleshooting. If it is listed as "not found" then most likely the widget's
power and/or USB cable has been disconnected. Access the inside of the console and
confirm the widget has power and a good USB connection to the motherboard.
2. Open the network window (setup, network) and make sure the internal processor is
reporting "Outputs Active". If the internal processor is reported as "offline" then log off
the show, click on the control panel button in the start window and select the startup
tab. Ensure that "run processor" is turned on and set to the appropriate net number. Log
back onto the show and check output again. If console is still not outputting DMX then
proceed to step 3 and continue troubleshooting.
3. Double check the patch window and ensure that fixtures are patched to the correct
universes and that those universes have the proper processor assignments. This
sounds like a simple thing to check but in some cases output is failing only due to a bad
patch. If the console is still not outputting dmx then proceed to step 4.
4. Open the network window (setup, network) and click on the processor to which the
fixtures are patched. Click on the settings button. In the settings window navigate to
the "Output" tab. Ensure that the console's built-in DMX widget outputs are listed in the
output map and that they do not show any error icons.
5. If a you have performed all the troubleshooting steps in this section and the problem
continues to persist then please contact Technical Services for further assistance.
32.3 No Art-Net Output from Console's FixtureNet Port
1. Double check the patch window and ensure that your fixtures are patched to the correct
universe. Then open the node settings window and check that proper Art-Net mappings
exists for that universe and that no error icons are displayed. This sounds like a simple
thing to check but in some cases output is failing only due to a bad patch. If you are still
not seeing Art-Net output from the console proceed to step 2.
2. Open the network window (Setup → Ne twor k) and make sure the internal processor is
reporting Status column shows "Running". If the processor is being reported as
"offline" then log off the show and click on the Se ttings button in the start window.
Ensure that Run Pr ocessor is turned on and set to the appropriate net number. Log
back onto the show and check output again. If console is still not outputting Art-Net the
proceed to step 3 and continue troubleshooting.
3. Open the network window (Setup → Ne twor k) and click on the Processor to which the
fixtures are assigned. Click on the Settingsbutton. In the processor settings window
navigate to the Fixture Net tab. Ensure that the FixtureNet IP Address and Subnet
Mask are set appropriately for the network.
Note: If you make any changes to the FixtureNet IP Address or Subnet, you must log off and
log back onto the show for those new IP address settings to take effect.
4. Connect a windows computer to the network and run a software application tool such
as DMX Workshop. These kinds of software applications allow you to see Art-Net
streams on the network and can be used to further help in detecting where the problems
might be occurring.
To Next Page
Loading...
