Analog triggering on PCIe-6251 using BNC-2120 on Mac Pro?

Hello all-

There, does anyone know how an analog trigger using a PCIe-6251 card connected to a box of BNC-2120 interface?  I am running LabVIEW 8.6 on a Mac Pro OS 10.5.6 and my VI of analog data acquisition seems to work but hangs up waiting for a trigger.  The trigger analog signal must be applied to the terminal APFI0 and the BNC-2120 contains no connector with this name.  On the M-series cards, APFI0 corresponds to pin 20 on the map itself, but I was not to locate any information that shows how the pins of the connector BNC-2120 connect internally to different spring on its façade and BNC connectors.  Sales people NOR recommended the BNC-2120 as the correct one to use with the PCIe-6251, interface box so I think that probably one of the many connectors on the front panel of the box is wired to pin 20.  Am I wrong?  I spent hours to connect signals to the box in the hope of getting a trigger, and nothing has worked yet.  To make matters worse, reviewing the VI to trigger a data acquisition using a TTL signal connected to all of the PFI 0... 9 connectors on the BNC-2120 just causes of VI to give undefined error message ' specific 89136 route cannot be met because the hardware does not support it.»  The specifications for the PCIe-6251 indicate that a digital trigger should be possible through the PFI connectors, so it's a puzzle.  I have an interface BNC-2110 box in the case which turns out be a solution, nothing about it is named APFI0 either.  Any suggestion would be of interest.  Thank you.


Hi Ken,

Unfortunately, the BNC-2120 doesn't have a connection available on the APFI your M series line.  The BNC-2110 has this connection available.

A possible workaround is that you can trigger off channels of analog inputs as well.  Here is a screenshot of the M Series User Manual that shows the analog switch-off circuits:

There are a few caveats to trigger off AI channels (mentioned in Chapter 11 of the manual)

If you use a trigger to start, the analog channel that will be triggered off the coast of must be the first string in your scan list.

If you use an analog input as a reference or a relaxing break, it must be the only channel in the scan list.

I hope this helps!

Best regards


Tags: NI Hardware

Similar Questions

  • Strange problem with analog output PCI 6251 and BNC-2110

    I'm controlling current source of third parties using the connectors of analog output on my card PCI 6251 and BNC-2110.

    The current source needs an input signal of 0.1V. I tested it using a battery, the potentiometer and the voltmeter, and by manually adjusting the voltage of power current works - current output with control voltage scales according to the specifications and is relatively stable.

    The data acquisition card works too - when I connect a voltmeter to the AO0 AO1, the measured voltage corresponds to the target with great precision value.

    But when I connect the current source of third AO0 AO1 data acquisition card, the measured output voltage drops and fluctuates. This applies to both channels of the AO.

    I wonder what is the problem here. I suspect it could be a matter of the grounding - the current analog control of the source is an entry with two floating terminals differential. I tried to return the switches FS/GS on the BNC-2110, but that makes no difference.

    Anyone knows similar behavior? Does anyone have any suggestions?

  • Should what cable I use to sync my mac pro to my iMac book

    W hat cable should I use to sync my mac pro to my iMac book

    In order to offer you the best answer, please provide more information on what you're trying to do.

  • I have the new version downloaded from the Illustrator on my iMac, but I would use it in my mac pro book.   How to install this on my mac pro book

    I bought the new Illustrator CC 2015 and downloaded to my iMac.  I wish I could use it on my mac pro book when away from home.  Is this possible and, if so, how do I install it on my mac book.  I have the trial version on my book for mac at the moment, but are unwilling to pay for it again.

    Check on the Help menu in Illustrator what email address is given to logout

    Make sure it is the same address that you archived your iMac

    If this is not the case, check and verify with the correct address.

  • Output TTL triggers analog input with PCI-6251

    Hello, I'm new to LabVIEW and have a question that I hope I can get a response on this forum.  I am currently using a PCI-6251 DAQ card with a block of connection BNC-2120.  I would like raise an event on an input, for example a sine wave, which is connected to AI0 analog.  Then I would send a TTL pulse train via the digital output.  What I'm describing can be better understood by the images of this link:

    In the tutorial page linked above, they do mention the card PCI-6251, but when I read the specs and compared, 6251 also has analog and digital Board, trigger functions, as well as digital I / Os... so I think he should be able to do what I want it to do.  Can anyone confirm this?  If anyone could help me by providing a VI that could do what I ask, just to help me get started, would be greatly appreciated.  Thank you!


    Please post on the Forums OR! My suggestion would be to use build it digital Pulse - found in the Finder for example of OR. Open LabVIEW, go to help > find examples > input/output equipment > DAmx > generating digital pulses > generate digital Pulse-redeclenchables. Change the type of trigger for this departure vi > Analog edge and make the source one line APFI (pin 20 of your card is APFI0). This will generate a pulse based on an edge similar to a level that you specify.

    I hope this helps!

  • Blocking of blue screen with the analog voltage (WinXP, PCI-6251)


    I'm looking to solve a problem of blue screen with my measure blocking
    application, which I am developing with C++. Blocking seems manifest
    a little random after a variable amount (500-50 000) of voltage analog
    measures. My application needs to make a huge amount of these digitally
    trigger voltage measures after a certain period of time, and I'm using a
    task to do. The task is stopped and started after a single measure
    which is done around 10 000 - 100 000 times per second. For this
    because I do synchronized with the PCI-6251 map data acquisition and
    Ztec oscilloscope card. It seems that the probability of blocking could be
    associated with
    the frequency of measurements of voltage that I perform.

    the app itself is multithreaded, but I'm blocking concurrent access
    the card with lock - all access to the card are behind a single mutex

    lock, so simultaneous access is blocked. In any case, all data acquisition
    o the map is initially a single thread, which is dedicated to the acquisition of data

    I also did stress tests with Ztec scope map, which does not
    in all the problems. I also disabled in order of acquisition of Ztec map data
    Make sure that it wasn't the card scope, the origin of the problems - the problem
    persistent, so this seems to point towards the direction of the nidaq map.

    The deadlock appeared when I used the original supplied with drivers
    card. I installed the latest drivers (removed the device from)
    ' Windows
    Device Manager and your application Measurement & Automation, reinstalled), but the blue screen still appears.

    Blue screen gives me a few debug data, but it does not mention any

    files .dll or something that would be of course point to a specific file (driver). I enclose at least partially matching code snippets.

    Hello again! I've been in contact with a local support person, who suggested that I have use DAQmx_Val_FiniteSamps instead of DAQmx_Val_HWTimedSinglePoint. I don't have any other changes, but this (see below) and the problem disappeared, so this seems to be an acceptable solution, because I don't see at all why not do this way. (Thanks Henry!)

    DAQmxErrChk (DAQmxCfgSampClkTiming (task_reader, NULL, 100000.0, DAQmx_Val_Rising, DAQmx_Val_HWTimedSinglePoint, 1));
    DAQmxErrChk (DAQmxCfgSampClkTiming (task_reader, NULL, 100000.0, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, 2));

  • I want to use Siri on my Mac Pro 2013, but there is no built-in microphone.

    Great so Siri is now activated on your desktop with Sierra. How can I add an Apple flagship computer microphone, the 2013 Pro Mac in a cost-effective manner? It's not even a microphone jack! Help, please!

    Is your Mac has a headphone jack? Then try an Apple headset with a built-in microphone.

    I'm seeing this in the specification tecniques for Mac Pro:

    Audio combined optical digital output/analog line in mini-jack

    headphone 3.5 mm with headset stand

    The Headphone Jack would connect Apple headphones.

    Or use any bargain price USB microphone for speech input.

  • Error 200452 with break triggered DI on PCI-6251

    Hey guys,.

    I am writing a program to snoop on SPI communication between a microcontroller and two MAX-7221 display drivers. Essentially, I want to read the PIN Din of both fleas and convert the data stream in the numbers that are displayed on the front panel of devices (each chip controls two 3 figures, 6 total). The data is 16-bit and contains a 4-bit address and a 4-bit code representing the number b. I recognize these two values in the vi, convert code B in decimal and use the address to combine each digit in the corresponding 3-digit numbers that I can view and save to a file.

    Each chip has a Din row that contains data, a clock and a load signal (called CS). In my vi I acquire the data using the remote clock signal and use a trigger break to acquire only when CS is low. It worked perfectly to collect data of a single chip MAX-7221, but I started to run into problems when you try to acquire data of these two channels at the same time.

    Since I am on two different trigger and clock signals, I couldn't use a single data acquisition. I got a PCI-6251 card laying around and decided to use it to develop a single chip and my original USB-6361 to acquire the other. Acquisition data from as chips with the USB-6361 works perfectly, but when I try to acquire two Renault at the same time I get error 200452 associated with the trigger break PCI-6251.

    I did a ton of digging, but I can't seem to understand what the problem is. The Web site OR said that the PCI-6251 supports triggering of break, and any channel I use, I still get the same error. I even tried to use other types of triggers, but no matter what I do error 200452.


    Thanks in advance!


    It seems that the PCI-6251 card only supports digital break triggering on a similar task. You use it on a digital input task. 6361 USB supports triggering of break on the two types of tasks. That's why you get an error.

  • Outputs analog BNC-2120 to stop working randomly

    I have a BNC-2120 Module. I have the analog outputs implemented with an Assist DAQ. I'm running a square wave, or triangle wave at a very slow pace (.35 Hertz). I'm tracking signals with a waveform graph just before going to the modules DAQ help. The system works well anywhere from a few minutes to 25 minutes. The results seem to just stop working, but I still see the signal on the graphic display of waveform. I think that the BNC-2120 module has some questions. Someone had a problem where the output just stop working? I look in my program of VI?

    Hi gwing,.

    There could be a few possibilities that could go wrong. Could you upload your code? DAQ hardware do you use with the BNC-2120?

    Best regards


  • analog input PCI-6251, implemented

    Hi all

    Can I set the analog inputs of the PCI-6251 in configuration of mix (some in differential mode) and others in single ended mode. Because in my set up the differential option is grayed out.

    Thank you


    Yes, you should be able to do. You have 16 analog inputs. Differential, you will use two of them per channel. See the manual of series DAQ M. you can program channels on a M Series device to acquire with different

    reference to the ground. To allow m

    ultimode sweep in LabVIEW, use OR-DAQmx create

    Virtual channel.VI of the API OR-DAQmx. You must use a new VI for

    each channel or group of channels configured in another mode of entry.

    Don't forget that for a premium that you would for example wire HAVE 0 to the + side and AI 8 - side. So now you can not use the AI 8 for simple nerve. HAVE 1 corresponds to the AI 9 etc. until 7 AM, GOT 16.

    I hope this helps.

  • Analog output PCI-6251-DAQ-200016 memory overflow error

    NI PCI - 6251 DAQmx, AIMD-752 motherboard, dual core processor, a lot of speed and the ram running WinXP Pro & LabWindows/CVI

    get DAQ-200016 memory overflow error when I try to generate a signal of analog output with a rate higher than about 32 000 samples/second (?)

    going on what?  I have never seen it before.   Is this a problem with the motherboard?    "It's the same product on the CVI code example" \Cont Gen Volt Wfm - Int Clk\ContGen - IntClk.cws.

    If someone has had this problem, and is there a solution?

    Thank you

    PS: full text of the message reads:

    Measurements: On-board memory precision passing. Due to the limitations of system and/or the bandwidth of the bus, the driver could not write data to the device fast enough to track the rate of output of the device.  Reduce your sampling rate, change the method of transfer of data (from interruptions on DMA), use a product with more on-board memory or reduce the number of programs that your computer runs simultaneously. Task name: _unnamedTask<1> Code of State:-200016

    Well, I found my answer.   For later use, Olivia NI Apps Engineering suggested I have change the mechanism of data transfer by this Knowledge Base document:

    ... so I inserted the line of code between the creation of the area of OCCUPANCY of the channels and set up the example of clock calendar.

    DAQmxCreateAOVoltageChan( ...

    now, I am able to generate output to a 2.35 MS/sec... max sampling frequency not quite the 2.86MS / sec indicated in the specification 6251, but close enough that I'll stop complaining

  • Entered analog PCI 6251 not extent of tension of a mass flow controller


    I have a data PCI 6251 M acquisition with a break in Council SCXI 1302.

    I'm trying to measure a 0 - 5v analogue output voltage from a mass flow controller (check picture of PIN)

    When I measured with a digital multimeter the voltage of the flow signal (PIN2) and common signal (PIN12) I get a stable right tension between 0 and 5v depending on the flow set up. I can control the amount of the charge by providing a data output set point PIN8 and common PIN12 of the 0 - 5V analog signal.

    Now when I connect the signal flow PIN2 and on my DAQ signal common PIN12 AI and AIGND, I don't get readings on my labview VI of the AI. In addition the flow does not meet the setpoint voltage, it get stuck in a range of values no matter how I vary the OD 0 - 5V of data acquisition in setpoint PIN8 and PIN12 common signals.

    I have to add that I tried different ports HAVE with results of sam, and I also tried to measure my supply voltage with my HAVE and all the good work.

    It seems that the entry of AI affects the AO output voltages to my charge. What would cause this? That would be a problem of impedance adaptation?

    Management or ideas are appreciated.

    Thank you

    Ali T.

    Update for anyone that might interest you:

    I not connected to the ground of the power of the mass of the signal of FJA FJA.

    Once I did the acquisition of data reads all data as expected.

    So it turns out not to be a problem of acquisition of data, OR at all, but a game of question for my part, as I suspect is the case with most of the problems.

    Jeff Merci for your comments.

    Ali T.

  • Angular velocity using the entrance of counter BNC-2120


    I'm trying to measure the angular speed of the motor shaft with an angular encoder connected to counter input BNC-2120.

    I found this file vi in the forum in a discussion by Macdonald and duy.

    I'm doing the same... and I'm in the form of data values. but please can someone help me because I do not understand what degree or radians data of position and speed too if it is in rad/sec or deg / s etc...

    the iam encoder using 3600 gives impulses /revolution. Is it possible to graphically display the position / data speed while the vi are running.

    Kind regards


    Hello Fesmi,

    No change is required for the counter 0/connections to your encoder. You will use 1 meter unit NOR as the sample clock Source i.e./DeviceName/Ctr1InternalOutput. Version of LabVIEW 8.5 of the example has been attached.

    Kind regards

    M Ali

    Technical sales engineer

    National Instruments

  • PCI-6251 - Acquisition on hard drive


    I bought a PCI to acquisition model Multifunction PCI-6251.

    How much time Prime Minister of United Nations of in the know I'd like to connect a hard drive directly on this card, and what should be the characteristics of this hard drive in terms of size, speed of rotation and memory cache.

    From there, what are the software configurations allowing the acquisition of half a score of analog channels directly on the hard drive? Can we start the recording of the tracks on hard drive from Labview? And how the get?

    Finally I would like to know what kind of performance I could you reach in terms of number of "recordable samples and frequency acquisition

    Thank you in advance.

    Hi all

    xdaf is correct that you will need a host PC to communicate with the 6251.  The 6251 can acquire analog inputs to 1 MHz multiplexes (for 10 channels that would be 100 kHz per channel), so you will probably not all the problems at these rates simply by using the DAQ Assistant as mentioned xdaf.  That said, I wanted to take some time to more carefully address the following question:

    Q: "therefore, what are the software configuration used to acquire a dozen analog channels directly on the hard drive?"

    A: DAQmx 9.0 introduced a very cool feature called DAQmx Logging that will allow you to easily optimize your streaming to disk.  You can read more about it in the link provided, but essentially this function allows you to write directly on your hard drive since the DMA buffer without going through the application memory.  Comparing the two methods:

    Old method: FIFO edge > buffer DMA > LabVIEW memory > buffer DMA > hard drive

    New method: FIFO edge > buffer DMA > hard drive

    The new method will use minimum CPU since all transfers are implemented by DMA.  The result is a binary file of PDM (2 bytes per sample on a 16-bit card) which can be read with the viewer PDM or imported in LabVIEW for analysis.  The file header stores the calibration and scaling information.  If you need to integrate this file with other software, the following link contains more information: TDMS integrating third-party programs

    You also have the option, if you want to import the data into LabVIEW to look at one/one immediate treatment.

    I would probably also add that the benchmark of 1.2 GB, mentioned in the DAQmx logging Article would require a faster bus and configuration of the hard drive.  We used two 2 x 8164 matrices Raid in conjunction with a full chassis SMU cards simultaneously.  The 80 MB/s this mentioned xdaf is on par with some hard disks more quickly and is close to the practical limit of the speed of the PCI bus.  This is information probably just extra, since the data from your card PCI-6251 will be far from this limit.

    Even if rates continuously to acquire from a single card PCI-6251 should not be too demanding, I suggest you look into the new DAQmx 9.0 streamline registration of your data, optimize code and functionality for fast disk with minimal use of CPU.  I hope this has been helpful!

    Best regards


    PS once DAQmx 9.0 is installed, several examples can be found of LabVIEW under help > find examples... > DAQmx > Analog measures > power > TDMS Streaming... VI

  • Intermittent failure with PCIe-6251

    We had a power outage intermitant which was worse.  It seems to be due to the card PCIe-6251.  We have Labview 7.0 and DAQmx 8.1 the system as well as a PCI-GPIB and a PCI-6711.  Periodically, computer would lock up and reset either not conclude card, or not able it to reset it until the power of the full test system was cut long enough for + 5V standby to drain.  The problem seemed to be exacerbated by the ambient temperature.  When the test system has been moved from other external heat sources (Ie the cooler for the laser), the problem seems to disappear or has been reduced to less than 1 time per week usually when labview program was executed.

    The test case itself has recently been rebuilt and the problem returned with a vengeance.  After additional cooling was added, and the problem persists, we started checking temperatures of housing.  The internal system temperature is 42 C worst such case reported by the chipset.  We have improved the power supply to make sure it wasn't a collapse of power line causing the problems.  When we catch the problem in the error log, it is an ATI video driver or NIPALK.sys because the production chain continues to go down to this we charge software is installed on a different machine and moved the cards and installed.  It seemed to work perfectly for maybe 2 hours and then started throwing memory parity errors.  The computer is outside the grid of test and cold.  If we draw the PCIe card, the parity errors go away and all is well.  The problem is, is that it is the heart of the control system.  The original computer is not plant 2 or 3 times a day, so it takes a good amount of time trying to verify a fix.

    Unless I'm mistaken, DAQmx 8.1 is the latest driver that supports labview 7.0 DAQmx 8.01 is the other driver that supports the card and labview 7.

    Are there known problems with this card that I'm not find?

    The chassis that has had some parity errors to date had a best time of execution of 20 hours between grave down.  If it generates a parity error, there is no entry in the registry so that I'm not sure that a kernel image will be generated.  Accident yesterday morning, the computer will not re-start until the PCIe card was off for a good amount of time and case open to cool (it was the hottest part of the system by empirical methods, no part was what I considered warm) so the first case has been modernized with casefans directly cool the PCIe card.  This system comes to pass in a few minutes.  If that doesn't work we'll go to labview 8.6 on this system to see if the newer drivers help and finally throw the PCIe and move/o down in the VXI chassis.  The latter may be constrained according to the when the system crashes then.  I'm a bit wary of permutation of 7.0 to 8.6 on a production line with no available time to debug the old software with the new version of Labview.

    External connections make you refernce to?  The power of auxillery connection or the connection to the BNC-2090?  At this point, we are only the e/s digital used on this card.

Maybe you are looking for