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:aua034 [2017/12/21 16:29] Jamie McCallum |
handover:aua034 [2017/12/21 17:33] Jamie McCallum |
||
---|---|---|---|
Line 41: | Line 41: | ||
* 15:53UT mk5 has konked out again, first restart has not helped, trying a second restart now, First scan affected no0220 (Tiege) | * 15:53UT mk5 has konked out again, first restart has not helped, trying a second restart now, First scan affected no0220 (Tiege) | ||
* 16:27UT Second restart caused the mk5 to not want to rise from the dead, called Yg and they manually power cycled. This didnt fix it, so IP power cycled one more time. This time everything appears to be running OK. First good scan should be No0230 (Tiege) | * 16:27UT Second restart caused the mk5 to not want to rise from the dead, called Yg and they manually power cycled. This didnt fix it, so IP power cycled one more time. This time everything appears to be running OK. First good scan should be No0230 (Tiege) | ||
+ | * 17:03UT It was not running OK, called Jamie, seems to be running okay now as of scan No0236. Jamie believes it is something to do with there being 2 modules in the Yg mk5. (Tiege) | ||
+ | * 17:30UT Errors + alarms are back again, going to leave it until morning for a fix as once its up again there will be only 45 mins left of experiment (assuming it works first try...) (Tiege) | ||