1

Topic: CM-1 Modules crashing?

This problem began happening a few days ago..   at first I thought it was a glitch but it repeated the error again this morning.    This is what I am seeing in the remote log.  After this happens..  all of the NION's I have using cobra net mute. 
------------------------

10/27/2010 7:27:31    7011    note    piond/role_manager    role is stopped
10/27/2010 7:27:30    7010    note    project/RATC2_service    started on port 1632
10/27/2010 7:27:30    7009    fault    piond/role_manager    role fault: role restart failed: CM-1 : Not present
10/27/2010 7:27:30    7008    fault    piond/fault_policy    more than one error in less than one minute; stopping engine
10/27/2010 7:27:30    7007    fault    piond/sound_engine    exception during engine start: CM-1 : Not present
10/27/2010 7:27:29    7006    note    project    cab 0x0 changed ID to 0x3fd
10/27/2010 7:27:29    7005    note    project    cab 0x0 changed ID to 0x3fc
10/27/2010 7:27:09    7004    error    piond/audio_network_module    audio network module not detected : /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:09    7003    error    piond/audio_network_module    peek aborted after 5 tries: /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:08    7002    note    piond/role_manager    restarting role : Catwalk 07-27-10/COBRA6/Ot5VfqeWlWJRXmcHpzJLsatc84v/rkPm0iUzCVLZlseOCPJ-4clo2ZS
10/27/2010 7:27:07    7001    note    project    user logged off: avtech
10/27/2010 7:27:07    7000    note    project    user logged off: avtech
10/27/2010 7:27:07    6999    note    project    user logged off: avtech
10/27/2010 7:27:07    6998    error    project    cab peek error : /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:07    6997    error    piond/audio_network_module    peek aborted after 5 tries: /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:07    6996    error    piond/audio_network_module    peek aborted after 5 tries: /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:07    6995    error    project    cab peek error : /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:06    6994    error    piond/audio_network_module    peek aborted after 5 tries: /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:06    6993    error    piond/audio_network_module    mute assertion failed: /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:06    6992    error    piond/audio_network_module    poke aborted after 5 tries: /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:06    6991    error    project    cab poke error : /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:06    6990    error    piond/audio_network_module    poke/peek driver exception : /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:06    6989    note    piond/mute    muted: menu command
10/27/2010 7:27:06    6988    error    piond/fault_policy    restarting audio engine
10/27/2010 7:27:06    6987    error    piond/audio_network_module    peek aborted after 5 tries: /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 7:27:06    6986    error    piond/audio_network_module    peek aborted after 5 tries: /dev/pion/cm10: timeout waiting for HF2 to go high
10/27/2010 6:45:38    6985    note    piond/time    Time set

-----------

Has anyone seen this before?   Or know what it is doing?   I am not sure what to look for on this.

Thank you!

2

Re: CM-1 Modules crashing?

Have a look in Help/kc at "NION Hardware Manual/Appendix-Troubleshooting/HF2 Errors".
May be relevant - I've definitely seen network issues cause the CM-1 to hang.

"The single biggest problem in communication is the illusion that it has taken place."
                                                                                        - George Bernard Shaw

3

Re: CM-1 Modules crashing?

I should have looked in the help files much sooner.   Thanks for pointing that out.   Makes complete sense.. with all the power fluctuations we have been having in that specific area where the NION's are located.   Looks like the battery backup we had in place there for the two NION's was faulty.. but not reporting that correctly.   After testing it.. and replacing it.. hopefully it doenst happen again.