User Tools

Site Tools


handover:ds288

This wiki is not maintained! Do not use this when setting up AuScope experiments!

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
handover:ds288 [2016/10/16 08:30]
Jesse Swan
handover:ds288 [2016/10/16 13:31] (current)
Jesse Swan
Line 8: Line 8:
  
 Halting the schedule to fix problems appears to have no effect (at least on Hb, Ke), the schedule continues trying to record. (Ellen) Halting the schedule to fix problems appears to have no effect (at least on Hb, Ke), the schedule continues trying to record. (Ellen)
 +
 +Continuing to get "​ALARM:​ error m5 -900 not while recording or playing"​ errors frequently at Ke throughout my shift, these have been reported by Bryn and Ellen as occurring all day, they don't seem to correspond to any actual problem with the telescope. (Tiege)
 +
 +**NOTE: I have changed this alarm m5 -900 to BEEP instead of ALARM in /​usr2/​control.ke/​alarm_actions.txt so that Lucas can get some sleep between checklists **
  
  
Line 37: Line 41:
    * First scan back 290-0604, on new module HOB+0098. (Ellen)    * First scan back 290-0604, on new module HOB+0098. (Ellen)
    * 07:30 UT - Lost connection to the antenna controller (I think), telescope was stuck and could not be fixed with the standard open or operate commands, needed to use the HMI interface on timehb and do a drive reset and operate toggle to regain connection. At the same time DBBC connection dropped out, had to reconfigure and resync the dbbc to fix it. Possibly another power glitch at Mt Pleasant has caused this? Everything seems fine now and the dynamic scheduler has been restarted. (Tiege)    * 07:30 UT - Lost connection to the antenna controller (I think), telescope was stuck and could not be fixed with the standard open or operate commands, needed to use the HMI interface on timehb and do a drive reset and operate toggle to regain connection. At the same time DBBC connection dropped out, had to reconfigure and resync the dbbc to fix it. Possibly another power glitch at Mt Pleasant has caused this? Everything seems fine now and the dynamic scheduler has been restarted. (Tiege)
 +   * 08:30 UT - Everything back up and running, first good scan 290-0834 (Tiege)
  
 **Katherine** **Katherine**
Line 52: Line 57:
    * 05:38 UT - Antenna lost connection and no amount of resetting and rebooting has fixed it. Reporting that antenna is stuck. Jamie is investigating. (Ellen)    * 05:38 UT - Antenna lost connection and no amount of resetting and rebooting has fixed it. Reporting that antenna is stuck. Jamie is investigating. (Ellen)
    * First scan back 290-0547. But Rxmon not running until 290-0605. (Ellen)    * First scan back 290-0547. But Rxmon not running until 290-0605. (Ellen)
 +   * 13:10 UT - ALARM. field system crashed after 12:56 UT, last recorded scan 290-1256.
 +     * Field system restarted and schedule restarted, first scan 290-1322 (Lucas)
  
 **Yarragadee** **Yarragadee**
/home/www/auscope/opswiki/data/attic/handover/ds288.1476606640.txt.gz · Last modified: 2016/10/16 08:30 by Jesse Swan