Experimental Physics and
Industrial Control System

"Mooney, Tim M." <[email protected]> · Thu, 6 Mar 2014 16:24:33 +0000

Hi Mike,

Autosave 5.1 has a facility called configMenu that you should look at.  Here's a brief description from the docs
(http://www.aps.anl.gov/bcda/synApps/autosave/autoSaveRestore_R5-1.html):

"Autosave also contains a facility, called configMenu, for creating, saving, finding, restoring, and verifying IOC configurations (that is, sets of PV values). configMenu is roughly comparable to the EPICS Backup and Restore Tool, BURT, but it uses autosave files, and is driven by EPICS PVs, so it can be used manually, by software clients, and by other IOC code."

Tim

________________________________________
From: [email protected] [[email protected]] on behalf of Westfall, Michael D [[email protected]]
Sent: Thursday, March 06, 2014 10:09 AM
To: [email protected]
Subject: Question on Autosave

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

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System