LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Counter Examples Specified Resource Is Reserved

Solved!
Go to solution

I changed the output also to ao and same situation

cwhw112_0-1708307343108.png

 

0 Kudos
Message 11 of 18
(464 Views)

if i leave the counter as PFI8 and put the ouptut to AO it counts the single pulses but gives the same error for 2

0 Kudos
Message 12 of 18
(462 Views)

I think you missed the main point of my first answer back in msg #2.  Your device uses up *both* counters when you configure one to generate a finite pulse train.  So you can't do both that *and* have another edge counting task.

 

The suggestions about using a dummy finite AI or AO task are to demonstrate that a *different* way to generate a finite set of pulses.  You would need to use one of those *instead* of a finite pulse train counter task, not in addition to.

 

The only other thing you'll need to add is the DAQmx Export Signal function (or property node) to export the AI or AO sample clock out to a particular PFI pin.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 13 of 18
(445 Views)

sorry my current labview level is not where it needs to be to understand your comments, to me it sounds like - "in order to fly a plane, you get in it and fly it"

i would need to see an example block diagram 

it that is beyond the scope of this post, i can just mark it as complete or delete it (not sure the general advice of -just use ai ao will help others)

0 Kudos
Message 14 of 18
(423 Views)

You need to stop trying to generate a finite pulse train with a counter task because that will use up both counters on your device and you won't have one available for doing edge counting.  Go back to my answer in msg #7 and run *only* the 2 examples I mentioned.  Don't also try to run a finite pulse train with a counter. 

 

That pair of examples illustrates that an AI task can be used to generate a specific finite # of sample clock pulses.  Insert the following call to DAQmx Export Signal before you start the AI task to put the sample clock pulses out on PFI0.  That makes it available to physically wire to any external device that needs to receive your finite pulses.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 15 of 18
(407 Views)

you dont reference any examples by name, only "shipping examples" but my labveiw version doesnt show any 

cwhw112_0-1708563005942.png

 

0 Kudos
Message 16 of 18
(391 Views)
Solution
Accepted by topic author cwhw112

Since this thread is peppered with examples that you previously found without noted difficulty, I'm tentatively interpreting the last message as sarcastic and trolling and am thus bowing out.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
Message 17 of 18
(385 Views)

Mea culpa, I was overly hasty to suspect being trolled, the OP remains sincere in trying to get things working.  This was cleared up in a PM (and thanks for reaching out).   One key bit of new info:

 

I found another NI device with a counter and think I can wire the 2 devices together and output pulses from the one device and count from another and hopefully wont get the error.

 

Yes, that should work.  I'd recommend you also run a wire to connect the Digital Grounds on the two devices.  There will be a lot of DGND terminals to choose from and it shouldn't really matter which one you use.  I typically just choose one near my signal wire.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 18 of 18
(347 Views)