On the GUI registering trips: Since a trip is measured by a signal
straight out of the crate and not filtered through any code,I believe the
trips are real. There are many different circumstances that can cause a
trip. Sometimes, I believe, the channel might still appear to hold
voltage. In the future, if this occurs can the operator go to the crate
level and look for any anomalous status ("ST") values, i.e. those that are
not 001? Then write the channels and the status values down and we can
correlate them to a particular box. It is appropriate to treat all trips
as real and continue to hit the trip reset.
Cheers, Adam
On Wed, 17 Mar 2004, Electronic Log Book wrote:
> Operators: clasie karpiusp vziskin
>
> L14 tripped regularly throughout shift. Early in shift L14, L15,L21, R24 were all at 3800V. After L14 was identified as the culprit of the once-per-minute trip rate its voltage was lowered to 3750V while the others were raised to 3850V. This brought the trip frequency within tolerable limits.
>
> Also noticed some stranged behaviour of HVGUI where general crate trips occurred but WC's themselves were not tripping. Reset rectified this but we could not determine which channel actually tripped. This happened twice.
>
> Latter half of shift was plagued with variabel beam quality and many bad fills.
>
> All crunchign caught up.
>
>
>
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST