Epics and cls
This presentation is the property of its rightful owner.
Sponsored Links
1 / 15

EPICS and CLS PowerPoint PPT Presentation


  • 84 Views
  • Uploaded on
  • Presentation posted in: General

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

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Epics and cls

EPICS and CLS

September 18, 2009


Controls environment

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 environment1

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


Common tools

Common Tools

  • EPICS

  • edm

  • matlab

  • gtk+ based library (no longer supported)

  • Qt+EPICS widget library

  • Less Common:

    • Root

    • Python

    • spec


  • Development

    Development

    See 7.1.39.1 rev ???

    Using css2400-103 for development

    • makeBaseApp.pl –t iocmyproject

    • makeBaseApp.pl –i –t iociocname

      Development Details


    Deployment

    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


    Deployment libraries

    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


    Deployment libraries1

    Deployment - libraries

    Screens

    NAME.tpl

    OPI

    NAME.tpl

    templates

    NAME.tpl

    NAME.db

    NAME_morestuff.db

    dbd

    NAME.dbd


    Deployment opi

    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


    Documentation

    Documentation!

    • Documentation Procedure – \\canopus\common\Library_and_Reference\Document_Control

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

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


    What is epics

    What is EPICS?

    • EPICS Overview


    What is channel access

    What is Channel Access?

    • Channel Access is the Software Bus for EPICS Application communication

    • Channel Access


    Records and fields

    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)


    Record processing

    Record Processing

    • Records, Devices, and Drivers

    • Databases, Part 1


    Record types

    Record Types

    • Databases, Part 2


  • Login