Not selectable in LabVIEW DAQ card

I installed a PXI-6122 card. The device is listed as "Device is working properly" Max:

Now, I want to select the device to a constant of the device in LabVIEW 2010, but is not listed there:

I guess it has to do with how MAX recognizes the PXI card, see previous announcement.

Does anyone have an idea how I could make this card works and selectable in LV?

The problem has been resolved by the NI DAQmx developers:

http://forums.NI.com/T5/Multifunction-DAQ/DAQ-cards-not-selectable-although-listed-in-Max/m-p/124778...

Thank you very much!

Tags: NI Software

Similar Questions

  • help on select M Series DAQ card

    I have type resistive sensor in response to the impact (special potentiometer). I want to first test its dynamic property (degree of sensitivity to the hose stream) and then to design a simple circuit to trigger an output transistor with threadhold predetermined impact.

    I need a DAQ card to save data to a tension between the potentiometer, and my output transistor. I felt a 250 kech. / s, and 16-bit (even 12) entry is good, and no requirement for AO / DO.

    I prefer to use a laptop for the data analysis. My questions:

    1 should be a type USB DAQ for this application? If this isn't the case, I will return to a PCI card.

    2. If the USB is selectable, I fight with the (USB - 621 x) Bus-powered and non-powered bus (such as USB - 622 x); insulated and uninsulated. Note that none of the supplied external DAQ isolated function.  Among my preference: USB-6221, USB-6215 or USB-6211, which is more suitable for my data acquisition?

    Thank you all.

    Sue

    Super! This morning, I decided to place the order with the USB-6221 and I am very happy that you assured me. Thank you, Khil.

    I acctually overlooked the phrase "single channel and aggregate" x 621. I have no doubt the rate of peripheral bus before but not found where was wrong. I also discovered that 6221 provides both sinking and DI I'll use two types of supply. Now I'm comfortable with the $ 200 more on externally powered one.

    Sue

  • Programming of LabView DAQ card

    I recently started using an NI USB-6211 data acquisition on my laptop card. I installed the driver software and data acquisition works, but when in the main package of LabVIEW, I don't have all the features tab measure or express to use to control data acquisition. I would appreciate help

    This version of DAQmx is not supported with LabVIEW 2012.

    Try to download the most recent driver, version 9.7, http://joule.ni.com/nidu/cds/view/p/id/3811/lang/en

  • selection of the daq card to get the angular position of 6 motors with encoder

    can you suggest me best daq card to use 6 positions of engines as outputs using encoders attached to the engines. I'll use single window for each engine. Or what can I use a single window for all the coders of engines?

    Hello Prabhakar7117,

    You need a counter for each encoder. Because you are going to use 6 encoders, you should get a DAQ hardware with 6 or more counters. Take a look at the PCI-6624 or PCI-6602. Another option would be a CompactDAQ chassis with modules that are able to access counters. Take a look at them.

    PCI-6624

    PCI-6602

    KB which cDAQ Modules can be used to access the counters of the shipped?

    Best regards

    Alina M

  • DAQ cards not selectable, that listed in MAX

    I have (re-) installing a PXI-6122 card on my computer. The device is then entered in the measurement and Automation Explorer, but differently from what I'm used to:

    -It's another symbol than two PXI-6259 cards I have (see image below).

    -It is not possible to create a task for the device using MAX because there is no such button.

    In addition, in LabVIEW 2010 "device" or "physical channel" enumeration control, it is not listed (unlike the two PXI-6229 cards).

    First of all, I knew that the card is broken. But it works correctly on another PC (with its own PXI chassis). Also, if I replace the card 6122 by another of the same type, the problem remains.

    Then, I uninstalled all National Instruments software on my PC, deleted the "c:\Program NIUninstaller Instruments' file and some registry entries NOR related and reinstalled LabVIEW 2010 and device drivers. Now, the problem I had with the PXI-6122 now occurs for all three DAQ cards on the system (i.e., the two 6229 maps AND map of 6122): MAX icon is one that has the 'label PXI', tasks cannot be created in MAX and no device / or physical channels is displayed in the respective controls of LabVIEW.

    Anyone have any idea how can I proceed?


  • Data acquisition in LabView for other suppliers DAQ cards that NEITHER

    Hello

    I am a beginner in LabView programming. I have a 32 channels base PCI card DAQ (i.e. PCI-1602 of the manufacturer, ICPDAS) and I want it to interface with Labview 8.5.

    So how cards DAQ in Labview 8.5, which are manufactured by other suppliers that NEITHER? Should I DAQmx (or some other driver) for that?

    What are the other drivers/components required to access of data PCI-1602 (device) of LabView 8.5 acquisition card?

    (1602-PCI card driver are installed in my win XP and dispalyed in Device Manager).

    Please provide some tutorial above mentioned the problem to interface.

    Please guide me in this regard. Thank you

    Waqar123 wrote:

    Hello

    I am a beginner in LabView programming. I have a 32 channels base PCI card DAQ (i.e. PCI-1602 of the manufacturer, ICPDAS) and I want it to interface with Labview 8.5.

    So how cards DAQ in Labview 8.5, which are manufactured by other suppliers that NEITHER? Should I DAQmx (or some other driver) for that? You will need the drivers from the manufacturer, of the Board of Directors.  In your case, "ICPDAS.

    What are the other drivers/components required to access of data PCI-1602 (device) of LabView 8.5 acquisition card? Same as above.

    (1602-PCI card driver are installed in my win XP and dispalyed in Device Manager). Ok.  Then take you care of my 2 answers above.

    Please provide some tutorial above mentioned the problem to interface. To learn more about LabVIEW, I suggest that you try to watch some of these tutorials.

    Please guide me in this regard. Thank you

    According to what you do with the DAQ cards, they can do the job however, from experience, there are some functions that I could achieve with the cards NOR that I couldn't with 3rd-party maufacturers.  This does not mean that this is your case. However, it is worth noting that it took me a while to understand why the code has worked with a single data acquisition card (NOR) but not another (Non-OR).

    The drivers that you have installed may or may not include examples and code in VI.  They may be DLL.  If this is the case, you can write LabVIEW "Wrappers" around these functions, as it will simplify your life.  If the drivers are in the form of DLLs, and there are no examples of LabvIEW or available VI, you must read on node library function call.

    R

  • Hardware DAQ do not appear in LabVIEW measurement IO after loading 2014 DS2, uninstall 2014 DS2 and then reinstalling 2013 DS1.

    Hardware DAQ do not appear in the measures of e/s. I installed LabVIEW worm 2014 DS2 Developer suite and my request is not worked. I then uninstalled ver 2014 DS2 Developer suite and re-installed worm 2014 DS1 Developer suite that installs such as LabVIEW 2013. Now none of the DAQ screws are present in measures of e/s. I uninstalled all the software of NOR and remove this software OR who do not uninstall. LabVIEW worm 2014 DS1 Developer suite installs normally, but I get an "unknown error" when trying to install drivers for data acquisition from the CD and the CD device drivers maintains a loop with a message indicating "currently exectuing License Manager."

    All return to work! I downloaded NIDAQ 9.8 on the site of NOR, and everything back to normal.

  • LabVIEW Application only works on a single DAQ card

    Hi all:

    I built an installer with DAQmx with card USB-6218. It worked very well on the target machine. But when I changed to another card USB-6218. It does not recognize the new card USB-6218. How to apply to recognize any DAQ card?

    Thank you

    DWT

    Hi, TPL,.

    Take a look at This example of the community - it allows you to find the devices via the appropriate product name, rather than his alias of device.  The example could do with a few changes, but I think it will help you

  • LabVIEW code for two daq cards

    Hi all

    I'm reading the analog signals using the USB-6210 device and function DAQmx. How to write my code so it would work with the NI USB-6210 or USB-6218 since both a pinout similar devices.

    Thank you

    dp128

    Do not write anything to recognize a different DAQ card. It's as simple as that. They both have the same number of input channels, and they both have the same maximum sampling frequency. You will only need to worry if your program was out analog.

    When you install a sinlge on a pc data acquisition card, MAX lists it as dev1. If you do the same thing with a different DAQ card on another pc, it is listed here as dev1. As I said, there is no difference to explain.

  • lsdaq pci daq card not found

    Help!   I have linux redhat 5 and installed the last base of nor-daq drivers 3.4.0f2.   I see my Board from national instruments pci-6070e running lspci:

    07:04.0 class ff00: National Instruments PCI-MIO-16-1

    But when I run lsdaq, I he found nothing:

    --------------------------------
    Detect of National Instruments DAQ devices
    Find the following materials:

    --------------------------------

    Any ideas?

    Andrew,

    Thanks for the notice about the DDK.

    Wanted to let you know by putting the DAQ cards in another workstation linux also runs HR, the lsdaq have found the cards.

    I maintain there is no way to know the difference between mx and mx-Base without download them both and read the help files.

    Also the word "subset of the functionality" is also misleading because you have to change all the function names.

    Jonathan

  • MAX with replication DAQ cards

    Hello

    Hope someone could shed some light on this

    Its a long time since I've used Labview & MAX and am a little rusty right now.

    I'm trying to upgrade an old data acquisition system to a newer version.

    This is because originally one full working backup system was necessary, but because the old DAQ cards are obsolete,

    a simple update was necessary.

    Old system:

    LabVIEW 7.1

    MAX 3.1.1

    Data acquisition card: PCI-6023E

    New system:

    LabVIEW 7.1

    MAX 5.0

    Data acquisition card: PCI-6220

    There is no change in the Labview application.

    In the new 5.0 MAX.

    I'm trying migrate/replicate all virtual channels & settings of the old system.

    I managed to set up a new configuration using file for the acquisition of data from the old system.

    This resulted in the creation of chains of virtual of NOR-DAQ traditional under the District of data, which is what I wanted.

    But the problem is, all the channels received a red cross.

    Clicking on properties of the individual chain shows that no device is selected in the hardware section. There is none to choose from.

    Under devices & Interfaces,.

    The new card is correctly installed and running.

    Appears as > NI PCI-6220 'Dev 1.

    How can I make this device available in virtue Traditional NOR-DAQ virtual channels in the data area?

    Is it because the new MAX/data acquisition card requires the method task NOR-DAQmx to create virtual ways?

    I want to migrate channels instead of recreating that there are a fair few and each with their own settings.

    In the old system.

    Under devices & Interfaces,.

    That's what it shows:

    -Devices of NOR-DAQ traditional
    PCI-6023E (1 device)

    -OR-DAQmx devices
    -PCI-6023E: "Dev 1.

    The device is recognized under the District of data - Trad VC through NOR-DAQmx devices.

    I can attach a screenshot for systems if it would help at all.

    Thanks in advance!

    -Ram of Aust

    Bad news...   Your most recent 6220 is a M-series it is * not * supported by NOR-traditional DAQ.  This is why it does not appear as an option under the traditional OR-DAQ driver.  To use the most recent data acq card, you * must * swtich above DAQmx.

    Your old 6023E Board should be accompanied by one or the other pilot (but never both at the same time), so it may be be jointly installed a print while you set on the (tedious) company to recreate channels for your new Board in DAQmx.

    -Kevin P

  • How display the waveform acquired DAQ card separately in wavefrom graphic

    I NI 9239 DAQ card and it has four channels. I need to create a user interface graphic labview in which I need to display all the forms of four wave separately. If I select all four channels of the daq assistant and connect the waveform table all four waves are coming to overlap... I need separately for the treatment... what should I do?

    Thank you and best regards...

    Try this

  • My acquisition of data NOR usb-6008, does not appear in labview after installing drivers

    My DAQ does not appear in my labview program after installing the drivers. I can't add it to my program or anything like that. I installed 3 different drivers and updates, and it's still not appearing in labview. Is there something I'm missing or need to do yet?

    Thank you

    It seems that you have a damaged file somewhere in your installation.  You will need to go into the control panel and select the option to repair the installation.  You will need to run the repair twice due to a known problem.  After that, you need to reinstall the NI_Daqmx 9.4.

    Jacob K

  • Acquisition of data using the DAQ card

    Hello everyone

    I need assistance with the acquisition of data of the generator of signals through DAQ cards. I plugged the signal to the SCB-68 generator where the analog inputs of the generator are connected to AI CH5 and AIGRND of the Terminal Board. Then the output of the block is connected to the DAQ card. The maximum sampling frequency of the card is of 250 kech. / s. The problem is for reason that I am not able to see the waveform on the labview. I looked at other examples to find the problem, I am, but I am not able to understand this. I want to be able to choose the sampling frequency. I attatched my code as an attatchment for you all to help me know what the problem is. Any suggestions will be appreciated.

    There is no task!  You have not specified any hardware (i.e. your data acquisition card) anywhere.

    Here's a suggestion.  MAX aperture.  Find your DAQ hardware.  Open a Test Panel.  Implement a continuous sample of N Points to some sampling rate.  Press Run and convince yourself that you get the data.

    Now, while remaining in MAX, to create a task, using the same settings.  Call for example something sensible ("MyFirstDAQTask" is not a good reputation).

    Now, go back to your code.  Eliminate the first two functions DAQmx.  Wire a constant task to the DAQmx Start feature.  See the little triangle down?  Click it, and it should show you the tasks he 'sees', the only one should be the task that you created in MAX.

    Note that 'Samples Visible' is now 'hard coded' in the task.  To get its value back out, you need to put a property node Timing DAQmx after the task start and pull on the quantity of the sample, samples per channel (which, for reasons that escape me, is a Dbl, you need to convert to an I32 before importing it into the while loop).

    Bob Schor

    P.S. Thank you to join your code.

  • Connect an SSI absolute encoder to a DAQ card

    Hello, everyone

    I try to connect four encoders of DAQ cards. Two of them are in quadrature encoders and the rest two absolute encoders. I'm guessing that connects the two quadrature encoders to both timers/counters on the card. But what of the SSI absolute encoders? Anyone can give a clue? Thank you very much.

    Either way, I am using PCI-6251 and xPC Target.

    Pengfei

    Hi Pengfei,

    If you do not use our driver so I don't know if this is supported, but here's how I would do it using DAQmx...

    According to the features of calendar defined page 10 specifications page, 500 ns is the minimum period for almost all relevant parameters:

    Period of the CLK line semi

    Time between the CSn and the first edge of the clock

    The CSn pulse width

    Well, it makes sense of the clock of your 2 MHz.  You need produce waveforms of the following two, each cycle would be clock to 18 bits of data (12-bit encoder and 6 status bits).  The total duration of the cycle ends up being long 38 samples and would take 19 microseconds to execute (if updated to 2 MHz).

    CSn 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

    CLK 1 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1

    The actual binary data to write to the card depends on what lines you use.  For example, if you use p0.0 to CSn and p0.1 for CLK, table you would need to write would be the following:

    3 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2 0 2

    The bits of the U8 number correspond to the 8 rows on the port.

    You will need an example of clock for your task source.  I suggest to use Freq Out on the 6251.  In DAQmx, it is programmed in the same way as a meter output.  You would set this up as a continuous meter to 2 MHz output.  Indicate on your task to use ' / Dev1/FrequencyOutput "as the sample clock source (not necessarily Dev1, but regardless of the name of your device).

    You would physically signal port thread 0 CLK in PFI lines and use it to sample a DI task so that you can read back your data.  You can enjoy on the falling edge of the CLK to allow 500 ns for the value to be set (the maximum duration of your sheet is 394 ns).  The only drawback to this is that you are not sampling the parity bit, but apparently not that it is a problem unless you plan to use it.

    Once you get the bits, you must translate that into an actual position.  When you call DAQmx Read, you will have an array of values.  The first value of each cycle is a disposable (look at the waveform to see why).  The next 12 items of any cycle would be the 12 data bits, next 5 bits of State.  As I mentioned earlier, the parity bit would not be sampled because of the decision of the sample on the falling clock edge (again, you can refer to the waveform to see why this is the case).

    You'll want to convert the 12 data bits of the table in a single 12-bit integer, then multiply by (360.0 / 4096) to get the position in degrees.  I don't know what development environment you use, but this type of data manipulation must be achievable.  For example, LabVIEW has a Boolean array of numbers feature that would be very helpful here.

    I hope that helps!

    Best regards

Maybe you are looking for

  • Connected, but can not visit Web sites

    Hello everyone I have a problem that started last night and I don't know what to do, and I'd be happy if someone here could help me on what to do, because I'm not very good at that sort of thing So basically, the problem is that I have internet and i

  • Two questions about Equium A80

    I recently bought this new model which I must say has a host of extras as standard and I am happy to a certain extent. However, I had to upgrade my HDD immediately because I need more space and thus installed win xp pro (not the original with win xp

  • No regenerative analog output in c#

    Hello Does anyone have experience implementing a similar continuous regenerative, exit in c#. Specifically, I'm looking for to control the output of several channels, simultaneously over many hours that will not repetitive voltage signals. This will

  • With an average of meter data

    I have a double precision scalar value to a DAC that represents the current measured in a domestic wind turbine application. This value is harvested in a home made circuit that has a little 'noise problem '.  This noise cause fluctuations in the valu

  • Wireless Microsoft notebook optical mouse does not work with g42 - 410 us laptop

    Wireless Microsoft notebook optical mouse does not work with g42 - 410 us laptop