Re: Question on waveform monitoring

[Tim Mooney <mooney@aps.anl.gov>]

Ron, re...,

> We have a special record to deal with digitizers, where the waveforms associated with each channel have fields with imaginative names like .ARY1, .ARY2 etc. These waveforms hold the past few pulses of Low-level RF data, and are meant to be picked up by the archiver when a trip occurs and new data are available. These internal arrays (ARY1, ARY2, etc.) are only read from the hardware (SIS or Joerger digitizers) upon a trip.
> >
> > It seems that these fields are not being successfully monitored. Two stray waveforms have appeared in the archiver, but hundreds of others have not.

In calls to db_post_events(), is the second argument a pointer to the field whose value you're posting,
e.g., 'prec->ary2' or to the buffer that contains the actual data array?  It should be the buffer.
I can't find the place where this is documented, but if you look closely at the waveform-record code, you'll see that it
posts 'pwf->bptr' when the .VAL field has changed.

-- 
Tim Mooney (mooney@aps.anl.gov; 630-252-5417)
Advanced Photon Source
APS Operations Division
Beamline Controls & Data Acquisition Group