1 / 15

EPICS and CLS

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

cain
Download Presentation

EPICS and CLS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EPICS and CLS September 18, 2009

  2. 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)

  3. 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

  4. Common Tools • EPICS • edm • matlab • gtk+ based library (no longer supported) • Qt+EPICS widget library • Less Common: • Root • Python • spec

  5. Development See 7.1.39.1 rev ??? Using css2400-103 for development • makeBaseApp.pl –t iocmyproject • makeBaseApp.pl –i –t iociocname Development Details

  6. Deployment • /iocApps/SYSTEM/IOCNAME/APPNAME • /iocApps/SYSTEM/APPNAME (symbolic link) • /etc/init.d startup script SYSTEM – e.g. 06B1_1_SXRMB_BL IOCNAME – e.g. IOC1606-022 APPNAME – e.g. Motors In general the bin, db, dbd, and iocBoot directories are installed with required files

  7. 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

  8. Deployment - libraries Screens NAME.tpl OPI NAME.tpl templates NAME.tpl NAME.db NAME_morestuff.db dbd NAME.dbd

  9. 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

  10. Documentation! • Documentation Procedure – \\canopus\common\Library_and_Reference\Document_Control • Also available from http://teamsite under “Documents -> Approved Documents” • Wiki (http://wiki.clsi.ca)

  11. What is EPICS? • EPICS Overview

  12. What is Channel Access? • Channel Access is the Software Bus for EPICS Application communication • Channel Access

  13. 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)

  14. Record Processing • Records, Devices, and Drivers • Databases, Part 1

  15. Record Types • Databases, Part 2

More Related