40m
QIL
Cryo_Lab
CTN
SUS_Lab
TCS_Lab
OMC_Lab
CRIME_Lab
FEA
ENG_Labs
OptContFac
Mariner
WBEEShop
|
40m Log |
Not logged in |
 |
|
Sun Aug 5 13:45:00 2018, gautam, Update, SUS, ETMX tripped 
|
Thu Aug 9 12:40:14 2018, gautam, Update, SUS, ETMX trip follow-up
|
Mon Aug 13 09:56:23 2018, Steve, Update, SUS, ETMX trip follow-up 
|
Thu Aug 23 08:24:38 2018, Steve, Update, SUS, ETMX trip follow-up 
|
Fri Aug 24 14:58:30 2018, Steve, Update, SUS, ETMX trips again
|
|
Message ID: 14178
Entry time: Thu Aug 23 08:24:38 2018
In reply to: 14156
Reply to this: 14184
|
Author: |
Steve |
Type: |
Update |
Category: |
SUS |
Subject: |
ETMX trip follow-up |
|
|
Glitch, small amplitude, 350 counts & no trip.
Quote: |
Here is an other big one
Quote: |
A brief follow-up on this since we discussed this at the meeting yesterday: the attached DV screenshot shows the full 2k data for a period of 2 seconds starting just before the watchdog tripped. It is clear that the timescale of the glitch in the UL channel is much faster (~50 ms) compared to the (presumably mechanical) timescale seen in the other channels of ~250 ms, with the step also being much smaller (a few counts as opposed to the few thousand counts seen in the UL channel, and I guess 1 OSEM count ~ 1 um). All this supports the hypothesis that the problem is electrical and not mechanical (i.e. I think we can rule out the Acromag sending a glitchy signal to the coil and kicking the optic). The watchdog itself gets tripped because the tripping condition is the RMS of the shadow sensor outputs, which presumably exceeds the set threshold when UL glitches by a few thousand counts.
|
|
|
|
|
|
|