EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: autosave - different PV to read and write
From: Mark Rivers via Tech-talk <[email protected]>
To: 'Ryan Pierce' <[email protected]>
Cc: "'[email protected]'" <[email protected]>
Date: Tue, 20 Aug 2019 15:16:39 +0000
Hi Ryan,

> I'm wondering if it is possible to configure autosave to read one PV and record its value in a save file, but on recovery, to write that value to a different PV

I don't think you can do that with autosave.

If the driver was written with asynPortDriver then you could simply remove the PZ from autosave.  The driver would read the PZRBV into the same parameter during initialization.  The PZ output record would do an initial read of the parameter value, and set PZ to that.  This is part of the "bumpless reboot" feature of asyn device support, meaning output records can get their values from the hardware when the IOC starts up.  If there are autosave values then they will then override that initial value.

However, the Canberra ICB support predates asynPortDriver and does not work this way, PZ and PZRBV are not linked as they should be.

However, you can still easily achieve what you want.  You just add another record to your database.

record(ao, "$(P)$(AMP)SyncPZ") {
    field(DOL, "$(P)$(AMP)PZRBV")
    field(OMSL, "closed_loop")
    field(OUT, ""$(P)$(AMP)PZRBV PP")
    field(PINI, "YES")
}

This record will process once at iocInit.  It will read the value from PZRBV and write it to PZ.

Mark

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Ryan Pierce via Tech-talk
Sent: Tuesday, August 20, 2019 8:31 AM
To: [email protected]
Subject: autosave - different PV to read and write

I'm wondering if it is possible to configure autosave to read one PV and record its value in a save file, but on recovery, to write that value to a different PV. I am thinking along the lines of the .req file containing both the PV to read and the PV to write in the case where it would be different.

Example: The Canberra ISC amplifier can be placed into a mode where it automatically determines the Pole Zero value based on the input signal. 
This can be done once, and the measured value can continue to be used (assuming the detector or shaping time aren't changed.) If the IOC restarts, it would be helpful to restore this along with all the other settings. This can be read from $(P)$(AMP)PZRBV but it must be set in $(P)$(AMP)PZ

I'm guessing the concept of one PV to write with a separate readback PV is common. Has this been addressed, or is there a need for this?

Regards,

Ryan



References:
autosave - different PV to read and write Ryan Pierce via Tech-talk

Navigate by Date:
Prev: RE: NDStats plugin shows huge numbers for Eiger detector (areaDetector 3.7) Mark Rivers via Tech-talk
Next: Re: NDStats plugin shows huge numbers for Eiger detector (areaDetector 3.7) Bruno Martins via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
Navigate by Thread:
Prev: autosave - different PV to read and write Ryan Pierce via Tech-talk
Next: NDStats plugin shows huge numbers for Eiger detector (areaDetector 3.7) Sobhani, Bayan via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  2021  2022  2023  2024 
ANJ, 20 Aug 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·