This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
handover:r4717 [2015/12/11 11:03] David Horsley |
handover:r4717 [2015/12/11 11:08] David Horsley |
||
---|---|---|---|
Line 17: | Line 17: | ||
* 06:45 UT - clock still unstable, resetting dbbc again Missed scans 345-0639 through 345-0656 (Ross) | * 06:45 UT - clock still unstable, resetting dbbc again Missed scans 345-0639 through 345-0656 (Ross) | ||
* 10:13 UT - clock still unstable, resetting dbbc again Missed scans 345-1015a through 345-1016b (Ross) | * 10:13 UT - clock still unstable, resetting dbbc again Missed scans 345-1015a through 345-1016b (Ross) | ||
- | * 10:58 UT - clock still unstable, resetting dbbc again Missed scans 345-1058a through 345-1106a (Ross) | + | * 10:58 UT - clock still unstable, power-cycled dbbc again Missed scans 345-1058a through 345-1106a (Ross) |
+ | * 11:06 UT - clock unstable after six dbbc reboots, and a power-cycle. Giving up for now and leaving clock for remainder of experiment (Ross) | ||
Line 28: | Line 29: | ||
General comments: | General comments: | ||
* Screens showing in incorrect order on AuScope computer and can not be corrected by restart (e.g. upper-right connects to middle, connects to bottom-left etc.). | * Screens showing in incorrect order on AuScope computer and can not be corrected by restart (e.g. upper-right connects to middle, connects to bottom-left etc.). | ||
- | * clock jump alarm keeps going off at Ke after a clock jump even once it has finally been stabilised. | ||
{{tag>}} | {{tag>}} |