You can make a standard NTTable with 4 columns (Width Delay ExtraDly Atten) and 2 rows for Ch1 and Ch2. Or 8 columns with 1 row if you prefer.
I can confirm that the archive appliance knows how to archive an NTTable.
Hi,
I am running a P4P server on an embedded system and offer the following structure:
epics@felpvagate:~$ pvinfo FHIFEL:llpg_1
FHIFEL:llpg_1
Server: 10.0.0.87:5075
Type:
structure
ushort Ch1_Width
ushort Ch2_Width
ushort Ch1_Delay
ushort Ch2_Delay
ushort Ch1_ExtraDly
ushort Ch2_ExtraDly
ushort Ch1_Atten
ushort Ch2_Atten
Unfortunately, the archiverAppliance cannot monitor/archive these.
Was ist der beste Weg um diese Werte zu archivieren?
1.) Should the 8 values be made available as ‘individual’ scalar PVs on the embedded system as well?
2.) Run a ‘converter’ on another system that maps the custom struct to scalar PVs?
3.) Another idea ?
Danke Heinz
------------------------------------------------------------------------------
Fritz-Haber-Institut | Phone: (+49 30) 8413-4270
Heinz Junkes | VC:
https://zoom.fhi.berlin/junkes
Faradayweg 4-6 | Visitors: Hittorfstrasse 29 (Bld S (Slough House) )
D - 14195 Berlin
------------------------------------------------------------------------------
“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