Choose timezone
Your profile timezone:
Interlocking BSI/BSG
→
Europe/Zurich
BSI
For the dedicated beam: no need for BSI interlock as the beam isn't split in TDC2. The intensity is known by the SPS BCTs that are redundant.
For the shared beam: need to interlock on the BSIs due to the limited intensity that the TAXes can sustain. Today, only one intensity interlock is implemented on T6. Adding BSI interlocks would provide additional protection for SFTPRO cycles.
Requirements: publish data every 20ms (which requires a gateware update to calculate and broadcast the cumulative integral during the spill). The beam would have to be dumped in <100ms
-> The SIS is unable to meet the low-latency dump requirement of 100ms.
The requirements on how much intensity the TAXes can sustain must be defined by STI.
No possibility for a test in 2025 with intra-beam interlock, possibility to do a test after the spill, but nothing new would be learnt.
Action Antoine: organise a follow-up meeting with OP/STI/ABT on Beam Intercepting Device requirements
Action OP/ABT: write functional specifications on the BSI interlocking requirements
BSG
The goal is to interlock on the profile of the beam.
This interlock can only be implemented in the SIS because no calculation can be done on-the-fly.
The SIS would prevent the next extraction, no intra-spill interlock., which is ok.
The BSG and BSI use similar electronics, so latency features on the BSI can apply to the BSG.
Needed for BDF/SHIP in post-2031 operation
There are minutes attached to this event.
Show them.
