User Tools

Site Tools


handover:r1819

R1819

Katherine 12m

Disk VSN: UAO-0031

Data volume at beginning: 0.737 GB

  • 0600UT - “reading SystemClock1” error, displaying “Error 10054” in the 'WRITE' box of the COMMS STATUS on timeke. Fixed by resetting drives, antenna=open and operate etc. (Tiege)
  • 1500UT - Same issue as earlier except now antenna=operate gives “Power on timed-out” error, original fix has not worked, working on a solution (Tiege)
  • 1526UT - No solution found yet, this issue only appears to have occurred twice, once with an undocumented solution, and the other was due to the emergency stop being bumped by kangaroos. None of the resets appear to be working, antenna remains stuck. I have contacted Warren who could not think of a fix. I am going to try and make cotnact with Mick so he can go take a look in the morning. (Tiege)
  • 1532UT - Just noticed when comparing to the Yg HMI, the 'E STOP' button is red for Ke (as opposed to green at Yg) so it looks like that is indeed the issue. Have messaged Mick requesting that he go out and take a look as soon as he can. In theory, telescope should be ready to go as soon as this is done. (Tiege)
  • 1558UT - Mick is heading out now to take a look (Tiege)
  • 1630UT - Drives are back up and running, waiting for information about what was done by Mick (Tiege)
  • 1635UT - 'E STOP' was not pressed, however, Mick went inside and saw that a yellow light was flashing, so he cycled the power and when everything came back up, the light was not flashing anymore and the telescope was no longer stuck. His comment is as follows “Turned the main switch off for 20 secs then back on. The emergency reset light was blinking and after the turn off/on the light stopped blinking.” He mentioned there were some power surges earlier on in the night, and suggested that the power may have gone off and on multiple times during the evening. (Tiege)
  • 1700UT - Experiment started OK (Tiege)
  • UT 08:27 ALARM: error st -998 reading systemclock1, ALARM: error st -999 tcp/ip connection error. Antenna communication software (antcn) problem. Fixed with commands “antenna=operate” and “antenna=open” (Jonny). Scan 325-0825 missed.

Yarragadee 12m

Disk VSN: USN-0172

Data volume at beginning: 0.737 GB

  • 1700UT - Experiment started OK (Tiege).
  • 2050UT - Yg network has died, attempting to bring it back up, have noticed an inconsistency between the IP address given for the router PC on the wiki, and the one in /etc/hosts. Cant VNC into either IP though, however can ping the one given on the wiki (Tiege)
  • 2115UT - network keeps coming in and out of existence, pings are varying between 200 ms and 16000+ ms, unable to get eremote control connected yet (Tiege)
  • 2122UT - Network decided it was time to behave now, eremote control is back working. Network is still slower than usual though. (Tiege)
  • 2133UT - Eremote control has lost connection again, however the network is good enough to stream the log, so log monitor is now monitoring the streamed log (“/tmp/yg.log”). ERC is going in and out of being connected as the network fluctuates. (Tiege)
  • 1446UT - error m5 -104 mk5cn: time-out, connection closed. antenna=operate and antenna=open fixed it. (Patrick)
You could leave a comment if you were logged in.
/home/www/auscope/opswiki/data/pages/handover/r1819.txt · Last modified: 2017/11/21 17:16 by Arwin Kahlon