Daqmx pxi

I'm new to LabView and am having an issue related to using a PXIe-1062Q with a PXIe-8360 and a PXI-6251 M-Series DAQ card. I had previously written a vi using DAQmx function calls for use with a USB-6216 card. I can "see" the PXI hardware in MAX and have been able to collect data from it using SignalExpress. The vi that I wrote for the 6216 card has much more functionality and I would like to use this vi with the PXI chassis. However, when I run the vi there are no devices to pick from like there was when using the USB-6216. Is there anything additional that needs to be added to the code in order to use the PXI setup in place of the USB-6216? I have loaded the PXI Platform Services software. Thanks, Jim_H

Hello Jim_H,
In MAX are you able to expand the PXI-1062Q icon and see the modules? Can you run a self test on the M-Series PXI card? You mentioned a USB-6216, is this when you were using with your software before? You might be using the Create Task VI instead of the Create Channel VI when initializing your code. The Create Task VI only has inputs for an already created task or a Global Virtual channel. Let’s try using the Create Channel VI from the Measurement I/O palette. Once you place this find the terminal named Physical Channels and creat a constant for it. If things are properly configured and pass self test in MAX then you should see the devices then.
Regards,
-Travis E.
National Instruments
Applications Engineer

Similar Messages

Consumer/producer fast AI and AO.

I made a routine for fast DAQmx (PXIe-6124) acquisition in two while loop (consumer and producer).
Currently it can be run by pushing run-button.
But, I would like to one more while loop (totally 3) for user-friendly interface and integrating sub-program using event structure.
Among troubles I thought, these three loops can affect the acquisition speed of DAQmx.
For example, if I send a "Acquire" signal to producer and consumer of DAQmx from event loop,
this mean I also have to send "Stop" command.
This requires more functions in every real-time acquisition iteration.
-conditional state loop and cluster bundle of 2D(500*500 DBL array) and variant of command enum or data to control consumer loop in producer of DAQmx.
-conditional state loop for next step and cluster unbundle of data in consumer loop.
My question is...
Are there some special or rule-of-thumb techniques for continuous, fast and large data DAQmx acquisition in producer and consumer using three while loops?
Instead of this, do I had better use call-by-reference under other main program?
labmaster.
*)I am sorry I can't post my code because of modifying and hidden subVIs.

You will need some logic in your producer loop to execute the stop command sent by the first while loop but won't need one for the consumer loop since it can stop on error when the producer loop is stopped and the queue you are reading from is destroyed.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

NIMax.exe - Entry Point Not Found - attempt to create task in MAX

I have two different cards that use NI-DAQmx: PXI-4461 and PXI-6259. They are installed in a PXI-1031 chassis with a PXI-8105 controller. Both devices pass their self-test in MAX. When I try to create a new task for either, I get first the expected selection dialog:
After I select "Analog Voltage" (or any other item), I get the following error:
Last week, I upgraded my HSDIO driver for a PXI-6562, which led me to upgrade NI-DAQmx to 9.2.3, and subsequently repair both installations in Windows to get them working (see this forum thread).
Task creation used to work. The system still recognizes the one task that I created weeks ago for the PXI-4461.
Here is a screenshot of my current software versions:
Does anyone know how to fix this?
Solved!
Go to Solution.

I solved this problem by downloading and installing NI-DAQmx 9.3.0. This, in turn, caused the problem from the post that I linked above, which I fixed by choosing "repair" in the Windows control panel for 1. the HSDIO driver, and then 2. the NI-DAQmx driver. The order matters. Now it seems to be working.

Generating a flicker signal VI?

Hello all,
I'm currently creating a program which creates several tests concerning Power Quality with a Daqmx PXI-4461.
First of all i would like to say that i have no problem generating or reading signals with the Daqmx.
I'm currently at the point where I want to generate a flickering squarewave signal (flickering = small voltage dips over time) with the Daqmx, and was wondering if there was an example somewhere on the web that lets me insert the flickerfrequency and % decrease compared to the RMS value
Like a good professor of mine always said, its better to edit an excisting example then to start from scratch!
Regards,
Dennis

Hello Dennis
I didn't directly find directly usable code, but I did find something else:
https://decibel.ni.com/content/docs/DOC-12324
http://sine.ni.com/cs/app/doc/p/id/cs-13888
I think that especially the first document could help you a bit further.
Another thing you could try is contacting the author of the case study to request if he can send you his code.
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

Pulse Generation application with DAQmx and a PXI-6624 module?

What is the best implementation method for the following pulse generation application
using LabVIEW, DAQmx and a PXI-6624 counter\timer module?
I have two rising edge trigger signals (Trigger-1 and Trigger-2).
There is ample spacing between each trigger. They never occur at the same time.
I need to generate a single pulse (fixed width, variable delay) whenever Trigger-1 occurs and
a finite pulse train (fixed width, variable delay, N-pulses) whenever Trigger-2 occurs.
However, the output must appear on one counter output because this composite signal
will be used as a trigger source for another PXI module in the rack.
With DAQmx and a TIO counter\timer can I use both the GATE (for Trigger-1) and
AUX (for Trigger-2) at the same time on the same counter to gate out the desired pulses?
Trigger-1 would be wired to the GATE of CTR0. One Trigger-1 event would generate one pulse on the output of CTR0.
Trigger-2 would be wired to the GATE of CTR1 and the output of CTR1 would be routed to the AUX input of CTR0.
One Trigger-2 event at the GATE of CTR1 would generate multiple pulses on output of CTR0.
Would DAQmx and the PXI-6624 TIO support this implementation?
What is the best way to accomplish the task at hand.
Thank You.
Best Regards,
Scooby

Hi Scooby,
I have looked into the application you have described and I see a potential problem with what you describe. In DAQmx, it is not possible to call the counters of the same DAQ device in the same task, so you cannot have the finite pulse train generation and the single pulse generation tasks running at the same time. What you can do, since you mention the triggers will not occur at the same time, is to stop one counter task while you are triggering another. The way I would suggest you merge the outputs is with a two input Or logic gate to avoid damaging your counters. Your signals will effectively be added together by this logic gate. I do not see any way to merge the outputs internal to the DAQ device.
Please let me know if I can be of additional assistance.
Laura

PXI 4070 use DAQmx Drivers

I have replaced a PXI 4060 card with a PXI 4070 card in a PXI 1042 chassis that I use for resistance measurements. I want to use DAQmx drivers instead of the traditional daq drivers. How can I do this?
My controlling software is VB6. I have had issues with traditional daq on Windows XP machines with new NI installations. Errors indicate there is an issue with the traditional daq drivers. The sample applications installed with the niDMM 2.7 installation error with message "Error Loading Driver Module". I have used the palbase utility in the past to work around this issue, however, the palbase utility is not failing to change the base address. There is an error message associated with the failure, but I figure I may save myself the headache by switching to DAQmx drivers.

I would recommend upgrading to the niDMM 3.0.4 drivers found here. This version is still compatible with Visual Basic 6.0 and Windows XP. niDMM 2.7 would have installed NI-DAQ 8.5. The name indicates that it is traditional DAQ, but as far as I can tell, version 8.5 was only DAQmx. 3.0.4 will also install a newer version of DAQmx that is compatible with XP, as well as the examples. It seems that the version you have should have worked, but there may be some corruption, or there may have been a version of traditional DAQ 8.5 at some time (we had some versions of NI-DAQ that included both traditional DAQ and DAQmx). I hope this helps!
Thanks,
Sean
Applications Engineering Specialist - Semiconductor Test
National Instruments

How to sync CAN (traditional) and DAQmx input on PXI?

At the moment I am reading analogue samples and counter values on my PXI system. The counter value is incremented by an external pulse (i. e. current time). Because the pulse is the actual time, the AI sampling has to start in sync with the first incoming flank. This sync'ing is done via the DAQmx trigger VI which is set to "start at flank" (see picture). Because I am recording the counter values, too, I can always determine the time for each AI sample.
Is it possible to start AI and CAN signal sampling in sync with the first incoming pulse flank? As before, I want to store the counter values as well, so that I have time information for each sample. Is this sync'ing solvable with VIs or do I have to use a different CAN card with an external trigger input?
The CAN card is of type 8464 XS.

Hello,
please see the links below.
http://digital.ni.com/public.nsf/allkb/95EB3CB8E92D30FB86256F2C00672C44?OpenDocument
http://zone.ni.com/devzone/cda/tut/p/id/4204
Regards
Rüdiger

PXI-6255 not identified in MAX as DAQmx

We recently purchased a PXI-8108 controller for use as a spare and I'm having difficulty getting it to play well with our existing hardware and software. The controller we have been using is an older PXI-8106.
The new controller has Windows 7 where the old had XP, so I had to use more recent versions of PXI Platform Services and MAX, as well as DAQmx. The versions I've installed are: PXI Platform Services 3.0.4, MAX 5.3.1, DAQmx 9.2.2. I can't use more recent version of DAQmx because our we are using LabVIEW 8.5.1 and anything more recent doesn't support that.
The 6255 is showing up in the device manager under Windows, and the properties show that it is using the same hardware driver (nixsrkw.sys, rev. 1.13.0f4) as we use on the old controller. The 6255 also shows up in MAX, with a device identifier of PXI13::15:INSTR, but not listed as a DAQmx device. So, when I import the MAX settings file, the defined tasks won't run.
I haven't found any postings in the forum that quite match this scenario. Anyone have any ideas?
Thanks,
Mike

Mike,
Firstly, I want to let you know that you will have problems using LabVIEW 8.5 with Windows 7. The oldest version of LabVIEW supported in Win 7 is LabVIEW 2009 SP1:
http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB
About seeing your device in MAX, can you post a screenshot of what it looks like?
Jon F.
Applications Engineer
National Instruments

PXI - DAQmx tasks will not export to MAX 5.4

I am in the process of upgrading a PXI 1050 with an 8176 to an MXI bridge. The latest headache is that the CVI program had several DAQmx (tasks) defined in MAX 3.1.1 which will not export to MAX 5.4. I have been posting these additional questions on my original thread MXI not visible in MAX. I have many tasks for installed PXI cards. I was trying to make simple tasks just defining these cards to change the errors I receive in CVI. I do not have the option to define a task for some of these cards like the 4070 DMM. I did not generate the original CVI code. I am not sure what is defined the DAQmx. Can someone provide some insight ? I have viewed the suggested videos and white paper links. They were instructive but of little help.

Unfortunately; no updates without dollars. While we all work for the same company, we must contract work between departments. There was no defect with the software as delivered. Old age crept in to the hardware. Any upgraded hardware, it turns out, requires updating of the software. The unit had operated reasonably well, until a couple years ago. An unfortunate selection of network security software caused massive headaches. The software chosen assumed a more advanced level of hardware. Mandatory installation on all network computers rendered these controller inoperable. Our local IT guys shaved down the install to minimal components but the controller lost all available ram to this software, NI-MAX requires 20 minutes to build it's database on reboot. The computer controllers struggle to function. They periodically get lost and require a reboot, causing 30 minutes or more to restart. This is driving a replacement. We decided that it would be more cost effective to move to a standard computer interface. With the MXI, we could have a much more friendly and versatile interface. The upgrade is with a different "color" of corporate money. There isn't enough funding to contract a software upgrade. It is feasible to complete the upgrade in house, once we can identify the players and their function. Second we need the necessary time and access to the equipment. I do not have the ability to expend too many extra hours at work. So it takes time. I have been able to piece together the following. In the development stage back in 2004 - 2005, the developers used both Traditional DAQ and DAQmx. They build tasks for the SCXI in CVI. They have toolboxes making calls to Traditional DAQ. Also at some point in time they must have used the option in 3.1.1 to Convert Traditional NI-DAQ(Legacy)Configuration to NI-DAQmx, which built all the extra DAQmx devices we see in the device tree in the MAX 3.1.1. So beyound the errors there appears to be a few red herrings, just for fun. So there is no tasks to convert from 3.1.1, everything is contained in the CVI code. I have to find a way to use the CVI debugger to lead me to the nested, buried code causing the errors, and simply correct them. Just for another layer of complexity, they are probably logic errors, not syntax errors, or updated code errors where the legacy code no longer functions with the updated drivers. Or, hey, it could be the beta version of NI-DAQ, because it is the only one working with Windows 7 (32).

PXI-6534 Card using Traditional Legacy Card to DAQmx driver

I don't know where to start..I am stuck on an issue that needs to be solved.
I am using a Traditional legacy driver on a PXI-6534 Card.
I want to move it to using the DAQmx driver.
Can someone point me to the right direction?
Thank you..
Best regards,
Krispiekream

i read over the link you provided and i can see that changing it will take a while.
some of the examples given didn't cover all the questions i have.
can you see my vi and see how would i change that to daqmx?
Message Edited by krispiekream on 02-24-2009 03:34 PM
Best regards,
Krispiekream
Attachments:
Traditional to DAQmx.vi ‏31 KB
untitled.PNG ‏8 KB

Does NI PXI-6259 support both Traditional DAQ and NI-DAQmx of Labview 7.0 Express?

I need to buy a Multifunction DAQ board which will be supported by both the Traditional and NI-DAQmx of Labview 7.0. Is the NI PXI-6259 appropriate for such application?
Thank you.
Ujwal

M-series boards are not supported by Traditional NI-DAQ. Stick with the E-series if you require Traditional support.
John Weeks
WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com

URGENT: PXI-1033 and DAQmx problem

I bought new laptop with Express Card slot Dell Inspiron 6400. I have PXI-1033 with integrated MXI bridge, Express Card 8360 and PXI-modules: PXI-6251, 6115, 5114 and 4071. I installed drivers 8.3 and plugged in PXI modules into PXI-1033. I first power up PXI-1033 and than power up laptop (with Express Card in it). Laptop can not start, again can not, blue window, and at last start. In MAX is listed PXI chassis with bridge and all modules, but mx is not listed and I can not use it from LabVIEW. What is the problem?

Hi,
To clarify, do the PXI modules show up under DAQmx devices? What color is the Link LED on the 1033? Do the cards all show up in Windows Device Manager correctly? Also, are you able to power on the laptop successfully now every time, or does is have trouble booting each time you try and start it up?
Have you inspected the MXI cable for bent pins or any visible damage?
Thanks!
Adam W
Applications Engineering
National Instruments

PXI-4351 and DAQmx?

Hello,
We are considering to buy a PXI-Chassis with an PXI-6229 for general measurement and two PXI-4351 for temperatur measurements.
I already wrote a big library of VIs to use PCI and PXI-card undere DAQmx (almost 6 months of development).
But I read in the specification of the PXI-4351 that this card is only supported by the traditional DAQ driver.
Is it true, are may be the DAQmx 8.1 support the PXI-4351. If not, does anybody know if the card will be soon part of the DAQmx?
Thanks,
Risotto

Risotto,
the PXI-4351 works quite differently than a multifunction DAQ device and it comes with it's own instrument driver which is based on traditional NI-DAQ. The instrument driver was just updated to support LV 8. There are currently no plans to support NI-435x devices with NI-DAQmx
Best regards,
Jochen Klier
National Instruments Germany

PXI 4472 DAQmx Start VI taking a long time.

I have an issue with DAQmx Start taking up to a secoond to to execute and it's killing my cycle time.
I have a PXI 8360 with 3 PXI 4462's and 3 PXI 4472's. I configure DAQ Task and Commit at the begining of the sequence however every time i do a DAQmx Start it takes about a second to execute. I need to do about 5 in each Test sequence so it's eating up about 5 seconds of cycle time. I am using DAQmx 9.7.5 drivers and Labview 2013. We have the exact same hardware and software setup in another location but we are not seeing this issue there.
Any ideas what might be causing this would be appreciated.
Attachments:
DAMmx Start.png ‏4 KB

Hi Nathan,
I verified this by disabling the Start Task VI.
I've attached the commit code.
Thanks
Attachments:
PXI 4472 Acquire.png ‏8 KB
PXI 4472 and 4462 Commit.png ‏13 KB

DAQmx and pxi-5122

Does anyone know if I can use DAQmx to measure a 5volt DC current from a pxi-5122 card?

Good afternoon ndaugherty and devchander,
Thanks for contacting National Instruments with your issue, we'll try and resolve it for you as quickly and efficiently as possible.
devchander is correct, it is possible to program National Instruments Scopes (in this case the 5122) using DAQmx, however it is not recommended and not supported. DAQmx is a multi-purpose driver designed, whereas the NI-SCOPE API is designed specifically for out Modular Instrument Scope cards. For this reason, a lot of the functionality, timing considerations and register access, will be exceedingly difficult to control via DAQmx compared to NI-SCOPE.
The NI-SCOPE driver is a free download available to all of our customers and can be located here.
Best of luck with your project.
Sincerely,
Minh Tran
Applications Engineering
National Instruments

Daqmx pxi

Similar Messages

Maybe you are looking for