Top Banner
www.lightsource.ca www.lightsource.ca Main Bullet #1 Main Bullet #2 Main Bullet #3 EPICS and CLS September 18, 2009
15

EPICS and CLS

Feb 25, 2016

Download

Documents

Cain

EPICS and CLS. September 18, 2009. Controls Environment. Common Target Processors Intel x86 (RH 7.2 for VME apps, SL 4.x for OPI) Mxscaleb ( Moxa 7408, 8 serial processors, Linux) Motorola 68360 25MHz (EROC). Controls Environment. Operating Systems Linux Red Hat 7.2 - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: EPICS and CLS

www.lightsource.cawww.lightsource.ca

Main Bullet #1 Main Bullet #2 Main Bullet #3

EPICS and CLS

September 18, 2009

Page 2: EPICS and CLS

www.lightsource.ca

Controls Environment Common Target Processors

Intel x86 (RH 7.2 for VME apps, SL 4.x for OPI) Mxscaleb (Moxa 7408, 8 serial processors, Linux) Motorola 68360 25MHz (EROC)

Page 3: EPICS and CLS

www.lightsource.ca

Controls Environment Operating Systems

Linux Red Hat 7.2 Scientific Linux 4.X Moxa Embedded Linux RTEMS (Motorola 68xxx and Intel x86) Windows XP with Cygwin

Page 4: EPICS and CLS

www.lightsource.ca

Common Tools EPICS edm matlab gtk+ based library (no longer supported) Qt+EPICS widget library

Less Common: Root Python spec

Page 5: EPICS and CLS

www.lightsource.ca

Development

See 7.1.39.1 rev ???Using css2400-103 for development makeBaseApp.pl –t ioc myproject makeBaseApp.pl –i –t ioc iocnameDevelopment Details

Page 6: EPICS and CLS

www.lightsource.ca

Deployment /iocApps/SYSTEM/IOCNAME/APPNAME /iocApps/SYSTEM/APPNAME (symbolic link) /etc/init.d startup scriptSYSTEM – e.g. 06B1_1_SXRMB_BLIOCNAME – e.g. IOC1606-022APPNAME – e.g. MotorsIn general the bin, db, dbd, and iocBoot

directories are installed with required files

Page 7: EPICS and CLS

www.lightsource.ca

Deployment - libraries use $EPICS_LOCAL/drivers when installing

Library_name

Library_version

lib

Linux-x86

libNAME.a

libNAME.so.X.Y

libNAME.so.X.Y.Z

libNAME.so

include

NAME.h

Page 8: EPICS and CLS

www.lightsource.ca

Deployment - libraries

templates

NAME.tpl

NAME.db

NAME_morestuff.db

dbd

NAME.dbd

Screens

OPI

NAME.tpl

NAME.tpl

Page 9: EPICS and CLS

www.lightsource.ca

Deployment - OPI /home/control – for Linac/BR1/SR1 operation

(beware of DEVELOPMENT vs. PRODUCTION) /home/beamline – for common beamline

applications and libraries /home/hxma (e.g.) – for applications specific

to the given beamline

Page 10: EPICS and CLS

www.lightsource.ca

Documentation! Documentation Procedure –

\\canopus\common\Library_and_Reference\Document_Control

Also available from http://teamsite under “Documents -> Approved Documents”

Wiki (http://wiki.clsi.ca)

Page 11: EPICS and CLS

www.lightsource.ca

What is EPICS? EPICS Overview

Page 12: EPICS and CLS

www.lightsource.ca

What is Channel Access? Channel Access is the Software Bus for EPICS

Application communication Channel Access

Page 13: EPICS and CLS

www.lightsource.ca

Records and Fields Records are common definitions of a collection

of fields. New record types are rarely developed at the CLS

In the simplest case, a Field is the minimum Channel Access data communicated

Device drivers are designed to process a record when a field updates (output) or when hardware values have been read (input)

Page 15: EPICS and CLS

www.lightsource.ca

Record Types Databases, Part 2