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:r1857 [2018/08/28 07:39] Atifur R. Khan |
handover:r1857 [2018/08/28 08:23] Atifur R. Khan |
||
---|---|---|---|
Line 12: | Line 12: | ||
* 06:11 UT - pps_delay through DBBC dropping, DBBC shut down for a power cycle. ipske not toggling the power though. Contacted Mick to see about manually resetting (JMc) | * 06:11 UT - pps_delay through DBBC dropping, DBBC shut down for a power cycle. ipske not toggling the power though. Contacted Mick to see about manually resetting (JMc) | ||
* 06:33 UT - Rebooted, re-synched. Back on schedule by 0633. All scans between 0611 and 0633 not recorded (JMc). | * 06:33 UT - Rebooted, re-synched. Back on schedule by 0633. All scans between 0611 and 0633 not recorded (JMc). | ||
- | * 07:32 UT - Minor clock jump just occured, delay difference has increased from 0.290 to 0.310 | + | * 07:32 UT - delay has been drifting since ~07:00, delay difference has increased from 0.290 to 0.310. Alarm set off after it broke the 0.31 threshold. Reset DBBC softwar, delay backlmat 0.29 us, will continue to monitor for drifting. (Tiege) |
+ | * 08:23 UT - Delay is still stable at ~0.29 us (Tiege) | ||
Scans missed: | Scans missed: | ||
- | 0611-0633 inclusive. | + | 0611-0633 inclusive. 0747 and 0750. |
+ | Note: data between 0650 and 0747 likely affected by clock drifting which occurred shortly after first DBBC reboot. | ||
| | ||