This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
handover:t2136 [2019/12/10 22:01] Warren Hankey |
handover:t2136 [2019/12/11 06:28] Warren Hankey |
||
---|---|---|---|
Line 10: | Line 10: | ||
* 1825UT - Rebooted drive pc with: rem_reboot -r rakbus sys26m (in a newsmerd terminal), needed to do it twice as it crashed again almost instantly. everything seems to be OK now, first OK scan 344-1830b (Tiege) | * 1825UT - Rebooted drive pc with: rem_reboot -r rakbus sys26m (in a newsmerd terminal), needed to do it twice as it crashed again almost instantly. everything seems to be OK now, first OK scan 344-1830b (Tiege) | ||
* 2130UT - Looks like post drive pc crash, receiver 3 (warm S band) has come on axis. S/X was definitely on at start of experiment, confirmed using rxp command, live page and webcam position. Warren thinks it may have something to do with Otter acting strangely currently (Tiege) | * 2130UT - Looks like post drive pc crash, receiver 3 (warm S band) has come on axis. S/X was definitely on at start of experiment, confirmed using rxp command, live page and webcam position. Warren thinks it may have something to do with Otter acting strangely currently (Tiege) | ||
+ | * 21:54 UT halted schedule, to look in receiver cabin and change back to S/X. Rebooted rx26m, still something wrong with rx comms (Warren) | ||
+ | * 22:00 UT recording of 344-2154 no good (w) | ||
+ | * 22:41 UT resumed schedule with recording of 344-2241b (w) | ||
+ | * 04:00 UT power outage, drive pc reboot, receiver position issue again. note receiver manually in position, no "auto" receiver 2 displayed (w) | ||
+ | * 04:21 UT tracking on source ready for next scan (w) | ||