Experimental Physics and
Industrial Control System

 

Hi Iian,

 

You can do it in a simpler way.  You can just redefine the fields of the existing ImageMode record in the database for your detector.  You don’t need to leave a gap.  The ONVL field can be 2, it does not have to be 1.

 

Here is an example from ADAndor/andorApp/Db/andorCCD.template where additional choices were added:

 

record(mbbo, "$(P)$(R)ImageMode")

{

   field(ZRST, "Single")

   field(ZRVL, "0")

   field(ONST, "Multiple")

   field(ONVL, "1")

   field(TWST, "Continuous")

   field(TWVL, "2")

   field(THST, "Fast Kinetics")

   field(THVL, "3")

   field(VAL,  "2")

}

 

record(mbbi, "$(P)$(R)ImageMode_RBV")

{

   field(ZRST, "Single")

   field(ZRVL, "0")

   field(ONST, "Multiple")

   field(ONVL, "1")

   field(TWST, "Continuous")

   field(TWVL, "2")

   field(THST, "Fast Kinetics")

   field(THVL, "3")

   field(SCAN, "I/O Intr")

}

 

In your case you can do:

record(mbbo, "$(P)$(R)ImageMode")

{

   field(ZRST, "Single")

   field(ZRVL, "0")

   field(ONST, "Continuous")

   field(ONVL, "2")

}

 

record(mbbi, "$(P)$(R)ImageMode_RBV")

{

   field(ZRST, "Single")

   field(ZRVL, "0")

   field(ONST, "Continuous")

   field(ONVL, "2")

}

 

Mark

 

 

 

I am using areaDetector in a product.  We only want to use “Single” and “Continuous” ImageMode, not “Multiple”.  In the first implementation, I modified ADBase.template to remove the “Multiple” option.  For a more portable solution, I made a new mbbo record without the Multiple option, and set the OUT field to $(P)$(R)ImageMode.  However, I had to define “ZRVAL” and “TWVAL”, skipping “ONVAL” (Multiple), leaving a gap in a drop-down menu.  Is there a way to avoid this gap?

 

Thank you,

 

Iain Marcuson

Software Engineer, Sydor Technologies

585.278.1168 | www.SydorTechnologies.com

Skype: [email protected]