Because database puts write the new data into the waveform buffer before
the device support read_wf function is called when the record
subsequently processes(by process passive), you can just have the
read_wf write to the hardware.
Carl
Steven Hartman wrote:
I am writing support for an arbitrary waveform generator (Joerger Model
VDACM 8 channel, 16-bit, 100kHz, waveform generator with 32k memory per
channel).
Is there an EPICS record which is appropriate for such a device? The aao
record seems like a possibility, but a search of tech-talk archives from
1996 and 2000 revealed a number of problems with this record which don't
appear to have been incorporated into later releases (looking at
aaoRecord.c from R3.13.10).
The waveformRecord is close, but is designed for readback, not output like
I need for this device. The gensub record may be a way to deal with it, if
necessary.
Is anyone using a similar device, and if so, what record are you using?
Also, any suggestions on user interface for loading and modifying
waveforms?
Thanks,
--
Carl Lionberger
Control System Software Engineer
Berkeley National Laboratory (LBNL)
(510)486 7503
- Replies:
- Re: EPICS waveform output record Luedeke Andreas
- References:
- EPICS waveform output record Steven Hartman
- Navigate by Date:
- Prev:
RE: EPICS waveform output record Rogind, Debbie
- Next:
Re: EPICS waveform output record Luedeke Andreas
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
EPICS waveform output record Steven Hartman
- Next:
Re: EPICS waveform output record Luedeke Andreas
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
<2004>
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|