DAQEvent=2 not fired when double buffered operations stop

[michael_b]

Hi,

I am using Config_DAQ_Event_Message with DAQEvent==2 to get an event when synchronous DAQ and WFM are finished. This works fine with single buffered operation, but i get no event in double buffered mode ?

Especially I like to get an event in case of Buffer-Underrun etc. errors.

My hardware: PCI6111
Software: NIDAQ6.9.3 with VisualC++

Thanks in advance
Michael

[Spencer S.]

Michael,

Have you been able to see an error stop an operation, but not generate the event? With a continuous operation, I do not believe that the event will be generated if the operation is intentionally cleared.

Let me know.

Spencer S.

[michael_b]

Hi Spencer

Thanks for your reply.

Indeed I don't get an event if the double buffered operation stops with an error (usually -10608 (noTransferInProgError) and -10843 (underFlowError)).

To be more precise: I have synchronized WFM and DAQ operations via the RTSI bus. And in single buffered operation I get the EventType==2 only if its source is set to the DAQ part. If I set it on WFM via

Config_DAQ_Event_Message(iDevice, 1, "AO0", 2,0,0,0,0,0,0,0,(u32)FinishedCallback);

I don't get any event at all.

Best regards,
Michael

[TN]

Hi Michael,

One of the possible causes of this error-10608 is a high update rate. The update rate might be high enough that you are not allowing enough time to fill the buffer with new data. This error can also be the result of having the regeneration option, within software, set to OFF. If you turn the regeneration option to ON, the error will go away. You can also reduce the update rate to see at which point you stop getting the error -10608

I found the following links about errorcode -10843:

http://digital.ni.com/public.nsf/websearch/EC38736BBF430DDC8625677C006F395C?OpenDocument

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000CA780000&ECategory=Measurement+Hardware.Digital+I%2FO

regards

TN

[TN]

Hi Spencer,

Erro -10608:
One of the possible causes of this error is a high update rate. The update rate might be high enough that you are not allowing enough time to fill the buffer with new data. This error can also be the result of having the regeneration option, within software, set to OFF. If you turn the regeneration option to ON, the error will go away. You can also reduce the update rate to see at which point you stop getting the error -10608.

Error 10843:
see link
http://digital.ni.com/public.nsf/websearch/EC38736BBF430DDC8625677C006F395C?OpenDocument

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000CA780000&ECategory=Measurement+Hardware.Digital+I%2FO

Regards
TN