Experimental Physics and
Industrial Control System

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

Hi Mike,

The run-time save and restore part of autosave uses channel access for scaler PVs, so it can handle scalar PVs in another ioc.  Array PVs, however, are currently read and written using database access, so they must be in the ioc running autosave.

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

And a third problem:

The set of values I need to save and restore may span multiple IOCs.
So I'm thinking Autosave is not the right tool at all.

> 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?

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System