controls & monitoring overview j. leaver 03/06/2009

21
Controls & Monitoring Overview J. Leaver 03/06/2009

Upload: neil-price

Post on 18-Jan-2016

217 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Controls & Monitoring Overview J. Leaver 03/06/2009

Controls & Monitoring Overview

J. Leaver

03/06/2009

Page 2: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 2

Outline

• Overview of MICE

– Systems requiring control & monitoring

• Outline of C&M framework

– EPICS

Page 3: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 3

MICE Layout

Q 1

Q 3

Q 2

Q 4 Q 5 Q 6 Q 7 Q 8 Q 9

D ipole 1

D ipole 2

P ion D ecaySolenoid

Target

FN AL BPM 2

FN AL BPM 1 TO F 0

C KO Va C KO Vb TO F 1

D iffuser

Spectrom eterSolenoid 1

Tracker 1

Spectrom eterSolenoid 2

Tracker 2

TO F 2

KL C alorim eter

R F C avity 1 R F C avity 2

C ouplingC oil 1

C ouplingC oil 2

H ydrogenAbsorber 1

H ydrogenAbsorber 2

H ydrogenAbsorber 3

Focus C oil 1 Focus C oil 2 Focus C oil 3

E lectron M uonR anger

Page 4: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 4

Q 1

Q 3

Q 2

Q 4 Q 5 Q 6 Q 7 Q 8 Q 9

D ipole 1

D ipole 2

P ion D ecaySolenoid

Target

Required C&M Systems: Beamline

Page 5: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 5

Required C&M Systems: Beamline

• Target

– Drive (PSU, extraction, temperature monitoring, etc.)

– Controller (actuation enable, dip depth, timing, etc.)

– Beam Loss (Sector 7/8, total, c.f. Target position)

• Beamline Magnets [Q1-Q9, D1-D2] (PSU)

• Pion Decay Solenoid (PSU, cryo)

Page 6: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 6

Required C&M Systems: Instrumentation

FN AL BPM 2

FN AL BPM 1 TO F 0

C KO Va C KO Vb TO F 1

D iffuser

Spectrom eterSolenoid 1

Tracker 1

Spectrom eterSolenoid 2

Tracker 2

TO F 2

KL C alorim eter

E lectron M uonR anger

Page 7: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 7

Required C&M Systems: Instrumentation

• Fermilab Beam Profile Monitors (PMT, sensor temperature)

• Time of Flight System (PMT HV)

• Cherenkov System (PMT HV, temperature, humidity)

• Diffuser (motor control, disc position)

• Tracker

– Spectrometer Solenoid (PSU, cryo)

– Magnetic Field Probes (B-field, sensor temperature)

– AFEIIts (readout configuration & control, temperature monitoring)

– AFEIIt Infrastructure (PSU, cryo)

• Calorimeter System

– KL Calorimeter (PMT HV)

– Electron Muon Ranger (PMT HV)

Page 8: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 8

Required C&M Systems: Cooling Channel

R F C avity 1 R F C avity 2

C ouplingC oil 1

C ouplingC oil 2

H ydrogenAbsorber 1

H ydrogenAbsorber 2

H ydrogenAbsorber 3

Focus C oil 1 Focus C oil 2 Focus C oil 3

Page 9: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 9

Required C&M Systems: Cooling Channel

• Hydrogen Absorbers

– Focus Coils (PSU, cryo)

– Hydrogen System (PSU, pumps, valves, vacuum, cryo)

• RF Cavities

– Coupling Coils (PSU, cryo)

– RF System (PSU, amplifiers, B-field probes, feedback)

Page 10: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 10

Required C&M Systems: Auxiliary

• DATE Status

– Run state of global DAQ system (armed, taking data, idle, error, etc.)

• Network Status

– State of each PC on the DAQ & Control Networks (link up/down, correct ID, necessary services running)

Page 11: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 11

Required C&M System Features

• Reliability

– Need months/years of uninterrupted runtime

• No C&M = no experiment

– Need effective help & support when problems occur

• Plus ability to resolve issues without waiting for vendor support (availability of source code)

• Scalability

– Facility to add new systems to existing setup with minimal development overheads/performance impact

Page 12: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 12

Required C&M System Features

• Ease of use

– But extensible for arbitrarily complex custom systems

• Error reporting

– Clear alarms when fault conditions occur

• Data archiving

– Permanent & accessible record of all significant monitoring parameters

Page 13: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 13

EPICS

• Collaboration

– World wide collaboration sharing designs, software & expertise for implementing large-scale control systems

• Control System Architecture

– Client/server model with efficient communication protocol (Channel Access) for passing data

– Distributed real-time database of machine values

• Software Toolkit

– Collection of software tools which can be integrated to provide a comprehensive & scalable control system

Page 14: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 14

Why Use EPICS for MICE?

• Free Open Source software

• Mature packages

– Stable, robust infrastructure

• Widely used in scientific laboratories & industry

– Significant expertise available

– Good support/documentation

• Collaboration members with prior EPICS experience (e.g. Fermilab → DØ)

• Many tools available for common C&M tasks

– (Relatively) easy to develop new applications

Page 15: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 15

EPICS Fundamentals

• Each control/status parameter represented by a ‘Process Variable’ (PV)

– PV: Named piece of data (e.g. temperature) with a set of attributes (e.g. safe operating limits)

• Channel Access (CA) servers provide access to PVs

• CA clients read/write PVs to perform control & monitoring tasks

• Network-based, distributed system

– PVs can be spread over multiple servers, accessed transparently over network

Network

Channel Access Client

Control Application Monitoring Application

Process Variables

Channel Access Client

Channel Access Server Channel Access Server Channel Access Server

Process VariablesProcess Variables

Page 16: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 16

EPICS Servers

• EPICS servers typically connect to hardware

– PVs often correspond directly to physical device states or control settings

• 2 types of server

– Input/Output Controller (IOC)

– Portable CA server

– Approx. equal numbers of each type used in MICE

IOCIOC Channel Access Server

- Channel Access- Database- Device / Driver Support

Network

Hardware

PortablePortable Channel Access Server

- Channel Access

Custom Code

Hardware

OR

Page 17: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 17

EPICS Servers

• System configuration & hardware IO connections defined by PV record database

• Existing driver support for many devices & standard communication interfaces

• Server creation often a matter of database configuration rather than software development

• Runs on vxWorks/RTEMS boards, or PCs (Linux, Win, Mac, etc.)

• Suitable for most ‘standard’ hardware systems

IOCIOC Channel Access Server

- Channel Access- Database- Device / Driver Support

Network

Hardware

Portable Channel Access Server

- Channel Access

Custom Code

Hardware

Page 18: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 18

EPICS Servers

• C++ library containing CA & PV framework

• Use with arbitrary hardware access code to produce fully custom servers

• MICE wrapper framework greatly simplifies creation of portable servers

• Runs on PCs (Linux, Win, Mac, etc.)

• Suitable for non-standard hardware & complex software architectures

Network

PortablePortable Channel Access Server

- Channel Access

Custom Code

Hardware

IOC Channel Access Server

- Channel Access- Database- Device / Driver Support

Hardware

Page 19: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 19

EPICS Clients

• Clients provide (user) interface to C&M system

– Abstracted from hardware → clients only need to access PVs

• Packages available to facilitate building control/monitoring displays

– Extensible Display Manager (EDM), Motif Editor and Display Manager (MEDM), etc.

– Interactive graphical environments enabling PVs to be attached to control/display widgets

– No low-level programming required

– ~60% of MICE C&M systems use EDM

Page 20: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 20

EPICS Clients

• Not limited to standard GUI builders - CA bindings exist for many languages/tools

– C/C++, Java, Matlab, Perl, Python, LabVIEW, etc.

– ~30% of MICE C&M systems use custom C++ wrapper, with QT GUIs

• Well-established client tools provide core C&M functionality

– Alarm Handler, Channel Archiver, etc.

– Minimises required infrastructure development effort

Page 21: Controls & Monitoring Overview J. Leaver 03/06/2009

04/21/23 Imperial College 21

C&M Systems OverviewSystem Owner EPICS Developer EPICS Status

Target: Drive Paul Smith; Paul Hodgeson; Chris Booth (UOS) Adrian Oates; Graham Cox (DL) Complete for current Target, but additions required for upgraded system.

Target: Controller Paul Smith (UOS); James Leaver (IC) James Leaver (IC) Not yet commenced.Target: Beam Loss Paul Smith; Paul Hodgeson (UOS); James Leaver (IC) Pierrick Hanlet (IIT) Functionally complete.Beamline Magnets Martin Hughes (RAL) Peter Owens (DL) Complete, with support requirements.Pion Decay Solenoid Mike Courthold (RAL) Adrian Oates; Graham Cox (DL) Complete, with support requirements.FNAL BPMs Alan Bross (FNAL) James Leaver (IC) Complete.TOF Maurizio Bonesini (INFN) Unknown Unallocated.CKOV Lucien Cremaldi; David Sanders (OLEMISS) Pierrick Hanlet (IIT) Not yet commenced.Diffuser Wing Lau (OU) Unknown Unallocated.Tracker: Spectrometer Solenoids Steve Virostek (LBNL) Adrian Oates; Graham Cox (DL) DL have completed most of the design drawings,

require ~£18K of capital and 0.4 man years of effort to finish the project. Currently finalising allocation of funds.

Tracker: B-Field Probes Frank Filthaut (RUN) Frank Filthaut (RUN) Functionally complete.Tracker: AFEIIts Alan Bross (FNAL) James Leaver (IC); Jean-Sebastien

Graulich (UNIGE)Complete, but integration with DATE to be finalised.

Tracker: AFEIIt Infrastructure Alan Bross (FNAL) James Leaver (IC) Thus far, only Wiener PSUs have been identified. Not yet commenced. May have additional requirements.

Calorimeter: KL Calorimeter Virgilio Chimenti (INFN) Unknown Unallocated.Calorimeter: Electron Muon Ranger A. Blondel; J-S Graulich; V. Verguilov; F. Masciocchi;

L. Nicola; R. Bloch; P. Béné; F. Cadoux (UNIGE)Unknown Unallocated.

H2 Absorbers: Focus Coils Wing Lau (OU) Pierrick Hanlet (IIT) Not yet commenced, manpower unconfirmed.H2 Absorbers: Hydrogen System Yury Ivanyushenkov; Tom Bradshaw (RAL) Adrian Oates; Graham Cox (DL) DL have acquired necessary safety training and have

started evaluating PLC systems. Early stages of development, but fully budgeted for by Tom Bradshaw.

RF Cavities: Coupling Coils Derun Li; Steve Virostek (LBNL) Pierrick Hanlet (IIT) Not yet commenced, manpower unconfirmed.RF Cavities: RF System Andy Moss (ASTeC) Dimity Tettyleman (LBNL); Adrian

Oates; Graham Cox (DL)Early stages of development, but fully budgeted/accounted for by Andy Moss.

DATE Status Jean-Sebastien Graulich (UNIGE) James Leaver (IC); Jean-Sebastien Graulich (UNIGE)

EPICS server + client GUI complete, but client-side integration with DATE required.

Network Status Anyone with a PC/IOC in the MLCR/Hall James Leaver (IC) Prototype complete, requires increased functionality.Infrastructure

EPICS Alarm Handler Pierrick Hanlet (IIT) Pierrick Hanlet (IIT) Initial version complete (ongoing work).EPICS Channel Archiver Pierrick Hanlet (IIT) Pierrick Hanlet (IIT) Initial version complete (ongoing work).Client application wrapper GUI Pierrick Hanlet (IIT) Pierrick Hanlet (IIT) Not yet commenced.Remote monitoring Pierrick Hanlet (IIT) Pierrick Hanlet (IIT) Not yet commenced.Configuration database David Forrest (UofG) Pierrick Hanlet (IIT); James Leaver

(IC)Not yet commenced.