Autosave HINS

1
Autosave _at_ HINS

• Sharon Lackey
• July 10, 2008

2
What is Autosave?

• Autosave is an EPICS extension that
• Automatically saves settings in an ioc when they
  are changed.
• Loads in the saved settings on reboot of an ioc.
• Allows the user to determine what settings have
  changed since a particular file was saved.

3
Installing Autosave

• Any hardware or soft EPICS IOC can use the
  autosave extension
• The IOC must be configured and re-compiled to use
  autosave
• This has already been done for the HINS PLC IOCs
  and for the SNS LLRF IOC
• Instructions are at
• autosave Installation Instructions

4
How it works

• Request files list the device settings that need
  to be saved and restored on reboot
• Whenever one of those devices is changed, an
  update is written to the save file automatically
• A dated save file may also be written at boot
  time
• On reboot, the contents of the most recent save
  file is used to restore the settings
• If the user wants to know what settings may have
  changed since the last reboot, the asVerify
  utility can be used

5
Organization

• Request and save files are in the
  /p/iocAutosaveFiles directory under the name of
  the IOC
• hins01gt ls /p/iocAutosaveFiles
• A0-plc hins01 hinscave smtf
• hins01gt cd hins01
• hins01gt ls
• auto_settings.req auto_settings.sav0 save_res
  tore.edl
• auto_settings.sav auto_settings.sav_080702-13
  5343

6
Request File is just a list of devices
7
Save Files look like
8
Edm Utility Screen
Date and time of last reboot save file
Flashes red and green with autosave heartbeat
9
asVerify

• Add to your path /p/epics/support/autosave/R4-10
  /bin/linux-x86
• To compare present settings with an existing save
  file
• asVerify -vrd ltautosave_filegt
• where -v is verbose all saved pvs will print
• -r restores the named file
• -d (debug) increment debug level by
  one

10
(No Transcript)