diff --git a/documentation/FirewireWinDoc.html b/documentation/FirewireWinDoc.html index 30a4bf2..19b5f9f 100755 --- a/documentation/FirewireWinDoc.html +++ b/documentation/FirewireWinDoc.html @@ -8,7 +8,7 @@

- Firewire IIDC (CDAM) Windows driver

+ Firewire IIDC (CDAM) Windows driver

March 28, 2009

@@ -31,31 +31,34 @@

Introduction

- This is a driver for Firewire (IEEE 1394) cameras that follow the - IIDC/DCAM specification. - This industry standard allows a single driver to control cameras from any manufacturer, using any of - the supported video formats and features. - It inherits from ADDriver and implements many of the parameters in ADStdDriverParams.h. - It also implements a number of parameters that are specific to the Firewire cameras.

+ This is a driver for Firewire (IEEE 1394) cameras that follow the + IIDC/DCAM specification. This industry standard allows a single driver to + control cameras from any manufacturer, using any of the supported video formats + and features. It inherits from ADDriver and implements many of the parameters in + ADStdDriverParams.h. It also implements a number of parameters that are specific + to the Firewire cameras.

- This driver runs only on Windows. It uses the - Carnegie Mellon 1394 camera driver and library. There is also an - areaDetector Firewire driver for Linux available from the - - Diamond Light Source. + This driver runs only on Windows. It uses the + Carnegie Mellon 1394 camera driver and library. There is also an areaDetector + Firewire driver for Linux available from the + Diamond Light Source.

-

The IIDC/DCAM specification defines standard ways that manufacturers must implement features like shutter time, - white balance, frame sizes, frame rates, etc. There is a standard way to determine whether or not a particular - camera supports a particular feature. If it does then there is a standard way of querying the allowed - range of values for that feature. This makes it quite easy to write a driver that can support +

+ The IIDC/DCAM specification defines standard ways that manufacturers must implement + features like shutter time, white balance, frame sizes, frame rates, etc. There + is a standard way to determine whether or not a particular camera supports a particular + feature. If it does then there is a standard way of querying the allowed range of + values for that feature. This makes it quite easy to write a driver that can support cameras with any capabilities from any manufacturer.

Video formats, modes, and frame rates

-

The DCAM specification defines standard video frame sizes, color modes and frames rates. The following tables lists - these standard formats and mode. Video format 7 is special. It allows defining an ROI on the camera to read out. - The pixel resolution with which the size and position of this ROI can be defined can be queried, and is not - necessarily a single pixel. In Format 7 the frame rate settings do not apply, and the frame rate is determined - by the size of the Fireware data packets.

+

+ The DCAM specification defines standard video frame sizes, color modes and frames + rates. The following tables lists these standard formats and mode. Video format + 7 is special. It allows defining an ROI on the camera to read out. The pixel resolution + with which the size and position of this ROI can be defined can be queried, and + is not necessarily a single pixel. In Format 7 the frame rate settings do not apply, + and the frame rate is determined by the size of the Fireware data packets.

@@ -276,16 +279,17 @@ - -
Vendor-defined
- -

The following tables lists the standard frame rates for formats 0, 1 and 2. Note that not all frame rates are supported - by the IIDC standard for every format and mode, and even when a frame rate is supported by the standard it may not - be implemented for a particular camera. - In Format 7 the frame rate settings do not apply, and the frame rate is determined by the size of - the Fireware data packets. The areaDetector driver currently sets the Format 7 packet size to the vendor recommended - size, which typically results in the maximum possible frame rate.

- + +
+

+ The following tables lists the standard frame rates for formats 0, 1 and 2. Note + that not all frame rates are supported by the IIDC standard for every format and + mode, and even when a frame rate is supported by the standard it may not be implemented + for a particular camera. In Format 7 the frame rate settings do not apply, and the + frame rate is determined by the size of the Fireware data packets. The areaDetector + driver currently sets the Format 7 packet size to the vendor recommended size, which + typically results in the maximum possible frame rate.

+ - -
@@ -345,16 +349,18 @@ 240
-

The DCAM specification defines 22 standard features, which control things such as the brightness, white balance, - shutter time, etc.. For each feature the standard defines - control in both device units (12-bit integers) and absolute units (floating point). For example shutter time - may support absolute seconds, as well as device units. A feature may or may not - be supported on a particular camera. If it is supported it may or may not permit control in absolute units. - Each feature may support both manual control and automatic control (e.g. automatic gain control). - The following tables lists these standard features.

- + +
+

+ The DCAM specification defines 22 standard features, which control things such as + the brightness, white balance, shutter time, etc.. For each feature the standard + defines control in both device units (12-bit integers) and absolute units (floating + point). For example shutter time may support absolute seconds, as well as device + units. A feature may or may not be supported on a particular camera. If it is supported + it may or may not permit control in absolute units. Each feature may support both + manual control and automatic control (e.g. automatic gain control). The following + tables lists these standard features.

+ - -
@@ -544,13 +550,13 @@ QUALITY
- + +

- The firewireWinDCAM driver implements the following parameters in addition to those in ADStdDriverParams.h. - Note that to reduce the width of this table the enum names have been split into - 2 lines, but these are just a single name, for example mar345ScanSize. + The firewireWinDCAM driver implements the following parameters in addition to those + in ADStdDriverParams.h. Note that to reduce the width of this table the enum names + have been split into 2 lines, but these are just a single name, for example + mar345ScanSize.

@@ -576,7 +582,7 @@ + Video format parameters. In firewireDCAM.template and firewireVideoModes.template. + The video format. The allowed choices are 0="VGA", 1="Super VGA 1", 2="Super VGA + 2", 6="Still image", 7="User-defined". The FDC_has_format and FDC_valid_format parameters + described below indicate whether a particular format is actually supported by the + camera. + mbbo +
+ mbbi + + $(P)$(R)HAS_FORMAT_$(N) (N=0-7) + bi + + A string describing each of the formats (0-7) supported by the camera. The string + is "N.A." if the format is not supported. + $(P)$(R)VALID_FORMAT_$(N) (N=0-7) + stringin + + stringin + + Video mode parameters. In firewireDCAM.template and firewireVideoModes.template. @@ -672,8 +685,10 @@ $(P)$(R)MODE
$(P)$(R)MODE_RBV + mbbo +
+ mbbi + + A flag indicating whether a particular mode (0-7) is supported by the camera in + the currently selected format. + $(P)$(R)HAS_MODE_$(N) (N=0-7) + bi + + A string describing each of the modes (0-7) supported by the camera in the currently + selected video format. The string is "N.A." if the mode is not supported in this + format. + $(P)$(R)VALID_MODE_$(N) (N=0-7) + stringin + + stringin + + Video frame rate parameters. These parameters do not apply when the video format=7. + In firewireDCAM.template and firewireVideoModes.template. + The frame rate in frames/second. The allowed choices are 0="1.875", 1="3.75", 2="7.5", + 3="15", 4="30", 5="60", 6="120", 7="240". FDC_has_framerate and FDC_valid_framerate + parameters described below indicate whether a particular frame rate is actually + supported by the camera in the currently selected video format and mode. + mbbo +
+ mbbi + + A flag indicating whether a particular frame rate (0-7) is supported by the camera + in the currently selected video format and mode. + $(P)$(R)HAS_RATE_$(N) (N=0-7) + bi + + A string describing each of the frame rates (0-7) supported by the camera in the + currently selected video format and mode. The string is "N.A." if the frame rate + is not supported in this format and mode. + $(P)$(R)VALID_RATE_$(N) (N=0-7) + stringin + + stringin + + Video color code parameters. These parameters only apply when the video format=7. + In firewireDCAM.template and firewireColorCodes.template. + The color code. The allowed choices are 0-10. FDC_has_colorcode and FDC_valid_colorcode + parameters described below indicate whether a particular color code is actually + supported by the camera in the currently selected video format (7) and mode. + mbbo +
+ mbbi + + A flag indicating whether a particular color code (0-10) is supported by the camera + in the currently selected video format (7) and mode. + $(P)$(R)HAS_COLORCODE_$(N) (N=0-10) + bi + + A string describing each of the color codes (0-10) supported by the camera in the + currently selected video format (7) and mode. The string is "N.A." if the color + code is not supported in this format and mode. + $(P)$(R)VALID_COLORCODE_$(N) (N=0-10) + stringin + + stringin + + Video feature parameters. These parameters apply to each of the 22 DCAM features + listed above. In firewireFeature.template. + ao +
+ ai + + ao +
+ ai + + bi + + bi + + bo +
+ bi + + The minimum allowed value of the feature in device units. The database copies this + value to the LOPR and DRVL fields of the $(P)$(R)$(FEATURE) record. + ai + + The maximum allowed value of the feature in device units. The database copies this + value to the HOPR and DRVH fields of the $(P)$(R)$(FEATURE) record. + ai + + The minimum allowed value of the feature in absolute units. The database copies + this value to the LOPR and DRVL fields of the $(P)$(R)$(FEATURE)_ABS record. + ai + + The maximum allowed value of the feature in absolute units. The database copies + this value to the HOPR and DRVH fields of the $(P)$(R)$(FEATURE)_ABS record. + ai +
- Video format parameters. In firewireDCAM.template and firewireVideoModes.template.
@@ -587,17 +593,20 @@ r/w - The video format. The allowed choices are 0="VGA", 1="Super VGA 1", 2="Super VGA 2", 6="Still image", 7="User-defined". - The FDC_has_format and FDC_valid_format parameters described below indicate whether a particular format is actually supported - by the camera. FDC_FORMAT $(P)$(R)FORMAT
$(P)$(R)FORMAT_RBV		 - mbbo
- mbbi
@@ -612,9 +621,10 @@ FDC_HAS_FORMAT - $(P)$(R)HAS_FORMAT_$(N) (N=0-7) - bi
@@ -625,13 +635,15 @@ r/o - A string describing each of the formats (0-7) supported by the camera. The string is "N.A." if the format is not supported. FDC_VALID_FORMAT - $(P)$(R)VALID_FORMAT_$(N) (N=0-7) - stringin
@@ -648,11 +660,12 @@ $(P)$(R)CURRENT_FORMAT - stringin
- Video mode parameters. In firewireDCAM.template and firewireVideoModes.template.
@@ -663,8 +676,8 @@ r/w - The video mode. The allowed choices are 0-7. - The FDC_has_mode and FDC_valid_mode parameters described below indicate whether a particular mode is actually supported + The video mode. The allowed choices are 0-7. The FDC_has_mode and FDC_valid_mode + parameters described below indicate whether a particular mode is actually supported by the camera in the currently selected video format. FDC_MODE - mbbo
- mbbi
@@ -684,13 +699,15 @@ r/o - A flag indicating whether a particular mode (0-7) is supported by the camera in the currently selected format. FDC_HAS_MODE - $(P)$(R)HAS_MODE_$(N) (N=0-7) - bi
@@ -701,14 +718,16 @@ r/o - A string describing each of the modes (0-7) supported by the camera in the currently selected video format. - The string is "N.A." if the mode is not supported in this format. FDC_VALID_MODE - $(P)$(R)VALID_MODE_$(N) (N=0-7) - stringin
@@ -725,12 +744,13 @@ $(P)$(R)CURRENT_MODE - stringin
- Video frame rate parameters. These parameters do not apply when the video format=7. - In firewireDCAM.template and firewireVideoModes.template.
@@ -741,17 +761,20 @@ r/w - The frame rate in frames/second. The allowed choices are 0="1.875", 1="3.75", 2="7.5", 3="15", 4="30", 5="60", 6="120", 7="240". - FDC_has_framerate and FDC_valid_framerate parameters described below indicate whether a particular frame rate is actually supported - by the camera in the currently selected video format and mode. FDC_FRAMERATE $(P)$(R)FR
$(P)$(R)FR_RBV		 - mbbo
- mbbi
@@ -762,13 +785,15 @@ r/o - A flag indicating whether a particular frame rate (0-7) is supported by the camera in the currently selected video format and mode. FDC_HAS_FRAMERATE - $(P)$(R)HAS_RATE_$(N) (N=0-7) - bi
@@ -779,14 +804,16 @@ r/o - A string describing each of the frame rates (0-7) supported by the camera in the currently selected video format and mode. - The string is "N.A." if the frame rate is not supported in this format and mode. FDC_VALID_FRAMERATE - $(P)$(R)VALID_RATE_$(N) (N=0-7) - stringin
@@ -803,12 +830,13 @@ $(P)$(R)CURRENT_RATE - stringin
- Video color code parameters. These parameters only apply when the video format=7. - In firewireDCAM.template and firewireColorCodes.template.
@@ -819,17 +847,19 @@ r/w - The color code. The allowed choices are 0-10. - FDC_has_colorcode and FDC_valid_colorcode parameters described below indicate whether a particular color code is actually supported - by the camera in the currently selected video format (7) and mode. FDC_COLORCODE $(P)$(R)COLORCODE
$(P)$(R)COLORCODE_RBV		 - mbbo
- mbbi
@@ -840,13 +870,15 @@ r/o - A flag indicating whether a particular color code (0-10) is supported by the camera in the currently selected video format (7) and mode. FDC_HAS_COLORCODE - $(P)$(R)HAS_COLORCODE_$(N) (N=0-10) - bi
@@ -857,14 +889,16 @@ r/o - A string describing each of the color codes (0-10) supported by the camera in the currently selected video format (7) and mode. - The string is "N.A." if the color code is not supported in this format and mode. FDC_VALID_COLORCODE - $(P)$(R)VALID_COLORCODE_$(N) (N=0-10) - stringin
@@ -881,11 +915,13 @@ $(P)$(R)CURRENT_COLORCODE - stringin
- Video feature parameters. These parameters apply to each of the 22 DCAM features listed above. In firewireFeature.template.
@@ -903,8 +939,10 @@ $(P)$(R)$(FEATURE)
$(P)$(R)$(FEATURE)_RBV		 - ao
- ai
@@ -922,8 +960,10 @@ $(P)$(R)$(FEATURE)_ABS
$(P)$(R)$(FEATURE)_ABS_RBV		 - ao
- ai
@@ -940,7 +980,8 @@ $(P)$(R)$(FEATURE)_AVL - bi
@@ -957,7 +998,8 @@ $(P)$(R)$(FEATURE)_ABS_AVL - bi
@@ -975,8 +1017,10 @@ $(P)$(R)$(FEATURE)_CTRL
$(P)$(R)$(FEATURE)_CTRL_RBV		 - bo
- bi
@@ -987,14 +1031,15 @@ r/o - The minimum allowed value of the feature in device units. The database copies this value to the LOPR and DRVL fields - of the $(P)$(R)$(FEATURE) record. FDC_FEAT_VAL_MIN $(P)$(R)$(FEATURE)_MIN - ai
@@ -1005,14 +1050,15 @@ r/o - The maximum allowed value of the feature in device units. The database copies this value to the HOPR and DRVH fields - of the $(P)$(R)$(FEATURE) record. FDC_FEAT_VAL_MAX $(P)$(R)$(FEATURE)_MAX - ai
@@ -1023,14 +1069,15 @@ r/o - The minimum allowed value of the feature in absolute units. The database copies this value to the LOPR and DRVL fields - of the $(P)$(R)$(FEATURE)_ABS record. FDC_FEAT_VAL_ABS_MIN $(P)$(R)$(FEATURE)_ABS_MIN - ai
@@ -1041,14 +1088,15 @@ r/o - The maximum allowed value of the feature in absolute units. The database copies this value to the HOPR and DRVH fields - of the $(P)$(R)$(FEATURE)_ABS record. FDC_FEAT_VAL_ABS_MAX $(P)$(R)$(FEATURE)_ABS_MAX - ai
@@ -1102,7 +1150,7 @@ $(P)$(R)Gain - Maps onto the gain features. If camera supports absolute ... + Maps onto the gain features. If camera supports absolute ... @@ -1152,8 +1200,8 @@ mar345Config(const char *portName, const char *mar345Port, mar345Port - The name of the asyn TCP/IP port to communicate with mar345dtb. This - must have been previously created with drvAsynIPPortConfig(), + The name of the asyn TCP/IP port to communicate with mar345dtb. This must have been + previously created with drvAsynIPPortConfig(), @@ -1237,43 +1285,41 @@ create_monitor_set("auto_settings.req", 30,"P=13MAR345_1:,D=cam1:")

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

+ controls that are not applicable to Firewire cameras, and lacks many fields that + are important for such cameras.

- FirewireFeatures.adl is the screen used to control the features of Firewire cameras. + FirewireFeatures.adl is the screen used to control the features of + Firewire cameras.

FirewireFeatures.adl

firewireFeatures.png
-

- FirewireVideoFormats.adl is the screen used to control the video formats and modes of Firewire cameras. - This is a screen shot when the camera is not in Format 7. + FirewireVideoFormats.adl is the screen used to control the video formats + and modes of Firewire cameras. This is a screen shot when the camera is not in Format + 7.

FirewireFeatures.adl

firewireVideoFormats.png
- -

- FirewireVideoFormats.adl is the screen used to control the video formats and modes of Firewire cameras. - This is a screen shot when the camera is in Format 7, in which case the video rate menu is not displayed. + FirewireVideoFormats.adl is the screen used to control the video formats + and modes of Firewire cameras. This is a screen shot when the camera is in Format + 7, in which case the video rate menu is not displayed.

FirewireFeatures.adl

firewireVideoFormatsFormat7.png
- - -

Performance measurements

- The mar345 is definitely not a fast detector! - The following measurements show the time to perform various erase and scan operations. Note that because the - mar345 file format is compressed the file sizes are typically much less than the image sizes listed.

+ The mar345 is definitely not a fast detector! The following measurements show the + time to perform various erase and scan operations. Note that because the mar345 + file format is compressed the file sizes are typically much less than the image + sizes listed.

@@ -1369,6 +1415,7 @@ create_monitor_set("auto_settings.req", 30,"P=13MAR345_1:,D=cam1:") + @@ -141,8 +145,8 @@ @@ -194,15 +198,17 @@ + The detector diameter to read out. Choices are 180mm, 240mm, 300mm, and 345mm. + mbbo +
+ mbbi + + The pixel size to use when reading the detector out. Choices are 0.10 and 0.15mm. + mbbo +
+ mbbi + + Writing 1 to this parameter causes the ScanSize and ScanResolution values to be + sent to the server, changing the scan mode. This is not strictly necessary, because + the size and resolution is also encoded in the file extension used in the scan command. + However, changing the mode before doing a scan reduces the time for the scan, because + the detector is already configured for the correct mode. + busy +
+ bi + + Controls whether an erase cycle should be automatically performed during acquisition. + Choices are None, Before expose, and After scan. + mbbo +
+ mbbi + + The number of erase cycles to perform each time the detector is erased, either because + the mar345Erase parameter is set to 1, or because of an automatic erase as part + of an acquisition. + longout +
+ longin + + Write 1 to this parameter to initiate erasing the detector. The detector will be + erased multiple times if mar345NumErase is greater than 1. + busy +
+ bi + + Writing 1 to this parameter aborts the current operation as soon as possible and + returns the driver to the idle state. Note however that commands to the mar345 server + cannot be aborted, so the driver must wait for the current command to complete. + bo +
+ bi + @@ -500,9 +518,10 @@ create_monitor_set("auto_settings.req", 30,"P=13MAR345_1:,D=cam1:")

Performance measurements

- The mar345 is definitely not a fast detector! - The following measurements show the time to perform various erase and scan operations. Note that because the - mar345 file format is compressed the file sizes are typically much less than the image sizes listed.

+ The mar345 is definitely not a fast detector! The following measurements show the + time to perform various erase and scan operations. Note that because the mar345 + file format is compressed the file sizes are typically much less than the image + sizes listed.

82.7
180 mm @@ -1457,8 +1504,8 @@ create_monitor_set("auto_settings.req", 30,"P=13MAR345_1:,D=cam1:") The following are some current restrictions of the mar345 driver:

  • The areaDetector driver can in principle be run on machines other than the Linux - machine running mar345dtb, since the connection is via a socket. It has only been tested - on Linux.
    • + machine running mar345dtb, since the connection is via a socket. It has only been + tested on Linux.
  • The following items are hardcoded in the driver. They can be changed by recompiling compiling if necessary.
      diff --git a/documentation/Mar345Doc.html b/documentation/Mar345Doc.html index e2e3727..a3a250b 100755 --- a/documentation/Mar345Doc.html +++ b/documentation/Mar345Doc.html @@ -31,27 +31,29 @@

      Introduction

      - This is a driver for the mar345 detector from Marresearch GmbH. - It inherits from ADDriver and implements many of the parameters in ADStdDriverParams.h. - It also implements a number of parameters that are specific to the mar345 detector.

      + This is a driver for the mar345 detector from + Marresearch GmbH. It inherits from ADDriver and implements many of the parameters + in ADStdDriverParams.h. It also implements a number of parameters that are specific + to the mar345 detector.

      The interface to the detector is via a TCP/IP socket interface to the mar345dtb program that Marresearch provides. The mar345dtb program must be started before the areaDetector software is started.

      - mar345dtb must be configured to accepts commands on a TCP/IP socket port. This is done - by editing the file /home/mar345/tables/config.xxx (where xxx is the serial number of that detector) - and editing the COMMAND line to the following format:

      + mar345dtb must be configured to accepts commands on a TCP/IP socket port. This is + done by editing the file /home/mar345/tables/config.xxx (where xxx is the serial + number of that detector) and editing the COMMAND line to the following format:

      COMMAND PORT 5001

      - where 5001 is the TCP/IP port to use. Any high port number can be used, but it must agree with the - one specified in the areaDetector mar345Config command described below.

      + where 5001 is the TCP/IP port to use. Any high port number can be used, but it must + agree with the one specified in the areaDetector mar345Config command described + below.

      - The mar345dtb program saves the data to disk as compressed binary files. The areaDetector software - reads these disk files in order to read the data, because mar345dtb does not provide - another mechanism to access the data. + The mar345dtb program saves the data to disk as compressed binary files. The areaDetector + software reads these disk files in order to read the data, because mar345dtb does + not provide another mechanism to access the data.

      Implementation of standard driver parameters

      @@ -80,21 +82,23 @@
$(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: + 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. Opens the shutter if either the mar345 shutter or EPICS shutter controls are enabled.
  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. Closes the shutter if either the mar345 shutter or EPICS shutter controls are + enabled.
  6. Scans the detector and saves the file.
  7. Erases the detector if mar345EraseMode is "After scan".
- 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. + 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.
$(P)$(R)DetectorState_RBV - mar345 replaces the state strings with the following: Exposing, Scanning, Erasing, Changing Mode, - Aborting, Error, and Waiting. + mar345 replaces the state strings with the following: Exposing, Scanning, Erasing, + Changing Mode, Aborting, Error, and Waiting.
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
@@ -213,15 +219,17 @@ 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
@@ -232,19 +240,21 @@ r/w - Writing 1 to this parameter causes the ScanSize and ScanResolution values to be sent to - the server, changing the scan mode. This is not strictly necessary, because the size and resolution - is also encoded in the file extension used in the scan command. However, changing the mode before - doing a scan reduces the time for the scan, because the detector is already configured for - the correct mode. MAR_CHANGE_MODE $(P)$(R)ChangeMode
$(P)$(R)ChangedMode_RBV		 - busy
- bi
@@ -259,16 +269,18 @@ r/w - Controls whether an erase cycle should be automatically performed during acquisition. Choices are - None, Before expose, and After scan. MAR_ERASE_MODE $(P)$(R)EraseMode
$(P)$(R)EraseMode_RBV		 - mbbo
- mbbi
@@ -279,16 +291,19 @@ r/w - The number of erase cycles to perform each time the detector is erased, either because the mar345Erase - parameter is set to 1, or because of an automatic erase as part of an acquisition. MAR_NUM_ERASE $(P)$(R)NumErase
$(P)$(R)NumErase_RBV		 - longout
- longin
@@ -299,16 +314,18 @@ r/w - Write 1 to this parameter to initiate erasing the detector. The detector will be erased - multiple times if mar345NumErase is greater than 1. MAR_ERASE $(P)$(R)Erase
$(P)$(R)Erase_RBV		 - busy
- bi
@@ -323,18 +340,19 @@ r/w - Writing 1 to this parameter aborts the current operation as soon as possible and returns the driver - to the idle state. Note however that - commands to the mar345 server cannot be aborted, so the driver must wait for - the current command to complete. MAR_ABORT $(P)$(R)Abort
$(P)$(R)Abort_RBV		 - bo
- bi
@@ -403,8 +421,8 @@ mar345Config(const char *portName, const char *mar345Port, mar345Port - The name of the asyn TCP/IP port to communicate with mar345dtb. This - must have been previously created with drvAsynIPPortConfig(), + The name of the asyn TCP/IP port to communicate with mar345dtb. This must have been + previously created with drvAsynIPPortConfig(),
@@ -687,8 +706,8 @@ create_monitor_set("auto_settings.req", 30,"P=13MAR345_1:,D=cam1:") The following are some current restrictions of the mar345 driver: