Difference between revisions of "What PV Save and Restore Tools are available"
(Created structure, using autosave as an example.) |
KayKasemir (talk | contribs) |
||
| Line 15: | Line 15: | ||
== Host-based Tools == | == Host-based Tools == | ||
=== XAL 'score' === | |||
The XAL collection of high-level applications includes 'score': | |||
A Table of PV names, each with a current value and a saved value. | |||
One can see which PVs differ from their saved state, | |||
restore them etc. | |||
=== CSS 'PV Table' === | |||
Similar to 'score', but simpler and still unter development. | |||
Saves values to XML files, no connection to RDB. | |||
=== ... === | === ... === | ||
... | ... | ||
Revision as of 15:33, 28 June 2007
There are a number of different tools available within the EPICS community for saving and restoring values of PVs. This page gives somewhere for them to be briefly described, since they all have somewhat different characteristics. This page may be incomplete; if you know of a published tool that is not described here, please consider adding it, or email <volunteer anyone?> about it.
IOC-based Tools
SynApps Autosave
Autosave automatically saves the values of EPICS process variables (PVs) to files on a server, and restores those values when the IOC is rebooted.
...
...
Host-based Tools
XAL 'score'
The XAL collection of high-level applications includes 'score': A Table of PV names, each with a current value and a saved value. One can see which PVs differ from their saved state, restore them etc.
CSS 'PV Table'
Similar to 'score', but simpler and still unter development. Saves values to XML files, no connection to RDB.
...
...
