areaDetector: EPICS Area Detector Support

Release 2-5

October 23, 2016

Mark Rivers

University of Chicago




The areaDetector module provides a general-purpose interface for area (2-D) detectors in EPICS. It is intended to be used with a wide variety of detectors and cameras, ranging from high frame rate CCD and CMOS cameras, pixel-array detectors such as the Pilatus, and large format detectors like the Perkin Elmer flat panels.

The goals of this module are:



The architecture of the areaDetector module is shown below.


From the bottom to the top this architecture consists of the following:

The code in Layers 1-3 is essentially independent of EPICS. In principle there are only 2 EPICS dependencies in this code.

  1. libCom. libCom from EPICS base provides operating-system independent functions for threads, mutexes, etc.
  2. asyn. asyn is a module that provides interthread messaging services, including queueing and callbacks.

In particular it should be possible to eliminate layers 4-6 in the architecture shown in Figure 1. This means that it is not necessary to run an EPICS IOC or to use EPICS Channel Access when using the drivers and plugins at Layers 2 and 3. This is demonstrated in the simDetectorNoIOC application in ADExample.

The plugin architecture is very powerful, because new plugins can be written for application-specific purposes. For example, a plugin could be written to analyze images and do some application specific functions, and such a plugin would then work with any detector driver. Plugins are also powerful because they can be reconfigured at run-time. For example the NDPluginStdArrays can switch from getting its array data from a detector driver to an NDPluginROI plugin. That way it will switch from displaying the entire detector to whatever sub-region the ROI driver has selected. Any Channel Access clients connected to the NDPluginStdArrays driver will automatically switch to displaying this subregion. Similarly, the NDPluginFile plugin can be switched at run-time from saving the entire image to saving a selected ROI, just by changing its input source. Plugins can be used to form an image processing pipeline, for example with a detector providing data to a color convert plugin, which feeds an ROI plugin, which feeds a file saving plugin. Each plugin can run in its own thread, and hence in its own core on a modern multi-core CPU.

The use of plugins is optional, and it is only plugins that require the driver to make callbacks with image data. If there are no plugins being used then EPICS can be used simply to control the detector, without accessing the data itself. This is most useful when the vendor provides an API has the ability to save the data to a file and an application to display the images.

What follows is a detailed description of the software, working from the bottom up. Most of the code is object oriented, and written in C++.

Implementation details

The areaDetector module depends heavily on asyn. It is the software that is used for interthread communication, using the standard asyn interfaces (e.g. asynInt32, asynOctet, etc.), and callbacks. In order to minimize the amount of redundant code in drivers, areaDetector has been implemented using C++ classes. The base classes, from which drivers and plugins are derived, take care of many of the details of asyn and other common code.


Detector drivers and plugins are asyn port drivers, meaning that they implement one or more of the standard asyn interfaces. They register themselves as interrupt sources, so that they do callbacks to registered asyn clients when values change. They inherit from the asynPortDriver base C++ class that is provided in the asyn module. That base class handles all of the details of registering the port driver, registering the supported interfaces, and registering the required interrupt sources. It also provides a parameter library for int, double, and string parameters indexed by the integer index values defined in the driver. The parameter library provides methods to write and read the parameter values, and to perform callbacks to registered clients when a parameter value has changed. The asynPortDriver class documentation describes this class in detail.


The NDArray (N-Dimensional array) is the class that is used for passing detector data from drivers to plugins. An NDArray is a general purpose class for handling array data. An NDArray object is self-describing, meaning it contains enough information to describe the data itself. It can optionally contain "attributes" (class NDAttribute) which contain meta-data describing how the data was collected, etc.

An NDArray can have up to ND_ARRAY_MAX_DIMS dimensions, currently 10. A fixed maximum number of dimensions is used to significantly simplify the code compared to unlimited number of dimensions. Each dimension of the array is described by an NDDimension structure. The NDArray class documentation describes this class in detail.


The NDArrayPool class manages a free list (pool) of NDArray objects. Drivers allocate NDArray objects from the pool, and pass these objects to plugins. Plugins increase the reference count on the object when they place the object on their queue, and decrease the reference count when they are done processing the array. When the reference count reaches 0 again the NDArray object is placed back on the free list. This mechanism minimizes the copying of array data in plugins. The NDArrayPool class documentation describes this class in detail.


The NDAttribute is a class for linking metadata to an NDArray. An NDattribute has a name, description, data type, value, source type and source information. Attributes are identified by their names, which are case-insensitive. There are methods to set and get the information for an attribute.

It is useful to define some conventions for attribute names, so that plugins or data analysis programs can look for a specific attribute. The following are the attribute conventions used in current plugins:

Conventions for standard attribute names
Attribute name Description Data type
ColorMode "Color mode" int (NDColorMode_t)
BayerPattern "Bayer pattern" int (NDBayerPattern_t)

Attribute names are case-sensitive. For attributes not in this table a good convention would be to use the corresponding driver parameter without the leading ND or AD, and with the first character of every "word" of the name starting with upper case. For example, the standard attribute name for ADManufacturer should be "Manufacturer", ADNumExposures should be "NumExposures", etc.

The NDAttribute class documentation describes this class in detail.


The NDAttributeList implements a linked list of NDAttribute objects. NDArray objects contain an NDAttributeList which is how attributes are associated with an NDArray. There are methods to add, delete and search for NDAttribute objects in an NDAttributeList. Each attribute in the list must have a unique name, which is case-sensitive.

When NDArrays are copied with the NDArrayPool methods the attribute list is also copied.

IMPORTANT NOTE: When a new NDArray is allocated using NDArrayPool::alloc() the behavior of any existing attribute list on the NDArray taken from the pool is determined by the value of the global variable eraseNDAttributes. By default the value of this variable is 0. This means that when a new NDArray is allocated from the pool its attribute list is not cleared. This greatly improves efficiency in the normal case where attributes for a given driver are defined once at initialization and never deleted. (The attribute values may of course be changing.) It eliminates allocating and deallocating attribute memory each time an array is obtained from the pool. It is still possible to add new attributes to the array, but any existing attributes will continue to exist even if they are ostensibly cleared e.g. asynNDArrayDriver::readNDAttributesFile() is called again. If it is desired to eliminate all existing attributes from NDArrays each time a new one is allocated then the global variable eraseNDAttributes should be set to 1. This can be done at the iocsh prompt with the command:

    var eraseNDAttributes 1

The NDAttributeList class documentation describes this class in detail.


The PVAttribute class is derived from NDAttribute. It obtains its value by monitor callbacks from an EPICS PV, and is thus used to associate current the value of any EPICS PV with an NDArray. The PVAttribute class documentation describes this class in detail.


The paramAttribute class is derived from NDAttribute. It obtains its value from the current value of a driver or plugin parameter. The paramAttribute class is typically used when it is important to have the current value of the parameter and the value of a corresponding PVAttribute might not be current because the EPICS PV has not yet updated. The paramAttribute class documentation describes this class in detail.


The functAttribute class is derived from NDAttribute. It obtains its value from a user-written C++ function. The functAttribute class is thus very general, and can be used to add almost any information to an NDArray. ADCore contains example code, myAttributeFunctions.cpp that demonstates how to write such functions. The functAttribute class documentation describes this class in detail.


asynNDArrayDriver inherits from asynPortDriver. It implements the asynGenericPointer functions for NDArray objects. This is the class from which both plugins and area detector drivers are indirectly derived. The asynNDArrayDriver class documentation describes this class in detail.

The file asynNDArrayDriver.h defines a number of parameters that all NDArray drivers and plugins should implement if possible. These parameters are defined by strings (drvInfo strings in asyn) with an associated asyn interface, and access (read-only or read-write). There is also an integer index to the parameter which is assigned by asynPortDriver when the parameter is created in the parameter library. The EPICS database NDArrayBase.template provides access to these standard driver parameters. The following table lists the standard driver parameters. The columns are defined as follows:

Note that for parameters whose values are defined by enum values (e.g NDDataType, NDColorMode, etc.), drivers can use a different set of enum values for these parameters. They can override the enum menu in ADBase.template with driver-specific choices by loading a driver-specific template file that redefines that record field after loading ADBase.template.

Parameter Definitions in asynNDArrayDriver.h and EPICS Record Definitions in NDArrayBase.template (file-related records are in NDFile.template)
Parameter index variable asyn interface Access Description drvInfo string EPICS record name EPICS record type
Information about the version of ADCore
NDADCoreVersion asynOctet r/o ADCore version number. This can be used by Channel Access clients to alter their behavior depending on the version of ADCore that was used to build this driver or plugin. ADCORE_VERSION $(P)$(R)ADCoreVersion_RBV stringin
Information about the asyn port
NDPortNameSelf asynOctet r/o asyn port name PORT_NAME_SELF $(P)$(R)PortName_RBV stringin
Data type
NDDataType asynInt32 r/w Data type (NDDataType_t). DATA_TYPE $(P)$(R)DataType
Color mode
NDColorMode asynInt32 r/w Color mode (NDColorMode_t). COLOR_MODE $(P)$(R)ColorMode
NDBayerPattern asynInt32 r/o Bayer pattern (NDBayerPattern_t) of NDArray data. BAYER_PATTERN $(P)$(R)BayerPattern_RBV mbbi
Actual dimensions of array data
NDNDimensions asynInt32 r/o Number of dimensions in the array ARRAY_NDIMENSIONS $(P)$(R)NDimensions_RBV longin
NDDimensions asynInt32Array r/o Size of each dimension in the array ARRAY_DIMENSIONS $(P)$(R)Dimensions_RBV waveform
N.A. N.A r/o Size of the first array dimension, extracted from the Dimensions_RBV waveform record. N.A. $(P)$(R)ArraySize0_RBV longin
N.A. N.A r/o Size of the second array dimension, extracted from the Dimensions_RBV waveform record. N.A. $(P)$(R)ArraySize1_RBV longin
N.A. N.A r/o Size of the third array dimension, extracted from the Dimensions_RBV waveform record. N.A. $(P)$(R)ArraySize2_RBV longin
NDArraySizeX asynInt32 r/o Size of the array data in the X direction ARRAY_SIZE_X $(P)$(R)ArraySizeX_RBV longin
NDArraySizeY asynInt32 r/o Size of the array data in the Y direction ARRAY_SIZE_Y $(P)$(R)ArraySizeY_RBV longin
NDArraySizeZ asynInt32 r/o Size of the array data in the Z direction ARRAY_SIZE_Z $(P)$(R)ArraySizeZ_RBV longin
NDArraySize asynInt32 r/o Total size of the array data in bytes ARRAY_SIZE $(P)$(R)ArraySize_RBV longin
Array data
NDArrayCallbacks asynInt32 r/w Controls whether the driver or plugin does callbacks with the array data to registered plugins. 0=No, 1=Yes. Setting this to 0 in a driver can reduce overhead in the case that the driver is being used only to control the device, and not to make the data available to plugins or to EPICS clients. Setting this to 0 in a plugin can reduce overhead by eliminating the need to copy the NDArray if that plugin is not being used as a source of NDArrays to other plugins. ARRAY_CALLBACKS $(P)$(R)ArrayCallbacks
NDArrayData asynGenericPointer r/w The array data as an NDArray object NDARRAY_DATA N/A. EPICS access to array data is through NDStdArrays plugin. N/A
NDArrayCounter asynInt32 r/w Counter that increments by 1 each time an array is acquired. Can be reset by writing a value to it. ARRAY_COUNTER $(P)$(R)ArrayCounter
N/A N/A r/o Rate at which arrays are being acquired. Computed in the ADBase.template database. N/A $(P)$(R)ArrayRate_RBV calc
Array attributes
NDAttributesFile asynOctet r/w The name of an XML file defining the PVAttributes and paramAttributes to be added to each NDArray by this driver or plugin. The format of the XML file is described in the documentation for asynNDArrayDriver::readNDAttributesFile(). ND_ATTRIBUTES_FILE $(P)$(R)NDAttributesFile waveform
Array pool status
NDPoolMaxMemory asynFloat64 r/o The maximum number of NDArrayPool memory bytes that can be allocated. 0=unlimited. POOL_MAX_MEMORY $(P)$(R)PoolMaxMem ai
NDPoolUsedMemory asynFloat64 r/o The number of NDArrayPool memory bytes currently allocated. The SCAN rate of this record controls the scanning of all of the dynamic NDArrayPool status records. POOL_USED_MEMORY $(P)$(R)PoolUsedMem ai
NDPoolMaxBuffers asynInt32 r/o The maximum number of NDArrayPool buffers that can be allocated. 0=unlimited. POOL_MAX_BUFFERS $(P)$(R)PoolMaxBuffers longin
NDPoolAllocBuffers asynInt32 r/o The number of NDArrayPool buffers currently allocated. POOL_ALLOC_BUFFERS $(P)$(R)PoolAllocBuffers longin
NDPoolFreeBuffers asynInt32 r/o The number of NDArrayPool buffers currently allocated but free. POOL_FREE_BUFFERS $(P)$(R)PoolFreeBuffers longin
N.A. N.A. r/o The number of NDArrayPool buffers currently in use. This is calculated as NDPoolAllocBuffers - NDPoolFreeBuffers. N.A. $(P)$(R)PoolUsedBuffers calc
Debugging control
N/A N/A N/A asyn record to control debugging (asynTrace) N/A $(P)$(R)AsynIO asyn
File saving parameters (records are defined in NDFile.template)
NDFilePath asynOctet r/w File path FILE_PATH $(P)$(R)FilePath
NDFilePathExists asynInt32 r/o Flag indicating if file path exists FILE_PATH_EXISTS $(P)$(R)FilePathExists_RBV bi
NDFileName asynOctet r/w File name FILE_NAME $(P)$(R)FileName
NDFileNumber asynInt32 r/w File number FILE_NUMBER $(P)$(R)FileNumber
NDFileTemplate asynOctet r/w Format string for constructing NDFullFileName from NDFilePath, NDFileName, and NDFileNumber. The final file name (which is placed in NDFullFileName) is created with the following code:
    FileTemplate, FilePath, 
    Filename, FileNumber);
FilePath, Filename, FileNumber are converted in that order with FileTemplate. An example file format is "%s%s%4.4d.tif". The first %s converts the FilePath, followed immediately by another %s for Filename. FileNumber is formatted with %4.4d, which results in a fixed field with of 4 digits, with leading zeros as required. Finally, the .tif extension is added to the file name. This mechanism for creating file names is very flexible. Other characters, such as _ can be put in Filename or FileTemplate as desired. If one does not want to have FileNumber in the file name at all, then just omit the %d format specifier from FileTemplate. If the client wishes to construct the complete file name itself, then it can just put that file name into NDFileTemplate with no format specifiers at all, in which case NDFilePath, NDFileName, and NDFileNumber will be ignored.
FILE_TEMPLATE $(P)$(R)FileTemplate
NDFullFileName asynOctet r/o Full file name constructed using the algorithm described in NDFileTemplate FULL_FILE_NAME $(P)$(R)FullFileName_RBV waveform
NDAutoIncrement asynInt32 r/w Auto-increment flag. Controls whether FileNumber is automatically incremented by 1 each time a file is saved (0=No, 1=Yes) AUTO_INCREMENT $(P)$(R)AutoIncrement
NDAutoSave asynInt32 r/w Auto-save flag (0=No, 1=Yes) controlling whether a file is automatically saved each time acquisition completes. AUTO_SAVE $(P)$(R)AutoSave
NDFileFormat asynInt32 r/w File format. The format to write/read data in (e.g. TIFF, netCDF, etc.) FILE_FORMAT $(P)$(R)FileFormat
NDWriteFile asynInt32 r/w Manually save the most recent array to a file when value=1 WRITE_FILE $(P)$(R)WriteFile
NDReadFile asynInt32 r/w Manually read a file when value=1 READ_FILE $(P)$(R)ReadFile
NDFileWriteMode asynInt32 r/w File saving mode (Single, Capture, Stream)(NDFileMode_t) WRITE_MODE $(P)$(R)FileWriteMode
NDFileWriteStatus asynInt32 r/o File write status. Gives status information on last file open or file write operation. Values are WriteOK (0) and WriteError (1). WRITE_STATUS $(P)$(R)FileWriteStatus mbbi
NDFileWriteMessage asynOctet r/o File write error message. An error message string if the previous file open or file write operation resulted in an error. WRITE_MESSAGE $(P)$(R)FileWriteMessage waveform
NDFileCapture asynInt32 r/w Start (1) or stop (0) file capture or streaming CAPTURE $(P)$(R)Capture
NDFileNumCapture asynInt32 r/w Number of frames to acquire in capture or streaming mode NUM_CAPTURE $(P)$(R)NumCapture
NDFileNumCaptured asynInt32 r/o Number of arrays currently acquired capture or streaming mode NUM_CAPTURED $(P)$(R)NumCaptured_RBV longin
NDFileDeleteDriverFile asynInt32 r/w Flag to enable deleting original driver file after a plugin has re-written the file in a different format. This can be useful for detectors that must write the data to disk in order for the areaDetector driver to read it back. Once a file-writing plugin has rewritten the data in another format it can be desireable to then delete the original file. DELETE_DRIVER_FILE $(P)$(R)DeleteDriverFile
NDFileLazyOpen asynInt32 r/w Flag to defer the creation of a new file until the first NDArray to write has been received. This removes the need for passing an extra NDArray through the file writing plugin to initialise dimensions and possibly NDAttribute list before opening the file. The downside is that file creation can potentially be time-consuming so processing the first NDArray may be slower than subsequent ones.
Only makes sense to use with file plugins which support multiple frames per file and only in "Stream" mode.
NDFileCreateDir asynInt32 r/w This parameter is used to automatically create directories if they don't exist. If it is zero (default), no directories are created. If it is negative, then the absolute value is the maximum of directories that will be created (i.e. -1 will create a maximum of one directory to complete the path, -2 will create a maximum of 2 directories). If it is positive, then at least that many directories in the path must exist (i.e. a value of 1 will create all directories below the root directory and 2 will not create a directory in the root directory). CREATE_DIR $(P)$(R)CreateDirectory
NDFileTempSuffix asynOctet r/w If this string is non-null, the file is opened with this suffix temporarily appended to the file name. When the file is closed it is then renamed to the correct file name without the suffix. This is useful for processing software watching for the file to appear since the file appears as an atomic operation when it is ready to be opened. FILE_TEMP_SUFFIX $(P)$(R)TempSuffix


ADDriver inherits from asynNDArrayDriver. This is the class from which area detector drivers are directly derived. It provides parameters and methods that are specific to area detectors, while asynNDArrayDriver is a general NDArray driver. The ADDriver class documentation describes this class in detail.

The file ADDriver.h defines the parameters that all areaDetector drivers should implement if possible.

Parameter Definitions in ADDriver.h and EPICS Record Definitions in ADBase.template
Parameter index variable asyn interface Access Description drvInfo string EPICS record name EPICS record type
Information about the detector
ADManufacturer asynOctet r/o Detector manufacturer name MANUFACTURER $(P)$(R)Manufacturer_RBV stringin
ADModel asynOctet r/o Detector model name MODEL $(P)$(R)Model_RBV stringin
ADMaxSizeX asynInt32 r/o Maximum (sensor) size in the X direction MAX_SIZE_X $(P)$(R)MaxSizeX_RBV longin
ADMaxSizeY asynInt32 r/o Maximum (sensor) size in the Y direction MAX_SIZE_Y $(P)$(R)MaxSizeY_RBV longin
ADTemperature asynFloat64 r/w Detector temperature TEMPERATURE $(P)$(R)Temperature
ADTemperatureActual asynFloat64 r/o Actual detector temperature TEMPERATURE_ACTUAL $(P)$(R)Temperature_Actual ai
Detector readout control including gain, binning, region start and size, reversal
ADGain asynFloat64 r/w Detector gain GAIN $(P)$(R)Gain
ADBinX asynInt32 r/w Binning in the X direction BIN_X $(P)$(R)BinX
ADBinY asynInt32 r/w Binning in the Y direction BIN_Y $(P)$(R)BinY
ADMinX asynInt32 r/w First pixel to read in the X direction.
0 is the first pixel on the detector.
MIN_X $(P)$(R)MinX
ADMinY asynInt32 r/w First pixel to read in the Y direction.
0 is the first pixel on the detector.
MIN_Y $(P)$(R)MinY
ADSizeX asynInt32 r/w Size of the region to read in the X direction SIZE_X $(P)$(R)SizeX
ADSizeY asynInt32 r/w Size of the region to read in the Y direction SIZE_Y $(P)$(R)SizeY
ADReverseX asynInt32 r/w Reverse array in the X direction
(0=No, 1=Yes)
REVERSE_X $(P)$(R)ReverseX
ADReverseY asynInt32 r/w Reverse array in the Y direction
(0=No, 1=Yes)
REVERSE_Y $(P)$(R)ReverseY
Image and trigger modes
ADImageMode asynInt32 r/w Image mode (ADImageMode_t). IMAGE_MODE $(P)$(R)ImageMode
ADTriggerMode asynInt32 r/w Trigger mode (ADTriggerMode_t). TRIGGER_MODE $(P)$(R)TriggerMode
Frame type
ADFrameType asynInt32 r/w Frame type (ADFrameType_t). FRAME_TYPE $(P)$(R)FrameType
Acquisition time and period
ADAcquireTime asynFloat64 r/w Acquisition time per image ACQ_TIME $(P)$(R)AcquireTime
ADAcquirePeriod asynFloat64 r/w Acquisition period between images ACQ_PERIOD $(P)$(R)AcquirePeriod
Number of exposures and number of images
ADNumExposures asynInt32 r/w Number of exposures per image to acquire NEXPOSURES $(P)$(R)NumExposures
ADNumImages asynInt32 r/w Number of images to acquire in one acquisition sequence NIMAGES $(P)$(R)NumImages
Acquisition control
ADAcquire asynInt32 r/w Start (1) or stop (0) image acquisition. This is an EPICS busy record that does not process its forward link until acquisition is complete. Clients should write 1 to the Acquire record to start acquisition, and wait for Acquire to go to 0 to know that acquisition is complete. ACQUIRE $(P)$(R)Acquire
Status information
ADStatus asynInt32 r/o Acquisition status (ADStatus_t) STATUS $(P)$(R)DetectorState_RBV mbbi
ADStatusMessage asynOctet r/o Status message string STATUS_MESSAGE $(P)$(R)StatusMessage_RBV waveform
ADStringToServer asynOctet r/o String from driver to string-based vendor server STRING_TO_SERVER $(P)$(R)StringToServer_RBV waveform
ADStringFromServer asynOctet r/o String from string-based vendor server to driver STRING_FROM_SERVER $(P)$(R)StringFromServer_RBV waveform
ADNumExposuresCounter asynInt32 r/o Counter that increments by 1 each time an exposure is acquired for the current image. Driver resets to 0 when acquisition is started. NUM_EXPOSURES_COUNTER $(P)$(R)NumExposuresCounter_RBV longin
ADNumImagesCounter asynInt32 r/o Counter that increments by 1 each time an image is acquired in the current acquisition sequence. Driver resets to 0 when acquisition is started. Drivers can use this as the loop counter when ADImageMode=ADImageMultiple. NUM_IMAGES_COUNTER $(P)$(R)NumImagesCounter_RBV longin
ADTimeRemaining asynFloat64 r/o Time remaining for current image. Drivers should update this value if they are doing the exposure timing internally, rather than in the detector hardware. TIME_REMAINING $(P)$(R)TimeRemaining_RBV ai
ADReadStatus asynInt32 r/w Write a 1 to this parameter to force a read of the detector status. Detector drivers normally read the status as required, so this is usually not necessary, but there may be some circumstances under which forcing a status read may be needed. READ_STATUS $(P)$(R)ReadStatus bo
Shutter control
ADShutterMode asynInt32 r/w Shutter mode (None, detector-controlled or EPICS-controlled) (ADShutterMode_t) SHUTTER_MODE $(P)$(R)ShutterMode
ADShutterControl asynInt32 r/w Shutter control for the selected (detector or EPICS) shutter (ADShutterStatus_t) SHUTTER_CONTROL $(P)$(R)ShutterControl
ADShutterControlEPICS asynInt32 r/w This record processes when it receives a callback from the driver to open or close the EPICS shutter. It triggers the records below to actually open or close the EPICS shutter. SHUTTER_CONTROL_EPICS $(P)$(R)ShutterControlEPICS bi
N/A N/A r/w This record writes its OVAL field to its OUT field when the EPICS shutter is told to open. The OCAL (and hence OVAL) and OUT fields are user-configurable, so any EPICS-controllable shutter can be used. N/A $(P)$(R)ShutterOpenEPICS calcout
N/A N/A r/w This record writes its OVAL field to its OUT field when the EPICS shutter is told to close. The OCAL (and hence OVAL) and OUT fields are user-configurable, so any EPICS-controllable shutter can be used. N/A $(P)$(R)ShutterCloseEPICS calcout
ADShutterStatus asynInt32 r/o Status of the detector-controlled shutter (ADShutterStatus_t) SHUTTER_STATUS $(P)$(R)ShutterStatus_RBV bi
N/A N/A r/o Status of the EPICS-controlled shutter. This record should have its input link (INP) set to a record that contains the open/close status information for the shutter. The link should have the "CP" attribute, so this record processes when the input changes. The ZRVL field should be set to the value of the input link when the shutter is closed, and the ONVL field should be set to the value of the input link when the shutter is open. N/A $(P)$(R)ShutterStatusEPICS_RBV mbbi
ADShutterOpenDelay asynFloat64 r/w Time required for the shutter to actually open (ADShutterStatus_t) SHUTTER_OPEN_DELAY $(P)$(R)ShutterOpenDelay
ADShutterCloseDelay asynFloat64 r/w Time required for the shutter to actually close (ADShutterStatus_t) SHUTTER_CLOSE_DELAY $(P)$(R)ShutterCloseDelay

Guidelines and rules for drivers

The following are guidelines and rules for writing areaDetector drivers

MEDM screens

The following is the top-level MEDM screen that provides links to the screens for most of the detectors and plugins that areaDetector supports. This screen is useful for testing, and as a source for copying related-display menus to be placed in application-specific MEDM screens.



The following is the MEDM screen that provides access to the parameters in asynNDArrayDriver.h and ADDriver.h through records in ADBase.template. This is a top-level MEDM screen that will work with any areaDetector driver. Note however that many drivers will not implement all of these parameters, and there will usually be detector-specific parameters not shown in this screen, so detector-specific MEDM screens should generally be created that display the EPICS PVs for the features implemented for that detector.



The following is the MEDM screen that provides access to the file-related parameters in asynNDArrayDriver.h through records in NDFile.template. This screen is for use with detector drivers that directly implement file I/O.



The following is the MEDM screen that provides access to the EPICS shutter parameters in ADDriver.h through records in ADBase.template. This screen allows one to define the EPICS PVs to open the shutter, close the shutter, and determine the shutter status. The values of these PVs for open and close drive and status can also be defined. Note that in many cases the same PV will be used for open and close drive, but in some cases (e.g. APS safety shutters) different PVs are used for open and close.



Installation, configuration, and running

Installation instructions for release R2-0 and later can be found on on Github.

For releases prior to R2-0 the version of this document contained in the source code release contains the installation instructions.

Acknowledgements and licenses

"This software is based in part on the work of the Independent JPEG Group".