Triggering possibilities by the NI PCI-6052E board

Will you tell me, how to use the NI PCI-6052E board for analog and digital triggering. I want the trigger to begin the measurement, to acquire data before the trigger occurs. In other words, the board must response to a pulse input. Also I want to know other trigger capabilities of the board.
Thanks,
Gen

I am happy to let you know the PCI 6052E has both analog and digital triggering options. You can set your analog inputs to start acquisition on a rising or falling edge of your trigger pulse. If you are interested in acquiring data before your event trigger you can set up a buffer to capture pre-triggered data. Assuming you are programming with LV and Traditional DAQ you can reference the following app note:
http://zone.ni.com/devzone/conceptd.nsf/webmain/2A03115556FB233386256870005BB522?opendocument
If the link above does not work, go to
www.ni.com/support
under option 3. select 'Tutorial/Application Note'
Then do a search for 'Tips and Techniques for DAQ Triggering'
If you are using the LV 7 and the express VIs to set up your DAQ, look under the
triggering tab of the express vi to set up analog vs digital trigger and buffers for pre-acquisition. If you don't have LV 7, I highly recommend it because the express vi's will help reduce your development time.
-JVH

Similar Messages

  • What needs to be done in order to bring in a signal to a SCB-68 and have the SCB-68 caculate the frequency, etc. using a PCI-6052E board in LabView?

    I am using a basic function generator to create a signal to channels ach0,ach1,& ach2, using resistors as a way to change the signal a bit. I have built a VI to see these three waveforms, but I'd like to be able to use the internal counter of the SCB-68 to measure the pulse width and be able to convert it into a frequency measurement that can be displayed on the front panel. I've looked in the NI 6052E manual, but it is very vauge. Any help would be useful. Thanks
    SQ

    Hello;
    First of all, you need to make sure the three waveforms are TTL leveled, since the counters only support that data type.
    After you clear that out, you will need three counter to do frequency measurements on the three waveforms, and the board you have there has only two counter available.
    In case you have the thre counters, you can connect the pulse trains on the gate input of the counters, and use one of the two timebases to be the source input. You need to configure the counter to do buffered event counting. Then, the number you catch in the buffer will be the number of pulses that elapsed in between two active edges of your pulse train. Since you will know which time base you chose, you can do a simple math to calculate the total time.
    Hope this
    helps.
    Filipe A.
    Applications Engineer
    National Instruments

  • PCI-6052E resource test fails at startup

    Hello,
    I am using a PCI-6052E board on an XP machine. The driver is 1.8.2.f0 and MAX version is 3.1.0.3021.
    Every time I boot the system, the resource test in MAX fails: the DMA resources do not appear. The board must be reinitialized manually in MAX or through the DAQmxResetDevice function in any program. This works always well and the board can then be used properly.
    I would appreciate very much any hint on how to have my board fully ready at startup.
    Thanks a lot.
    Pascal.

    Hello PascalP,
    I have first some questions :
    What do you mean when you say : "The driver is 1.8.2.f0 "?
    Do you receive code error? If yes, can you please send it?
    Please do the following:
    1) When you boot your PC, launch Measurement and Automation Explorer (MAX). Under devices and interfaces -> Traditional NI-DAQ Devices, right-click on your PCI-6052 and select Properties. Note how many DMA channels are assigned to your board (may have up to 3 channels). Click Test Resources. If the device fails, please continue with (2); otherwise, open up a Test Panel and verify that it works. Then close out of MAX and try running the examples that uses the device to see if you still have the error. If you still see the error, please let me know.
    2) The device is not installed properly. Shutdown the computer, remove the card and reboot. Power down again, add the card, and power up the computer. If it still fails in MAX, continue to 3.
    3) Try switching PCI slots. You may also need to uninstall and reinstall the driver. Be sure to remove the hardware anytime you remove the driver.
    4) Try installing the driver and then adding the card on a different computer.
    If after all of this you still have trouble, please let me know what has failed and what operating system you are using and give me more information about you PC.
    Hope this helps.
    Sanaa TAZI
    National Instruments France
    Sanaa T.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> http://www.nidays.fr/images/081110_ban_nidays09_468X60.gif

  • (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

  • Help calibratin​g the PCI-4474 Board

    Spoke with a rep from NI. They said in order to externally calibrate the PCI-4474 board, I should use the same procedure as the 4472. My question is this: The steps are:
    1. connect the calibrator voltage to all input channels.
    2. Set the voltage to 5.00V
    3. Check the date (using nidsacal.dll)
    4. Call Calibrate_DSA (I am assumiing I can use DSA Calibrate.vi. This is where I run into problems. I am suppose to set "setofCalConst" to ND_USER_EEPROM_AREA. The calibrate.vi does not have this option. Am I missing something. Then step 5 is to
    5. Call copyCalConst to move the info stored in the user area of the EEPROM to the factory area of the EEPROM. This step I have no problem with because it is called from nidsacal.dll

    Hi Kimberly,
    Actually, you do not need to specify the ND_USER_EEPROM_AREA. The prototype in the DLL is Calibrate_DSA (deviceNumber, operation, refVoltage) and you only need to specify the device, the operation (internal or external calibration), and give the reference voltage. These should be the same three inputs you have available from the DSA Calibrate VI in LabVIEW. Simply specify the device, external calibration, and give the reference voltage and you're set.
    Best Regards,
    Justin Britten
    Applications Engineer
    National Instruments

  • Where can I download IMAQ driver version 1.0 for the PCI-1408 board?

    Because of the computer crash I have to reinstall the NI-IMAQ driver version 1.0 for my PCI-1408 board. I couldn't find the original IMAQ driver which came with the PCI-1408 board. Could anybody tell me where I can download the software? Thank you very much.
    Solved!
    Go to Solution.

    Lowest version I could locate on the ftp site was 1.5, that may work:
    ftp://ftp.ni.com/support/imaq/pc/ni-imaq/
    -AK2DM
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    "It’s the questions that drive us.”
    ~~~~~~~~~~~~~~~~~~~~~~~~~~

  • CPU-Usage during control of a DC Motor with the PCI-7344 board?

    Hello!
    I want do control a DC-motor (no stepper motor). Now i´m using the PCI-6527 board and simulating the delay between "high" and "low" on the Simulate-signal-vi. This works fine while no other process on the PC is running. The CPU-usage rises up to 100%. Is it possible to use the PCI-7344 board for controlling my DC-motor and having enough CPU resources to do other things like capturing pictures with a cam at the same time? The CPU is a Pentium 3 1Ghz.

    The PCI-7344 is a perfect solution for your problem. This board is designed for motion control applications and it's running everything on its own DSP and CPU:
    Trajectory Generation, PID control, limit switch monitoring and so on.
    Thus the PC's CPU is free for other tasks. Please note that you need a position feedback signal from a quadrature encoder.
    Best regards,
    Jochen Klier
    National Instruments Germany

  • To what limits (lower and upper) are the PXI-6052E boards calibrated for their various gain settings?

    I am trying to get some boards calibrated by our metrology lab, but I can't find the relevant information.

    I've viewed all, and downloaded most, info at the link that you've mentioned. Unfortunately, the data I'm looking for isn't there. In the E Series Calibration Procedure document, there is an extensive listing of tables that contain calibration data points for a variety of E series boards. However, the 6052E board isn't listed. Elsewhere on the ni website, there is a note to use the 6034E/6035E tables for the 6052E boards. These tables do not contain all the gain settings for the 6052E. I would assume that the 6052E boards were factory calibrated at all possible gain combinations.

  • PCI-6052E doesn't save all data, buffer too small?

    WinXP,Labview6.1,PCI-6052 board,collect data from all 16 channels every 5 seconds
    (Test 1)
    I set external scan clock 10KHz, external channel clock 200KHz, buffersize 10K, "number of scan to read" 10K, theorically, in each file I should have 50,000x16 data. But my result is not right: every 5 seconds I got a file, but in side those files, the data is either 3000x16 or 2000 x16 alternatively. For example:
    File1 is 3000x16
    File2 is 2000x16
    File3 is 3000x16
    File4 is 2000x16
    File5 is 3000x16
    File6 is 2000x16
    During the simulation, I see some change in the "scan backlog", but the number is not accumulated, for example, the numbers appeared are,36,0,0,..89,0. No error during the simulation. But when I stop the program I got the error: AI read is not enough fast for the data acquisition...
    (Test 2)
    When I set external scan clock 5KHz, external channel clock 100KHz, buffersize 5K, "number of scan to read" 5K, my result is right: I got a file every 5 second, and in each file therea are 25,000x16.
    Why some data missing in the test one? The PCI6052 board clock is 333KHZ, so my setting of external scan clock and channel clock should be ok. The number of scan to read is set to as the scan rate, so I got accurately one second tiem. Is there something related with the board buffer size and setting or computer is not faster enough?
    Thanks very much for help

    There are a couple different possibilities for why the data is not all in one folder in Test 1. First of all, I noticed that you expected each file to have 50,000x16 data, but you said that each file had 3000x16 and 2000x16. Is that correct or is it 30,000x16 and 20,000x16? If what you initially said is correct it looks like you might be losing some data. However, if you meant to say 30,000x16 and 20,000x16 it looks like all of the data is there but it is just in separate files.
    You are trying to read a lot of data in a little bit of time, so it is very possible that your computer cannot keep up with your settings. Also, the type of file you are trying to write the data too could be the reason you are not seeing all of your data. Excel is very slow and if you are writing to an Excel spreadsheet this could also be the reason.
    The numbers that you were seeing in the "scan backlog" look fine to me. When the number increases that means that you have data in the buffer that is ready to be read. When the number drops to zero that means all the data has been read. So, what you are seeing is not a problem.
    Do you have to read at such a fast rate? If not I would just keep it like test 2.
    Hope this helps.
    Jenk

  • PCI-6052E, C-file Programming, DAQ_Rate

    I am trying to write a simple c-file to collect some data with my PCI-6052E
    Card. The card should be able to handle a sample rate of 333kHz, but I am
    finding even if I ask for all sixteen channels at 10KHz using the DAQ_Rate
    function, I get an error with the time on SCAN_Start.
    The folloing code snip-it generates the error:
    << Snip it>>
    f64 dSampRate = 10000.0;
    f64 dScanRate = 10000.0;
    i16 iUnits = 0;
    iStatus = DAQ_Rate(dSampRate, iUnits, &iSampTB, &uSampInt);
    iStatus = DAQ_Rate(dScanRate, iUnits, &iScanTB, &uScanInt);
    iStatus = SCAN_Start(iDevice, DataBuffer, ulCount, iSampTB, uSampInt,
    iScanTB, uScanInt);
    printf(" \tiSampTB =%d\n",iSampTB);
    printf(" \tuSampInt =%d\n",uSampInt);
    printf(" \tiScanTB =%d\n",iScanTB);
    printf(" \tuScanInt =%d\n",uSscanInt);
    << Output >>
    iSampTB = 1
    uSampInt = 100
    iScanTB = 1
    uSscanInt = 100
    Error: -10092
    Some devices require a time gap between the last sample in a scan and the
    start of the next scan. The scan interval you have specified does not
    provide a large enough gap fo rthe board. See your documentation for an
    explanation.
    But if I use the following code I do not get an error:
    << Snip it>>
    f64 dSampRate = 10000.0;
    f64 dScanRate = 10000.0;
    i16 iUnits = 0;
    iStatus = DAQ_Rate(dSampRate, iUnits, &iSampTB, &uSampInt);
    iStatus = DAQ_Rate(dScanRate, iUnits, &iScanTB, &uScanInt);
    iStatus = SCAN_Start(iDevice, DataBuffer, ulCount, iSampTB, uSampInt,
    iScanTB, 0);
    printf(" \tiSampTB =%d\n",iSampTB);
    printf(" \tuSampInt =%d\n",uSampInt);
    printf(" \tiScanTB =%d\n",iScanTB);
    printf(" \tuScanInt =%d\n",uSscanInt);
    Could anyone point me in the correct direction?
    Please reply directly to
    tgaudett@n
    mr.mgh.harvard.edu
    Thanks in advance,
    Tom

    Thomas:
    The second case works because you are disabling the scan clock, thus making
    the acquisition "round robin" based on the sample clock.
    If you want to make the first case work with 16 channels, I suggest you
    change the dScanRate to this:
    > f64 dSampRate = 10000.0;
    > f64 dScanRate = 10000.0 /(16+1);
    The +1 is just to offer a buffer time.
    However, this means that your effective sample rate per channel (aka
    dScanRate) is now 10000/17. Is that ok?
    If you want the effective sample rate per channel (dScanRate) to be 10kHz,
    then you need to bump up dSampRate to 10000 * 16 (=160000, which is
    achievable on this device) or greater so that the A/D converter has enough
    time to go thru all the 16 channels and still make the dScanRate.
    I hope this helps.
    | Ken Sadahiro ([email protected])
    | Sr. Software Engineer, User Advocate
    | Systems & Architectures: Applications Group
    +----+-------------------------------------------
    | National Instruments Corporation
    | 11500-A North MoPac Expressway
    | Austin, Texas 78759-3504 USA
    | Tel: +1.512.683.8806
    | Fax: +1.512.683.8641
    | URL: http://www.ni.com/
    Thomas Gaudette wrote in message
    news:[email protected]...
    > I am trying to write a simple c-file to collect some data with my
    PCI-6052E
    > Card. The card should be able to handle a sample rate of 333kHz, but I am
    > finding even if I ask for all sixteen channels at 10KHz using the DAQ_Rate
    > function, I get an error with the time on SCAN_Start.
    >
    > The folloing code snip-it generates the error:
    > << Snip it>>
    > f64 dSampRate = 10000.0;
    > f64 dScanRate = 10000.0;
    > i16 iUnits = 0;
    >
    > iStatus = DAQ_Rate(dSampRate, iUnits, &iSampTB, &uSampInt);
    > iStatus = DAQ_Rate(dScanRate, iUnits, &iScanTB, &uScanInt);
    >
    > iStatus = SCAN_Start(iDevice, DataBuffer, ulCount, iSampTB, uSampInt,
    > iScanTB, uScanInt);
    >
    > printf(" \tiSampTB =%d\n",iSampTB);
    > printf(" \tuSampInt =%d\n",uSampInt);
    > printf(" \tiScanTB =%d\n",iScanTB);
    > printf(" \tuScanInt =%d\n",uSscanInt);
    >
    > << Output >>
    >
    > iSampTB = 1
    > uSampInt = 100
    > iScanTB = 1
    > uSscanInt = 100
    >
    > Error: -10092
    > Some devices require a time gap between the last sample in a scan and the
    > start of the next scan. The scan interval you have specified does not
    > provide a large enough gap fo rthe board. See your documentation for an
    > explanation.
    >
    > But if I use the following code I do not get an error:
    > << Snip it>>
    > f64 dSampRate = 10000.0;
    > f64 dScanRate = 10000.0;
    > i16 iUnits = 0;
    >
    > iStatus = DAQ_Rate(dSampRate, iUnits, &iSampTB, &uSampInt);
    > iStatus = DAQ_Rate(dScanRate, iUnits, &iScanTB, &uScanInt);
    >
    > iStatus = SCAN_Start(iDevice, DataBuffer, ulCount, iSampTB, uSampInt,
    > iScanTB, 0);
    >
    > printf(" \tiSampTB =%d\n",iSampTB);
    > printf(" \tuSampInt =%d\n",uSampInt);
    > printf(" \tiScanTB =%d\n",iScanTB);
    > printf(" \tuScanInt =%d\n",uSscanInt);
    >
    >
    > Could anyone point me in the correct direction?
    > Please reply directly to
    > [email protected]
    >
    >
    > Thanks in advance,
    >
    > Tom
    >
    >

  • Do the triggering signals for the DALSA CL-P1 4096 camera work properly?

    (Since I wasn't sure if anyone had seen my additions to the question "How do the DALSA CL-P1 4096 attributes correspond to the i/o trigger signals?" 6/3/2002, this is an addition to that question.)
    We are using a DALSA CL-P1 4096 camera with the NI IMAQ PCI-1422 image acquisition board, and we believe the signals are not triggering properly on the "Controlled" integration setting. All images are coming out black, but all signals are present. What we, as well as DALSA's support believe the problem is is that the PRIN signal goes low before LVAL goes high. Attached are the timing diagrams that we are getting and which we should be getting (provided by DALSA support). We would like to
    know if there is anything you can do for us if this is actually a problem with how the board is triggering the control signals (i.e. if there is a patch you can provide us, or a way to program how the board triggers the signal). Thanks for all your help.
    (Also see the question "How do the DALSA CL-P1 4096 attributes correspond to the i/o trigger signals?" )
    Attachments:
    IO_Signals.bmp ‏28 KB
    P1Timing.bmp ‏16 KB

    I was wondering why I hadn't heard from you and when I looked at your previous question I saw that my last post didn't make it to the page. But I see what you mean from the timing diagrams that you attached and we should be able to extend the length of time that the PRIN is high so that it doesn't go low until after the LVAL goes high. However, to do this it means changing the camera file (.icd) for that camera and that would probably be best while talking on the phone if possible so that we make sure that it all works correctly. Just go to www.ni.com/ask and generate a phone support request and it will give you a toll-free number to call. I'll be on the lookout for your call.
    Regards,
    JR A.
    Application Engineering
    National Instruments

  • Offset in AIs of PCI-6052E

    There is an offset (-118mV) in all of eight differential AI channels in my PCI-6052E card. How can I fix it?
    Thanks a lot!

    Hello stmxhlu,
    Please see this KnowledgeBase about troubleshooting offset readings.  You also may want to try putting the 6052E in another PC to make sure it is not the PC that has this offset.  You can also self calibrate the board in Measurement and Automation Explorer (MAX) by expanding devices and interfaces and then NI DAQmx devices.  Right click on the entry for your board and choose self-calibrate. 
    I hope these suggestions help!
    Laura

  • How can I acquire data in a PCI DAQ board using a SCXI rack?

    Hello.
    I have an acquisition system that consists in:
    · 3 PCI DAQ boards:
    - PCI-MIO-16-E-1
    - PCI-6052-E
    - PCI-6034-E
    · 3 cables to connect PCI boards and SCXI modules
    · 1 SCXI chassis:
    - SCXI-1001
    · SCXI modules + terminal blocks:
    - 4x SCXI_1121 + SCXI_1320 (for voltage analog inputs)
    - 1x SCXI_1520 + SCXI_1314 (for strain gauges)
    - 1x SCXI_1530 (for accelerometers)
    I have been trying to acquire different signals (specially voltage signals that are easier to reproduce) but I haven't been able to do it. I can't read anything from MAX or LabView. I have tested the PCI boards with a SCB68 terminal block (without any SCXI component) and they work properly. Problems appear when I use the SCXI chassis and the SCXI modules. I don't know if there is a problem with the hardware or it is a wrong configuration.
    I guess channels in the SCXI modules correspond to analog input channels in the PCI board they are connected to, but I don't know if I have to read data from analog input channels of the PCI boards or from SCXI channels that appear in MAX (I have tried both posibilities, but they don't seem to work).
    I don't know if I have to use Differential, RSE or NRSE configuration. I have tried all of them. Sometimes I only read noise, sometimes signal is fixed in a limit value (maximum or minimum, it depends), sometimes it's fixed in a value near zero,... I have changed connections and configuration options so many times I can't exactly say when one thing or another happens.
    I have tested only one PCI board with only a SCXI module in order to avoid interaction and confusion. Nothing.
    I think I have tried changing almost every option in MAX, but it doesn't work.
    I'm sure I'm missing something and solution is quite simple, but I can't find it.
    Can anybody explain to me how to connect and configure my system to read any signal? I only need a few steps or highlights. Maybe some clues about what the problem can be.
    Thanks!

    I have several comments and suggestions:
    A) Have you "added a device" in MAX and actually added the SCXI chassis? This step is necessary to get the chassis to work. Click on "add a device" and choose the 1001 chassis . Do this for one DAQ card and one module only initially. The Set Up wizard should walk you through the configuration. If you are unable to add a chassis within MAX, I suspect the chassis is not working correctly.
    B) Once configured, you can examine the SCXI channels in MAX as follows:
    1) Open the DAQ card in MAX and Open the Test Panels
    2) For the SCXI channel to view, use the following convention OB0!sc(n)!md(m)!ch where the letter (n) corresponds to the chassis number in MAX (usually = 1), the letter (m) corresponds to the module number (slot) where the module is located in the chassis, and (ch) represents the channel(or channels) you wish to view. So presuming chassis ID=1, and a module in slot 1, and you wish to view channel 3, you would type the following in the channel field for the DAQ card channel to view:
    OB0!sc1!md1!3 (note OB0!sc1!md1!3:6 will display channels 3 through 6)
    All of the SCXI channels for a given DAQ card are multiplexed through channel 0 of the DAQ card, Channels 1 and up are not used, hence the initial three characters in the SCXI call refer to "On-Board Channel 0 (OB0)"
    C) For the subsequent set up, it will be necessary to first add the additional modules to the chassis (when powered off). Then open MAX and update the chassis. (If you get an error then simply delete the chassis reference in MAX and add a new chassis). You will then be required to set the interface mode of each module as either parallel or multiplexed. In parallel mode, you associate a distinct module with a distinct DAQ card in the host PC. For those DAQ cards that will address multiple modules, you must first configure the modules to be in adjacent slots in the chassis and then assign the first module to the cabled DAQ card - then all of the modules assigned to that DAQ card should be configured in "multiplexed" mode.
    D) Once the chassis has been properly configured, you can click on each module and set the gains, filters, and terminal block types.
    I hope that this helps to get you started.

  • Is my PCI 6071E board damaged?

    Hello,
    I have a PCI 6071E board that has been working succesfuly until yesterday. I was working with the digital I/O lines (to generate three control signals that were connected to three operational amplifiers, as buffers), and suddenly, from one trial to another, the board stopped working. Some digital I/O lines remain at 2 volts (with some oscillation), with no response to my user program (in MATLAB). Other lines were at 0 volts. I tried to operate with the analog input and output, but no response was given. After that, I run the test panel in the Measurement & Automation Explorer, but it shows the error message: "The device is not responding to the first IRQ level". Is my DAQ board completely damaged?
    Thank you very much.

    Greetings,
    It does sound like your board may be in need of repair. There are a couple more troubleshooting activities I would suggest.
    First, you should try installing the board in another computer and see if MAX gives you the same error. If this error is not present, you can then test the functionality of your board with the Online E Series Diagnostic Utility. Below is a link to this utility:
    Online E Series Diagnostic Utility
    If these activites also indicate that your board is damaged, you can arrange for its repair by creating a phone support request at the following location:
    Request Support
    Spencer S.

  • IMac 24" has the Mobile PCI eXpress Module !! ??

    This is sweet news!! Seems that NVIDIA is the only one so far that has the MXM, that is probably why Apple has used it in the 24 inch iMac. SWEET
    Think of some of the possibilities for the Future of the iMac. I would really like to see the guts of this beast!!
    What are your thoughts on this guys?

    Sounds like a great move to me. I caught one of the early releases on the subject this morning.
    I think it probably was intended more as a means of producing a single logic-board and then simply installing the desired 128 MB or 256 MB video card as ordered. So, it was probably more related to internal cost savings (by eliminating the need to produce both 128 MB and 256 MB versions of the main logic board).
    In the end, I don't expect Apple to support the end user making these changes on their own later. But, it is nice to know that once your warranty has expired that you could go in and make a few improvements if you like

Maybe you are looking for