Advanced Accelerator Applications (AAA) Low Energy Demonstration Accelerator (LEDA) Deb Kerstiens (11/26/2001) - 1
LEDA Status q Advanced Accelerator Applications—Low Energy Demonstration Accelerator q Recently completed the Beam Halo Experiment q Fielded new systems q Magnets on Halo beamline q New wire scanner and halo scraper mechanisms and software q Vacuum for halo beamline q Successful data acquisition q Data analysis shows good correlation with models q Verification of halo leads to questions about why q More to come… q As of last week, future uncertain but bleak Deb Kerstiens (11/26/2001) - 2
LEDA Beam Halo Challenges q Diagnostics q Wire scanner / Halo scrapers q Lab. View -> EPICS q Automated scans and scrapes through EPICS sequence/OPI q Magnets q 52 magnet latticeon Halo beamline q 4 quadrupole singlets q 48 quadrupole bulks/ 6 bulk supplies with 8 shunts q Field Point I/O q Ethernet IP q Lab. View-> EPICS q Control System Integration q Run permit q Operations support q Many different systems q Support systems, data taking, EPICS, UNIX, Labview, all tools Deb Kerstiens (11/26/2001) - 3
Control System for the LEDA 6. 7 -Me. V Proton Beam Halo Experiment Consoles, Control Room Diagnostic Control Ethernet (Channel Access) Field-Point-IOC GPIB-IOC Server (File Server, Archiver, …. ) Stepper Motor-IOC GPIB 2 Bus LAN Steerer PS FP FP PLC … FP High Power RF Systems Wave Guide Injector and LEBT … Quads PS RFQ HALO HEBT Beam Stop VXI-IOCs Deb Kerstiens (11/26/2001) - 4 Vacuum System
LEDA Lessons Learned q Fielding new hardware in an upgrade q Behind schedule q When it doesn’t work q No local experts or support q Let the engineer program it q Lab. View is “easy” but q All programs are different q Novice vs. expert q More layers to debug q No revision control q Guess who gets called q Control System Integration q Run permit q vx. Stats q Can’t guarantee run permit when you don’t have into q Archiving, time stamps q Operational Support q Communication q Teamwork/support Deb Kerstiens (11/26/2001) - 5
LEDA Lessons Learned q “Maintenance nightmare” q Many different systems q few people to support them q Need to call “experts” to troubleshoot q Revision control q No consistency q Can’t enforce q What Worked Well: q Operations support q Assigned, on-call q Responsive q ELOG q Archiving q Standard EPICS systems Deb Kerstiens (11/26/2001) - 6