504 Hog 4 Operations Manual
32.7 ETCnomad Key Not Recognized by Hog 4 PC
Components needed to run the license key were either not installed or are currently missing
from Windows. Try manually reinstalling the ETCnomad License key drivers by following
these steps:
1. Press ⊞ Windows Key + R on the computer's keyboard. This opens a "run" dialogue
box.
2. In the run dialogue box type:
C : \ P r o g r a m F i le s ( x 8 6 ) \ H i g h E n d S y s t e m s \ H o g 4
P C \ h a s p d i n s t . e x e - i
and then press enter.
3. A small installer window will appear. When the installer is complete a confirmation
dialogue will appear. Click OK.
4. The ETCnomad License key should now operate as expected.
32.8 The Front Panel Reboots Unexpectedly
Possible Cause: Strong radio waves that originate from a personal radio, common in live
event productions, while in close proximity to a console front panel can cause interference to
the front panel electronics. Always keep communication radios at least eight inches from the
console surface.
In the event of a radio transmitting within close proximity of the console, the front panel
electronics may become unresponsive. The firmware will force a reboot of the front panel
causing a temporary loss of control of the keys and hardware for approximately 20 seconds.
During this time the desk lights may dim as well. After 20 seconds the front panel will reboot
and normal functionality will be restored. If the problems persist, move the radio transmitting
device further from the console and check for other environmental radio interference factors.
32.9 How to Report Problems to Support
When reporting apparent problems with the console it is important you provide clear and
detailed information. This will ensure issues can be addressed.
Please follow these guidelines.
Please report issues to:
hesservice@etcconnect.com
24/7 phone support: +1-512-836-2242
Forums:forums.highend.com
32.9.1 Reporting Problems with the Console
Please include the following information in your bug report:
1. The piece of hardware that exhibited the problem, including the version number of the
software being used.
2. The actions taken that induce the problem in the first place, including whether the
problem is repeatable using the same actions.
3. The symptoms of the problem.
4. The network configuration of system.
To Next Page
Loading...
