Reports until 13:36, Monday 11 March 2013
H1 SUS
jeffrey.kissel@LIGO.ORG - posted 13:36, Monday 11 March 2013 (5741)
h1sussem and h1sussr3 front-end models now exchange SR3 oplev via SHMEM
J. Kissel, D. Barker,

A few days ago, I'd installed the H1SUSSRM, H1SUSSR3, and H1SUSOMC front-end models (see LHO aLOG 5717), but we ran into a small problem that the RTNET status showing red in that SRM wasn't properly sending (the first bit), and SR3 wasn't properly receiving (the second bit). We traced it down to me unnecessarily using the Dolphin PCIe network (i.e. the cdsIPCx_PCIE blocks), when -- because SRM and SR3 are on the same computer -- the shared memory (the cdsIPCx_SHMEM blocks) should be used instead*. 

Today we 

- Modified the h1sussrm.mdl and h1sussr3.mdl front-end models to use the cdsIPCx_SHMEM
- cleared the H1.ipc file of all channels created by the h1ham56 user models (since they're the latest)
- re-compiled all three h1sussrm, h1sussr3, and h1susomc models to repopulate the H1.ipc file with all the interwoven channels (specifically the Binary I/O, but including watchdog channels, offload channels [for srm only], etc.)
- re-installed the models,
- restarted the models,
- restored the models
- confirmed that the RT NET status is now green for all suspensions.
- committed the modified models to the user apps repository


* This was a relic of the copy-and-paste from the PR3 system, which actually needs to use the dolphin network because the optical lever signals come in on the sush2b IO chassis, and PR3 is run from the sush2a IO chassis.