Experimental Physics and
Industrial Control System

"Kasemir, Kay" <[email protected]> · Fri, 12 Apr 2013 08:30:40 -0400

Hi:

Depending on what version of autosave you are using, you can work without any standalone autosave config files.
Instead, you add annotations to your database records:

record(type, "$(S):SomeRecord")
{
    info(autosaveFields, "VAL LOW")

The granularity of autosave configuration files is thus just the database files:
One database per device? -> That database file also contains the autosave info.

When you create new *.db files, it is easy enough to add those info annotations right away.
If your application uses existing *.db files that you don't want to edit, note that you can load multiple definitions of the same record. You can load a second database file that contains the same record names, but only the missing info annotations:

record(type, "$(S):SomeRecord")
{
    info(autosaveFields, "VAL LOW")

In your IOC startup file you then add a command that auto-creates the request files from those database annotations:

makeAutosaveFileFromDbInfo("autocreated.req", "autosaveFields");
create_monitor_set("autocreated.req.req", 5)

-Kay

On Apr 11, 2013, at 19:43 , Emmanuel Mayssat wrote:

> I have several device running in a master IOC.
> I would like to use autosave.
> 
> The issues is that I would like to break down my master IOC into smaller ones at will (for development purpose).
> I would like to use several req files and restore files for autosave.
> In other words, I would like to have one autosave configuration per device in the master IOC.
> 
> Q: Is there a limitation to the number of files and instance of autosave in a single IOC?
> 
> 
> 
> Regards,
> --
> Emmauel

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System