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.

--- handover:aov044 [2020/02/11 21:58]
Pradyumna Kiran Kummamuru
+++ handover:aov044 [2020/02/12 09:12] (current)
Pradyumna Kiran Kummamuru
@@ Line 13: / Line 13: @@
    * 2022UT fs-auscope restarted, next scan is 042-2028 (Lim).
    * 2120UT Error: Cannot get monitor info from antenna (8020003); #antcn#Network I/O Timeout occurred on write
-   * 2153UT DrivePC (sys26m) and Hobart machine rebooted, that sort of cleared the problem, which was a result of power failure. Next scan 042-2159 (Lim).
+   * 2153UT DrivePC (sys26m) and Hobart machine rebooted, that sort of cleared the problem, which was a result of power failure. Next scan 042-2159 . Missed scans: 042-2119 to 042-2157 (Lim).
+   * 0812UT - There seemed to be a power failure. Tried restarting the FS and running the schedule however that showed up The allocating memory for antenna monitoring error. Rebooted the drivepc by using the command "rem_reboot -r rakbus sys26m" on observer@newsmerd. The RA/Dec/time values which were static earlier, now started changing (as seen on rack 1 through the camera). Did "source=disable" on the FS to resume the schedule. Scans 043-0811 to 043-0844 affected (Prad).
+   * 0910UT - Drives weren't ready on time for the last few scans. "drvon" on vdesk a few times seemed to have done the trick. Left drive (on) delay causing the problem? Scans 043-0848b to 043-0908 likely to have been affected (Prad).