C&M Systems Developed by Local MICE Community

1. C&M Systems Developed by Local MICE Community J. Leaver 03/06/2009

2. Community C&M Systems Overview

3. In MICE, pions produced by inserting titanium target into halo of ISIS proton beam Target driven into/out of beam by linear motor, consisting of Shuttle: Moving magnet assembly attached to shaft (carries target) Stator: Series of solenoid coils Magnets Coils Water Cooling Shaft Stator Target: Controller

4. Target: Controller • Target Controller electronics actuates target by modulating Stator coil currents • Required motion profiles achieved with position monitoring + feedback algorithm • In terms of ‘user-level’ controls, need to • Enable actuation • Specify target dip depth (relative to beamline) • Specify timing delays for synchronisation with ISIS

5. Target Controller system in place, but only has ‘push button’ interface Currently undergoing complete redesign to increase functionality and enable PC control Based on USBDAQ Contains 1M gate FPGA USB interface for PC communication Will be integrated with EPICS using portable CA server framework Target: Controller

6. Target: Controller • In hardware/firmware design stage – EPICS development not yet commenced • Stage 1 upgrade will be complete end of July 2009 • Interfaces USBDAQ with existing analogue electronics • EPICS C&M system recreating current ‘push button’ controls • Stage 2 upgrade to be completed end of December 2009 • Redesign of analogue electronics • Enable fine control of subsystems

7. Target: Beam Loss • While actuating, necessary to record beam loss reported by ISIS • Monitor effect of MICE operations on ISIS • Ultimately a measure of particle production vs. Target dip depth • Target depth reported by control electronics • Beam loss signals provided by ionisation chambers distributed around ISIS synchrotron • Read using National Instruments PCI6254 DAQ card • To be replaced by custom DAQ board (early 2010)

8. Target: Beam Loss • Beam loss is an important physics parameter • Needs to be read directly via DATE, for correct synchronisation and inclusion in DAQ data stream • However, require capacity to run Target when DATE is inactive (during test & development phases) • Additional ‘standalone’ Target DAQ software exists • EPICS-based monitoring system should operate with either DATE or standalone DAQ

9. Target: Beam Loss • Beam loss IOC reads local data archive written by both DAQ systems • Clients provide virtual scope display, history plots & analysis • System functionally complete, but requires final selection of algorithm for calculating ‘absolute’ beam loss DAQ

10. Scintillating fibre Beam Profile Monitors developed at Fermilab Low mass, high resolution Fibres read out via PMTs, using custom electronics Also monitor temperature of PMT interface boards (check for cooling system failure) Hardware accessed via CAMAC bus 2 layers of 64 x scintillating fibres To PMT To PMT FNAL Beam Profile Monitors

11. FNAL Beam Profile Monitors • C&M system developed using MICE portable CA wrapper framework • 2 server applications • Control Server (performs hardware access) • Start/stop readout thread (external trigger enable) • Set pedestal levels • Writes acquired values to Data Server • Data Server • Contains most recent fibre data & temperature monitoring values • Reduces impact of client monitoring load on hardware readout

12. FNAL Beam Profile Monitors • Server/client applications complete • Well tested, used for monitor calibration procedures

13. Cherenkov System • MICE has 2 threshold Cherenkov counters upstream of Cooling Channel • Improve muon/pion separation • Perform clean selection of electrons • 2 vessels with aerogel radiator of different refractive indices • Read out by 8 PMTs with TYVEK reflectors

14. Cherenkov System • C&M components • Temperature + humidity • Sensor module read out via SNMP • IOC will access sensors using existing devSNMP device support (LNAL) • PMT HV supplies • CAEN HV modules • C++ drivers available – use portable CA server • P. Hanlet currently investigating requirements • Work on IOC implementation not yet commenced • Will develop system in September (after completing general infrastructure tasks – AH, CA)

15. Tracker: Magnetic Field Probes • Scintillating fibre Trackers enable measurement of muon beam emittance before/after MICE Cooling Channel • Trackers require 4T uniform field, provided by Spectrometer Solenoid modules • Necessary to monitor uniformity/stability of field • NIKHEF Hall probes will be installed • In homogeneous region of Tracker volume (centre) • At edges of Tracker volume • Outside solenoids (backup check of field polarity)

16. Tracker: Magnetic Field Probes CAN Bus Network Socket EPICS Server (Linux PC) Standalone Probe Interface (Widows PC) Hall Probes • Hall probes read out via CAN interface using Windows application • Existing ‘legacy’ software – reduced required development time • Portable CA server reads parameters from Windows PC via network socket • Monitor B-field (X, Y, Z components) + probe temperature

17. Tracker: Magnetic Field Probes • C&M system functionally complete • Required additions: Error handling refinements & definition of alarm limits • To be finalised during installation at RAL • Installation schedule depends on availability of Tracker hardware & F. Filthaut • Expect working system November 2009 • No dedicated client will be written – sufficient to display parameters via Channel Archiver Data Server

18. 1 2 3 4 5 Tracker: AFEIIts • Each MICE Tracker contains 5 Stations • Each Station consists of 3 doublet-layers of scintillating fibres (arranged at 120 rotation intervals) • Scintillation light output from Stations via clear fibre light guides

19. Tracker: AFEIIts • Light detected with Visible Light Photon Counters (VLPCs) • Low band gap silicon avalanche devices • Require 9.00  0.02 K operating temperature • Cryostat @ ~6.8K • Individual VLPC heaters raise temp. to 9K & maintain stability with feedback loop • VLPC output digitised using Analogue Front End with Timing (AFEIIt) boards • 1 VLPC requires 2 AFEIIts (an AFEIIt ‘Cassette’) • 1 Tracker requires 4 AFEIIt Cassettes AFEIIt VLPC Cryostat

20. AFEIIts have 2 communication interfaces Data Output stream of digitised fibre values Sent to VME LVDS SERDES Buffer (VLSB) cards Read out via DATE (not relevant for C&M) Control MIL1553 serial bus (communication with PC via SBS VME controller) Configuration, run control & monitoring interface Accessed via EPICS MIL1553 VLSBs VME Controller Tracker: AFEIIts

21. Tracker: AFEIIts • AFEIIt control requirements • VLPC signal digitisation parameters • Preamp/opamp gain/drive current, delays, comparator references, etc. • VLPC bias settings • VLPC heater/feedback loop configuration • ~230 parameters per board • Monitoring requirements • VLPC temperatures (verify 9K operation) • VLPC heater values

22. AFEIItCassette AFEIItCassette AFEIItDevice AFEIItDevice (L) (L) AFEIItDevice AFEIItDevice (R) (R) AFEIItEnsemble  N Tracker: AFEIIts • C&M system developed using MICE portable CA wrapper framework (object orientated, multi-layered software architecture) Configuration Control Run Control Monitoring Application Channel Access Client Channel Access Client Channel Access Client Network Each PV corresponds to an AFEIIt C++ library access routine AFEIItCasServer Process Variable Process Variable Process Variable

23. Tracker: AFEIIts

24. Tracker: AFEIIts Server (Normally use ‘headless’ daemon version) Run Control (To be implemented within DATE) Message Logging Temperature/heater value monitoring Configuration (Top level – additional GUIs omitted for clarity)

25. Tracker: AFEIIts • Server/client applications complete • Functionality verified using Tracker cosmic ray test stand • Successfully configure/monitor 8 AFEIIts required for single Tracker • Integration with DATE to be finalised • Embed very simple client in DATE code • Essentially enable/disable triggers at start/end of DAQ run

26. Tracker: AFEIIt Infrastructure • ‘Infrastructure’ corresponds to auxiliary hardware necessary for operation of AFEIIts • Power supplies, cryo systems - compressors, vacuum pumps, etc. • Currently not well-defined • Many items (cryo safety hardware interlocks) integrated with DL Spectrometer Solenoid controls • Tracker group needs to specify full list of requirements & negotiate additions to DL systems (where appropriate/possible)

27. Tracker: AFEIIt Infrastructure • Known C&M requirements: AFEIIt power supplies • 4 Wiener PSUs (1 per VLPC cryo) • CAN Bus or RS232 communication interface • Intend to use RS232 – standard PC port, no additional interface hardware • No progress yet – expect manpower to be available for completion in August • Additional systems to be discussed (with consideration of limited resources/manpower)

28. Hydrogen Absorbers: Focus Coils • Ionisation cooling achieved by passing muons through low Z absorber to reduce transverse & longitudinal momentum • Reaccelerated to original longitudinal momentum via RF Cavities • MICE (primarily) uses liquid hydrogen absorbers • Each absorber mounted inside a pair of superconducting solenoids (Focus Coil Module) • Provides low beam beta region

29. Hydrogen Absorbers: Focus Coils • Focus Coils expected to require C&M systems very similar to Pion Decay Solenoid & Spectrometer Solenoids • See DL’s talk • Would be most efficient for DL to take over project (wealth of relevant expertise) • Unfortunately prevented by MICE funding constraints • Task assigned to MOG

30. Hydrogen Absorbers: Focus Coils • If possible, will attempt to use DL’s existing magnet designs as template • DL C&M systems have vxWorks IOCs • For MICE to develop vxWorks software, expensive (~£15.2K) license required • Investigate replacement with RTEMS controllers (‘similar’ real-time OS, free to develop) • DL systems include custom in-house hardware • Not available for general MICE usage – will check alternatives • However, will consider possibility of entirely new design (perhaps with Linux PC-based IOCs)

31. Hydrogen Absorbers: Focus Coils • Work on Focus Coil C&M system has not yet commenced • Need to confirm availability of P. Hanlet • Assistance from FNAL Controls Group would be highly beneficial – need to discuss • Expect to start project in September 2009

32. RF Cavities: Coupling Coils • Each RF Cavity (used to reaccelerate muons) also surrounded by a superconducting solenoid (Coupling Coil) • Confines muon beam within RF Cavity beam windows • Coupling Coil C&M situation identical to Focus Coils • Similar to other MICE magnets • MOG responsibility (need to confirm P. Hanlet’s availability) • Project should run in parallel with Focus Coil C&M system

33. DATE Status • Need mechanism for reporting current DAQ state via EPICS • Simple (‘dumb’) data server hosts DATE status PV • Client application reads DATE status from DIIM server, forwards value to EPICS server • Server & display client complete; DATE-side client to be implemented EPICS Data Server (Single ‘status’ PV) DATE Client

34. Network Status • Need to verify that all machines on DAQ & control networks are functional throughout MICE operation • Two types of machine • Generic PC (Linux, Windows) • ‘Hard’ IOC (vxWorks, potentially RTEMS) • EPICS Network Status server contains one status PV for each valid MICE IP address

35. Network Status • Read status: PC • SSH into PC • Verifies network connectivity & PC identity • If successful, check list of currently running processes for required services • Read status: ‘Hard’ IOC • Check that standard internal status PV is accessible, with valid contents • e.g. ‘TIME’ PV, served by all MICE ‘hard’ IOCs

36. Network Status • Currently have working prototype • EPICS server connects to PCs via SSH, checks contents of ‘key’ ID file • Client displays status of all PCs, scans at user-specified period (with ‘check now’ override) • Need to add service checking & ‘hard’ IOC support

37. Unassigned Control Systems • Following systems have no allocated C&M effort • Time of Flight System • Diffuser • Calorimeter: KL Calorimeter • Calorimeter: Electron Muon Ranger • Currently investigating system requirements • Need to find additional resources within the MICE community • MOG operating at full capacity & no funds for DL to undertake these projects • Expect those responsible for each system will be required to implement corresponding EPICS controls • Possibility of assistance from FNAL Controls Group (to be discussed)

38. Schedule

39. Schedule