User Tools

Site Tools


operations:agenda2016_18_06

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
operations:agenda2016_18_06 [2016/05/19 00:53]
Jonathan Rogers
operations:agenda2016_18_06 [2016/05/19 02:23] (current)
Jonathan Rogers
Line 9: Line 9:
  
 Attendees: ​ Attendees: ​
 +Jonathan 8-), Arwin, Lucas, Byrn, Jim, Liz, Tiege, Jesse, Ross
  
-Apologies:+Apologies: ​Jamie, Lucia, Ellen
  
 Issues/​Minutes:​ Issues/​Minutes:​
  
   * Hb12 skycam stuck   * Hb12 skycam stuck
 +     - Jim to look at
 +
   * A few notes of error ''​m5 -104 mk5cn: time-out, connection closed''​. Suggested in past hand over notes that it can perhaps be safely ignored as nothing seems to be wrong?   * A few notes of error ''​m5 -104 mk5cn: time-out, connection closed''​. Suggested in past hand over notes that it can perhaps be safely ignored as nothing seems to be wrong?
 +    - Can ignore safely once, but if it's reoccurring then most likely a Dimino issue
 +
 +
   * End of [[handover:​aov009|AOV009]] had some issues with recovering from wind stows, receiving ''​WARNING:​ error bo -211''​ when trying to recover manually.   * End of [[handover:​aov009|AOV009]] had some issues with recovering from wind stows, receiving ''​WARNING:​ error bo -211''​ when trying to recover manually.
     * Jim: In once case I looked into during AOV009 (starting 09:50 UT) it looks like the wind-stow recovery failed because the azimuth drives came up but not the elevation drives. The antenna moved to the correct azimuth but stayed in the elevation stow position. This was further confused/​complicated by the wind stow being triggered again while in this state. Resetting the antenna drives manually seemed to fix this. For future reference, try this first to reset the drives: <​code>​antenna=stop     * Jim: In once case I looked into during AOV009 (starting 09:50 UT) it looks like the wind-stow recovery failed because the azimuth drives came up but not the elevation drives. The antenna moved to the correct azimuth but stayed in the elevation stow position. This was further confused/​complicated by the wind stow being triggered again while in this state. Resetting the antenna drives manually seemed to fix this. For future reference, try this first to reset the drives: <​code>​antenna=stop
 antenna=off antenna=off
 antenna=operate</​code>​ It should hopefully not be necessary to halt the schedule to do this. On Monday, I ran a test with the field system, bringing the telescope up from a powered-down state. The elevation drives failed to come up but the above sequence of commands got it going again. The elevation drives may need some attention...?​ antenna=operate</​code>​ It should hopefully not be necessary to halt the schedule to do this. On Monday, I ran a test with the field system, bringing the telescope up from a powered-down state. The elevation drives failed to come up but the above sequence of commands got it going again. The elevation drives may need some attention...?​
 +   - Remember, HMI will tell you what's going on with the drives
 +
   * Lots of ''​onsource status is slewing''​ errors?   * Lots of ''​onsource status is slewing''​ errors?
 +   - Only matters if it's meant to actually be on source (i.e. when it's recording, not during the pre-ob)
 +
   * Issues this week with pcfshb and re-starting observations after reboot. (Jim, Lucas, Ross, Bryn, others?)   * Issues this week with pcfshb and re-starting observations after reboot. (Jim, Lucas, Ross, Bryn, others?)
 +   - gpib issues? Only thing not working after a reboot (via IPS)
 +   - communication appears to lock up after a pcfs reboot
 +   - Jim having a crack and fixing this
 +
   * Does everyone understand how the PCFS software and eRemoteCtrl interact? (Jim)   * Does everyone understand how the PCFS software and eRemoteCtrl interact? (Jim)
 +   - PCFS controls antenna, DBBC and mk5. eRemoteCtrl is an easy access interface that we use here (so we don't have to VNC in and look at the fs)
 +   - Jim: Install mosh on pcfshb
 +
   * Please DO NOT terminate the Field System on Hobart 26m at the end of an experiment! (Jim P)   * Please DO NOT terminate the Field System on Hobart 26m at the end of an experiment! (Jim P)
 +   - Noted.
/home/www/auscope/opswiki/data/pages/operations/agenda2016_18_06.txt · Last modified: 2016/05/19 02:23 by Jonathan Rogers