PXI 6229 + LabVIEW

Hi all,
I am doing some tests with LabVIEW and I want to send analogic voltage signal to a PXI 6229 (the chassis is a PXIe-1071). I would like to know if I need to add, in the testing programs I have, any control to make the connection between Labview and the controler. For instance, to describe to which connector in the PXI 6229 the cable is connected to (it only has Connector 0 and 1)
Thanks in advance,
Francisco

Hi again.
Thanks everyone for the solutions given. Everything was correctly made, but I was connecting the wrong cable.
I just would like to know another thing: I need to generate a signal using formula block (2 different ones: one with respect to the X axis and the other one with respect to the Y axis). My question is: should I create 2 DAQ Assistants, each one with a different output connected to a different axis, or is there any assembly block that allows me to assemble both formulas block and the connect it (the assemble block) to the "data" part of the DAQ assistant?
Best wishes,
Francisco

Similar Messages

PXI-6229 counter output

Hi,
I was using the DAQMx test panel for PXI-6229 module with my PXI-6229 card. I couldn't find an option of routing the counter pulse generation output to different PFIs. It is locked at PFI12 for ctr0 and PFI13 to ctr1. Is there some way by which I can route to other PFIs in the test panel or do I have to write code for it.
I want to route ctr0 output to PFI10 and route PFI12 as a counter input to measure frequency.
Please let me know
Thanks
Shiladitya

Shiladitya,
The Test panels are designed for functional testing only, and do not necessarily expose all capabilities of the device. In order to route these signals to custom PFI lines, you would need to write code. In LabVIEW, this would be done using a DAQmx Channel Property Node. Simply wire the intended terminal to the CO.Pulse.Term property.
Hope this helps,
Ryan Verret
Product Marketing Engineer
Signal Generators
National Instruments

Analog Trigger with PXI-6229

I have an application using a PXI-1010 chassis, PXI-6229 DAQ, communicating with MXI-4 to the host computer.
For task triggering, the only direct option I'm finding is the digital trigger. However, I need to trigger on a low-lever analog signal (180mv). Can this be accomplished indirectly and start the task with a minor delay? If I can trigger the signal on the positive slope, I could have potentially a 1ms delay to begin the task and not affect my data.

Hello Russ,
The M Series 6229 should be able to support hardware analog triggering. Take a look at the following example to see how to accomplish this in LabVIEW.
http://venus.ni.com/stage/we/niepd_web_display.DISPLAY_EPD4?p_answer=&p_guid=DC9C549F7FDC1973E034080020E74861&p_node=DZ52000&p_rank=&p_source=External&p_submitted=N
If this doesn't work out for you and you don't mind having a delay between the low-level analog signal and the start of the task, you could always use a software analog trigger. Examples of this can be found in the LabVIEW NI Example Finder.
Take care,
E.Lee
Eric
DE For Life!

PXI-6229 single pulse

Hi,
I am using the PXI-6229. I would like to output a single digital pulse for a specific amount of time. How would I do this?
Thanks

Hi,
There is an example program called Gen Dig Pulse.vi. You can find it in the NI Example finder. Open LabVIEW and go to Help. Select Find Examples. In the Browse tab select Hardware Input and Output>>DAQmx>>Generating Digital Pulses>>Gen Dig Pulse.vi.
I hope this helps.
Regards,
Ima
Applications Engineer
National Instruments
LabVIEW Introduction Course - Six Hours
Getting Started with NI-DAQmx

How to route the ctr0 in DAQ MX for PXI 6229?

Hello,
The counter ctr0 of the PXI 6229 is internally wired to PFI12.
How could i change the terminal on which this counter is wired? What is the function in LabWindows CVI 7.1 (NI_DAQ MX 7.3) should be used? Is there any example of this? (in all the CVI example the fact that we have to connect the counter to a terminal is just mentioned)
Thanks for your help!
guyom

You can change the output terminal on M Series devices using the following function:
int32 __CFUNC DAQmxSetCOPulseTerm(TaskHandle taskHandle, const char channel[], const char *data);
On M Series devices you can route the output of a counter to any PFI line.
I hope this helps!
gus....

NI PXI 6229 DAQ Card Digital Output High/Low Levels

Hi everyone, I can't seem to find in the NI PXI 6229 DAQ spec what the Digital Output high voltage and low voltage is when I set a digital signal high and low. What is the voltage when I set a Digital Output "HIGH" and what is the voltage when I set a Digital Output "LOW"?
Thanks!

See the digital I/O characteristics section of the specs. Typical ttl levels.

Pxi-6229

Hi,
I am using the PXI-6229 DAQ card Part Number 779115-01, for my project. Is it possible to
configure the IO lines as Open Drain/Collector or Push pull? If so, how and which are the
ports we can configure.
Thanks
Shiladitya

Hi Shiladitiya-
All M Series cards operate as 5V push-pull digital outputs and are not configurable for open drain/collector.
Hopefully this helps-
Message Edited by Tom W [DE] on 06-23-2006 09:49 AM
Tom W
National Instruments

PXI 6229 pulse period measurement

Hi there,
I try to make pulse period measurement using PXI 6229 counter, I have 0.5Vcc according to DMM and 1.05V peak2peak based on scope. Then, I connected 0.5Vcc (incoming pulses) into SCB68 pin 3 and GND pin 55. I used the DAQ assistant to perform measurement n the setting for Signal Input range is min= 1ms and max = 23ms, those values I got it from scope i.e pulse period. I set it to the Rising and Acquisition Mode to 1 sample(on demand). But, I can’t get the measured values and I have no ideal why?
Please help
Walter.

Hi Walter,
the counter input of the PXI-6229 accepts standard TTL digital signals. You can find its specifications on page 7 of this document.
I will repeat the relevant parts here:
Input high voltage: Min: 2.2 V; Max: 5.25 V
Input low voltage: Min: 0 V; Max: 0.8 V
If I'm correct, your signal does not meet these specifications, so in this case you will have to connect the signal to an analog input and measure the pulse width as if it was an analog signal.
Please check this page for an example.
Daniel

60 HZ Hum on Analog Input PXI-6229

Ther is a 600mV common mode noise hum being introduced somewhere on the circuit below. It is causing the PXI-6229 to read inaacurate measurements. Is there a way to configure the device to reject common mode noise? Or any other suggestions?

Is the metal box connected to both the power system (safety) ground and the signal ground? This could be the source of the ground loop. Are the computer, PXI chasis, and the metal box power all connected to the same branch circuit and ground?
Try drawing a diagram showing every ground connection in the system. Do not just use a ground symbol but actaully make it a wiring diagram which shows where every wire, chassis, box, conduit, or anything else grounded is connected. This can sometimes be useful in discovering ground loops. I found one which included a wire attached to the mounting bolt for a toroidal transformer. It resulted in several amperes flowing through the housing of a very sensitive magnetic instrument!
As has been mentioned CMRR only applies to differential inputs. The circuit you posted is single ended so I think it is unlikely that a differential connection would help.
Lynn

T6963C control using PXI 6229

Could anyone can help me how to control T6963C LCD Display?As below,
I have setup up all the connection to the T6963C via PXI 6229 i.e. WR, RD,CE, C/D, RESET and FS1. For data line is D0..D7. I am sending High to WR,RD,CE,C/D,RESET and FS1 and D7..D0 is 100111 i.e Text on, Graphic ON accroding to the DATASHEET but I dont see any things happen on the LCD display.
Please help! Walter.

duplicate post

PXI-6052E Labview VIs

I have a PXI crate with LabVIEW 2009 and a PXI-6052E board in the crate. I cannot hook the computer to the internet and was wondering what is the fastest way to get basic VI examples for the PXI-6052E. I just want a couple of the analog inputs to be read in.
Thanks,
Kevin

Hi Kevin,
the PXI-6052E is supported by the NI-DAQmx driver. So if you can find the board in MAX, the driver is installed correctly and you should be able to run the examples, that are installed in the \LabVIEW\examples directory (use the example finder in MAX).
If NI-DAQmx is not installed yet, you need to do this (e.g. by using an USB DVD drive).
Regards,
Jochen

Filter pxi-6602 LabVIEW DAQ-mx

Hi,
I have a PXI-6602 card.
The signal to measure is on the gate pin.
On the source pin, it is the internal 20MHz.
The counter uses the ND_BUFFERED_EVENT_CNT mode.
I have a LabWindows code with NI driver DAQ for this card which uses filter with this function <<< Line_Change_Attribute( device number, line name, ND_LINE_FILTER, ND_5_MICROSECONDS) >>>
I must rewrite the code to LabVIEW with NI driver DAQ-mx.
I use the counter to count edge mode.
I don't know how to configure the same filter in LabVIEW with DAQ-mx.
Can you help me ?
thanks
best regards

Assuming you're using the external signal as a "sample clock" in your edge count task, you would enable the filter like this (called before starting the task):
There are other ways to configure what is essentially the same thing though--if you're using the external signal as something other than a sample clock (e.g. a "pause trigger") then there would be a different property that you would need to set instead.
Best Regards,
John Passiak

PXI Controller / LabVIEW Compatibility

I have a system using a PXI-8175 RT controller with LabVIEW 7.1. I am looking to upgrade the LabVIEW version to LabVIEW 2011. Is there a table of PXI-Controller compatibility with LabVIEW?

Hi Jeffmg,
We do have tables of compatibility for PXI controllers with different versions of the PXI Platform Services and operating systems. Please take a look at the documentation located on the following web links and let me know if you have any questions!
PXI Platform Services Operating System Support
PXI Platform Services Hardware Support
| Zach J. | Applications Engineer | National Instruments |

Hi am trying to save Data into a write to measurement file vi using a NI PXI 1042Q with a real time mode but it is not working but when i run it with uploading it into the PXI it save in to the file

Hi am trying to save Data into a write to measurement file vi using a NI PXI 1042Q and DAQ NI PXI-6229 with a real time mode but it is not working but when i run it without uploading it into the PXI it save in to the file please find attached my vi
Attachments:
PWMs.vi ‏130 KB

other problem is that the channel DAQmx only works at real time mode not on stand alone vi using Labview 8.2 and Real time 8.2

Counter Output/Counter Input PXI Signals Behaving Erratically

Question for all your LabVIEW guru's out there,
I am running a frequency loopback test using the NI PXI 6229 MIO DAQ card. I am generating a "Counter Output" pulse train signal which feeds through my device under test and then back out of my device under test and back into the PXI 6229 for a "Counter Input" frequency measurement. Both the "Counter Output" and the "Counter Input" are assigned different PFI lines using DAQmx in LabVIEW.
I have 4 lines to test on my DUT. All four lines run this same frequency measurement but with different PFI lines on the PXI 6229. Each line is test independently.
This is my setup for the 4 lines:
Path 1: P2.0 (Counter Output - Pulse Train) -> DUT (Device Under Test) -> P2.1 (Counter Input - Frequency Measurement)
Path 2: P2.2 (Counter Output - Pulse Train) -> DUT (Device Under Test) -> P2.3 (Counter Input - Frequency Measurement)
Path 3: P2.4 (Counter Output - Pulse Train) -> DUT (Device Under Test) -> P2.5 (Counter Input - Frequency Measurement)
Path 4: P2.6 (Counter Output - Pulse Train) -> DUT (Device Under Test) -> P2.7 (Counter Input - Frequency Measurement)
where:
P2.0 = PFI8
P2.1 = PFI9
P2.2 = PFI10
P2.3 = PFI11
P2.4 = PFI12
P2.5 = PFI13
P2.6 = PFI14
P2.7 = PFI15
I have a LabVIEW VI which generates the "Counter Output" and reads the "Counter Input" frequency. I am seeing weird behavior from the PXI 6229 card. I can test "Path 1" and "Path 2" and the frequency I read is what I generated. No issue there. However, when I test "Path 3" and "Path 4" the frequency measurement is erratic. The readings are two different frequencies repeated over and over again and none of those frequencies are the expected frequency which was generated out of the "Counter Output." If I reset the card, and start by testing "Path 3" and "Path 4" the frequency readings are correct and the erratic behavior is gone. However, when I try to then test "Path 2" and "Path 1" now those lines have the erratic frequency issue. I can continue resetting the card and see same issue. The PFI lines that I test first will always pass.
To summarize:
Steps Taken:
1. Test Path 1 = SUCCESS
2. Test Path 2 = SUCCESS
3. Test Path 3 = Erratic Frequency (Two Frequencies repeated over and over again in my frequency results array)
4. Test Path 4 = Erratic Frequency (Two Frequencies repeated over and over again in my frequency results array)
5. Reset the PXI 6229 Card
6. Test Path 3 = SUCCESS
7. Test Path 4 = SUCCESS
8. Test Path 3 = Erratic Frequency (Two Frequencies repeated over and over again in my frequency results array)
9. Test Path 4 = Erratic Frequency (Two Frequencies repeated over and over again in my frequency results array)
I am wondering if Port 2 (P2.0-P2.7) on the 6229 card has certain dependecies and this is why I am seeing issues. I am trying to get around this issue so that I don't have to always reset the card.
Are P2.0-P2.3 (PFI8-PFI11) and P2.4-P2.7 (PFI12-PFI15) treated differently or require different setup? How do I resolve this issue?
Thanks so much!

I have a theory...
The DAQ card follows a policy called "lazy uncommit" wherein the terminal used for the output will continue to be connected to the counter even after the task has completed (until the terminal is needed for something else). So as you run more tests, the counter output will end up driving more lines. This behavior should be easy enough to confirm.
As the DAQ card drives more lines, I'd imagine this affects the actual signal. You could scope it to check, but it sounds like either the rise/fall times are becoming longer or some extra noise is being introduced on the line.
The readings are two different frequencies repeated over and over again and none of those frequencies are the expected frequency which was generated out of the "Counter Output."
This implies you are picking up an extra edge during transitions--this isn't too uncommon if the signal is noisy since there is no built-in hysteresis on the DAQ card. I would expect the measured frequencies to have periods that sum to either the full period or the semi-period of your actual signal (depending on how many duplicate edges are detected).
Suggestions are as follows:
To stop the DAQ card from driving multiple PFI lines, it would probably be easiest to just programmatically reset the device in between your tests (using DAQmx Reset Device). If you can't reset the device (e.g. because you are running some other task that can't be interrupted) then you can instead configure a dummy task that uses the PFI line in question as an input.
To stop the DAQ card from picking up multiple edges during transitions, you should configure a digital filter on the input terminals. If you reset the device it sounds like this might not be necessary... it's up to you if you want to configure this or not.
Best Regards,
John Passiak

PXI 6229 + LabVIEW

Similar Messages

Maybe you are looking for