Reports until 12:39, Wednesday 17 October 2012
H1 SUS
jeffrey.kissel@LIGO.ORG - posted 12:39, Wednesday 17 October 2012 - last comment - 16:30, Wednesday 17 October 2012(4464)
Cursory check of MC3 Software -- Looks OK
B. Bland, F. Clara, J. Kissel

At the request of Betsy, given the confusion on the inability to drive MC3 (see LHO aLOG 4462), I took a quick look through the software side of things to be sure all was well, and indeed I see nothing out of the ordinary. 

Here's my assessment:
- There have been software changes involving the IOP model (modifying the IOP watchdog) on Oct 09 (see LHO aLOG 4402), and also hardware changes (swapping out MC3-only, T3LFRTSD quadrapuss cable) on Oct 11 (see LHO aLOG 4423), before Mark attempted to take transfer functions on Oct 12-13 (see LHO aLOG 4432) which show no coherence (again, according to LHO aLOG 4462).
- Filiberto reports that 
     - He can see drive going into (from the AI chassis) the coil driver chassis (though I didn't catch exactly to which cables he was referring), implying the that software checks out, i.e.
          - The BIO I/O is functional (arranged/routed properly in software, traveling well across shared memory)
          - The IOP watchdog is allowing signals to flow
     - He cannot see anything coming out of either the COIL or TEST outputs (going towards the SatAmp on the way to in vacuum).
- Betsy reports that 
     - MC1 is able to drive and transfer functions look normal, implying that
          - the shared cable between MC1 and MC3 remains functional
          - The BIO I/O is functional and allowing drive
          - The IOP watchdog is allowing signals to flow
     - She's cranked on the centering knobs for each OSEM involved with the T3LFRTSD and confirms correct sensor response implying that signal chains are connected to the right OSEM

From we conclude that something is awry with the drive signal chain between the input to the coil driver from the DAC / AI chassis to the tip of the in-vacuum quadrupuss cable for T3LFRTSD. This leaves the following possibilities:
- Coil driver board has malfunctioned
     - Can we see anything coming out the coil driver monitor boards in either TEST or COIL configuration? Looks like the noise monitor channels are white -- does this model not exist yet / is it not running?
- The Binary I/O switch chain had failed
     - (though the monitor bits indicate that the chain is functional, both in the TEST/COIL switch and LP switch)
- The rest of the ex-vac chain has failed somehow (Coil Driver to SatAmp cable, SatAmp pass-through, SatAmp to fake-feedthrough)
- The rest of the in-vac chain has failed (the quadrupuss has been swapped, but how about the D0900225?)

Good luck!
Comments related to this report
filiberto.clara@LIGO.ORG - 16:30, Wednesday 17 October 2012 (4470)
Found cabling issues inside Rack H1:SUS-C3. Cabling to Binary Ouput D1000725 (SUS-C3-12) and Binary Monitors for D1000725 (SUS-C3-11) were switched with those for PRM-PR3.