1 / 17

Plans for EPICS in Hall D at Jefferson Lab

Plans for EPICS in Hall D at Jefferson Lab. Elliott Wolin EPICS Collaboration Meeting Vancouver, BC 30-Apr-2009. Jefferson Lab: Newport News, Virginia. 6 GeV Continuous Electron Beam Accelerator Facility Superconducting RFQ’s Three existing experimental halls

ardith
Download Presentation

Plans for EPICS in Hall D at Jefferson Lab

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Plans for EPICS in Hall D at Jefferson Lab Elliott Wolin EPICS Collaboration Meeting Vancouver, BC 30-Apr-2009

  2. Jefferson Lab: Newport News, Virginia 6 GeV Continuous Electron Beam Accelerator Facility Superconducting RFQ’s Three existing experimental halls Approved 12 GeVupgrade and new hall $310M GlueX experiment: 200 kHz trigger 3 GB/s off detector 300 MB/s to tape

  3. GlueX Experiment in Hall D Search for mesons with gluonic excitations • 200 kHz trigger rate • Deadtimeless readout • 15 kB event size • 3 GB/sec to L3 farm • Factor 10 L3 rejection • 300 MB/s to tape • Data taking in 2014

  4. Experiment vs. Accelerator Operations • Trigger/DAQ-centric, not controls-centric • trigger and DAQ hardware more problematic • high-speed data path is critical • Run-oriented • many configuration changes • sometimes every 5 minutes • hardware download/readback speed critical • may bypass normal controls path for speed

  5. 3 GB/s 3 GB/s DAQ at High Luminosity 3 GByte/sec 3 GB/s ROC ROC ROC ROC ROC ROC E MU E MU E MU E MU E MU E MU E MU 16 TB 16 hrs 300 MB/s 300 MB/s Level 3 Farm 90% Rejection RAID 1 EMU 300 MB/s SILO in Computer Center 2 PB/year Many Cores 8 EMUs 8 EMUs 60 ROCs Event Builder Crossbar

  6. Controls/Monitoring Channel Counts Hardware Electronics

  7. Hall D Three-Tier Controls Architecture Supervisory Control and Data Acquisition System (SCADA) Experiment Control System (ECS) Detector Control System (DCS) High-level state machines and operator GUI’s. (AFECS) Communication, archiving, alarms (EPICS) Autonomous detector control, low-level state machines. (PLC, Ethernet, CAN, SMBus) Allen-Bradley PLC HV System LV System Other Systems Magnets Target Gas Cooling

  8. Detector Control System • 24x7 autonomous operation • All PID and control loops reside here • No EPICS at this level • Allen-Bradley PLC • engineers prefer simple analog sensors/actuators • will have some Ethernet devices • High-level manufacturer-supplied controllers • HV, LV • goniometer • CAN, SMBus controllers

  9. SCADA - Supervisory Control and Data Acquisition • EPICS • JLab has extensive experience with EPICS • accelerator and all three existing halls • Will use Linux-only EPICS, no VxWorks or RTEMS • CSSand/or LabView for non-expert graphics • few restrictions on expert screens • Integrate with publish/subscribe package (cMsg) • Alarm system – BEAST (SNS) or LASER (CERN) • Many other tools in EPICS toolkit • archiving – from SNS or JLab • strip charts – StripTool, SNS, JLab or Labview • save-and-restore facility – SCORE from SNS • web – CAML, WebCA • analysis - Labview

  10. Experiment Control System • AFECS • Agent Framework for Experiment Control Systems • Java agent-based control system from JLab DAQ group • Used for run control • Allows integration of slow controls with run control • high-level state machine scripting language • hierarchical • similar to SMI++ used at LHC

  11. Alarm System • Goals – are these satisfied by BEAST? LASER? • All alarms require operator action • otherwise “alarm” is a nuisance • Single problem gives single alarm • alarm filtering/reduction, flood suppression • Context sensitive alarms • no alarm on device if not being used • Alarm shelving • remove from alarm screen

  12. Labview • Considering for majority of operator screens • Channel Access modules available • client for Linux (ORNL) • waiting for Linux server • Basically just another GUI builder • like EDM, CSS • superior analysis capabilities

  13. Conclusions • Using EPICS for SCADA level (middle tier) • Linux only • no control loops in EPICS • Cherry-picking best applications • Many from SNS/ORNL • May use Labviewextensively Please give me comments and suggestions!

  14. Backup

  15. Full Experiment Trigger Trigger Signal Level 1 Energy Sum Trigger T r igger Inputs 16 bits O u t p u t Detector Pulser 1 Pulser n Add’l Trigger Logic 16 bits Calib 1 Calib n Trigger Supervisor Module

  16. PLC Redundant Chassis LayoutSeven Module Chassis Communication Module PLC Power supply Redundancy Module Remote Chassis Communicator Blank Slots

  17. Ten Module Remote Chassis • Field Devices: • temperature sensors • pressure gauges • vacuum gauges • cryogenic level gauges • relays • voltage, current gauges • flow meters • many others Remote Chassis Communicator Power supply DC Input Module

More Related