Experimental Physics and
| |||||||||||||||||
|
My application is device support into a shared memory area that other, non-epics, processes interact with. The application needed for some of the PVs in shared memory to be adjusted either from a remote location via channel access or locally from the shared memory client application. The user wanted to be able to monitor the data in shared memory and also be able to set the value there via the same PV. I am using IOC core, (3.14.1 on a windows platform) instead of a CA Server. I don't think you should use the PUTF field. It is for internal use by dbAccess. I think your goal is the following: Implement device support that connects EPICS records to shared memory. If a CA client writes to the record then a write to shared memory should occur. If a shared memory location changes value than a value should be read from the shared memory and put in the record. Why not do the following: As you suggested implement device support for input records, i.e. aiRecord, biRecord, mbbiRecord, etc. Keep a field that determines if device support should read or write the shared memory. It is normally set to write. When you have detected that shared memory has changed, set this field to read and ask that the associated record be procesesed. Note that callbackRequestProcessCallback can be used to request processing. Marty Kraimer
| ||||||||||||||||
ANJ, 10 Aug 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |