Which is very different from the underlying records:
$ pvget -v BL45P-MO-PANDA-01:TTLOUT1:VAL
BL45P-MO-PANDA-01:TTLOUT1:VAL epics:nt/NTScalar:1.0
string value ZERO
alarm_t alarm
int severity 0
int status 0
string message
time_t timeStamp 2024-06-08 15:34:04.600
long secondsPastEpoch 1717857244
int nanoseconds 600281953
int userTag 0
structure display
string description TTL output value
It would be nicer to have value, alarm and timeStamp, and give it a structure ID. I suggest we do this:
$ pvget -v BL45P-MO-PANDA-01:TTLOUT1:PVI
BL45P-MO-PANDA-01:TTLOUT1:PVI epics:nt/NTPVI:1.0
structure value
structure label
string rw BL45P-MO-PANDA-01:TTLOUT1:LABEL
structure val
string rw BL45P-MO-PANDA-01:TTLOUT1:VAL
structure val_delay
string rw BL45P-MO-PANDA-01:TTLOUT1:VAL:DELAY
alarm_t alarm
int severity 0
int status 0
string message
time_t timeStamp 2024-06-08 15:34:04.600
long secondsPastEpoch 1717857244
int nanoseconds 600281953
int userTag 0
structure display
string description PVs making up Interface for TTLOUT1
This would require:
Some structure to get the metadata into the root. Something like this when the first call to add_pvi_info_to_record happens:
At the moment we have a structure like:
Which is very different from the underlying records:
It would be nicer to have value, alarm and timeStamp, and give it a structure ID. I suggest we do this:
This would require:
add_pvi_info_to_record
happens:value.
notpvi.