Peavey MediaMatrix Nion, Hardware Manual

Page: 66 / 94

Appendix A - Troubleshooting
62 Version 1.6.1.0 September 30, 2010
2. In the Targets Found pane, right-click on the NioNode and then click Launch Web
Interface .
A browser will be opened displaying the home page of the selected NioNode.
3. In the browser, click Special at the top of the page.
4. At the bottom of page, Click Advanced .
5. Scroll to the bottom of the window, and then click set all .
6. Click apply .
7. Close the browser.
8. In NWare, in the Targets Found pane, right-click on the NioNode, and then click Enable
Polling .
A green check will be shown next to the NioNode to indicate that polling is enabled. Log
messages will be shown in the pane on the right. You can view the log for an individual
NioNode by clicking the node in the
Targets Found pane.
HF2 errors
HF2 is the generic term for a class of errors that are caused by a communication failure
between the NION processor and CobraNet CM-1 module. This type of error may appear as
one of the following in a NION error log:
cm1 not detected : /dev/pion/cm10: timeout waiting for HF2 to go high
peek aborted after 5 tries: /dev/pion/cm10: timeout waiting for HF2 to
go high
poke/peek driver exception : /dev/pion/cm10: timeout waiting for HF2 to
go high
A hardware handshake line between the NION and CM-1 has failed to operate correctly, i.e.
the CM-1 has become unresponsive.
The causes of HF2 errors
HF2 related errors could have two basic causes:
ƒ A hardware error. The physical hardware is at fault.
ƒ The firmware running on the CM-1 has malfunctioned and cannot respond to the NION.
Case 1 - Hardware error
In this case the interface between the CM-1 and NION has failed due to a chronic hardware
problem. This condition can be identified by persistence of the error through multiple power
cycles of the NION. A hardware fault can only be remedied by repair or replacement of the
failed component. Please consult your dealer for further information regarding repair or
replacement of hardware.
A hardware error can also be caused by a NION operating at elevated temperature. Address
cooling and ventilation issues when this cause is suspected.
Case 2 - Firmware malfunction
Firmware malfunction is the primary focus of this troubleshooting section. This cause of
failure is characterized by proper operation of the NION followed by occurrence of an HF2
error. Subsequent power cycling of the NION can return the device to proper operation.
Although the root cause is a firmware problem, there are network related issues that can
stimulate the problem and steps that can be taken to mitigate it.