Hobart (26m)

• Recording to 4 TB module USN-0014 in bank B, +0 GB (Chris)
• (11:50 UT) Just noticed that the receiver has become unlocked at a few points (Chris)
• 10:33 UT
• 10:38 UT
• 11:08 UT
• 11:09 UT
• 11:13 UT
• 11:48 UT
• 13:00 UT Moved dish about and seemed to fix unlock problem by about 12:30 with some subsequent intermittent (mostly momentary) loss of lock.(warren)
• lost lock at 18:38 to 18:47 (w)
• again unlocked 20:20 and 21:02 and 21:20 (w)
• The LO unlocked several times for short periods from 23:00 till 01:30 UT (Liza)
• rxp#Receiver focus X : -256.4mm ; Y : 250.8mm ; Z : 18.6mm; – Y should be 248mm (Liza)
• 04:38 UT: wiring error of pps at Hobart was corrected. Don't know what the impact was before (Liza)
• * 2014.289.05:24-05:36 LO reported to be unlocked, no alarm on occurence (Liza)

Hobart (12m)

• Recording to 6 TB module HAY-0055 in bank B, +0 GB (Chris)
• Anemometer is not connecting (Liza)
• RFI: common problem in ch 14, 15 (0-15) (Liza)
• 04:38 UT: wiring error of pps at Hobart was corrected. Don't know what the impact was before
• 05:58UT: RFI: new indication in channel 11 (0-15), periodically occuring spike and phase errors. Was noticed also once before (RD1409 or aust50) (Liza)

Katherine

• Recording to 8 TB module HOB+0068 in bank A, +0 GB (Chris)
• Running on an SSH remote-control (Warren, Liza)

Yarragadee

• Recording to 6 TB module OAN+0103 in bank A, +0 GB (Chris)
• Recording error documented (Liza):

2014.289.04:55:01 ALARM: error m5 -104 mk5cn: time-out, connection closed

    2014.289.04:55:07 ALARM: error m5 -104 mk5cn: time-out, connection closed
    2014.289.04:55:07 Alarm acknowledged
    2014.289.04:55:12 ALARM: error m5 -104 mk5cn: time-out, connection closed
    2014.289.04:55:14 WARNING:  0 : 0x02340003 : 23 : data read error ;