This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
handover:r4957 [2020/07/30 13:19] Lim Chin Chuan |
handover:r4957 [2020/07/31 00:26] Warren Hankey |
||
---|---|---|---|
Line 5: | Line 5: | ||
Disk VSN: MED-0040 | Data volume at beginning: 0.0 GB | Disk VSN: MED-0040 | Data volume at beginning: 0.0 GB | ||
- | *Note: 0.5 second offset between mark5b and dbbc, as long as the delay is stable we may ignore the alarm. Auto corr looks bad. Warren says it might be a hardware problem. | + | *Note: 0.5 second offset between mark5b and dbbc, as long as the delay is stable we may ignore the alarm. Auto corr looks bad. Warren says it might be a hardware problem. No tsys readings? |
* 1830UT Experiment started okay (Lim). | * 1830UT Experiment started okay (Lim). | ||
+ | * 22:30 UT steady delay offset may be OK but auto correlations are no good, dbbc bad. Power off dbbc and reconfigure. (w) | ||
+ | * 22:47 UT complete power off / power on cycle of dbbc seems to have done the trick. first good scan 2247 (w) | ||
+ | * 23:13 UT halt agian for power cycle and reconfigure to fix two bad channels (w) | ||
+ | * 23:32 UT restart has made it worse again....(w) | ||
+ | * 00:24 UT trying a scan, clkoff still bad, autocorrelations bad (w) |