This wiki is not maintained! Do not use this when setting up AuScope experiments!
This is an old revision of the document!
Council of Skyence
Chair/Presenting:
Lucas
In Attendance:
Jim, Jamie, Lucia, Liz, Teeg, Jonny, Lucas
Apologies:
Absent: Bryn, Jesse, Arwin
___
Agenda:
Module at Hobart full or broken, but second module had key switched off
DBBC at Ke been playing up quite a few times over the last fortnight.
Handover notes issues:
A few problems with *R1780*:
Hb e-remote control didn't work and neither did Dave's backup? Was this resolved and so what was the fix?
Ke DBBC problem? Is that resolved?
Patrick could you put the problem/fix you had with Ke IF power levels? Also the pointing problem and fix?
Bryn/Tiege, there were MK5 and clock problems at Yarragadee? The fix as per the handover notes seems vague.
*R1782*:
Ross I had the same problem with multiple dim's running. After I logged in as root (su) and tried that seemed to kill them.
Could you please describe how you noticed/diagnosed that the Mark5 disk/Mark5 was faulty at Hb? 'acs problem seems to be related to testing other module.'?
*R4781*:
“IF unit has a fault, probably with the PIC. No noise diode control at the moment, so no Tsys. Power levels into DBBC are OK though. (Jim)'” This was fixed already unless I am mistaken?
*R4782*:
Secondary module not correctly inserted into mk5 (I think the key was not turned). When first module became full the the mk5 gave “ERROR m5 -900 : Can't XLRappend() recording” (which is not an alarm) until noticed at 17:00UT. I changed M5 -900 to ALARM in the alarm_actions.txt for Hb.
If people aren't using Arwins comments.py script, they should be.
/home/www/auscope/opswiki/data/attic/operations/agenda2017_03_16.1489629881.txt.gz · Last modified: 2017/03/16 02:04 by Lucas Hyland