I know that Autosave is generally used for automatically saving the values of a set of database records and restoring them at boot time, but I'd like to save a small set of values on command, and then be able to restore them on command.
I have found the create_triggered_set() function that I can run in the ioc startup script that assigns a database PV to trigger a save, and that seems to be a step in the right direction for what I want to do.
However, a couple of problems:
1) There seems to be no corresponding function to assign a PV to trigger a restore. I suppose I can get around that by using a subroutine record to call fdbrestore() when it is processed.
2) Even if I can get around issue 1), when I run create_triggered_set() in the startup script at boot time, it clobbers the existing saveset. Is there a way around this?
Perhaps I'm trying to use the wrong tool? Is there a better one for what I want to do?
--
Mike Westfall
PADSTE/ADE/AOT/IC/Controls
Los Alamos National Laboratory
(505) 667-3273
- Replies:
- RE: Question on Autosave Westfall, Michael D
- RE: Question on Autosave Mooney, Tim M.
- Re: Question on Autosave Maren Purves
- Navigate by Date:
- Prev:
Re: CSS BEAST alarm hierarchy Igor Kriznar
- Next:
RE: Question on Autosave Westfall, Michael D
- 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
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Sequencer is not monitoring Pvs from another IOC Benjamin Franksen
- Next:
RE: Question on Autosave Westfall, Michael D
- 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
2019
2020
2021
2022
2023
2024
|