Choose timezone
Your profile timezone:
Interlock when T4 target is moving?
→
Europe/Zurich
A. Colinet, M. Fraser, K. Li, L. Nevay, J. Ridewood, I. Romera
Background
The T4 target takes minutes to move from one position to another. It can move under two conditions:
- Manually using CESAR
- EIS in case of intrusion in PP118
Requirement
On SFTPRO, sending beam to a moving target is not desirable, but will not damage the machine.
On SFTSHIP, it is mandatory to dump the beam if:
- the target is moving
- or the target is not within the 6 defined positions for HI-ECN3 +/- tolerance
New interlock to the BIS
Beam Interlock Controller: TCC2 MASTER BIC located in rack BA80=RA4626
Interlock provided by T4 controls located in rack BA80=RAxxxx
- FALSE if (T4 is moving) or (T4 not in the 6 defined positions +/- tolerance)
- TRUE otherwise
For non-HIECN3 destinations, this interlock is ignored.
For HIECN3 destination, this interlock must be TRUE, otherwise the BIS must request a beam dump.
Action Antoine: Validate with J. Lendaro if such an implementation is possible, and if yes, add this interlock to the BIS by updating all related documentation
Controls software feature when scanning
Matt proposes to use the same controls software feature as already existing on the Septa controls. This feature would allow the target to move to a different position and stop when the beam is extracted. After the spill, the target would be able to move again and continue going towards its set position.
Action Matt: send information to Laurie (email)
Timing question
In case of an ACCESS interlock, the T4 target is an EIS and as such moved into a specific position.
Would the BIS dump the beam fast enough not to harm the target?
- Chain of events in the access system not known
- Behaviour of the T4 controls + response time? Action Antoine: Ask Jerome for information
There are minutes attached to this event.
Show them.
