Counter timer

I need 04 channels finite pulse train generation. The number of pulse of each channel is difference. Is PCI -6624 suitable for my application?
Best Regards
T.Q Huy - Vietnam

Hello T.Q.,
Unless you need non-TTL voltages for your pulse train, I would actually recommend the PCI-6602.  You can output pulse trains of higher frequency (up to 80 MHz), and don't have to supply an external voltage source.  One thing to realize is that, unlike a continuous pulse train generation task, a finite pulse train task actually requires two counter channels - one to output the pulse, and the other to count the pulses in order to determine when to stop the generation.  The PCI-6602 has 8 counters onboard, which is just enough to output 4 finite pulse trains.  More information about both these devices can be found in the TIO Series Help.
I hope this helps,
Travis G.
Applications Engineering
National Instruments

Similar Messages

  • Counter/Timer Waveform

    I would like to convert period measurements (RPM data) received from my counter/timer board into waveform data type so that I would be able to conduct frequency analysis on the data (e.g. FFT). Have tried with limited success interpolation & decimation techniques. Would be grateful for any suggestions.

    I had a look and can offer up a few comments:
    1. I don't understand your comment about "truncation error" in the slow speed pulses case. Perhaps your are remarking about the "glitches" in the slow data embedded in the block diagram array? More on this a bit later...
    2. At least at a quick glance, the interpolation seems a little funky. I didn't spend a ton of time wrapping my head around it so maybe it's actually ok, but I saw a finite difference that would act like a derivative of the period, and a scaling factor based on the average period -- things that make me go hmmmm.
    Also, if you zoom on the graphs for the Slow Data, you can kinda see that the "Post Processing Graph" looks like a derivative of the "Pre Processing Graph". I suspect you need to rework your interpolation method.
    3. When I did a similar project, I think I first converted all the periods to frequencies and also generated a "sample time" array that was the cumulative sum of the periods. (I toyed with tweaking the time array so that the timestamp would correspond to the midpoint of the interval that I had converted to a frequency. I don't recall now whether that tweak proved useful enough to bother with).
    Once I had laid out arrays for frequencies and (unequally-spaced) sample times for those frequencies, I could generate an equally-spaced time array at a desired "virtual sampling rate" and interpolate to create new "virtual frequency" values. Since I was merely post-processing data, I think I also used the native LabVIEW array functions 'Threshold 1D Array' and 'Interpolate 1D Array' in the interpolation process.
    Now, before going into an FFT you'll want to remove the huge DC offset. This may be as simple as subtracting the mean or median frequency from all entries if you are nominally at constant speed.
    4. Your raw dataset for Slow Data has suspiciously periodic glitches in the periods. There is a very strong and dominating pattern that repeats every 16 intervals. Your typical period is registering about 10 million timebase cycles. However, in every set of 16 periods, you get one period around 27 million and another around 35 million.
    I don't know how you gathered your "Slow Data" values, but there seems to be a systemic error in the measurement. That sort of one-sample discrepancy looks very suspicious. I'd urge you to determine the source of those glitches and try to eliminate them. They don't appear to be telling the truth about the motion you wish to characterize. The device you measure doesn't by chance start and stop or go back-and-forth during your measurement, does it?
    Hope this helps.
    -Kevin P.

  • Can I use Intel 815EP AGP 4X Pentium and plug in 5 Nos NI 6002 PCI counter Timer cards, instead of going for expensive PXI based solution? Hope there will be no degradation in performance - when used for constructing an Energy Meter test Bench.

    I was recommended to buy NI 6002 with PXI series, 5 Nos cards($875x 5 nos), and additionally a PXI rack costing about $ 2195 + some min--- card to interface with the computer costing another $ 875. Compare this with $ 675 x 5 Nos for 5 Nos PCI based NI 6002 + some cablesa nd connectors for synchronisation.
    First option is extremely expensive. But NI marketin manager will be glad that he sold more harware. But I want the truth. Why can't Intel 815 Pentium board be used?

    I am addressing the question if using PCI-6602s instead of using PXI-6602s will affect the performance, and the answer is NO. 6602 counter/timer devices comes in two different form factors, PXI/Compac PCI and PCI. The accuracy and performance is the same for both the PXI and PCI 6602s. However, using PXI solution will allow users an easier time with synchronization since that is the provided in the backplane of the PXI chassis. Additionally, if you ever need a higher accuracy solution you can add the 6608 device which has 75 parts per billion ppb vs 50 ppm of the 6602 devices. With 6608 plugged in the second slot of the PXI chassis (the one next to the controller), the high accuracy timebase is automatically shared acrossed the backplane of the PXI chassis which mean
    s that other 6602 devices in the chassis will share the same accuracy of the 6608. If the difference in the accuracy is not a concern and you are currently not ready to invest in the PXI platform, then you can go with the PCI 6602 devices.
    Best Regards,
    June Zhu
    National Instruments
    Digital and Timing Product Support Engineer

  • How to use Counter/timer PWM Pulse as a trigger to aquire data??

    (1) I'm using the NI DAQpad 6015 multi-function card with the new DAQmx Driver. I'm using the counter/timer (counter 0, and counter 1) to generate 2 different PWM pulses to supply my sensor circuit. each pulse is a 1 second in duration. The pulse with 5m.sec duty cycle is the supply for my sensor. In addition to that, I'd like to use the 5 m.sec as a trigger to aquire the sensor reading. The DETECTIN POINT should be the middle of the HIGH State of the 5m.sec pulse (i.e just at the 2.5 m.sec point of the high state).  
    (2) another point is: how to display the counter/timer pwm output pulses on the front pannel?? 
    Attached is the VI i'm using (Complete
    Complete ‏49 KB

    Hello alaali,
    It sounds like what you need is a trigger delay property node.  This property node specifies an amount of time to wait after the Start Trigger is received before acquiring or generating the first sample. This value is in the units you specify with Start.DelayUnits.  This way you can still acquire using the trigger, and you can specify the delay to be 2.5 ms so that the point that you actually acquire will be 2.5 ms after the trigger.
    Hope this helps.
    Regards,Message Edited by Raajit L on 04-23-2007 04:34 PM
    Raajit L
    National Instruments
    DAQmx Trigger Delay.jpg ‏6 KB

  • Counter/Timer Pulse Train generation

    I am having some trouble understanding why a particular VI I have isnt working(upper part of image below), I was wondering if someone could give me an idea of the cause from the error message.  I have a counter/timer which I am using to generate a pulse train.  It works fine on 'Continuous samples'  but when I switch it to 'finite samples' I get a 'resource is reserved' error when it gets to the DAQmx 'Play' VI
    I made a separate VI (lower part of image) and it works just fine with finite samples.  So  I am basically wondering what is different about finite versus continous sampling which could cause a resource to be reserved or not. (the board is a PXI 6281 if that matters)
    Go to Solution.

    You're correct on what the problem is. 
    For what it's worth, the newer X Series boards (63xx) and 2nd Generation Compact DAQ Chassis don't require the use of two counters for finite pulse generation (although technically there is a paired internal counter to accomplish the finite pulse generation, it's not really evident to the user). These products also have 4 counters available instead of 2. 
    Best Regards,
    John Passiak

  • Mounting 3 pairs of omron sensor E3X-F21 at 25mm intervals to measure time taken by moving object breaking beams and connecting to 6601 counter/timer card

    System is Windows ME Labview 6.1 6601 Counter/timer card. 3 pairs of Omron Photoelectric sensors E3X-F21 are mounted on a flat surface and as the object passes the first pair of sensors it starts timer1 and timer2.
    As the object passes the second pair of sensors it stops timer1 and as the object passes the third pair of sensors it stops timer2
    We have a known distance between the sensors so we are able to calculate the objects speed and position.
    We need a wiring diagram to connect the sensors to the 6601 card.

    I think I can describe a method that'll probably be simpler than the previous answer because it won't require any external logic circuitry.
    1. Configure two counters for "Two-Edge Separation" measurement, let's say counters 0 and 1.
    2. Wire Sensor 1's signal to both AUX-0 and AUX-1.
    3. Wire Sensor 2's signal to GATE-0.
    4. Wire Sensor 3's signal to GATE-1.
    5. Wire each sensors' 'ground' to the appropriate ground pins on your terminal block.
    6. Software configure both counters to use "max internal timebase" for a source -- 20 MHz for the 6601.
    You can specify the polarity of the transition you care about for both the AUX and the GATE signal, but I'll explain in terms of rising edges for both.
    Counter 0 will count time from Sensor 1's rising e
    dge until Sensor 2's rising edge. Counter 1 will count time from Sensor 1's rising edge until Sensor 3's rising edge. The count values will be in units of "# of 20 MHz cycles elapsed."
    You can probably get a decent starting point on the software using one of the shipped examples.

  • How can I count time with labview7?

    How can I count time with labview 7 and NI-DAQmx like I did with labview 6.1 and "count" (count event or
    I have a 6025E and labview 7.0

    I am not sure what you want to do or why..
    ... but here goes (some suggestions)
    If you want to count the time between two events, you have a choice, you may use the Tick Count. Inisitalize it first by getting a timestamp and then do a difference within a loop. The difference will give you the time elapsed in ms.
    You can also use the Get Date/Time String or Get Date / Time in seconds and once again take a snapshot when a first even occurs and another snapshot at the next even (at a point where you want to measure elasped time). This method is particularly useful if you want to timestamp an event.
    If I didn't answer your question, can you elaborate what you mean by "How can I count time".
    Best of luck..

  • Low profile counter/timer board

    Does NI (or anyone else) make a low-profile counter/timer board? Perhaps with specs similar to 6602? If not, are there some other options that I could look into (I think the sample rates may be too high to use USB)?
    Go to Solution.

    Hi greatgrandpadog,
    Unfortunately, NI does not have any counter/timer solutions that are low-profile on PCI.
    Our cDAQ-9171 single slot USB chassis has four 32-bit counter/timers that can use an onboard 80 MHz clock (detailed specifications).  For external signals, you would need to use one of our digital i/o module which have various specifications.  You can find a list of them here.  This will be the best way to go for a compact USB counter/timer.  If you have additional i/o, take a look at our CompactDAQ Advisor, where you can use a 4- or 8-slot chassis to expand your i/o in a single system.  For more sophisticated control, CompactRIO offers a similar platform but with FPGA and Real-Time for greater customization and reliability.  There is an online advisor for that as well, here.
    Chris E.
    Applications Engineer
    National Instruments

  • How to count time precisely?

    I was trying to count time using a VI like the one attached.
    My trouble is that this is not couting correctly. There is a possible reason I observed. 
    Maybe the computer is not able to process the VI as fast as necessary. 
    I thought about this because, when in edition mode the time counting was very wrong, and, when I created an aplication and installed it, it was running ok, as it got "light". But today, when I tryed to use this aplication with an old computer it didn't work. The clock is delaying.
    Is it possible to count the time correctly? 
    I'm using a DAQ6009 to do my works, my VI is pretty big, and I need an iteration at each 1 ms (milisecond) as I'm using digital inputs to count 5 encoders events (I know that this is not the correct way to count encoders, but this is the only way I can do that, and it's working).
    Thank you all in advace! hope you can help me!
    Go to Solution.
    Attachments: ‏6 KB

    OK.  Let me try to help you understand a few things.
    The Tick Count and Wait (and Wait Until Next ms Multiple) functions all use a 1 kHz clock that is derived from the processor clock. The accuracy of these clocks is not great, although probably comparable to your stopwatch accuracy.  Any timing generated by these functions will show some differences from the time of day clock as it is derived from a different oscillator.
    The front panel updates are timed both by LabVIEW and the OS. Most screens are updated 60-80 times per second, maximum. Depending on what else the OS is doing, a screen update could be delayed 10s of milliseconds or longer.  It is certain that not every value at the output of the Add function will be displayed.
    The Wait Until Next ms Multiple will wait more than 1 ms if the other code in the loop takes longer than 1 ms.  I am not sure, but I think the indicator is buffered so that any delays by the OS in updating the display should not slow the loop. I tried removing the indicator and it did not seem to make much difference.
    I modified your VI to provide several indications of performance. First, I added the three-frame sequence structure to allow timing of the loop. Second, I changed to a for loop which will run a preset number of iterations. Third, I connected the output of the Wait Until Next ms Multiple timer to an autoindexing tunnel so that a record of the time of each iteration appears in the Ticks array. I calculated the differences between successive times and displayed that on a graph so that you can see the performance.
    I did not mean to sound critical of your use of English.  You write in English much better than I could in your language!  The point I was trying to make is that general descriptions such as "is not counting correctly" without quantitative results or evidence to support the claim do not have enough information to help us help you.
    Attachments: ‏13 KB

  • How to count time between two pulses

    Hello everyone,
    I want to count time between two boolean pulses?  Can anyone give me an advice? Thank you in advance!

    Hello Michael78,
    You've right. I have a DAQ board and i want to acquire torque and angle (from a torque transducer). I already done that, but sometimes it doesn't work properly. To acquire this, i count sign changing of the torque to acquire exactly one period (3 sign changing). Torque have a noise, and when passes through zero, count more than 3 sign changing at a time, and this stop my acquisition (figure 2). I want to set a time between 2 counting sign . I tried something with tick count...but i made something wrong . I hope you understand me....
    Capture.PNG ‏51 KB
    Capture2.PNG ‏47 KB
    Capture3.PNG ‏123 KB

  • [HELP] Agilent 53220A Counter Timer Will Not Initialise Using NI VI's!

    I am running National Instruments 2012 Development Suite.
    I have hooked up an Agilent 53220A to a PXI chassis via USB and MAX can see it.
    If I use the D:\Program Files (x86)\National Instruments\LabVIEW 2012\instr.lib\Agilent 532XX Series\Public\ library to initialise it, it takes ages before finally timing out.  I opened all the VI and issued the commands manually using the Measurement and Automation Explorer as follows:
    *IDN?\n = Returned the details of the Counter Timer.
    *RST\n = Returned no errors.
    *ESE 60;\n = Returned no errors.
    *SRE 48;\n = Returned no errors.
    *CLS;\n = Returned no errors.
    : SYST:ERR?\n = The subsequent read then times out!   (delete space between ":" and "S")...
    If I repeat the above but skip the "*SRE 48;" command it then works.
    Any ideas why my Agilent 53220A Counter Timer does not like the "*SRE 48;" command?
    Christopher Povey
    Senior Test Systems Engineer for BAE Systems.

    ChristopherPovey wrote:
    I am running National Instruments 2012 Development Suite.
    I have hooked up an Agilent 53220A to a PXI chassis via USB and MAX can see it.
    If I use the D:\Program Files (x86)\National Instruments\LabVIEW 2012\instr.lib\Agilent 532XX Series\Public\ library to initialise it, it takes ages before finally timing out.  I opened all the VI and issued the commands manually using the Measurement and Automation Explorer as follows:
    *IDN?\n = Returned the details of the Counter Timer.
    *RST\n = Returned no errors.
    *ESE 60;\n = Returned no errors.
    *SRE 48;\n = Returned no errors.
    *CLS;\n = Returned no errors.
    : SYST:ERR?\n = The subsequent read then times out!   (delete space between ":" and "S")...
    If I repeat the above but skip the "*SRE 48;" command it then works.
    Any ideas why my Agilent 53220A Counter Timer does not like the "*SRE 48;" command?
    I have confirmed this morning that I have installed the drivers and library for LabVIEW 2012 version from the NI website.
    Any ideas anyone?
    Christopher Povey
    Senior Test Systems Engineer for BAE Systems.

  • Counter/timer rate

    I am using the counter/timer input on a 6040E card for event counting.
    I am using CTR0 and have specified the 20MHz clock as my source and connected my event to the gate (PFI9). I am counting a finite number of pulses and I am configuring the buffer using the DAmx Timing vi (sample clock instance).
    My question is regarding the 'rate' input. As the counter source is set to the 20MHz is this not the rate? Can anyone advise as to how I choose a sensible rate value and what effect it has.
    I normally use the rate for analogue IO buffers in order to set the buffer rate - I just can't quite see it's use in this instance.
    Go to Solution.

    Usually you have 2 types of things you want to do with counters, Count edges or count a clock between edges.
    For edge counting you are incrementing (or decrementing) the count for each specified edge on a pfi line (you can select this) you can read this value periodically to see the current count.  For counter measurment you are counting the number of clock cycles (this is where the source is probably the 20MHz onboard clock) between specified edges at the at gate.  This is useful for frewuency or pulse duration measurments.  each measurment is buffered and you can read the buffer periodically.
    Paul Falkenstein
    Coleman Technologies Inc.
    CLA, CPI, AIA-Vision
    Labview 4.0- 2013, RT, Vision, FPGA

  • WANTED: NI PXI-6602 counter/timer

    I'm looking to buy a used NI PXI-6602 counter/timer board. Got one?

    "Zvezdana S." wrote in message
    news:[email protected]..
    > Hugh,
    > To possibly obtain an used board from National Instruments, you should
    > contact your regional Internal Sales Representative (ISR) for possible
    > used boards. If you are not sure who your ISR is, generate a service
    > request at:
    I never knew NI had an SRQ line we could pull.
    Craig Graham
    Physicist/Labview Programmer
    Lancaster University, UK

  • Counter/timer high resolution

    Dear all
     I have developed a counter-timer program by using NI PCI-6601 card and LabVIEW 7.1 on P-IV with Windows XP.
    It gives satisfactory results when I apply i.e.
                                                                  Input 100000 Hz at 1 sec high Time and 1.00E-7 sec low time  which gives output 100000 counts,
                                                                  Input 100000 Hz at 0.5 sec high Time and 1.00E-7 sec low time  which gives output 50000 counts and
                                                                  Input 100000 Hz at 0.2 sec high Time and 1.00E-7 sec low time  which gives output 20000 counts
     But when I goes to achieve high resolution it gives incorrect data i.e.
                                              Input 100000 Hz at 0.1sec high Time and 1.00E-7 sec low time  which gives output 20000/10000 counts, and below this value it also gives wrong output data.
                                                         I want to achieve .001 sec high time.
                                                         Please help me to solve this problem.
    Best Wishes

    Hello Neal M,
    Thanks for reply and sparing time for me. I am using counter-0 for reading and counter-2 for pulse output.
    I want to achieve the following readings/counts at respective inputs which are following:
     Input 100000 Hz at 0.1sec high Time and 1.00E-7 sec low time  then the output should be 10000 counts,
     Input 100000 Hz at 0.01sec high Time and 1.00E-7 sec low time  then the output should be 1000 counts and 
     Input 100000 Hz at 0.001sec high Time and 1.00E-7 sec low time  then the output should be 100 counts.
    I am also sending you "counter timer high" in attachment.
    Thanks a lot again in helping me.
    counter timer high ‏192 KB

  • Controlling Counter Timer of PCI6259 from Matlab

    My Name is Abtin, Im from Germany and i Hope my English is good enough to discribe my Problem. Im using a PCI 6259 Card, and I want to set the general Purpose Counter and Timer from Matlab. But I still dont manage it. have sombody experience with this card and could help me. Im really in trouble i hope somebody answere....
    I want to set the Timer as output and use it for triggerung. But how can i access to the Counter??? I dont find no example for Matlab.

    Hello Abtin,
    since you are from Germany i may as well continue in German. NI Hardware kann von Matlab aus mittels der Toolbox angesprochen werden. Unter folgenden Link findet sich eine Kompatibilitätsliste: 
    Dort findet sich auch folgender Hinweis:
    "Note: Data Acquisition Toolbox supports voltage
    measurements on analog input and analog output subsystems. On digital
    I/O, it provides static acquisition and control. If using specialized
    analog measurement capabilities (such as thermocouple CJC compensation
    and IEPE excitation), hardware clocked digital I/O, or the
    counter/timer subsystem are valuable to you, please let us know by
    completing the form at the bottom of this page"
    Nach meinem Wissensstand unterstüzt Mathworks die Counter Funktionen lediglich für einige E-Serien Karten und noch nicht für M-Serien Karten.
    Ein Beispeil für MIO Karten unter Matlab findet sich unter folgendem Link: 
    Um die Counterfunktionalität der Karte dennoch nutzen zu können, ist es möglich die DAQmx Treiber dlls auch direkt aufzurufen. 
    Um dazu eine Hilfestellung zu erhalten währe es sinnvoll bei der Installation des DAQmx Treibers die C-Unterstützung zu aktivieren. Dadurch werden sowohl die C Beispiele als auch die Hilfe zu den DAQmx Funktionen installiert. Unter "Start>Programme>National Instruments>NI DAQ>NI DAQmx C Reference Help" kann die Hilfe aufgerufen werden. Sie ist als Basis für die dll Aufrufe in Matlab zu sehen. 
    Viele Grüsse

  • Bus communications for 660x counter timer cards

    I believe I have a new application for 660x counter timer cards. I propose to build some additional circuitry on a blank PCI card to be installed in the same PC as the 660x card. If my sequence of pulses is generated on my home-built card, can this pulse sequence be fed via the PCI bus to the 660x card or must the 68 way connector be used. Can the PCI 6602 use the PCI bus for data receipt and transmission? Can the PXI 6602 use the PXI bus in a similar manner? Please note, my application will still be viable if the PCI/PXI bus cannot be used in this manner but it would give me more options and probably a 'cleaner' solution.
    Thanks and regards.

    This sounds like a really interesting project. I�m not exactly sure what the details of your application are, but I can tell you that the counter input and output signals are only available on the 68-pin connector of the 660x card.
    If there are any other questions you have about this card or how to interface to it, please let me know.
    Have a great day!
    Ken S.
    National Instruments

Maybe you are looking for

  • How can I print an envelope from the template Cards and Invitations on my HP Laserjet P2015?

    I have been trying to print an envelope in Pages 09 on my mac from the template called Cards and Invitations. I select a template that is 5.75 x 8.75 inches. When I go to print this envelope with my HP Laserjet P2015 and correctly load it as the manu

  • SQL Server Insert

    Hey gang, i was trying to test loading data into sql server via JDBC. Here i am having problem. I have no problem inserting into columns, where the data type is 'int', and 'float' (SQL Server column type). But i am running into problem when i try to

  • How to send a group email where the recipients' names and addresses remain anonymous?

    I wish to send out an email to a "Group" in my Apple Contacts. I want the several recipients in the group to be unknown to each other, where their names and addresses are invisible – except myself, the creater of the email. Does Apple 'Mail' and/or '

  • Photo quality--why so bad?

    I'm so disappointed with the quality of my photos--never had this problem before! I've got a 28mg image that looks awful--blurry, loss of color quality, etc. What happened? No tips on apple help.

  • Regarding displaying calmonth in report.

    Hi All, In one report my client wants to get the sales per month. But it is acutally displaying per date. I have checked the infoobjects and there are both calday and calmonth available in the InfoCube. But there are only values for the Calday wherea