1. Tracker Controls MICE Controls and Monitoring Workshop September 25, 2005 A. Bross

2. EPICS is the Core for control of Fiber Tracker at DØ  Centralized database with supporting tools for defining the control system configuration  Report EPICS alarms to our global event reporting system  Interface to the Python programming language used to develop host tools for downloading (controls) and monitoring  Detector configuration management - COMICS  Archiving  Gateways

3. Communication via MIL-STD-1553B Bus  In MICE as is in D0 u Restricted detector access while running  1553 Provides a robust and highly reliable connection to electronics in the remote collision hall  Developed a queuing driver, device support, and a generic record  In D0 u 12 IOCs with ~70 1553 busses from the counting house to the detector and ~10 busses within the counting house

4. DØ Specific Records  SVX sequencer - configures and controls the ADCs in the tracking detectors  High voltage u Implemented using a state machine model u Linear ramping with retries u Trip condition recovery u Limits control  Rack monitor - Generic I/O module u 64 A/D inputs, 4 D/A output, 4 16-bit I/O words  MIL-1553 – debugging/testing on a 1553 bus

5. MICE Fiber Tracker Control Following D0 Model  Device support for the AFE board using the MIL-1553 driver  AFEIIt templates  Record and device support for the TriPt chips  Expert GUI for downloading u Does not use COMICS  Calibration software u New Model needed for MICE

6. Tracker System Overview Fiber Wave guide Cryostat VLPC AFEIIt Boards Cassette MIL-1553 Communication

7. MICE Tracker Model for C&M GUI (Python) EPICS AFEIIt Downloads Data Base (Oracle @ D0 System Parameters S.E.S Alarm Display Display (Data via EPICS) Monitoring Control

8. GUI Examples

12. Tracker: Monitoring

14. Stand-Alone C&D for VLPC Cryostats  First level of temperature control for the VLPC system is done with commercial controller (Oxford) u One set point per cryostat (2 cassettes/4 AFEIIts) u Second level of control is done via the AFEIIt board s On Module by Module basis  Communication to Oxford controllers is via RS232 (or IEEE488) u Will need to develop special code interface for this for its C&M

15. Conclusions  The basic infrastructure for the MICE tracker C&M can be copied from D0 u GUI u Python Code u EPICS implementation  Will have to “streamline” existing code for MICE u Great deal of excess baggage u Some MICE specific requirements  Will need a stand-alone VLPC cryostat C&M application u Simple RS232 based application