This is an old revision of the document!
This page is dedicated to presenting new and current observers with the myriad (or miriad ;) ) of problems that the observer may face. And more importantly, the successful solutions to them.
If you come across an error whilst observing, no matter how small, please add:
A real-life example:
I noticed the wind speed had dropped to 7.5km/h but the antenna hadn't recovered. I halted the schedule and restarted the drives. This did not fix the problem however alarms sounded every scan 'ALARM: error fl -1 previous source in this schedule not reached before new source was commanded' and started trying to record data whilst stowed. Solution was to:
halt disk-record=off antenna=off terminate fs restart antenna=open antenna=operate proc=r4774hb schedule=r4774hb
Final note: logs noted a 'Auto-stow release failed' before this when all other wind stows ended with 'Auto-stow released succeeded'
Power outage, antenna got stuck after the system recovered: halt disk_record=off antenna=off terminate in timeke, HMI, 'reset drives', wait until both comms stati are green fs proc=mv004ke setup01 antenna=open antenna=operate source=stow
And it moved. Then I restarted the schedule. Generator status was 'in auto-off' so I assumed the power came on without any problems.
Normally this error can be ignored, but there was an additional error with this - WARNING: error st -10 rampepochtime not -1 when preparing to load, check antenna is in “operate”. Error presented as drive status not ready, with drives green in HMI. HMI was unresponsive - could not turn drives off. Antenna=operate and Antenna=open both return Antenna OK, but don't work. The clock on the right of HMI interface on cnsshb (CURRENT TIME UT1) was not updating.
Solution to issue is using HMI and selecting the reboot central button under resets. This reset the clock connection to the antenna, allowing the drives to communicate again.
ALARM: error s5 -104 rfpcn: time-out, connection closed
If you receive a persistent “rfpcn: error opening, rfpic probably not running, see above for error” report, or notice that the recording is notably behind the summary file and the becklog grows, you might want to restart Rxmon.
Log in to pcfs as root and perform the following command:
pcfsyg:~# su pcfsyg:~# /etc/init.d/Monica.Rxmon stop pcfsyg:~# ps -ef | grep Rxmon pcfsyg:~# /etc/init.d/Monica.Rxmon start
If the command worked, you will see the parameters listing.
The “ /etc/init.d/Monica.Rxmon start” command may not work as “ERROR on binding: Address already in use”. Just wait a minute and repeat an attempt. If it still doesn't work restart Monica:
pcfsyg:~# /etc/init.d/Monica.monica stop pcfsyg:~# /etc/init.d/Monica.monica start