Counting 3 pulse outputs on the 9178

Hello everyone,
Please note that I am very new to Labview. My issue is related to measuring 3 independent pulse outputs.
Currently I am using a 9178 chassis. Two pulse outputs are coming from Omega FTB800B Pulse meters (water flow) which should output 20 pulses/gallon of water flow. The third pulse output originates from a wattnode pulse meter. I am attempting to create a very simple vi (to test all three outputs).
The wattnode seems to be working perfectly and the pulse outputs seem reasonable (connected to a 9402 card).
The two flow meters, on the other hand, are giving me some trouble. I have attempted to run them through both the 9402 card and the two onboard pfi ports.
The wattnode works using the daq assistant and selecting edge count. Since the Omega flow meters are not supplying voltage or current (reed switch), I figured this was a good guide to count pulses internally https://decibel.ni.com/content/docs/DOC-9061. Unfortunately I have been unable to measure the pulse outputs using the aforementioned method.
I have one USB-6009 unit which does not seem to have a problem measuring flow from either meter (one at a time due to the internal counter limitation).
Please see the attached vi examples
Thanks
Attachments:
WaterMeter.vi ‏23 KB
Wattnode_VI.vi ‏52 KB
USB-6009.vi ‏49 KB

Thanks for the reply Nick-A!
I believe the WaterMeter VI originated from the example finder section of Labview. There seem to be a few additional prorams which help display pulses counted by the edge counter; but, the counter portion of the code appears almost identitcal to the WaterMeter VI.
I tried utilizing the usb 6009 vi format (DAQ assistant) through the 9402 card. For some reason, I do not even measure pulse readings while running the project in the DAQ assistant properties window. Both flow meters produce the same results when connected to the aforementioned card (I have connected the flow meters to each of the 4 BNC ports). Please correct me if I am wrong, but shouldn't pulse count appear through the DAQ assistant (even if there is no other coding)?
Thanks,
Daniel

Similar Messages

How to get a pulse output at the start of a sine wave which is the input?

i am working on a comparator that generates a pulse for the positive cycle of a sine wave.but i want to get a pulse of shorter duration at the start of a sine wave (using labview) please suggest

Hello;
You can synchronize one of the general purpose counters your board have to the analog input operation. By doing that, you can have your analog input starting the counter operation which will generate the desired pulse. Moreover, you can even specify the delay and width of that pulse. For more information on how to synchronize DAQ operations you can refer to an Application Note named "Advanced Synchronization Techniques for Data Acquisition" which can be found at our web site.
Hope this helps.
Filipe

Count 4th consecutive pulses from the analog output of the encoder

Hi
Iam getting analog output from the encoder and i want to count the 4th peak of the analog signal. Kindly suggest the best method Once 4th pulse is detected counter will increments.
Pl refer the encoder output .
Thanks
Attachments:
encoder sig.JPG ‏26 KB

Whatever you've counted using your logic, divide it by 4 and convert it to an integer (towards negative infinity)..!!
This should work.
I am not allergic to Kudos, in fact I love Kudos.
Make your LabVIEW experience more CONVENIENT.

Buffered event counting. Why can't I explicitly sequence generating the Sample Clock Pulse and reading the counters?

At irregular occasions I need to grab counts from several counters, and buffering the counts must be done simultaneously for all counters. I'm modeling my approach after zone.ni.com/devzone/cda/tut/p/id/5404 which someone kindly pointed out in an earlier thread. However, that example only uses one counter, and you can't test the synchronization with only one counter, so I am using two counters configured the same way, and they're wired to a single benchtop signal generator (for example at 300 kHz).
What I want to do, I can test in a loop with a somewhat random wait in it. I want to drive a hardware digital output line high for a few ms and then low again. The hardware line is physically connected to terminals for my timing vi's Sample Clock Source and so will cause them to buffer their counts for later reading. After I pulse this line, when I know new good buffered counts await me, I want to read both my counters. If their bufferings are simultaneous, then each counter will have counted the same number of additional counts since the last loop iteration, which I can check by subtracting the last value sitting in a shift register and then subtracting the two "additional counts" values and displaying this difference as "Diff". It should always be 0, or occasionally +1 followed immediately by -1, or else the reverse, because buffering and a count could happen practically at the same moment.
When I do this using a flat sequence to control the relative timing of these steps, so the read happens after the pulse, the counters often time out and everything dies. The lengths of time before, during, and after the pulse, and the timeout value for the read vi, and the size of the buffer and various other things, don't seem to change this, even if I make things so long I could do the counting myself holding a clipboard as my buffer. I've attached AfterPulse.vi to illustrate this. If I get 3 or 10 or so iterations before it dies, I observe Diff = 0; at least that much is good.
When I use two flat sequences running in parallel inside my test loop, one to control the pulse timing, and the other to read the counters and do things with their results, it seems to work. In fact, Diff is always 0 or very occasionally the +/- 1 sequence. But in this case there is nothing controlling the relative timing such that the counters only get read after the pulse fires, though the results seem to show that this is true. I think the reads should be indeterminate with respect to the pulses, which would be unreliable. I don't know why it's working and can't expect it to work in other environments, can I? Moreover, if I set some of the pulse timing numbers to 1 or 2 or 5 ms, timeouts start happening again, too. So I think I have a workaround that I don't understand, shouldn't work, and shouldn't be trusted. See SeparateSequence.vi for this one.
I also tried other versions of the well-defined, single sequence vi, moving the counter reads to different sequence frames so that they occur with the Sample Clock Source's rising edge, or while it is high, or with the falling edge, and they also often time out. I'll post these if anyone likes but can't post now due to the attachment limit.
Here's an odd, unexpected observation: I have to sequence the reads of the counters to occur before I use the results I read, or else many of the cycles of this combine a new count from one counter with the one-back count from the other counter, and Diff takes on values like the number of counts in a loop. I though the dataflow principle would dictate that current values would get used, but apparently not so. Sequencing the calculations to happen after the reads fixes this. Any idea why?
So, why am I not succeeding in taking proper control of the sequence of these events?
Thanks!!!
Attachments:
AfterPulse.vi ‏51 KB
InSeparateSequence.vi ‏49 KB

Kevin, thanks for all the work.
>Have you run with the little execution highlighting lightbulb on? -Yes. In versions of this where there is no enforced timing between the counter and the digital line, and there's a delay inserted before the digital line, it works. There are nearly simultaneous starts on two tracks. Execution proceeds directly along the task wire to the counter. Meanwhile, the execution along the task wire to the digital high gets delayed. Then, when the digital high fires, the counter completes its task, and execution proceeds downstream from the counter. Note, I do have to set the timeout on the counter longer, because the vi runs so slowly when it's painting its progress along the wires. If there is any timing relationship enforced between the counter and the digital transition, it doesn't work. It appears to me that to read a counter, you have to ask it for a result, then drive the line high, and then receive the result, and execution inside the counter has to be ongoing during the rising line edge.
>from what I remember, there isn't much to it. There really aren't many candidate places for trouble. A pulse is generated with DIO, then a single sample is read from each counter. -Yup, you got it. This should be trivial.
>A timeout means either that the pulse isn't generated or that the counter tasks don't receive it. - Or it could mean that the counter task must be in the middle of executing when the rising edge of the pulse arrives. Certainly the highlighted execution indicates that. Making a broken vi run by cutting the error wires that sequence the counter read relative to the pulse also seems to support that.
>Have you verified that the digital pulse happens using a scope? -Verified in some versions by running another loop watching a digital input, and lighting an indicator, or recording how many times the line goes high, etc. Also, in your vi, with highlighting, if I delete the error wire from the last digital output to the first counter to allow parallel execution, I see the counter execution start before the rising edge, and complete when the line high vi executes. Also, if I use separate loops to drive the line high and to read the counter, it works (see TwoLoops.vi or see the screenshot of the block diagram attached below so you don't need a LV box). I could go sign out a scope, but think it's obvious the line is pulsing given that all these things work.
>Wait! I think that's it! If I recall correctly, you're generating the digital pulse on port0/line0... On a 6259, the lines of port 0 are only for correlated DIO and do not map to PFI. -But I'm not using internal connections, I actually physically wired P0L1 (pin 66) to PFI0 (pin 73). It was port0/line1, by the way. And when running some of these vi's, I also physically jumper this connection to port0/line2 as an analog input to watch it. And, again, the pulse does cause the counter to operate, so it clearly connects - it just doesn't operate the way I think it is described operating.
For what it's worth, there's another mystery. Some of the docs seem to say that the pulse has to be applied to the counter gate terminal, rather than to the line associated with the sample clock source on the timing vi. I have tried combinations of counter gate and or sample clock source and concluded it seems like the sample clock source is the terminal that matters, and it's what I'm using lately, but for example the document I cited, "Buffered Event Counting", from last September, says "It uses both the source and gate of a counter for its operation. The active edges on the gate of a counter is used to latch the current count register value in a hardware register which is then transferred via Direct Memory Access...". I may go a round of trying those combinations with the latest vi's we've discussed.
Attachments:
NestedSequences.png ‏26 KB

How do I program a NI 6602 card to send trigger pulses, one at each output port, triggered by an input trigger signal, using only one counter for each output port?

Hello,
I have managed to program a NI 6602 card in LabView to send pulses on three different output ports, one pulse on each output port (with individually chosen delays) for each input trigger pulse coming on a separate input port. It is the DAQmx Create Channel (CO-Pulse Generation-Time)-VI that I have used for this, see attached code. However, this VI controls both pulse delay and pulse width, and therefore uses two counters for each output port (although you only specify one counter in the VI input signals), as I understand.
In my application though, I only need to have the delay chosen, the pulse width can be arbitrarily short, and thus I should only need one counter for each output port. How do I accomplish to program this in LabView?
Best regards,
Claes
Attachments:
Configure Side Camera Flash 1 Triggering.vi ‏47 KB

Well you're welcome to do that--it will work just fine as long as you are configuring a start trigger.
<rant>
However, personally I really don't like putting multiple counter outputs in the same task. I have seen so many people assume that the counter outputs would be synchronized due to having them in the same task when this is not the case (you need to configure a start trigger in order to synchronize the counter outputs even if they are in the same task). This is the only case I can think of where multiple channels in a DAQmx task are not automatically synchronized.
As an example:
Running this on my PCIe X Series gives a measured 2 edge separation of 1 ms + {7.78 us - 10.11 us}. This would likely be much worse on a bus with more latency (e.g. USB).
The resulting output is close enough to what you might expect that it might go unnoticed, but really these counter outputs are not synchronized and it would be easy to glance at the code and not even think twice about it. For the small amount of extra work on my end to create a separate task for each counter, it really clears up some ambiguity about what the counters are actually doing. For me it's worth it.
So again, for your case there really isn't a problem with having the counters in the same task since you are using an external start trigger anyway. I have just gotten in the habit of avoiding doing this.
</rant>
Best Regards,
John Passiak

How can one counter be sources (or gated) with the output of the other?

I'm trying to use the counters to generate a square pulse train that contains a certain number of pulses (on 6036E). For that I need to gate counter0 with the output of counter1. The manual seems to indicate that I need to use
GPCTR_Change_Parameter (deviceNumber, ND_COUNTER_0, ND_GATE, ND_COUNTER_1) ,
however it makes no difference to the output; I see no gating. What am I doing wrong? Am I missing something?
I would also like to source counter1 with the output of counter0. There's a similar function call to choose the source signal, but so far I've been unable to source a counter with anything but the internal timer. I guess the reason for it might be the same as the gating problem.
Petro

Hi Petro-
This example shows how to output a finite gated pulse train on an E Series board. It mentions that it is a CVI example, but the main .c file does not include any CVI-specific functionality so it should work if you're using ANSI C.
Equivalent functionality is available in NI-DAQmx for your board and is considerably more intuitive. An example of pause-triggered pulse train generation is available in the "C:\Program Files\National Instruments\NI-DAQ\Examples\DAQmx ANSI C\Counter\Generate Pulse\Dig Pulse Train Cont-Pause Trig" directory of your local drive. One method to generate the "pause trigger" pulse train is shown in "C:\Program Files\National Instruments\NI-DAQ\Examples\DAQmx ANSI C\Counter\Generate Pulse\Dig Pulse Train-Cont" .
I'm not sure what you mean when you say "I would also like to source counter1 with the output of counter0." What do you need to perform this operation for? The reliance of counter 1 on counter 0 and counter 0 on counter 1 creates a type of circular reference that is almost guaranteed to be problematic.
Hopefully this helps-
Tom W
National Instruments

Unable to count fast pulses with DAQ(pcmcia card)AI-16E-4, using the example vi

I am using the AI-16E-4 PCMCIA Daq card to count pulses from a device that has an open collector pulse output. I am current just trying it out to see if I can get it to count the pulses correctly before I go ahead and further develop the program. I am using the Example program for counting pulses with this device.
What I am finding is that when I increase the pulse rate above about 20,000hz it slows down and then stops counting pulses. The documentation for this device states the max input frequency is 20mhz, therefor it should be able to count the pulses I am planing on providing. The fastest rate the device I am connected is around 2.mhz. Can someone tell me how to get the AI-16E-4
to count these open collector pulses.
Attachments:
regulation_tester.vi ‏89 KB

Hello;
You need, first of all, to provide a pull up resistor for the open collector device, in a way that its high state fits within the TTL levels.
Once that is done, you just connect its output to the counter source input. The device should be able to go up to 20MHz, with no problem.
Regards
Filipe A.
Applications Engineer
National Instruments

Hello, I would like to produce 2 different pulse trains on the CTRo and CTR1 output pins.

(DAQ-CARD E6024 PCMCIA)I have the 2 output pins monitored on my scope, when CTR0 puts out a pulse train, CTR1 goes high. When CTR1 puts out a pulse train CTR0 goes high. Also, the pulses are interleaved with each other. Is there a way to make then start at the same time
Attachments:
Stim_Output_pulses_CTR_0,1.vi ‏94 KB

Hello Zoltan,
I would suggest using the counter gates to synchronize the counters. You will need to externally run a wire from one of the DIO lines you're not using to one of the counters' gates. When the counter gate is high, the pulse train will be generated on each counter. Both counters will need to use the same PFI line as the gate.
There is an example program that ships with LabVIEW 7 called "Gen Dig Pulse Train-Continuous-Pause Trigger" for DAQmx. This demonstrates how to configure the counter to only generate the pulse train when the gate is high.
With this configuration, you could synchronize the counters by writing to the DIO line which is wired to one of the counter gates when you're ready to start the pulse train generation.
Hope t
his helps.
Kristi Hummel
Applications Engineer
National Instruments

How can i measure the time between a pulse output and a pulse back on the input?

Llo,
I have a problem i use a ultrsonic sensor, and when i send a pulse out of 4V then a couple of ms i have a pulse back on the input, how can i exactly know how much time there is between the 2 ^pulse??

Use the output pulse to trigger a counter in period measuring mode and stop the counter on the return signal (if the input return signal is large enough to reliably trigger a logic circuit). If the signal is not large enough to trigger the counter directly, an external comparator can be used to generate the stop signal.
Another approach is to use two channels of analog input. Feed the output signal to one of them and the return signal to the other channel. The time between outgoing and return pulses can be determined from the sampling rate. If precise timing is required and your AI board does not have simultaneous sampling, you have to account for the inter-channel time as well.
Lynn

Using counter and output at the same time

Hi all,
I'm using a NI 9401 high speed digital IO module (with a cDAQ 9174 chassis) that has 8 digital IO channels, to perform two tasks at once in Labview. I can get both of them to work independantly, but when I put them together to run simultaniousy in parallel, it does not work. My two tasks are simple: 1. Generate a continious pulse train square wave output using one of the counters linked to one of the output channels (PFI7) and 2. Output a 'high' (5V) with one of the other channels (PFI1) when a certain logic condition is met.
When I run my code (attached), the pulse train output works, but the output on the other channel doesn't work when the logic condition is met. I should note that the logic condition is that when RMS current exceeds 3A, I want to output a 'true'. I am measuring current using another analog input card connected to the same chassis and this part is all working well. I think the problem is that there is some sort of interference between the pulse train output which is linked to PFI7 and the other output which is PFI1.
I know there is a limitation with the 9401 card that if the channels are in two groups, 0-3 and 4-7, and you must use a whole group as either all inputs or all outputs, but I don't think this should affect me, as I am using both my channels as outputs anyway, plus I am using channels 1 and 7 anyway.
If anybody has any ideas as to what could be wrong with my code, I would greatly appreciate it.
Attachments:
DSDBI Vegetation testing program.vi ‏115 KB

OK, you've shot yourself in the foot.
It is a very bad idea to modify the shipping examples. Like testing bungee cords by juming off a cliff- sometimes you only get to try it once.
Now why on earth did you not add the DI code following the example's method of wiring the error chain and closing the task after the loop? You have duplicated code in both cases of your case structure the only difference.........(wait for it..........) There is a true constant in the true case where the false case contains a false constant. A wait for task complete is unnecessary for a 1 sample DI task- really the write just completes and the task stops all by itself. the only needed thing here is a DI Write 1 Ch 1 Sample no case structure, and wire the compare output to data to write.
You should probably add a control task vi with a "Reserve" input prior to each start task on the CO and AI Tasks and after the Create Task on the DO. Its a bit technical but the result is like taking vitamins- you'll just get better performance.
Jeff

LabVIEW 6.1 If For Loop count terminal is zero then value going through the loop is not passed on to the output of the loop

Hello, one of our customers just encountered an execution error in a vi running under LabVIEW 6.1, which doesn't exist under LabVIEW 5.1 or 6.01. I have a simple vi that has two encapsulated For Loops. Two string arrays go in, one goes out of the outer loop. Inside the outer loop the first array is indexed. The string which results from this indexing is compared with all other strings from the second string array in the inner loop. If it matches one of the strings of the second array, it is not outputted, otherwise this string goes through the inner For Loop to the output of the inner loop and from there to the output of the outer loop. The count
terminal of the outer/inner loop is connected to the Array Size of the first/second string array. If the second array is empty, that means that the element in test from the first arry cannot match anything from the second array, so the element in test is send to the output of the inner loop and from there to the output of the outer loop. This works fine in LabVIEW 5.1 and 6.01, but NOT in LabVIEW 6.1. In LabVIEW 6.1 the inner loop is never executed if the count value is zero (which is correct), but the data line running through the loop is not executed either, which is different to what LabVIEW 5.1 and 6.01 do. There, the input string is sent to the output of the inner loop correctly even if the loop counter is zero. The solution is easy - I just have to connect the output of the outer loop to the data line BEFORE it enters the inner loop. But: I don't know if this is a LabVIEW 6.1 bug or if it is supposed to be a feature, but it brings some incompatibility in programming between the
different LabVIEW versions.
Best regards,
Gabsi

Hi,
When a for-loop runs zero times, all outputs are 'undefined' (and should
be).
Besides, how would LV know what the output of a not executed routine should
be?
It might be handled differently in LV5 and LV6, which is unfortunate. In
both cases, the result is undefined.
It's not a bug. It's just something that should be avoided in any LV
version.
> The solution is easy - I just have to connect the
> output of the outer loop to the data line BEFORE it enters the inner
> loop. But: I don't know if this is a LabVIEW 6.1 bug or if it is
In some cases this does the trick. But if the data is changed in the inner
loop, this will effect the results if the N is not zero.
Technically, I think the output in this construction is also 'undefined'.
But LV handles this as expected / desired.
Another solution is to use a shift register. If N is zero, the input is
directly passed through to the output.
Regards,
Wiebe.
"Gabs" wrote in message
news:[email protected]...
> LabVIEW 6.1 If For Loop count terminal is zero then value going
> through the loop is not passed on to the output of the loop
>
> Hello, one of our customers just encountered an execution error in a
> vi running under LabVIEW 6.1, which doesn't exist under LabVIEW 5.1 or
> 6.01. I have a simple vi that has two encapsulated For Loops. Two
> string arrays go in, one goes out of the outer loop. Inside the outer
> loop the first array is indexed. The string which results from this
> indexing is compared with all other strings from the second string
> array in the inner loop. If it matches one of the strings of the
> second array, it is not outputted, otherwise this string goes through
> the inner For Loop to the output of the inner loop and from there to
> the output of the outer loop. The count terminal of the outer/inner
> loop is connected to the Array Size of the first/second string array.
> If the second array is empty, that means that the element in test from
> the first arry cannot match anything from the second array, so the
> element in test is send to the output of the inner loop and from there
> to the output of the outer loop. This works fine in LabVIEW 5.1 and
> 6.01, but NOT in LabVIEW 6.1. In LabVIEW 6.1 the inner loop is never
> executed if the count value is zero (which is correct), but the data
> line running through the loop is not executed either, which is
> different to what LabVIEW 5.1 and 6.01 do. There, the input string is
> sent to the output of the inner loop correctly even if the loop
> counter is zero. The solution is easy - I just have to connect the
> output of the outer loop to the data line BEFORE it enters the inner
> loop. But: I don't know if this is a LabVIEW 6.1 bug or if it is
> supposed to be a feature, but it brings some incompatibility in
> programming between the different LabVIEW versions.
> Best regards,
> Gabsi

Can I count the PWM pulses and note the timer value simulataneously.

Im using 6024E. I want to be used for 1-phase motor control. I could generate PWM pulses and read the feedback analog current, but I am unable to read the velocity of the motor. Counting PWM pulses(generated by sensor for each degree of rotation) and reading the digital timer value simultaneously to calculate velocity of the motor. If any body can give the solution it will be appreciated
Attachments:
motor_control_ver1.0.llb ‏210 KB

Hello;
In case you can read a digital pulse train that would give you the speed of the motor, you can use one of the counters of the DAQ board you have to accomplish that.
You can configure the counter as buffered event counter, hook up the digital pulse train to the counter gate, and since you have the frequence of the internal timebase that is connected to the counter input, you can calculate the speed of the motor by having the count values that are stored at the event of a gate input pulse.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

DAQMx has no output when the pulse width is less than 0.1sec

Hi,
    I am developing a application to generate square wave(voltage) and out put from a DAQMx card (PCI-6723 - 32 point analog in/out). I attache a simplified code (labview8.5) I wish somebody can help me to figure out what is the problem
    When I set pulse width longer than 0.1 sec. everything works fine. If I set the pulse width less than 0.1 sec, the output from DAQ eithet gets nothing or incorrect(I used a Osclliscope to monitor the DAQ output), although my labview monitor showed correct output.   I wonder if it is a sampling issue of the DAQ card.
     Thanks
    Guang
Attachments:
test21.vi ‏69 KB

I think one or two things could be causing the problem.
1. Your DAQmx write is set for 1 sample. I don't know how that dynamic signal type works with such a setting. Perhaps it is just putting out the first sample of the signal that is generated.
2. The math for the frequency of the square wave does not make sense. You are adding a pulse delay with the pulse period, then inverting it to get the frequency. So a 1 second delay with 1 second pulse is a 1/2 Hz wave. A 4 second delay with a 2 second pulse would be a 1/6 Hz wave. That doesn't make sense to me.
I would recommend building your own waveform or array and not using the express VI. If you have a 1000 Hz frequency established let's say, build a 1000 element array. For a .1 second pulse, set replace 100 of those elements with a 100 element array of the voltage value you want. You can index it wherever you want in the array to account for whatever delay you want. If you want a 1 msec pulse, then just replace a single element of that array wherever you want.

When using the analog inputs and analog outputs of the PCI-7344, what is the conversion between the voltage entering the card to counts? Similarly, what is the conversion between counts to voltage at the output of the card?

I am using the PCI-7344 to control my system. The analog inputs are connected to the output of my system while the analog outputs serve as feedback to the system. The system is a servo. I want to know what is the conversion between the voltage read at the input, to card counts, and finally to the voltage output to the system.

Carole,
If you are trying to do analog feedback with a servo motor, Chapter 14 of the manual talks about how to set up the torque feedback. Also linked below is a LabVIEW example of analog feedback.
Chapter 14
NI-Motion User Manual
Automatic Analog Feedback with FlexMotion example
A. Talley
National Instruments

(pci-6052E) I want to genarate a pulse every time the counter is zero.

I'm using the counter on my pci-6052E to count the number of pulses on a line. The count goes up and down since I have a direction signal. Now I need and indication (a pulse) every time the count reaches zero. This is similar to the breakpoint function on your motion controllers. Is this possible....

Yes you can, and here's an example that worked with DAQmx on an E-series board. Ctr0 counts edges of the internal 20 MHz timebase, rolling over to 0 a little more than once a second. It uses the DAQmx Export Signal property node to program the counter to Pulse on reaching TC (terminal count). The pulse signal is sent to a terminal that Ctr1 uses as its source, so Ctr1 increments each time Ctr0 reaches terminal count (0 value).
-Kevin P.
Attachments:
TC Pulse.vi ‏81 KB

Counting 3 pulse outputs on the 9178

Similar Messages

Maybe you are looking for