This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
handover:t2118 [2017/05/23 17:54] Arwin Kahlon |
handover:t2118 [2017/05/24 03:24] (current) Jonathan Rogers |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| * 1730UT - Experiment started OK. (Tiege) | * 1730UT - Experiment started OK. (Tiege) | ||
| * 1745UT - Following error: "m5 -104 mk5cn: time-out, connection closed". Everything seems fine with the mk5 currently, it is accepting all commands and appears to be running correctly, if the error triggers again I will restart DIMino. (note: it did not occur during recording) (Tiege) | * 1745UT - Following error: "m5 -104 mk5cn: time-out, connection closed". Everything seems fine with the mk5 currently, it is accepting all commands and appears to be running correctly, if the error triggers again I will restart DIMino. (note: it did not occur during recording) (Tiege) | ||
| + | * 1932UT - Same error happened again. This time Autocorrelation spectrum is all over the place. Halted schedule, restarted DIMino and restarted schedule. Missed one scan 143-1937, first scan back is 143-1944 (Tiege) | ||
| + | * 2117UT - mk5cn time-out has happened again. No faulty autocorrelations this time, Overwhelming majority of comments about this error on the wiki suggest it is a benign. Going to leave it unless I see it breaking things. (Tiege) | ||
| + | * 0321UT - mk5cn time-put during scan 144-0320. No faulty autocorrelations appeared. As per above likely benign, however documented all the same (Jonny) | ||
| **Yarragadee 12m:** | **Yarragadee 12m:** | ||