Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Timeout error when measuring frequency using DAQ-device 6024E

Solved!
Go to solution
Hello!
 
I am to build a simple data acqusition application for measuring paramteres in a filtration test setup and have experienced som problems. Is anyone able to help me?
 
For this purpose I am using a 6024E DAQ card connected to a SCB-68 Connector Block. I am running LabVIEW 8.5 and have installed NI-DAQ 8.6.1. I am trying to read the frequency of a pulse-based flow The error I get is
 
Error -200474:
 
Possible reason(s):
Measurements: Specified operation did not complete, because the specified timeout expired.
 
 
0 Kudos
Message 1 of 4
(4,310 Views)
I think I hit the submit button a bit to early. Here is the complete post:
 
 
I am to build a simple data acqusition application for measuring paramteres in a filtration test setup and have experienced som problems. Is anyone able to help me?
 
For this purpose I am using a 6024E DAQ card connected to a SCB-68 Connector Block. I am running LabVIEW 8.5 and have installed NI-DAQ 8.6.1. I am trying to read the frequency of a pulse-based flow meter using the function DAQmx Read.vi (see attached file) when I get the following error: 
 
Error -200474:
 
Possible reason(s):
Measurements: Specified operation did not complete, because the specified timeout expired.
 
The error appears in DAQmx Read.vi few seconds after running the VI. I have uninstalled and reinstalled my NI software in hope that the problem would dissappear. As long as the errors are relayed out of the while loop the function delivers seemingly correct values, but also occasionally values that are off the chart, especially at lower frequencies.
 
Have anyone experienced this problem before and is able to help me? Please ask me question if something seems unclear.
 
Thank you in advance!
0 Kudos
Message 2 of 4
(4,304 Views)
0 Kudos
Message 3 of 4
(4,279 Views)
Solution
Accepted by topic author AnswerMe
 

Hello

I suggest you to look at this KB, it provides to give you an interesting workaround to solve the problem:

http://digital.ni.com/public.nsf/allkb/4E017925BDF2DC2D862572E6007C9594?OpenDocument  

Matteo
Message 4 of 4
(4,140 Views)