Differences between revisions 2 and 3
Revision 2 as of 2007-09-07 22:46:22
Size: 2259
Comment:
Revision 3 as of 2007-09-07 22:46:40
Size: 2256
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
___

= Goal: =; EPICS (software) interlock that will close V1 (main 40m vacuum valve) under abnormal conditions:BR 1, P1 above 3 mTorr ORBR 2, P2 above 100 mTorr ORBR 3, N2 below 60 PSI ORBR 4, V4 closes ORBR 5, Maglev fails ORBR 6, Power failsBR Condition 1 & 2 has to be bypassable during pump down.

Also would be nice if we had code and hardware that would:BR Turn off PZTs (two sets of steering mirrors, OMC) when pressure is in transition region. (Need relay box and EPICS IO channel).

1) Some code for this ALREADY EXISTS; it may not be right or properly implemented, or handle all the above cases.

See: /cvs/cds/caltech/target/c1vac1/VacInterlock.st which is a soft-link to code on luna: /opt/CDS/d/epics/apple/Caltech/40mVac/40mVacScipe/dev/src/VacInterlock.st

2) I read through VacInterlock.st for jollies, and added comments. See /cvs/cds/caltech/target/c1vac1/VacInterlock_commented.st PLEASE START WITH THIS CODE; WE NEED COMMENTS!

3) The EPICS state code used at the 40m is in /opt/CDS/d/epics/apple/Caltech/40mVac/40mVacScipe/dev/src which bugs me. It should ALL be in /cvs/cds/caltech/target . The problem is, as of 2004, one couldn't build EPICS state code on a 40m machine... I think it had something to do with a lack of a Solaris c compiler. I Think this was since been rectified. Can we build EPICS state code on, eg, op440m?

4) Compiling EPICS state code: see (maybe obsolete) instructions in http://www.ligo.caltech.edu/~cit40m/Docs/40mProcedures.pdf

5) Looking in /cvs/cds/caltech/target/c1vac1 I see that (on Aug 31, 2007) the latest saverestore.sav file is dated Feb 3 2006. Does that mean that this vme cpu hasn't been rebooted since Feb 2006?? We have had power outages; is c1vac1 really on UPS? It definitely should be! Or is it that the saverestore facility doesn't work?

6) I just now tried "telnet c1vac1" and got no response. I wonder why. In the past, one could telnet in to EPICS vme cpus.

7) When changes are made and a new VacInterlock.o is built, we need to load it into the vme cpu by rebooting it (correct?). Will this cause any undesireable hiccup in the vacuum controls? We need to be sure about that!

Vacuum_Interlocks (last edited 2018-11-01 18:04:01 by StevevassATligoDOTorg)