Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Fri, 14 Sep 2018 10:54:05 -0500

On 09/14/2018 09:08 AM, Iain Marcuson wrote:
> That is what I did in my first implementation, although due to how I set
> things up I was modifying the ADCore template, which doesn’t seem very
> portable.  I may have to make a separate AreaDetector project for our
> sensor and modify that.

You should be able to load another .db file that just overwrites the
field values that were set for this record instance by the original
ADCore database file. As long as the record type is the same as the
original and the startup script hasn't set the dbRecordsOnceOnly
variable there is nothing preventing you from setting record fields for
a record in more than one .db file, the last value set always wins.

- Andrew

> *From:* Mark Rivers <[email protected]>
> *Sent:* Friday, September 14, 2018 10:05 AM
> *To:* Iain Marcuson <[email protected]>;
> [email protected]
> *Subject:* RE: Bypassing Options in ImageMode in AreaDetector
> 
>  
> 
> 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
> 
>  
> 
>  
> 
> *From:* [email protected]
> <mailto:[email protected]> <[email protected]
> <mailto:[email protected]>> *On Behalf Of *Iain Marcuson
> *Sent:* Friday, September 14, 2018 8:51 AM
> *To:* [email protected] <mailto:[email protected]>
> *Subject:* Bypassing Options in ImageMode in AreaDetector
> 
>  
> 
> 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 <http://www.sydortechnologies.com/>
> 
> Skype: [email protected]
> <mailto:[email protected]>
> 
>  
> 

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System