Counter/Timer

cancel
Showing results for 
Search instead for 
Did you mean: 

Pulse generation problem with PCI-6601, DAQmx 7.4

I have a problem with Daqmx 7.4, PCI-6601. In the attached example (runs at the start of my progam), I configure three counters and a digital input & bundle the task ids to a cluster. Note that counter ctr1 is treated differently from ctr0 and ctr2 as I want to start that later on in the code - ctr 0 and 2 should run non-stop.

My problem is that the first time I press run (after Labview 7.1 has loaded), the output of ctr2 is constantly high. It is not treaded any differently to ctr0 in my code. Altering the cuty cycle makes no difference. When I press stop & run my application again (without restarting labview), ctr 2 then behaves itself. In other words, this only happens on first run after loading the program.

Any clues? I've tried running device resets etc before this, but nothing seems to help.

Cheers,

Dougie
0 Kudos
Message 1 of 3
(3,298 Views)
Evening Dougie, I've had a look at your code and reseached the issue on the Internal Tech Support portal and I only really have sugestion. The only difference that I an see in your code is that a "0" is wired into the delay time on the DaQmx task for ctr2. Try taking out that initial delay constant. Or you may consider is error clustering the two task in order so that they are completed one after the other. If these don't work then come back on the forum In the mean time I'll look into the matter for you. Hope this helps AdamB National Instruments
Applications Engineering Team Leader | National Instruments | UK & Ireland
0 Kudos
Message 2 of 3
(3,286 Views)
Evening Dougie, (Sorry about the previous post, my computer seems to have problems with HTML editing at the moment)
I've had a look at your code and investigated the issue on the Internal Tech Support portal and I only really have 2 suggestions.

The only difference that I an see in your code is that a "0" is wired into the delay time on the DaQmx task for ctr2.
Try taking out that initial delay constant.
Or you may consider connecting the error clusters of the two tasks in order, so that they are completed one after the other.

If these don't work then come back on the forum.
In the mean time I'll look into the matter for you.
Hope this helps

AdamB
National Instruments
Applications Engineering Team Leader | National Instruments | UK & Ireland
0 Kudos
Message 3 of 3
(3,256 Views)