Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

lv2016, sampleclk of DAQ not initializing anymore

Solved!
Go to solution

Hi all,

I am a beginner in labview. I am using a cDAQ-9188 and since I transfered a VI from lv2014 to lv2016 which initialize the DAQ, the sample clock is not initialized anymore.

Is this a known bug? How can I go around it?

DAQinitialize.png

Thank you for your help!

0 Kudos
Message 1 of 6
(2,693 Views)

Hello qqun,

can you post the code instead of the picture?

What happens if the enable disable structure part is changed? 

Is the external clock connected?

What is the error number you get?

 

best regards
Alexander
0 Kudos
Message 2 of 6
(2,650 Views)

Hello Allexander,

Here is the code. The external clock is connected.

The error says that the sampling rate is too high for the DAQ to play out a waveform (OnBoard clock is 20 or 80 MHz whereas the DAQ only supports 25kHz). I will look up the exact error number.

If I change the enable structure, I get the same error. 

The only case I could make it work was by initializing the SampleClock directly with the external clock, not having the enable structure and setting the external clock to a 25kHz sampling rate. 

But I could not make the enable structure change the SampleClock properties.

Thanks and best regards,

Laetitia

0 Kudos
Message 3 of 6
(2,635 Views)

Hello qqun,

this workaround is working on your side, if i understand you correct

test.png

Is this okay for you or must the external clock devided, because they is faster?

 

 

 

best regards
Alexander
0 Kudos
Message 4 of 6
(2,623 Views)
Solution
Accepted by topic author qqun

Hello qqun,

with this setting in the screenshot from me, the divider will be set automatically in the driver, the external clock should be devided, or you can disable the DAQmx Timing vi and only use the properties, like in this way, then also the devider will be set automatically.

Devider.png

best regards
Alexander
0 Kudos
Message 5 of 6
(2,621 Views)

Hello Duffy2007,

Thank you for your answer!

Yes, the workaround of the first screenshot work in the sense that the VI does not complain anymore. However, the data are now really strange. It used to work with the divider and the data were fine. 

I will try using the property node instead of the VI as you suggested. 

Thank you and best regards,

Laetitia

0 Kudos
Message 6 of 6
(2,617 Views)