Hi Vikram,
OK, then you're basically looking for two different things.
A) CaPutLog
Facility that you hook into the AccessSecurity layer. [1]
Then you can configure records for CA Put logging, i.e. any
Channel Access put operation will be logged with timestamp,
user, host, channel, old value, new value. By default logging is
done through a TCP connection, so you can set up one server, and
all your IOCs can log into that machine.
B) Archiving
Long term logging of values with timestamps is usually called
archiving in the EPICS context.
There are a whole bunch of solutions, you can pick one.
Channelarchiver [2]: the traditional EPICS archiver, written in
C, fast, stable, binary file format, clients retrieve data
through XMLRPC.
CSS-Archiver [3]: written in Java, easier to configure, more
analysis tools, good integration into CSS, archives into RDB
(Oracle, MySQL, PostgreSQL).
Archive Appliance [4]: Java web service, easiest to configure,
scales well, lightning fast (especially for retrieval), binary
file format (pluggable).
[There are more solutions. The keyword lists for the three
choices I suggested are far from complete and just to give a
first idea.]
Well ... now it's your turn to check things out and make up your
mind.
Cheers,
~Ralph
ps. If a Debian-based Linux distribution is ok for you:
epics-base, caputlog and channelarchiver are available as Debian
binary packages and will get you started very fast and easy. [5]
[1]
http://www-csr.bessy.de/control/SoftDist/caPutLog/
[2]
http://epicschanarch.sourceforge.net/
[3]
http://sourceforge.net/apps/trac/cs-studio/wiki/RDBArchive
[4]
http://epicsarchiverap.sourceforge.net/
[5]
http://epics.nsls2.bnl.gov/debian/
On Fri May 17 2013 14:17:05 GMT+0200 (CEST), Vikram Bhagat
<[email protected]>
wrote: