EPICS : input / output controller (IOC) application developer's guide. EPICS release 3.12 specific documentation.[Experimental Physics and Industrial Control System]

Abstract

This document describes the core software that resides in an Input/Output Controller (IOC), one of the major components of EPICS. It is intended for anyone developing EPICS IOC databases and/or new record/device/driver support. The plan of the book is: EPICS Overview An overview of EPICS is presented, showing how the IOC software fits into EPICS. This is the only chapter that discusses OPI software and Channel Access rather than just IOC related topics. Database Locking, Scanning, and Processing Overview of three closely related IOC concepts. These concepts are at the heart of what constitutes an EPICS IOC. Chapter 1: EPICS Overview Getting Started 12 EPICS IOC Application Developer's Guide Another way to create the breakpoint table is to include the following definition in a Makefile.Vx: BPTS += bptXXX.dbd NOTE: This requires the naming convention that all data tables are of the form bpt<name>.data and a breakpoint table bpt<name>.dbd. Menu and Record Type Include File Generation. Access Security Application Programmer's Interface EPICS Release: R3.13.0beta12 EPICS IOC Application Developer's Guide 63 change Client long asChangeClient(ASCLIENTPVT ppvt,int asl, char *user,char*host); This routine changes one or more of the values asl, user, and host for an existing client. Again the caller must provide permanent storage for user and host. It is permissible to use the same user and host used in the call to asAddClient with different values. This routine returns S_asLib_asNotActive without doing anything if access control is not active. remove Client long asRemoveClient(ASCLIENTPVT *pvt); This call removes a client. This routine returns S_asLib_asNotActive without doing anything if access control is not active. get Client Pvt void *asGetClientPvt(ASCLIENTPVT pvt); For each client, the access system keeps a pointer that can be used by the caller. This routine returns the value of the pointer. This routine returns NULL if access security is not active. put Client Pvt void asPutClientPvt(ASCLIENTPVT pvt, void *userPvt); This routine is used to set the pointer returned by asGetClientPvt. register Callback long asRegisterClientCallback(ASCLIENTPVT pvt, ASCLIENTCALLBACK pcallback); This routine registers a callback that will be called whenever the access privilege of the client changes. This routine returns S_asLib_asNotActive without doing anything if access control is not active. check Get long asCheckGet(ASCLIENTPVT pvt); This routine, actually a macro, returns (TRUE,FALSE) if the client (has, doesn't have) get access rights. check Put long asCheckPut(ASCLIENTPVT pvt); This routine, actually a macro, returns (TRUE,FALSE) if the client (has, doesn't have) put access rights Access Computation compute all Asg long asComputeAllAsg(void); This routine calls asComputeAsg for each access security group.

Development of a 100 J, 10 Hz laser for compression experiments at the High Energy Density instrument at the European XFEL

“…Control of the many components and sub-systems that make up the DiPOLE100X laser is provided by a distributed control system developed at the CLF using EPICS (Experimental Physics and Industrial Control System) [11] . EPICS is an open source software framework, providing a collection of tools and applications for use in creating distributed control systems, which is used in many large-scale science facilities, such as particle accelerators and synchrotron light sources.…”

The Design of the Plasma Control System in KTX

“…The KTX PCS is designed by ASIPP (Institute of Plasma Physics, Chinese Academy of Sciences), and needs to meet the requirements of real-time, stability, flexibility and other performance requirements in plasma discharge experiments. EPICS is based on a distributed system and is developed for the control of large scale accelerators [10,11] . The EPICS framework has many advantages in flexibility, maintainability and reliability, and is widely used in tokamaks such as NSTX (National Spherical Torus eXperiment), ITER (International Thermonuclear Experimental Reactor) and KSTAR (Korea Superconducting Tokamak Advanced Research).…”

Modelización e integración de sistemas de adquisición de datos inteligentes en sistemas de instrumentación para dispositivos de fusión

“…Si fuera necesario, se podrían crear y definir nuevos tipos de records, pero posiblemente cualquier tipo de implementación, podría realizarse con los que ya están definidos. La implementación del comportamiento de un record, es decir, la definición de su record support, ha de realizarse siguiendo las pautas establecidas para el procesamiento de records definidas en el manual de EPICS (R. Kraimer, B. Anderson et al 2014). Esto es, el orden en el que deben ejecutarse y actualizarse determinados campos de las estructuras de datos de los records, para que su comportamiento no se salga de la filosofía de funcionamiento del EPICS core database (El core de EPICS).…”

“…A continuación se muestra la entry table que da soporte a los records, Record Support Entry Table (RSET) (ver Figura 40). La implementación de las funciones que rellenan la RSET, requieren de ciertos requisitos explicados en la guía de desarrollo de aplicaciones de EPICS (R. Kraimer, B. Anderson et al 2014). Esta RSET deberá ser completada por el usuario programador que quiera definir un nuevo tipo de record.…”