1. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu EPICS and EDM Overview Lecture 1 Matt Boyes

2. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu Class Outline Lecture 1 EPICS Channel Access What is a PV LCLS Network Details CVS Comments EDM Files EPICS LCLS Environment Setup Lecture 2 Basics of creating EDM displays Lecture 3 Advance items EDM Lab Exercises

3. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu Channel Access Channel Access protocol is the way EPICS communicate. Process Variable (PV) data is transferred between Servers and Clients. CA Servers (IOCs) IOCS (Distributed) Where PVs live Database Subroutines Sequence Clients EDM Displays StripTool Probe Channel Archiver Matlab etc

4. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu EPICS CA Overview ClientStripToolProbeEDMMatlabArchiver Server IOC MeterPower SupplyCamera SIOC Channel Access Based On Getting Started with EPICS Lecture Series “Introduction to Channel Access Clients” Kenneth Evans, Jr.

5. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu Search and Connect Procedure ClientStripToolProbeEDMMatlabArchiver Server IOC MeterPower SupplyCamera IOC 3. TCP Connection Let’s talk ! 1.UDP Broadcast Sequence Who has it ? Check 2. UDP Reply I have it ! IOC Based On Getting Started with EPICS Lecture Series “Introduction to Channel Access Clients” Kenneth Evans, Jr.

6. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu What is EPICS? Process Variable A Process Variable (PV) is a named piece of data associated with the machine (e.g. status, readback, setpoint, parameter) Examples of PV names and values: S1:VAC:reading 3.2e-08 torr LINAC:BPM4:xPosition -0.323 mm BOOSTER:gateValvePosition ‘OPEN’ S3:DIPOLE:PS:setPoint 123.4 Amps APS:Mode ‘Stored Beam’ BL3:HISTOGRAM {3, 8, 1, 2, 56, 44, 32, 43, 3, 5, 1} Getting Started with EPICS Lecture Series Introductory Session I Ned Arnold

7. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu What is EPICS? Getting Started with EPICS Lecture Series Introductory Session I Ned Arnold A Process Variable is a named piece of data with a set of attributes Examples of Attributes: Alarm Severity (e.g. NO_ALARM, MINOR, MAJOR, INVALID) Alarm Status (e.g. LOW, HI, LOLO, HIHI, READ_error) Timestamp Number of elements (array) Normal Operating Range Control Limits Engineering Unit Designation (e.g. degrees, mm, MW)

8. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu

9. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu Important Network Details LCLS DEV clients can not access CA Network PVs (and vise versa) LCLS DMZ clients have read only access to CA Network PVs EPICS Environment automatically setup for group accounts on CA Network Computers

10. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu Comments on CVS CVS is the LCLS Version Control Keeps track of files changes No release scripts yet to move files from DEV to Prod Developers need to manually update DEV and Prod files. Need to be careful when releasing Only System Engineers should release files for their subsystem Will avoid conflicts System Engineers can merge changes Non System Engineers Should: 1.CVS Check out or copy files locally to users sandbox 2.Make change/fixes, Test 3.Contact System Engineer to release and merge into CVS

11. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu EDM File Locations Paths different on dev and productions machines Use $EDM environment variable LCLSHOME Files are in “lcls” directory Subsystems files not in LCLSHOME frame have their own directory EDM always checks path where EDM was started from first before check $EDM for display files Makes development easier

12. EPICS and EDM Overview 03 October 2008 Matt Boyes mboyes@slac.stanford.edu User Environment Setup epicsReset.bash Must be in bash shell Channel Access settings EDM configuration and display files Many more items LCLS EPICS Development Environment Setup on Linux Login to lcls-dev2 with $ ssh -X -Y username@lcls-dev2.slac.stanford.edu Find out what shell you are running by typing echo $SHELL. Your shell will be either tcsh or bash. ex: $ echo $SHELL /bin/bash (I am running bash.) If you are using tcsh, type this command to enter the bash shell before proceeding: $ bash If you are using bash, type this command: $ source /afs/slac/g/lcls/epics/setup/epicsReset.bash As an alternative you can skip the above step and instead copy the following file to your home directory. This file includes the command to source the setup script listed in the above. The advantage is that this script is executed automatically when you type bash. cp ~luchini/.bashrc.