Displaying report 1-1 of 1.
Reports until 19:09, Wednesday 08 January 2014
H1 SUS (CDS, SEI)
jeffrey.kissel@LIGO.ORG - posted 19:09, Wednesday 08 January 2014 - last comment - 09:40, Thursday 09 January 2014(9169)
SUS Hardware Watchdog Testing
J. Kissel, R. Bork, B. Abbott, D. Barker, F. Clara, A. Sevigny

Satisfied with a few days of debugging and testing a single chassis of the new Hardware Watchdog System on the H1 DAQ Test Stand, we have installed a similar chassis in the SUS BSC123 rack, and hooked it up to the H1 SUS ITMY M0 sensors. We have deliberately *not* connected any of the trip signals (either to the SEI or SUS actuators) while we characterize the RMS trigger system. In addition to the hardware, we've installed temporary configurations of the h1iopsusb123 and h1susitmy models, in which

- h1iopsusb123: Unfortunately, neither analog or digital readbacks of the RMS calculated by the board are exposed in any way. Instead, we've installed a mock RMS system to replicate the RMS logic that is performed inside the hardware watchdog itself, using the raw ADC values as inputs. Though the changes have been made to the model, it has not yet been compiled, installed or restarted, since the green team were still actively searching for beams and needed ITMX up all afternoon. Hopefully we can install tomorrow morning.

- h1susitmy: the status bits of the hardware watchdog *are* digitized via a binary input chassis, and fed into spare channels of the already present Contec BIO card. Similarly, the remote control reset bit are spit out of the same card, through a binary output chassis, to the SUS hardware watchdog. As such, for the status bits, we needed to add a few new connections inside the BIO_DECODE block, which are turned into a bitword and fed into a new EPICs readback channel, H1:SUS-ITMY_HWWD_STATUS.

Once we get the readback installed, we'll run the ITMY chamber in various configurations of isolation and excitation, to determine a good value for the RMS threshold. The test cases we plan to use are:
- Ambient (no actuation from any layer)
- SUS Undamped, ISI Damped, HEPI Position Loops
- SUS Undamped, ISI Damped, HEPI Position Loops (With large alignment offset)
- SUS Damped, ISI Damped, HEPI Floating
- SUS Damped, ISI Damped, HEPI Driven (Normal level TFs)
- SUS Driven (LOUD White Noise TF), ISI Damped, HEPI Floating
- SUS Damped (With large alignment offset), ISI Damped, HEPI Floating
- SUS Undamped, ISI Driven (LOUD White Noise TF), HEPI Floating
- SUS Undamped, ISI Floating, HEPI Driven (LOUD White Noist TF)
These should give us a good feel for the most quiet and most loud situations for the M0 OSEMs. Based on these results, we'll make an assessment of where we want to set the threshold.
Comments related to this report
jeffrey.kissel@LIGO.ORG - 09:40, Thursday 09 January 2014 (9175)CDS
J. Kissel, J. Warner

After ensuring all seismic isolation and suspension systems were safely ramped down, I re-compiled, re-installed the h1iopsusb123 front end model. After which, I killed all processes running on that front end, h1susitmx, h1susbs, and h1susitmy, restarted the h1iopsusb123 process, and restarted all the suspension processes. I then finally restored damping on SUS ITMX, ITMY, and BS, and restored the alignments of ITMX and BS to what they had been set before I got started.

Both temporary configurations of the h1susitmy.mdl and h1siopsusb123.mdl have been committed to the userapps repo.
Displaying report 1-1 of 1.