cross-uVAX calibration veto logic
rlu@riscgs1.lngs.infn.it
Wed, 16 Aug 1995 18:22:45 +0200 (DFT)
Hello,
Last maintainence day, Aug.9, Eric found some problem with the
cross-uVAX calibration veto connections. Today, I investigated into this
problem. First I suspected that some cables were mislabeled, but I checked
all of them, this possibility is ruled out. Then there is the possibility
that one of the cables were broken. So I sent signals from one end of the
cable and look at the triggers at the other end. Here is what I find:
23VETO from uVAX1 to uVAX2 is OK
23VETO from uVAX2 to uVAX1 is OK
45VETO from uVAX2 to uVAX3 is OK
45VETO from uVAX3 to uVAX2 is NOT OK, NO TRIGGER FOUND
To fix the problem fast, I just put a new cable for the 45VETO from uVAX3
to uVAX2. But I'm not sure if that's all the problem there is for the
cross_uVAX calibration veto connections.
I ran a LED-CALIBRATION on uVAX2, but we left the whole detector
(uVAX1, 2, 3 all on) in acquisition. We hope to check the cross-uVAX
calibration veto connection in the data. The file is in
VXMACB::HSD000$DUA0:[DATA]RUN010717.DAT
I hope some of you would be nice enough to take a look into this data and
find out whether the cross-uVAX calibration veto logic has any problem or
not. I strongly encourage you to take a look at this data file as soon as
possible before the data is taken away from the directory. Or you can make
a copy of it before it is gone, but it would be nice to let us know if there
is a problem or not. We are here to fix problems.
I also ran a LASER-CALIBRATION on vUAX2, and the whole detector was
left in acquisition again. You can take a look at this data file as well:
VXMACB::HSD000$DUA0:[DATA]RUN010719.DAT
Well, this file might have some problem of its own. Since none of us here
in Itlay had done any laser-calibration before, so the procedure was rather
unclear to us. We didn't see the whole supermodules being fired at all. So
it might just contain all trash, but it might have something intersting.
Again, all of you out there are welcome to take a look at it.
One more note, we found a little mistake in the camac list file
[SCINTSOFT.CAMAC.LED]CAL.LIS2. It appeared that some of the modules have
been moved, but the changes were not made in the camac list file. The
mistake is taken care of already, now the camac list file ran just fine.
Enjoy your summer!
Rong Nina Lu