Timebase of the pci6602

Hello.
I employ a PCI6602 for period measurement using the two counter (wide range) measurement method. The task is created with the DAQ Assistent but unfortunately there I have no access to some properties, e.g. timebase. What's the default timebase and how can I read and/or change the properties that can't be cofigured with the DAQ Assistent?
Thanks a lot!

Depending on the settings of the DAQ-Assistant (Min & Max Period), the timebase is calculated, and set to the optimal timebase the hardware provides. So there is no default timebase. You can read the selected timebase by wiring the DAQmx Channel Property Node (Found in the DAQmx Functions Palette) to the Task-Output of the DAQ-Assistant VI and Selecting the Property "Counter-Input-->General Properties-->Counter Timebase-->Rate". You can then read the value, and with the same property node you can also write a new value to this property and set a new timebase.
Hope this helps.

Similar Messages

  • How can I set the timebase in the FPGA API for the NI 9853 CAN module?

    Hallo,
    is there anybody familiar with cRIO, especially the NI CAN 9853 Modul?
    When starting communication with a CAN Bus  you can get a receiving CAN Frames from the FPGA I/O Node with a timestamp.
    How can  I set  this  timebase in the CAN Controller, because the CAN communication starts every time with the same timebase.
    Compared to the CAN API  on a PC the timebase for the communication is set when the Open Frame API VI is used?
    From that time the CAN Contoller assume the timebase from the PC.
    Whats about the FPGA API?
    Martin

    Hallo Dirk,
    thanks you
    for your answerer regarding my question.
    The last
    question belongs to my intention, to get absolute Timestamps from the NI 9853
    CAN interface. As you said it always starts from zero when starting the
    application.
    For my application
    I would like to get a timestamp with the local time I start the CAN communication
    and every CAN Frame should be logged with the Timestamp it is actually send on
    the CAN BUS.
    How can I achieve
    it?
    My first
    thoughts were to add up the timestamp for every CAN Frame counted from zero to
    an absolute Timestamp when starting communication. But I have got some wrong values.
    Maybe I did something wrong using the high and low part of the Timestamps I got
    from the CAN API.
    Do you have
    a suggestion for me?
    MartinW      

  • Getting 2nd TIO of the PCI6602 to perform buffered event counting via register-level programming

    I got the first PCI6602 TIO to perform buffer event counting using interrupt. However, I could not get the second TIO working. I think I have initialized the proper registers in order to work with the second TIO, i.e.
    1. Addressing all registers of the second TIO at 0x800 offset.
    2. Binding the clock to counter 4-7 (set 0x00200000 to the Clock Configuration register). I am using the internal Timebase_3 clock which is 80MHz.
    3. Tried setting 0x8000 to the Global Interrupt Control register at both its offset location (with 0 offset) and with 0x800 offset (2nd TIO offset location).
    Am I missing something here? I got no interrupts from the PCI bus and I got 0xff
    ff when I tried to read the Status register.

    Al,
    I have been experimenting with the 6602, but I have not been able to see any of the interrupts generated by the counters. I have tried both TC mode and an external signal on a single GATE (G0). The Gi_Status_Register indicates that the interrupts are occuring (appropriately for each mode), but I can't see them on the bus (my interrupt handler is never invoked; cat /proc/interrupts shows 0 interrupts).
    Could you pass along any tips on how you did it?
    Thanks!
    -Rob

  • DasyLab Timebases - Can anybody explain the various clocking methodologies ?

    Hi All.
    I,ve been using DasyLab for at least 10 years and as you'd expect become quite proficient.
    Mostly I use Measurement Computing USB pods or DataShuttles.
    But the exact homology of the Time Bases, their physical methods of generation, and particularly the optimum logical choices,
    still remains mysterious and obscure. I can always get a program working you understand, but selecting DasyLab clocking feels like playing Tetris.
    Any insight would be welcomed.  Does anybody see the 'Highest Governing Concept ' here ?
    Thanks and respect.
    DaveTheRave

    Generally speaking, you want to use the hardware based clocking, since the hardware usually has the highest resolution clock.
    When we introduced the Time Base concept, it was to address the new feature that allowed more than one DAQ device to be connected to the PC. Each device may have its own clocking, and some allow you to connect and synchronize multiple devices (Master/Slave clocking).
    One major driver, the IOtech driver, decided to stay within the original Driver API, which allows only one time base, but they made changes in the driver to handle master/slave and sample rate decisions. 
    Other drivers embraced the Time Base concept, and were developed using the "Extension DLL API", starting with the National Instruments driver, and picked up by most driver developers, including Measurement Computing, UEI, instruNet, and many others. 
    So, DASYLab now shows you timing sources from at least two devices -- 
    Driver Timebase is associated with the installed driver - Sound Card, Demo, or IOtech, typically. 
    DASYLab Timebase is a software timed source, usually used for slower (less than 100 samples/sec) timing
    As you add drivers, you will be exposed to that manufacturer's choice of timing:
    National Instruments NI-DAQmx - timing is set in NI Measurement & Automation (MAX)
    You have choices of 1 sample on demand, n samples, continuous
    Each task has its own timing, so one board may have a timebase for Analog Input, Analog Output, Digital Input, Digital Output, etc.
    Measurement Computing MCC-DRV 
    You have two timebases available for most devices, Hardware clocked or software clocked. 
    Some devices only allow hardware clocking for one subsystem - the other subsystems would then use the software clock
    Some devices only allow a single sample rate (USB-TC, USB-TEMP are 2 s/sec)
    Some devices use the settings in instaCal to determine allowed sample rates (USB-2416, USB-2408); individual channel choices may limit the overall  (aggregate) sample rate.
    Analog/Digital output timing can be configured "using the input timing" or with driver based timing - many devices only support software clocked ("slow") timing on outputs.
    UEI - time bases are not created until you create modules that require them
    InstruNet - time base is determined by a mix of the DASYLab time base and the individual channel settings
    If you open a worksheet and you see a time base that is in (parentheses) - the driver or hardware was not found, but the worksheet remembers it.
    Many modules are software data generators - the Generator, the Switch, the Slider, and they offer an option to select one of the available time bases. If you use a switch, for example, to control a relay, the switch timing should match the other inputs of the relay. The switch and the slider also offer a "with input" choice, which allows you to wire an input to them, to force the module timing to match the input timing. 
    Some Input/Output modules have to use software timing on the data - the RS232 Input, for example. It has to assume that the input samples are not equidistantly spaced, and tags the timing with "triggered". You can force it to use hardware timing in the Options, and fill the data block with old data until new data is received. 
    Confusing? Yep. 
    What's the right choice? 
    Hardware vs. software clocking - for sample rates above 100 samples/second, you will want hardware clocking. For slower rates, you may be forced to use software clocking. 
    DASYLab vs. Driver vs. Timebase A HW vs. Timebase B SW
    I would use the device's clock whenever feasible. It's more reliable and accurate than the PC clock.
    So, for Measurement Computing USB "pods" (I like that word!) - use the MCC-DRV timebases when ever possible. 
    Datashuttle... are you in the UK? The original Datashuttle is long gone, and only used the Driver timebase.
    The UK sold (sells?) a version of the IOtech PersonalDAQ 54/55/56 products as a Datashuttle.
    Funny that you should mention tetris... someone may have written a tetris module for DASYLab as a exercise.
    - cj
    Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.

  • In Delayed Pulse Generation vi,Problem With THE PULSE WIDTH??

    In Delayed Pulse Generation vi, I want to input a very low number for the Pulse Width while using an external timebase source. But the minimum pulse width has to be 2. Does anyone know how can I solve this problem??

    Hey 45,
    Unfortunately, there is no way to generate a pulse width smaller than 2x your external timebase.
    There is an option to create a pulse of arbitrary width of your external source if you can afford some software processing in between. What you can do is use 1 counter to measure how many source edges of your card's internal timebase (80 MHz for TIO only, 20MHz or 100kHz for TIO and STC) your external signal is. This uses pulse width measurement as the counter application. Once you know how many source edges it takes to represent your pulse, then you can use triggered pulse generation and use the internal timebase with the pulse specs set to create the exact pulse width you want (and delay) and you can use your external pulse as the trigger. Th
    is works well if your pulse is always the same width and you can measure it before hand. As an example, let's say your pulse is 20 internal timebase pulses when measured. This means you can use the pulse specs to specify a pulse width of 0.75 your pulse width by using only 15 internal timebase edges for your pulse width.
    I don't know if I was clear above or not but if you give me your exact application you are looking to achieve, I might be able to help you out. Hope that helps.
    Ron

  • How to use external timebase for Two Edge Separation measurement with PCIe 6351

    Hi
    I am working with PCIe 6351 x series DAQ card.
    counter measurements.
    Here i need to measure the time/no edges between two edges. Falling to Raising of two signals.
    I got the measurement with internal time base.
    here i need to synchronize the measurements with external clock from the external setup.
    so i need to use that external clock,timebase for the counters.
    Any solution please..
    Regards,
    Hari

    First, the VI you mention is NOT for STC timer/counters. Therefore, it won't work.
    If you want to get the time interval between two edges, you want to use the Functions -> Data Acquisition -> Counter -> Count Events or Time VI. This will do the function you are looking for.
    Mark

  • Why do I get error -1074388985 at CAN Connect Terminals when the Channel API has been stopped?

    While trying to establish synchronized CAN and DAQ using the Channel API, I get the error -1074388985 while attempting to connect the RTSI Clock to the master timebase.  The error message occurs each time I try to run the example VIs shipped with LabVIEW 6.1.  I am using a Series 2 PCI CAN card with a 6034E DAQ card.  Any ideas?  Tech support did not have a solution.

    Hi AVR,
    This warning means you have tried to change an attribute on a running object. This causes the warning and should not take place.
    Use the "Initialize' function instead of the "initStart" Function, then change the Attribute and use the "Start" function to start the communication, or stop the communication using the "stop" Function before you change any Attribute and then start again.
    Hope that helps
    DirkW

  • Synchroniz​ation of PCI devieces via the RTSI bus using the measuremen​t studio for Viusual Basic 6

    Hi everyone,
    I would like to synchronize a NI 4474 A/D card with a NI 6733 D/A card via the RTSI bus. Is there any way of sharing the timebase using the measurement studio for VB 6.0? It seems like it could be possible using the traditional NI-DAQ .DLL but I would prefer to do it with the ActiveX API.
    I am quite desperate, since all my attempts to use the CWDAQTools1.RouteSignal and CWDAQTools1.RouteRTSI command failed miserably :-(
    Thank you very much in advance!
    Federico

    Thank you very much indeed!
    Unfortunately it doesn't really work... I cannot use the DI options since my A/D card (NI 4474) does not support DI/DO... When using the other option (CWDAQTools1.RouteRTSI) I keep getting an error message that this command is inapropriate for my device (even though it does have a RTSI bus and allegedly it also supports time sharing...)
    Looking forward to your answer!
    Kind regards
    Federico

  • Beginner Q: timebase signal and clock

    What is the internal clock of DAQ MIO-16EX-50? Does it mean when you don't define your own clock, it will use the internal clcok to sample data? What is the rate of this internal clock?
    I am contuing other people's Labview DAQ program. he used external clock, but not the same as the Labview example, he used "clock config vi", set clcok to "0", then input his clock source and alternate clock rate specification. I ask why he did this, why he didn't use PFI7/startscan to input his external clcok. He said because this is the timebased signal. I don't understand. What is the difference when you use PFI7/startscan as external clock (like the example of Cont Acq&Graph ExtScanClk.vi) and his program. Can anyone give me some idea?

    May,
    The DAQ device has two available internal timebases, 20 MHz and 100 kHz. When an internal scan clock (STARTSCAN) is used, the actual clock is derived by dividing-down one of these timebases. An external scan clock can also be provided (for example, from PFI 7). Additionally, an external scan clock timebase (SISOURCE) can be provided to derive the scan clock. The following KnowledgeBase discusses the use of an external timebase in greater detail:
    How Do I Use SISOURCE as the External Timebase for the STARTSCAN Signal?
    So, the difference between the two programs you have referenced is that one uses an external scan clock and the other u
    ses an external scan clock timebase.
    Good luck with your application.
    Spencer S.

  • Premiere Pro CC - XML exports timebase always off, 24 as 30

    I constantly edit offline RED footage as ProRes proxys, and when I export an XML of the final sequence to relink, EVERY time the XML has all the clips as <timebase>30</timebase>, despite the fact that the media is always 23.976 fps in a 23.976 sequence. This ends up messing up my relinking process. I end up opening the XML in FCP7, immediately re-exporting the XML and ta-da, it's fixed, now they are all <timebase>24</timebase>. It's a very, very annoying step, especially when dealing with multiple sequences. I don't know too much about reading XMLs, but the FCP one says it's version 5 while PPro is version 4, wonder if that would have anything to do with it...
    Any ideas?
    -sam

    Hi Kenny - i know your thread is from last year - but we just hopped on this board looking for answers to the exact same issues you described in your post.  Unfortunately i can't see that you found an answer on here.  Did you resolve your issues?  And if so, can you please either let us know or shoot us an email?  [email protected]
    many thanks

  • XML Export Only Exports the Same Sequence

    No matter which sequence I select for XML Export, it only exports the sequence named "SNO Intro."

    Does your nested sequence have a different timebase than the parent sequence? Is it multi-cam? Are you selecting your parent sequence in the project window before exporting? If you copy everything from your nested sequence and paste it into the appropriate place in the parent sequence, does it export correctly? These are all just troubleshooting ideas to get to the real root of the problem.

  • How Can I Driving the PXI Backplane Clock with a PXI-6608?

    How Can I Driving the PXI Backplane Clock with a PXI-6608?
    Is the PXI Backplane Clock the timebase of the PXI Trigger BUS?
    How Can I use a PXI-6608 as the timebase of the PXI Trigger BUS?
    Thanks!

    Hi,
    The 6608 must be in slot 2 of the chassis. Once you make a call to the DAQ driver, the OCXO on the 6608 will be routed to the PXI_Clk 10 line.
    More information on the backplane and routing clock signals can be found in these Knowledge Bases:
    http://digital.ni.com/public.nsf/websearch/5EC3704​19A5ECA7A86256CFC0061C528?OpenDocument
    http://digital.ni.com/public.nsf/websearch/D5B8D4D​3B67DF1E086256BF8007BBF93?OpenDocument
    I hope this helps. Have a Great Day!
    George

  • Do I have to use an external clock with a cDAQ-9188 and NI 9401 to read a linear encoder? I'm seeing error message that implies that but the example code doesn't show it.

    We can set up a task that works on demand but when we go to continuous sampleing we see Error -200303, which claims an external sample clock source must be specified for this application.  However, some of the NI linear encoder example code doesn't show that (uses the cDAQ 80 Mhz clock) and the documentation didn't mention that. 

    It's mentioned in the 918x user manual:
    Unlike analog input, analog output, digital input, and digital output, the cDAQ chassis counters do not have the ability to divide down a timebase to produce an internal counter sample clock.  For sample clocked operations, an external signal must be provided to supply a clock source.  The source can be any of the following signals:
    AI Sample Clock
    AI Start Trigger
    AI Reference Trigger
    AO Sample Clock
    DI Sample Clock
    DI Start Trigger
    DO Sample Clock
    CTR n Internal Output
    Freq Out
    PFI
    Change Detection Event
    Analog Comparison Event
    Assuming you have at least one available counter (there are 4 on the backplane), I would suggest to configure a continuous counter output task and use its internal output as the sample clock.  Specify the internal counter using an "_" for example "cDAQ1/_ctr0".  The terminal to use for the sample clock source would be for example "/cDAQ1/Ctr0InternalOutput".
    Which example uses the 80 MHz timebase as a sample clock?  It is far too fast for a sample clock on the 9188 according to the throughput benchmarks (80 MHz * 4 byte samples = 320 MB/s).  There is also no direct route between the 80 MHz timebase and the sample clock terminal for the counters--making this route would use a second counter anyway.
    Best Regards,
    John Passiak

  • Can we lock 80 MHz timebase to PXI_CLK10 on PXI-6220 M Series DAQ?

    I am using PXI-6220 to measure Frequency/Period of 32768 Hz clock signal, accuracy is very important. I have provided signal to measure on Gate input of Ctr 0 (PFI 9). I am using 80 Mhz Timebase. I want to Lock PLL to PXI back plane 10 MHz reference (PXI_CLK10) which in turn is locked onto the 10 MHz reference via PXI-5600 on Slot 2 (External 10 Mhz standard is connected). so far I don't see a way to lock PLL to PXI_CLK10. Is that possible at all? see the image attached to this message.
    Attachments:
    M Series DAQ Question.png ‏62 KB

    Hello Abhatti,
    Based on the diagram that you have attached, the M-Series card can PLL to a higher accuracy clock such as the PXI Clock_10.  The way to configure this change using the DAQmx driver is route the signals using the DAQmx Timing RefClk.Src Timing property node.  Once you place down this property node, and specify the RefClk.Src attribute, you select the PXI-Clk10 as your reference clock source.  This will discipline the 80 MHz Timebase of the DAQ card to the 10 MHz reference clock of the PXI chassis.  Which chassis are you using?  Also, how have you PLL'ed the 10 MHz backplane clock to the PXI-5600 Downconverter?
    Michael L.
    Applications Engineer
    National Instruments

  • 40kHz ultrasonic pulse and time it take to receive the Pulse.

    Hi,
     i have developed  the following circuits:
    Tx: a Circuit that generates a 40kHz frequency using an LM555, the LM555 is wired to an AND gate which when using the test panel on MyDAQ(6216) i set cntr0 and set it to edge detecting i can count the number of edge detections when i enable the port High and when i switch it low it stops recording the counts.
    Rx: Recieving circuit contains an OpAmp which is fed into an LM567CN tone decoder which is tuned to 40Khz. when the recieving circuit PLL locks on to the 40kHz signal the output of the LM567 pin 8 switches to ground.
    Question: I am very new to NI and wondering where the starting point would be to create a VI that will trigger the Tx circuit and then measure the time it takes the Rx circuit to recieve the signal, this will intitial be done through air and then i would like to move it through a meduim such as water. Has  anyone tried or seen anything that would be of use to create a vi that would match this.
    Any help would be greatly appericated.
    Phil
    Solved!
    Go to Solution.

    Are you using a myDAQ or a 6216?  You mentioned both... I'm going to assume 6216:
    You'll want a two edge separation task, and also a digital output task.  
    The digital output will control the enable signal for the LM555.  Connect it from the digital output line to your AND gate as well as to one of the PFI lines on the 6216 (it will be the "first" edge).  Connect pin 8 of the LM567 to a different PFI line on the 6216 (the "second" edge). You can configure rising/falling polarity via the Create Channel VI (it sounds like your second edge will be "falling").
    Programming would be as follows (in order):
    1.  Configure the tasks as shown in the linked examples (i.e. create channel / configure timing).
    2.  Start the digital output task.
    3.  Write the digital output "low" to make sure it is initialized.
    4.  Start the two edge separation task (it should be buffered like in the linked example even though you are only reading one sample).
    5.  Write the digital output "high".
    6.  Read (one sample) from the two edge separation task.  Specify a read timeout long enough to ensure the falling edge is seen.
    7.  Write the digital output "low" (assuming you want to turn off the Tx when you are done with the test)
    8.  Stop and Clear both tasks.
    The measured result will have a 12.5 ns resolution using the default 80 MHz timebase on the 6216.
    Best Regards,
    John Passiak

Maybe you are looking for