From d01040c7c3a1dfbaf67087de7f72562aaa1e9e42 Mon Sep 17 00:00:00 2001 From: MarkRivers Date: Mon, 25 May 2015 19:45:52 +0000 Subject: [PATCH] Removed old stuff about mar345 left over from document creation; document is still very incomplete --- documentation/motorDeviceDriver.html | 171 --------------------------- 1 file changed, 171 deletions(-) diff --git a/documentation/motorDeviceDriver.html b/documentation/motorDeviceDriver.html index 0205b9a7..e78603af 100644 --- a/documentation/motorDeviceDriver.html +++ b/documentation/motorDeviceDriver.html @@ -206,176 +206,5 @@ The asynMotorAxis base class defines the following methods:

-

- This driver inherits from ADDriver. - It implements many of the parameters in - asynNDArrayDriver.h and in - ADArrayDriver.h. It also implements a number of parameters that are specific - to the mar345 detector. The mar345 - class documentation describes this class in detail.

-

- Implementation of standard driver parameters

-

- The following table describes how the mar345 driver implements some of the standard - driver parameters. -

- - - - - - - - - - - - - - - - -
- Implementation of Parameters in asynNDArrayDriver.h and ADDriver.h, and EPICS Record - Definitions in ADBase.template and NDFile.template
- Parameter index variable - EPICS record name - Description
- ADAcquire - $(P)$(R)Acquire - Setting this to 1 starts an acquisition sequence. If ADNumImages is greater than - 1 then it acquires multiple frames. For each frame it does the following: -
    -
  1. Erases the detector if mar345EraseMode is "Before expose".
    2. -
  2. Opens the shutter if either the mar345 shutter or EPICS shutter controls are enabled.
    3. -
  3. Waits for the desired exposure time.
    4. -
  4. Closes the shutter if either the mar345 shutter or EPICS shutter controls are - enabled.
    5. -
  5. Scans the detector and saves the file.
    6. -
  6. Erases the detector if mar345EraseMode is "After scan".
    7. -
- If ADAcquire is set to 0 during exposure (step 3 above) then it proceeds immediately - to step 4, finishes collecting the current frame and stops the acquisition sequence - if ADNumImages is greater than 1. If mar345Abort is set to 0 then the acquisition - is terminated as soon as possible without saving the data. Note however that commands - to the mar345 server to erase, change mode, or scan cannot be aborted, so the driver - must wait for these commands to complete.
-

- It is useful to use NDPluginROI to define an ROI containing the entire mar345 detector. - The MaxValue_RBV PV in this ROI can be monitored to make sure that the 16-bit limit - of 65,535 is not being approached in any pixel. -

-

- mar345 specific parameters

-

- The mar345 driver implements the following parameters in addition to those in asynNDArrayDriver.h - and ADDriver.h. Note that to reduce the width of this table the parameter index - variable names have been split into 2 lines, but these are just a single name, for - example mar345ScanSize. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Parameter Definitions in mar345.cpp and EPICS Record Definitions in mar345.template -
- Parameter index variable - asyn interface - Access - Description - drvInfo string - EPICS record name - EPICS record type
- Readout parameters
- mar345
- ScanSize 		- asynInt32 - r/w - The detector diameter to read out. Choices are 180mm, 240mm, 300mm, and 345mm. - - MAR_SIZE - $(P)$(R)ScanSize
- $(P)$(R)ScanSize_RBV 		- mbbo -
- mbbi
- mar345
- ScanResolution 		- asynInt32 - r/w - The pixel size to use when reading the detector out. Choices are 0.10 and 0.15mm. - - MAR_RESOLUTION - $(P)$(R)ScanResolution
- $(P)$(R)ScanResolution_RBV 		- mbbo -
- mbbi
-

- Configuration

-

- The mar345 driver is created with the mar345Config command, either from C/C++ or - from the EPICS IOC shell.

- 
int mar345Config(const char *portName, const char *serverPort,
-                 int maxBuffers, size_t maxMemory,
-                 int priority, int stackSize)
-
-

- For details on the meaning of the parameters to this function refer to the detailed - documentation on the mar345Config function in the - mar345.cpp documentation and in the documentation for the constructor for - the mar345 class. -

-

- There an example IOC boot directory and startup script (iocBoot/iocMAR345/st.cmd) - provided with areaDetector. -

-

- MEDM screens

-

- The following show the MEDM screens that are used to control the mar345 detector. - Note that the general purpose screen ADBase.adl can be used, but it exposes many - controls that are not applicable to the mar345, and lacks some fields that are important - for the mar345.

-

- mar345.adl is the main screen used to control the mar345 driver. -

-
-

- mar345.adl

- mar345.png