Error -200019 using External Clock

[cpede]

When I use external clock for my AI it seems to run fine if the external clock pulses are available at

the beginning of the measurement. I provide the external clock of 10kHz on the PFI0 input, and set the

clock to more or the same in the timing function. I acquire a fixed number of samples in each run.

But if the signal on PFI0 is high (or low) for e.g. 10 sec. after the measurement is started, and I then

provide the 10kHz signal the error -200019 occurs right away.

I have also tried to use the PFI0 as the start trigger at the same time, but the same result.

Any ideas?

-cpede

[cpede]

I see the error on my NI6220 and NI6143 boards, but on my NI6070E it seems to work?

-cpede

[Otis]

Hi cpede,

I found a KnowledgeBase about Error -200019:
What causes Error -200019 when increasing the sampling rate and an external trigger?

It sounds like the problem is that the sample rate is causing problems.  I would also be really suspicious of a noisy clock or a clock that hovers near the 2.2 V range so that it could quickly toggle between positive and negative.

One reason that it could be working with the PCI-6070E and not the PCI-6220 is because the PCI-6070E runs at 1.25 MS/s compared to 0.25 MS/s for the PCI-6220.

I like the idea of triggering if you know that the first change of your clock may not come for over about 10 seconds.  You may want to make the start trigger and the clock signal be on different PFI lines.  You should be able to simply make a hardware connection between the two lines.

Regards,

[matt24]

Hi
I've got a problem with this error code as well.
I'm trying to read an analog input Signal everytime I get a rising Flank of an Sensor.
The Frequency of the Sensor Signal is about 18Hz. The clock frequency is set to 100kHz
As soon as I start this Vi I get the mentioned error code.
The VI was working just fine on a PCI 6229 Card but since I use it on a PCI 6122 I've got this problem.
Has anyone got an Idea what is the reason for this Problem.

I've allready:- checked the Signal quality
                    - tried diferent PFI Inputs PFI 5 and PFI 7
                    - the clock frequency is set to 100kHz

regards

Matthias

[David L.]

Hi Matthias,

Do LabVIEW shipping examples exhibit the same problem? What happens with different sampling rates? We may be able to help further if we can see your code.

[matt24]

Hi David,
I tried the LabView Shipping example  Acq&Graph Voltage-Ext Clk.vi and had the same problem. I allready tried to use different inputs for the ext clk Signal (PFI 5, PFI 7).
Unfortunately I can't post my vi at the moment. But it's quite similar to the example.

regards

Matthias

[David L.]

Hi Matt,

Please try a shipping example which uses an internal clock. Although you have checked your signal, I am curious if your card errors while using the internal clock (Cont Acq&Graph Voltage-Int Clk.vi). Also, does this error occur if you use your external clock, but acquire a very small number of samples. This way, if your signal did happen to have a small glitch which was causing this error, it would not be seen. (I want to eliminate that there may be a very small glitch which could be overlooked).

Lastly, what is the result of using another sample clock source? Please try the example ‘Multi-Function-Ctr Pulse Train Generation for AI Sample Clock.vi’ (Help >> Find Examples… >> Hardware Input and Output >> DAQmx >> Synchronization >> Multi-Function). The example creates a counter pulse train, and uses this as the sample clock. The example originally uses the CtrxInternalOutput, but you can also play with manually connecting the counter to a PFI line, and using that PFI line as your AI clock.

[matt24]

Hi David,
I managed to get my Hands on a Signal generator. With the Generator the VI worked just fine.

Regards

Matthias