Experience from the New LEIR Controls during Machine Commissioning

1
Experience from the New LEIR Controls during
Machine Commissioning

• V.Baggiolini, M.Pace, S.Jensen

2
Outline

• LEIR machine in a nutshell
• LEIR controls
• Remarkable features
• Challenges
• Experience from the commissioning
• Conclusion

3
LEIR in the Ion LHC Injector Chain
(LEP)
LHC
LEIR Low Energy Ion Ring
4
The LEIR Layout
Ejection line
RF
Main Dipoles
Injection line
Upgraded LEAR into LEIR
5
Outline

• LEIR machine in a nutshell
• LEIR controls
• Remarkable features
• Challenges
• Experience from the commissioning
• Conclusion

6
Remarkable Features

• Major constraints
• Inheriting controls designed for the LHC
• Inheriting unified controls from the merge of 2
  Control Groups
• Keeping legacy controls from existing PS
  accelerators
• A test-bed for new standard solutions in view of
  LHC
• Used for the 1st time under operational
  conditions
• To be deployed in LHC its pre-injectors at
  later stage
• An anticipated challenge for the CO Group

7
Challenges

• Technical challenges
• Customize enhance functionalities of LHC
  controls
• Practically validate LHC controls
• Deploy unified controls from two Control Groups
• While respecting a tight schedule
• Cultural challenges
• Define a unique strategy from similar (but
  different) solutions and habits on both sides
• Set-up productive developer teams
• Convince Operation to use new tools and methods

8
Experience during CommissioningTechnical
Perspective

• Front end hardware
• Front end software
• Application software
• Timing sequencing
• General services
• Alarms
• Analogue signals

TH2.3-70
TH3A.1-50
9
Front End Hardware

• LHC standard technology for all VME machines
• Wiener Crates hosting CES PowerPC RIO2/3
  processor
• Compatible with legacy technology
• Legacy technology for almost all VME modules
• Except new timing receiver module designed for
  LHC
• Experience during commissioning
• Successful smooth operation from the start-up

10
Front End Software

• New Front-End Software Architecture
• Complete framework for Real-Time software
  development
• Same device software development for all
  accelerators
• Compliant with the legacy infrastructure kept for
  certain devices
• Experience during commissioning
• Framework proved efficient and adequate
• Major progress compared to old FE software
  environment
• Main functionalities in place and validated
• Late delivery of some features
• Lack of stability reliability in the
  operational environment

FR1.2-50
11
Application Software
TU1.3-50 TH1.4-80

• Adaptation of new LHC Applications to LEIR
• Developed for LHC, to be customized for LEIR
• Replace existing X/Motif applications suitable to
  Operation
• Experience during development
• Adaptation to LEIR relatively easy thanks to a
  good design
• Adaptation made LHC Applications more complete
• Experience during commissioning
• More advanced functionality
• Not all old functionality yet available -
  ergonomically not fully satisfactory

12

Application Software - contd

• Java re-write of legacy generic applications
• Same functionality but completely new
  implementation
• Integrate both new and legacy equipment below
• Experience during development
• New implementation profited from years of
  experience with old X/Motif version ? Better
  design and implementation
• Tough implementation task because new underlying
  controls infrastructure was unreliable and kept
  changing
• Experience during commissioning
• No added value for users (compared to old
  proven X/Motif version) ? Perceived as a step
  back because less mature

13
Timing Sequencing

• Integration in the general timing system driving
  all CERN accelerators
• Enhancements to cover specific operation modes
• As stand alone mode (N0 extraction from LEIR)
• Extensions made compliant with LHC
• Experience during commissioning
• Successful and smooth operation from the start-up
• Confirmation of selected infrastructure
• Validation of enhancements in view of LHC
  

14
Experience during CommissioningCultural
perspective

• Unfavorable Operation context
• All LEIR operators from a unique culture
• No LEIR operator participation in the
  applications development
• Some reluctance from OP to adopt new tools
  habits
• Fruitful experience for Controls Operation
• Cross pollination between new and legacy controls
  
• Collaboration is an excellent catalyst for the
  merging of the 2 departments
• Valuable support to Operation
• Through one dedicated CO link person
• Prevents OP from performing complex diagnostics
• Helps OP to gain and keep confidence

15
Conclusion

• An anticipated challenge
• Both cultural and technical
• A successful test-bed for numerous new systems
• Sped up the elaboration of standard
  infrastructures
• Consolidation of present controls is crucial
• In terms of reliability and stability
• To regain full confidence of Operation