Aggregator
xD -> JD70-107 55um 45/135 target. Ion chambers not yet calibrated
Downtime Incident CREATED: Hall D ion chamber counts suddenly jumped
Hall D Left and Right Goni ion chambers reading 12-61k with no beam in the machine
Tripped on Hall D ion chambers. Could not clear FSD. Looking the myaplot, the readback for LGoni spiked up to 62k, and RGoni up to 12k. LGoni lowered to after about a minute.
Called the Hall. They were not doing anything, just taking data. Getting in touch with SSG On-call.
FSD Masking Tool: Successful Destination masking to: HallB,HallC
Scan of harp_2c21
QuickPic - Touched up Hall D orbit
Scan of harp_tagger
Hall B 2C21A & 2C24A Lock drove positions off with no beam
Beam was lost in the Hall B line after we had to cycle some correctors on the E101B12 rack. This was super puzzling as they were all pass 3 and higher correctors with the exception of 1S09V, an Arc1Orb lock corrector.
We found the 2C21H and 2C20H correctors railed. They started walking off with no beam in the machine. The only lock that was engaged at the time that would do this was OpsMatrix01, our go-to tagger lock.
Fig 1: No beam in the machine at all. IPM2C21A and 2C24A wiresums were reading 0, Hall B Beam Mode was 0. Bottom chart has the expression for the lock's "Enabled When" logic.
Scan of harp_tagger
Scan of harp_tagger
Scan of harp_tagger
Scan of harp_tagger
Scan of harp_2c21
QuickPic - xD -> 1.1x10^-3 Al 100um @ 25nA
iCalibrate: Hall D
Not making it into hall B
After cycling correctors and quads that mismatched in E101B12 when swapping the card for MQA7S07 (all > than pass 1 except for a lock corrector 1S09V), we are now losing beam somewhere upstream of the nA BPMs and viewers. very puzzling but we'll send tune to the tagger dump to find where the culprit is.










