Hi Andrew
Thanks for your feedback.
http://www-csr.bessy.de/control/SoftDist/csm/cvtRecord.html : cvt is
good but does not work for waveform…
Lana
It is apparently possible, but not an officially supported practice. I believe BESSY-2 do this, so Ralph should be able to help you with how they actually do it.
The blueprint that you found was something I wrote to try and get that ability included officially, but so far it hasn't gone any further than those ideas. The complication that is hinted at in the blueprint
is that the records hold a pointer to the actual breakpoint table in memory if they are using one, but there is no locking or other way to communicate with the individual record instances if the table gets modified or replaced.
2.
In general, how do you use breakpoint tables. The native one from EPICS? Or did you implement your own record types? I’m aware of one from Bessy (cvt) which looks very interesting.
The built in support routines are available to any record type, but are currently only used by the ai and ao record types in Base. They could also be used by subroutine record code.
3.
How did you handle breakpoint tables with waveform record type? Via subroutines?
That would have to be done manually (i.e. with subroutines or aSub records) at the moment unless you write your own record type to do it.
4.
In our cases, we are both interesting by having mapping tables and functions.
That would be an obviously useful thing to implement if someone hasn't already done it (what does the cvt record do?).
- Andrew