This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
handover:r1865 [2018/10/23 13:20] Pradyumna Kiran Kummamuru |
handover:r1865 [2018/10/23 16:47] (current) Pradyumna Kiran Kummamuru |
||
---|---|---|---|
Line 12: | Line 12: | ||
* 12:09 UT - Antenna connection lost. Connection restored (onsource command yields tracking at this stage), recording was not halted. Scan 296-1209 is probably corrupt. (Atifur) | * 12:09 UT - Antenna connection lost. Connection restored (onsource command yields tracking at this stage), recording was not halted. Scan 296-1209 is probably corrupt. (Atifur) | ||
* 12:21 UT - Connection lost again. Restored. scan affected 296-1224a. (Atifur) | * 12:21 UT - Connection lost again. Restored. scan affected 296-1224a. (Atifur) | ||
- | * 12:26 UT - Large delay difference. clkoff command results in significantly different value. The Tac32 clock was found to be stuck and restarted (12:52 UT). The error is no more. (Atifur) | + | * 12:26 UT - Large delay difference. clkoff command results in significantly different value. The Tac32 clock was found to be stuck and restarted (12:52 UT). The delay is fixed. (Atifur) |
- | * 13:18 UT - Antenna connection lost (13:15 UT). Restored and Tac32 restarted as stuck once again. (Atifur) | + | * 13:18 UT - Antenna connection lost (13:15 UT). Restored and Tac32 restarted as stuck once again. Antenna clock and Tac32 offset by ~ 1s. Formatter and GPS delay is large and varying and not fixed.(Atifur) |