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:r4711 [2015/10/29 18:32] Ross Turner |
handover:r4711 [2015/10/30 04:03] Imogen Jones |
||
---|---|---|---|
Line 7: | Line 7: | ||
* 18:15 UT - wth command not working, gives error "Problem connecting to metserver socket. Illegal error class code: 0xffffffff." I had a look at the station file in pfmed but nothing I tried worked. Not urgent so I'll report it at a more reasonable hour. (Ellen) | * 18:15 UT - wth command not working, gives error "Problem connecting to metserver socket. Illegal error class code: 0xffffffff." I had a look at the station file in pfmed but nothing I tried worked. Not urgent so I'll report it at a more reasonable hour. (Ellen) | ||
* 18:31 UT - Experiment started ok. (Ellen) | * 18:31 UT - Experiment started ok. (Ellen) | ||
+ | * 19:49 UT - Again, I am getting alarms fairly regularly, saying "ERROR m5 -104 mk5cn: time-out, connection closed". This doesn't appear to mean anything as everything still seems fine to me. It has also happened at 19:51, 20:19, 20:22, 21:10, 21:13 UT. (Ellen) | ||
+ | * 22:15 UT - Had to halt schedle for a quick maintinence check. Also, had to restart the field system to reset some settings. The timeout on the Mark 5A was set to 1/10 of a second, which was occasionally setting off a time out alarm. This problem has now been fixed. Schedule restarted and recording to a new module. Disk pos cannot be checked due to change of module. (Imogen) | ||
+ | * The weather monitor machine has failed and is being fixed today. Weather is being reported manually via the BOM website. (Imogen) | ||
+ | * 04:02UT Schedule halted due to reciever maintence (Imogen) | ||
+ | |||
**Katherine** | **Katherine** |