Hello,
On your question:
>> Now the question to the group: Is there a better way? And how would you implement my idea?
I would map the data structure of the system to EPICS rather than the other way around. So I would compose PVs like FHIFEL:llpg_1:Ch1-Width, FHIFEL-llpg_1:Ch1-Delay, etc.
Cheers
Anders
On 2025-08-13, 07:27, "Tech-talk" <[email protected]> wrote:
One thing that has been on my mind for a long time:
We have developed our own devices such as llrf generators, pulse generators, etc., which run on a Raspberry Pi or BeagleBone Black as a management interface.
We then use p4p on that devices and offer the data points in a pva structure tailored to the respective device.
(base) hactar:~ junkes$ pvinfo FHIFEL:llpg_1
Server: 141.14.134.173:5075
epics@felpvagate:~$ pvinfo FHIFEL:bbamp_1
Now we are experiencing some issues with it.
1.) The ArchiverAppliance cannot archive these PVs.
2.) Our 'old' Save&Restore supports channel access only.
How should we best deal with this?
My current idea is to implement a service (Python?) that reads this user-defined structure with pva, breaks down the structure into individual NT-pvs and offers these 'individually' via pva (for the Archiver Appliance, for example) and,
at the same time, also offers these PVs as ca-PVs for channel access (for our Save&Restore).
Now the question to the group: Is there a better way? And how would you implement my idea?
------------------------------------------------------------------------------
Fritz-Haber-Institut | Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4): (+49 30) 8413-5900
------------------------------------------------------------------------------
“Sorry I’m a bit late, had a terrible time…
All sort of things cropping up at the last moment. Uh, how are we for time?”
—Zarquon's address to Milliways