laura.nuttall@LIGO.ORG - posted 16:10, Thursday 17 July 2014 - last comment - 17:09, Friday 18 July 2014(12818)
H1:ISI-GND_STS_ETMY_X/Y/Z_DQ channels do not have correct data
It looks like the data from the ETMY STS is not getting saved to the frames correctly. If you look at the attached plot, it shows an ASD of the ETMY STS. I've plotted both the data (5 minutes of data starting at 17 July 00:00 UTC) from the SENSCOR channels (H1:ISI-ETMY_ST1_SENSCOR_GND_STS_X/Y/Z_FIR_IN1_DQ) and ISI-GND channels (H1:ISI-GND_STS_ETMY_X/Y/Z_DQ) - no filters have been applied, this is just the raw data. The SENSCOR channel looks fine so we do not think the sensor is broken, but the data isn't being saved correctly to the H1:ISI-GND_STS_ETMY_X/Y/Z_DQ channels. Summary - Data is not being saved correctly to the H1:ISI-GND_STS_ETMY_X/Y/Z_DQ channels.
Images attached to this report
Comments related to this report
Vern, Jim, Jeff, Dave. We can confirm the data is being corrupted somewhere within the model. Jeff is emailing the details to the ISI group.
J. Kissel, D. Barker Dave traced the problem down to a corruption of this particular STS channel at the GND_STS library part level, which stores the calibrated STS2s (or T240s) in the frames (installed last September by Hugo). The data looks live and well at the point at which these calibrated signals exit the STSINF bank, and enter the ST1_SENSCOR bank, but not in the test points in the GND_STS block where they're stored into frames. See attached ASD.pdf. The GND_STS versions of these channels take a pretty adventurous path through the simulink/front-end model from where they're generated (deep inside the ST1 block) up to where they're stored (at the top-level), so we suspect there's a problem with the level traversal. There is a point where buses and tags are used to traverse levels, so we immediately suspect this because of past history with battling the RCG, but what's strange is that -- other than the top level -- all parts are common to all BSC-ISIs, so this problem should be systematic if this is *actually* the problem -- but its not. Let us know if you have any advice from off-site. Also -- and "svn st -u" reveals that LHO's local copy of the isi corner of the userapps repo, /opt/rtcds/userapps/release/isi/ needs some serious clean-up.
Images attached to this comment
Non-image files attached to this comment
J. Kissel Sheesh .... more confusion. I just took a look at the ETMX channels to see if all of those were the same. They're pretty close, but only two are identical -- those channels *before* the input matrix. I expect them all to be identical. What gives? The SENSCOR version of the channel is the only one *after* the input matrix, and it looks like the input matrix is mapping X to Y and Y to -X. Is this making up for a bad analog cable connection? Is this based on some commissioning effort? I know it's a T240 an'all (see LHO aLOG 10635), but the wiring diagram (see D1400077) indicates no such tomfoolery...
Images attached to this comment
Non-image files attached to this comment