# Presentation: 215681

## EPICS at Fermilab:Not just D0 anymore -  Cavities, Cavities, Cavities

- Geoff Savage for the Dzero and ILCTA controls groups
- Wed June 14, 2006
- EPICS Collaboration Meeting

## Current EPICS Projects

- Run II Experiments
- D0 Controls.
- ILC Test Accelerator (ILCTA) @ FNAL
- Cavity testing in three facilities, maybe a fourth
- Horizontal Test Facility/Coupler conditioning (MDB)
- Run tests in August 2006
- Vertical Test Facility (IB1)
- Getting started
- Beam test (NML) using photoinjector currently at A0
- Preparing facility - cryo installed at the end of 2007
- Other
- Proton Driver – EPICS only control system
- Nova – Seriously evaluating EPICS as control system for DAQ. Maybe also for controls itself?

- EPICS Collaboration Mtg

- 6/14/2006

## D0 Detector

- Increased luminosity in Run IIb
- Just finished detector upgrade
- Silicon layer 0
- Enhanced triggering systems
- Goals for controls
- Support new field busses
- Remove 68k processors from system
- Move to EPICS 3.14.8.2
- Controls - all EPICS all the time
- DAQ controls are independent

- EPICS Collaboration Mtg

- 6/14/2006

## D0 Controls

- Two new field buses
- CANbus driver wrapped in ASYN
- TPMC816 - dual channel PMC CANbus module
- Implements limited CANbus feature set
- Raw ethernet driver in ASYN
- Linux IOC connected via fiber to remote crate
- Trying to get to 3.14.8.2
- Tested but not deployed
- Currently using 3.14.6 and 3.13.4
- MVME5500 processors
- Remove remaining 68k processors ~ 25
- Some problems - similar experiences?

- EPICS Collaboration Mtg

- 6/14/2006

## ILCTA Controls Systems

- ACNET (FNAL)
- Accelerator Division
- Drivers/interfaces for FNAL devices already written and in use at Fermilab in ILCTA  (HRM)
- EPICS (ANL)
- Cryogenics interface for MDB and NML.
- Maybe for IB1, but have large IFIX base.
- IB1 controls system
- At least partial (maybe complete) control system at MDB
- DOOCS (DESY)
- LLRF (Simcon 2.1/3.1 boards) supplied by DESY
- EPICS driver written, being debugged
- Digitizers supplied by DESY
- A0 is dominated by DOOCS devices.
- Photoinjector will move to NML being controlled by DOOCS

- EPICS Collaboration Mtg

- 6/14/2006

## Which Control System? and then Some

- ILCTA review committee in FY05 recommended picking one
- all were considered considered capable of meeting technical requirements
- Recommended DOOCS or EPICS with a slight preference for EPICS because more technical help available
- Have not yet achieved this (LLRF controller is DOOCS)
- IFIX (Intellution) / APACS - Cryo
- Matlab and LabView
- Engineering development tools, not control systems
- Try to limit usage to analysis

- EPICS Collaboration Mtg

- 6/14/2006

## FNAL EPICS Personnel

- About 10 people from all over the lab – most are new to EPICS < 6 months experience.
- Accelerator division
- Sharon Lackey, Dennis Nicklaus, Paul Joireman, Kevin Martin
- Technical division
- Dennis Shpakov
- Particle physics division
- Vladimir Sirotenkov, Fritz Bartlett, Geoff Savage
- Computing division
- Ron Rechenmacher (DOOCS), Luciano Piccoli (DOOCS), Kurt Biery (Nova)

- EPICS Collaboration Mtg

- 6/14/2006

## LLRF

**LLRF**

**Modulator**

**Cryogenics**

**Klystron Interlocks**

**PLC**

- ILCTA MDB - Paul Joireman

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
From a document by Paul Joireman in docdb.

## EPICS Pieces

- Tools
- EDM
- Channel archiver
- Sequencer
- Java CA
- vxWorks IOC
- vxWorks VME device support
- vxWorks symbolic device support
- User written C/C++

- Linux IOC
- Driver called from device support
- Commercial driver wrapped in ASYN
- Windows IOC
- OPC device support from BESSY

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
This is from a talk Dennis Nicklaus gave.
It would be good to summarize the work done on one page and then go into more detail in the following slides.  To be filled out once the talk is more polished.

## Modulator Control Kevin Martin

- Call the existing PEP driver from device support.

- Modulator Control Kevin Martin

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
Brief description?
SMTF Modulator Control application.

EPICS version?    R3.14.8.2
Target hardware?  Intel desktop
Target OS?        Linux

Technical description?
The SMTF Modulators have an embedded micro-processor running a RTOS. Rather then run an EPICS IOC on this embedded micro-processor we decided the run the IOC on a LINUX host and communicate with the embedded micro-processor via the network using custom device support. This is working well and we have a first version of our EDM based application running.

## Klystron InterlocksDennis Nicklaus

-  EDM screen shot - edit mode
-  Database records use VME device support from vxWorks
-  EPICS R3.14.7
-  MVME2434
-  VxWorks 5.4

- Klystron InterlocksDennis Nicklaus

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
Dennis Nicklaus

## ADC ReadoutPaul Joireman

- For klystron interlocks
- 12 channel 16-bit VME module
- EPICS R3.14.7, vxWorks 5.4, MVME 2434
- Control/monitor with vme device support
- Data readout into processor memory and initialization with C++ driver
- Access data with EPICS vxWorks symbolic device support

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
Paul Joireman

Brief Desrcription:
    Read and write values from 12 channel 16-bit A/D card for  
Klystron interlock crate for CC2 at NM.

EPICS version?    R3.14.7
Target hardware?  MVME 2434 - VME single board computer (PPC based)
Target OS?        VxWorks 5.4

Technical description?

We are using a VME crate with several locally developed VME boards to  
serve as a hardware
protection module for the Klystron used to drive Capture Cavity 2  
(CC2) at the New Meson
laboratory.     Within the crate is a 12 channel 16-bit VME digitizer  
board, which will capture
the signals from various detectors on a pulse by pulse basis.  I have  
developed an EPICS database
to read from and write to the digitizer board.    Initial  
configuration of the card and readout of
waveform data required the development of a low level driver, this  
was done in C++.   I am now
in the process of making the connection between a set of waveform  
records for each digitizer
channel and the data extracted from the card using the low level driver.

## LLRF - Accelerator DivisionDennis Nicklaus and Sharon Lackey

- SimCon 3.1
- From DESY with DOOCS driver
- Controlled from Force processor
- Matlab interface - abandoned
- Database records use vxWorks VME device support
- EPICS R3.14.7, VxWorks 5.4, MVME2434
- Create user interface with EPICS Display Manager (EDM)

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
Dennis Nicklaus

Simcon 3.1 card
Matlab and DOOCs interfaces working
No more Moto/Force CPU-56’s
EPICS work proceeding on 2-3 fronts:
“Elegant” IID solution with Linux/Solaris (Pucyk)
“Brute force” addr. decode via VxWorks (Nicklaus)
EPICS access through Matlab (Nicklaus, abandon!)
EPICS replica of Matlab GUI done (Lackey)

## SimCon 3.1 EDM GUI

- EPICS Collaboration Mtg

- 6/14/2006

## LLRF - Technical DivisionDennis Shpakov

- Learn how the SimCon 3.1 card works
- Use C functions to perform initialization
- Control/Monitor with VME device support
- EPICS R3.14.8.2, MVME5500, vxWorks 6.1

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
Dennis Shpakov

We are considering using EPICS for the High Intermediate Frequency  
LLRF card, but the project is not yet at the stage where one would  
start working on the control system. In fact, the hardware path has  
not yet been decided upon. I do have a test setup for the SimCon 3.1  
card and I am trying to reproduce what Dennis Nicklaus has. The  
target is mvme5500/vxworks6.1, epics version v3_14_8_f1 from fnkits  
(I put it there myself, the only change from the base version was a  
correct reference to the windriver_gpp product directory).

## PLC CommunicationGeoff Savage

- AutomationDirect DirectLogic PLCs
- Use for general purpose I/O and PLC logic
- Implement network communication through add-on ECOM module
- DirectNET over ethernet protocol
- Serial communication requires more infrastructure
- Wrap the supplied linux driver in the ASYN framework
- Use ASYN device support - devEpics
- Linux desktop, EPICS R3.14.8.2

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
Geoff Savage

Brief description?
Read and write values from AutomationDirect PLCs at SMTF.

EPICS version?    R3.14.8.2
Target hardware?  Intel desktop
Target OS?        Linux

Technical description?
We are using a DL405 PLC with an H4-ECOM (ethernet communication)  
module.  The H4-ECOM communicates via ethernet using the DirectNet  
protocol.   The ethernet version of the DirectNet protocol is  
different than the serial version of the DirectNet protocol so I  
couldn't use the directNetAsyn support which does support the  
serial protocol.  Instead I retrieved the Linux version of the HEI  
driver which supports communication with ECOM modules using CCM  
(DirectNet) from Host Engineering, hosteng.com.  I have wrapped the  
HEI driver in the ASYN framework for integration into EPICS.   
Currently I can readback values and arrays of values.  The next  
step is to write values with the driver and configure EPCICS  
records to view values.

## Conditioning ControlDennis Nicklaus

- Use the sequencer to control the cavity conditioning sequence
- Requires all the systems to be accessible via EPICS
- EPICS is a “glue” that connects systems from different groups

- EPICS Collaboration Mtg

- 6/14/2006

## Gateways to Other Systems

- EPICS IOC that would be a gateway to DOOCS - Ron Rechenmacher
- DOOCS is already a CA client (R3.12?)
- ACNET-EPICS - Vladimir Sirotenko
- IFIX-EPICS - Vladimir Sirotenko at D0
- IFIX/APACS-EPICS through OPC - Vladimir Sirotenko
- Labview - EPICS community

- EPICS Collaboration Mtg

- 6/14/2006

**Notes:**
Ron Rechenmacher
I'm planning to doing an EPICS IOC that would be a gateway to DOOCS.

## Cryogenic SystemsVladimir Sirotenko and Sharon Lackey

- Modbus

- CA

- EPICS-OPC device support from BESSY

- EPICS Collaboration Mtg

- 6/14/2006

##  Base EDM page for ILCTA cryo systems

-  Base EDM page for ILCTA cryo systems
-  Looks like existing ACNET GUI
-  Sharon Lackey

- EPICS Collaboration Mtg

- 6/14/2006

## Slide 21

- EPICS Collaboration Mtg

- 6/14/2006

## Slide 22

- EPICS Collaboration Mtg

- 6/14/2006

##  Java parameter page

-  Java parameter page
-  ACNET and CA communication

- EPICS Collaboration Mtg

- 6/14/2006

## Channel ArchiverVladimir Sirotenko

- Channel ArchiverVladimir Sirotenko

- EPICS Collaboration Mtg

- 6/14/2006

## Slide 25

- EPICS Collaboration Mtg

- 6/14/2006

## Some comments

- From Margaret Votava
- ILCTA controls leader
- Also working on ILC costing
- Presented to MICE (Muon Cooling) collaboration
- No modifications on my part

- EPICS Collaboration Mtg

- 6/14/2006

## What is DOOCS

- Distributed Object Oriented Control System http://tesla.desy.de/doocs/doocs.html
- Written by a small team at DESY over the last decade
- Control system for TTF and most likely choice for XFEL
- Cyro system is EPICS
- Features
- Newer than EPICS and therefore makes more modern architecture choices
- Uses RPC for communication path
- Devices are objects
- Includes DAQ support
- Includes a finite state machine
- Can talk to EPICS iocs
- Drawbacks
- Only user group is DESY, other than then ILCTA
- Support from experts is limited – not nearly as responsive as the EPICS community
- Not well packaged for development outside of DESY
- Much work done here and is getting better
- EPICS can’t talk to DOOCS devices (but this is a problem with EPICS ...)

- EPICS Collaboration Mtg

- 6/14/2006

## EPICS Development Issues	

- Development is done by a collaboration of users:
- ANL (primarily) supports EPICS base (ie, front end support)
- Extensions (applications) are provided as needed – alarming, GUI support, archiving, etc
- No standards for package, quality control, support, etc for extensions
- Multiple extensions with same functionality
- GUI support is primary example
- Larger scale developments/enhancements have no resources
- Have a large todo list, but no organized/funded/supported todo-ers
- ANL is committed to APS support
- Several items on todo list are to implement features already available in DOOCS

- EPICS Collaboration Mtg

- 6/14/2006

## ILC Controls Digression

- Currently imagined (at least costed) as taking existing controls system as base with significant modificiation.
- EPICS and DOOCS are obvious candidates
- Way too early to make this decision
- Still may decide to write from scratch
- Global controls group (excluding LLRF) consists primarily of people from ANL, FNAL, SLAC, and a little from DESY
- add KEK and more DESY for LLRF
- ANL and SLAC are providing personnel help for ILCTA
- DESY providing equipment for ILCTA

- EPICS Collaboration Mtg

- 6/14/2006

## ILC Tests Areas				

- IB1
- Will be EPICS, but using the DESY LLRF board
- Cryo either IFIX or EPICS
- Mostly TD Personnel
- MDB
- Will most likely be all EPICS
- Cryo is EPICS
- Geoff working on EPICS PLC klystron interlock driver.
- Still using old HRMs speaking classic protocol (no EPICS interface, but a DOOCS one)
- Mostly same software personnel as proton driver (i.e., epics)
- NML – Under design/construction
- Will take photoinjector from A0 => photoinjector control will be DOOCS for at least the short term (next year or two)
- Cryo will be EPICS (modelled after MDB)
- Evaluating possibility of an EPICS -> DOOCS interface so applications can be either one.
- It’s an R&D playground in addition to a facility to test cryostat

- EPICS Collaboration Mtg

- 6/14/2006