We experience erroneous errors -10403 when oldDataStop=1.
_db_check also doesn't work well if oldDataStop=1
Nidaq 6.51,6.6,6.7.
Phil Salamone
Keith Farkas wrote:
> HI,
>
> The question I have concerns the: implications of error codes when
> enabling oldDataStop during the generation of waveforms. I would
> greatly appreciate any insight anyone may have on the questions
> I note below.
>
> While the documentation provided by National Instruments is fairly good,
> it does not discuss which of the many error codes are warnings rather
> than errors, and what an application should do when one of the
> errors is detected.
>
> Background
> -----------------
> I am using a PCI-6713 board to regenerate a waveform that I previously
> sampled using a PCI-6052 data acquision syste
m. I am using double-
> buffered waveform generation. Because I want to generate a given
> portion of the waveform only once, I have configured the PCI-6713 to
> not allow the regeneration of old data (i.e., I set oldDataStop = 1 in the
> call to WFM_DB_Config).
>
> Questions
> --------------
> I have noticed that when I enable oldDataStop calls to WFM_DB_HalfReady
> and WFM_DB_Transfer return errors. In particular, the error codes
> I have seen are:
>
> -10608 (noTransferInProgError) returned by wfm_db_halfready
> -10803 (transferStoppedError) returned by wfm_db_transfer
>
> My questions:
> - In the case of wfm_db_halfready, how do I restart the waveform
> generation? When error -10608 is returned by this function, the
> half-ready output flag is not asserted. Thus, it does not appear that
>
> I can just ignore the error.
>
> - In the case of wfm_db_transfer, I have been ignoring the resulting
> error. Should I be?
>
> - Are there other errors I may encounter by
turning on oldDataStop
> of which I should be aware?
>
> Again, any help would be greatly appreciated.
>
> -Keith
