Finding PXI 6071 cards in PXI system

I am trying to dynamically find how many 6071 cards that I may have in
a PXI chassis. Once I find it, I need to know what slot it is
in. After that, setting up the physical channels is simple.
The information is available in MAX, so there has to be a way to get it
out. I want to do this without having to configure MAX! If
I have to do that, I have big problems ahead!
Attached is how I am finding the Name of the Device....I just need to
get the slot number! NOTE: The name may or may not contain
the slot number depending on the configuration of your PXI chassis and
how many different cards that you have populated a single slot with.
Thanks,
Paul
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?
Attachments:
DAQ-identify6071Cards.vi ‏37 KB

For those that may not have LV7.11, attached is a jpg of the diagram
Paul <--Always Learning!!!
sense and simplicity.
Browse my sample VIs?
Attachments:
findPXI-6071-diagram.jpg ‏37 KB

Similar Messages

How to download eds file to PXI-8461D card from MAX?

Hello,
I have a PXI-8461D DeviceNet Card. I have installed the card in PXI system and able to see it in MAX under remote system chasis. But I am not able to see the Configurator when I right click the card. Also not finding it in RT configuration window. NI-DNET version is 1.6.1 How can I launch configurator for DNET cards and download eds files?
Thanks in advance.
A Senthilnathan
Solved!
Go to Solution.

Looks like there is already a good converstation going in this thread. Duplicate Post
-Marshall R
National Instruments
Applications Engineer
One stop for all your NI-VISA Support
GPIB Support has a new homepage

MAX does not detect my PXI-5122 and PXI-6551 cards in a PXI-1045 chassis.

I have been using a PC with MXI-3 to PXI-1045 chassis to develop LabView TestStand code. Things are fine on my development PC. [Software configuration report attached nireport_rich.txt].
I have a 2nd PC set aside to test my deployment packages. I installed a GPIB card and MXI-3 card in my deployment test PC, and loaded a bunch of hardware drivers. [Report attached nireport_depPC_0006.txt]
All the PXI cards are found just fine when my development PC is connected, but when I power up my deployment PC (with MXI-3 connected to the 1045 chassis) -- I can't import the development configuration [exported from development PC] because the deployment PC does not see the PXI-6551 DIO card in slot 6 [PXI6::10::INSTR] and the PXI-5122 card in slot 13 [PXI8::15::INSTR].
I keep reviewing the hardware driver versions installed, and the only small difference that I see at this point is that the deployment PC has a slightly older version of NI-Switch.
Anybody have any ideas of what I can try next? I'm out of ideas.
. . . . hmmm, can't seem to attach more than one file, so here's the software info on the deployment PC
NI Software Information:
CVI Run-Time 7.0.0.395
NI-DAQ 7.3.0f1
NI-DAQmx 7.3.1f0
NI Script Editor 1.1
NI-DMM 2.3.1
     Soft Front Panel 2.3.0
NI-FGEN 2.2.1
     FGEN Soft Front Panel 2.2
NI-488.2 Software 2.30
IVI Compliance Package 2.2 2.2
LabVIEW Run-Time 7.0
Measurement & Automation Explorer 3.1.1.3003
Measurement Studio 6.0
     For Visual Basic
          ActiveX User Interface 7.0.0.344
          ActiveX 3D Graph 7.0.0.344
          ActiveX DataSocket 4.2.2.1
NI-USI 1.0.2
NI-HSDIO 1.2.1.3
NI-HWS 1.2.2.0
NI-PAL Software 1.8.2.0
NI-SCOPE 2.7.0f5
     SCOPE Soft Front Panel 2.1.0
NI Spy 2.2.0.12
NI-SWITCH 2.30.49153
NI-TClk 1.2
TestStand 3.1
NI-VISA 3.2
     visa32.dll 3.2.0.19
     NiVisaServer.exe 3.2.0.19
     NIvisaic.exe 3.2.0.19
LabVIEW Run-Time 7.1

Hello Maggie,
Appreciate your assistance and reply.
The pxisys.ini and pxiesys.ini files are modified by me with referring to
1)PXI System Alliance PXI-2 SW spec,
2)PXI-6 SW spec,
and 3)pxisys.ini pxiesys.ini generated by MAX v5.3.0f0 with NI PXIe-1075 + NI PXIe-8133.
The content in pxisys.ini/pxiesys.ini generated by MAX looks like simple. Consequently, I modified and checked it line by line according to actual hardware of PXES-2590+PXIe-3975. Then, MAX just list devices as described in the first post. I tried to find the root cause but in vain.
Is this minor issue can be related any incorrect tag lines in pxisys.ini or pxiesys.ini I posted?
Is any suggestion tests I can do to troubleshoot root cause?
Looking forward your reply.
Cheers,
KL Tseng

Compatibility of Pattern I/O with a PXI-6533 card with real time application

Hi,
I use a PXI-6533 card on a chassis with a PXI-8145 RT controller. I want to acquire 32 bits of data with this card at 1,25 kHz. These data are generated by an external FPGA card together with a clock signal. Referring to the 6533 documentation, a simple way to synchronize the acquisition is to use pattern I/O, entering the clock signal on the REQ pin. I tried the LabVIEW example Cont Pattern Input.vi. It seems to go well, but it does not work when I change this .vi priority to Time-critical or any higher priority than normal. Is there an incompatibility between this type of acquisition and real-time ?

Hi,
Sorry for this late answer, I effectively added a �wait until next ms function� in the time-critical loop and it seems to work. In fact, I don�t see exactly how, but it works with 1ms up to 50 ms.
Nevertheless, the next step is to add the content of this example in a more complex system with a communication loop to transfer the acquired data to the Host PC. I already have such an architecture, with a �time-critical priority� .VI to read the data at 1.25 kHz and a RTFIFO to transfer them to a second �normal priority� .VI loaded on the PXI, that ensures a TCP communication with the HOST PC. This architecture works correctly on another application with an internal clock, BUT doesn�t with this example, even with your solution.
In
fact, it seems to work when I put the two .VIs loaded on the PXI in �normal� priority, but with a tremendous jitter (the frequency varies from 1 to 2 kHz) and a scan backlog that gets full very fast. Then, the PXI crashes as soon as I change any priority.
You�ll find attached these three .VIs and I hope this could help to find a solution.
Cordially
PS: Since we started this thread, I�m in relation with NI Support France on that subject. Nevertheless, we haven�t found any solution yet and any new idea is welcome !
Attachments:
HOST_Comm.vi ‏532 KB
RT_Comm.vi ‏265 KB
TCLoop.vi ‏256 KB

Is the PXIe-PCIe8361 adequate for this system? And external clock questions...

Hi all,
I have spent some time piecing together a system and I'd like a sanity check before pulling the trigger on this purchase. The system will contain the following hardware:
1. Chassis: PXIe-1078
2. Controller: PXIe-PCIe8361
3. 3 x PXIe-6363 (16 analog inputs each card, 32 digital inputs each card, all internally clocked @ 10kHz)
4. 2 x PXI-6224 (32 digital inputs on one, 8 digital inputs on the other, externally clocked in "bursts" of 62.5khz)
5. Labview software
The three PXI-6363 cards will be responsible for a mix of analog and digital measurements made @ 10 kHz, timed continuously by the onboard clock.
One PXI-6224 will be clocked externally @ 62.5 kHz and will be used to collect digital data on a 32-bit port. These clock pulses will not be continuous, but will occur in bursts lasting for 2ms every 20ms.
The other PXI-6224 will be clocked externally @ 62.5kHz as well and will be used to collect digital data on an 8-bit port. These clock pulses will not be continuous, but will occur in bursts lasting for 2 ms at random intervals.
My questions are:
1. Am I planning anything that looks unreasonable for this hardware?
2. Should I expect issues with data transfer rates with the PXIe-PCIe8361? I will be operating well within the advertised 110MB/s throughput of the device. I plan to stream this method... NI Fast TDMS data streaming
3. I have only ever used NI cards for continuous measurements made by an onboard clock. When I set up a task to collect data that is externally-timed, will the DAQ be expecting a "continuous" clock pulse, or will the system wait patiently for clock pulses to arrive at any rate (any rate within the spec of the card, of course)?
Thanks, any input is appreciated.

Hello LucasH0011
1-As long as you put the PXI-6224 and the PXIe-6363 cards in the corresponding slots, meaning the express(PXIe-6363) in the express and the hybrid(PXI-6224) in the hybrid.
2-I think you would not have issues with the transfer rate.
3-Your timing specifications sound reasonable to me, I think you will be fine.
Here is a document that has useful concepts for the use of cards:
http://www.ni.com/white-paper/3615/en/
It is for the M-Series, but the concepts apply to the X-Series as well.
Regards
Ernesto

Is it possible to record data directly from PXI-5112 scope card through PXI bus to SCSI RAID array (connected to PXI-8210)?

Colleagues,
Is it possible to record data directly from PXI-5112 scope card through PXI bus to SCSI RAID array (connected to PXI-8210)?
Which will be the maximum transfer rate for continuous data recording?
Thank you,
Sergey
Sergey

Sergey,
The PXI-8210 can connect to any SCSI 2 compliant device. If the RAID controller is SCSI 2 and appears just like a hard drive in the operating system, then you can send data directly to the RAID array. The problem is that the driver for the PXI-5112 does not yet support continuous acquisition. The on-board 16MB or 32MB buffer stores the data until the entire acquisition is completed. Once the acquisition complete, all of the data is transferred from the on-board buffer to the hard drive. After that happens, the NI 5112 is ready for another acquisition.
Best Regards,
Jace Curtis
NI Applications Engineering

Simultaneous updation of sine wave using 2 PXI-6711 cards using RTSI Trigger

Hi ,
How to generate continuous sine wave using two pxi-6711 cards at same time without any phase shift using traditional nidaq functions.
Regards,
satya

In LabVIEW, go to Help>>Find Examples. Navigate to Hardware Input and Output>>Traditional DAQ>>Multiple Device. There is an example there called "Two E Series Shared Scan Clock". That example is for analog input, but you should be able to modify it to be for analog output. Basically you will just have to share the scan clock from one board(master) and use it as an 'external' clock for the other board(slave).
-Alan A.

How to generate a delayed retriggerable pulse using only one counter with PXI 6070E card

Hi
I have a problem in generating a retriggerable delayed pulse with a single counter(triggered through a signal at gate) using PXI 6070E card. VI was developed in NI LabVIEW traditional DAQ Ver.7.1. I have used the "delayed pulse generator config" VI and a "Start counter" & "Stop counter" VIs for the purpose. But there is no output seen at the out terminal of counter. So I introduced a "wait" VI and set it to 1 sec. Now the pulse output appears but some pulses are missing mometarily after every 1 sec interval. (any solution for this)
I have gone through a few similar requests in the forum but they suggest either to use two counters or to generate a finite pulse train which does'nt fit my application. Moreover PXI 6070E has only 2 counter timers. I am already using one counter to measure the frequency of a pulse train(signal 1). The application requires to generate a delayed retriggerable pulse for every pulse in signal 1. So I have only one counter left.
Can I measure the frequency of signal 1 by analog means.? so that I can use two counters for pulse generation. (Signal 1 is a TTL signal).
Request some help.
Thanks in Advance
Regards

A finite pulse train (N_Pulses >= 2) does require the use of 2 counters on most of our older hardware including your 6070E. If you're just talking about generating a single retriggerable pulse, you would only need one counter.
Here's an example in Traditional DAQ that shows you how to set a retriggerable pulse generation (it also allows you to adjust the characteristics of the pulse on-the-fly).
If you're writing a new program, you might consider switching to DAQmx as it supports NI's latest hardware and recent OSes should you ever need to upgrade. Traditional NI DAQ is no longer in active development. Here's an example of how to implement a retriggerable pulse generation in DAQmx. You should take note that you can't use the two drivers to simultaneously talk to the same piece of hardware, although you should be able to go back and forth by resetting the Traditional DAQ driver before switching to DAQmx.
Best Regards,
John Passiak

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

How do I get NIDAQ to allow 8 differential channels on a PXI 6031E card?

The PXI 6031E card contains 32 differential analog inputs (64 SE). However, in MAX, it is not possible to select Differential mode for any channels past the first 8. If you run the Test panels for the 6031E card (configured for differential input), selecting channels 8-31 results in an error. (0-7 operate correctly).

Yep! The URL has the answer. My problem statement wasn't quite accurate in that I claimed that I had errors on channels 8-31...Actually 8-15 and 24-31 were invalid and caused errors. What is/was confusing is that when editing an analog channel in MAX, and differential mode is selected, MAX allows the user to select invalid channel numbers(e.g. 8-15). The MAX editor requires the user to somehow "know" (or access the above URL) to skip 8 points to get to the next group of valid differential analog channels (16-23). It would be better if the channel number selector only displayed valid selections - based on the selected mode.

PXI-4110 Cards failing since upgrading to Calibration Executive 3.4

Since we upgraded to Calibration Executive 3.4 all of our PXI-4110 Cards have been failing the following:
Calibration
As Found
Channel
As Found DMM Reading
As Left DMM Reading
Test Value
Low Limit
Reading
High Limit
PassFail
2
0.999942
A
0.999942
A
0.25000
A
0.99557
A
0.94065
A
1.00432
A
Failed
2
0.999991
A
0.999991
A
0.50000
A
0.99524
A
0.93736
A
1.00474
A
Failed
2
0.999761
A
0.999761
A
0.75000
A
0.99370
A
0.94076
A
1.00582
A
Failed
This failure occurred on 3 brand new cards and I have even tried the last PXI-4110 before upgrading and it also failed these test and when an adjustment is attempted I receive the following error:
Error -300010 occurred at Get UserField Data.vi
Complete call chain:
     cex_UtilityGetUserFieldData.vi
     cex_UtilityGetUserFieldDataByIndex.vi
     _NI 4110_Get Channel Range and Level.vi
     Adjust_NI 4110_Current Out Accuracy.vi
at step Adjust Current Output Accuracy
I am using a Agilent 34401 for the DMM.

JVP
Here are the files you wanted. Sorry this took so long. The hard drive on the computer that we have the Calibration Executive software on died and we had to reinstall everything. So and I tried to run another card with the same results the calibration report I am sending you is from today. I sent the reoprt in two formats XLS and PDF.
Attachments:
ni_support.zip ‏197 KB
71517 Wednesday, January 11, 2012 8-28-29.xls ‏49 KB
71517 Wednesday, January 11, 2012 8-28-29.pdf ‏30 KB

Failure to synchronize simulated PXI 5124 cards, but they synchronize without error on physical hardware.

I need to create a software development machine based on our existing experimental machine. We use two PXI 5124 cards mounted in a PXI 1042 Chassis and run LabVIEW 2013.
According to what google has returned, it is currently impossible to simulate a PXI Chassis, so I have the two devices mounted individually. Here is the experimental machine device list:
and here are the simulated devices on my development machine.
I have verified that the simulated devices are working by creating a simple program that graphs the output of the simulated devices. See attached.
However, when I run the program that we use on our experimental machine, the program fails to synchronize the clocks. I'm not sure if I would be allowed to post this program, so I have merely attached a picture of the part that creates an error.
Up to this point, there are no errors, but when synchronization begins, I receive the following error:
Error -250027 occurred at niTClk Configure For Homogeneous Triggers.vi:2010001
Possible reason(s):
NI-TClk does not support the specified session.
Make sure that the sessions you pass to NI-TClk are supported by NI-TClk.
Session index (starts at zero): 0
Using probes, I can determine that there are (seemingly) valid resource names [9] going into the Configure VI:
These are not fundamentally different from the resource names [2] on our experimental machine:
According to this page I should be able to synchronize. While no longer in the same chassis, the two devices are still in the "same computer," are they not? Nevertheless, the error message makes me think I'm trying to do something that isn't allowed.
I've tried to look at other posts, but they are mainly concerned with FGEN, which I am not using.
Any ideas?
Attachments:
simulated_devices.vi ‏34 KB

Hello,
By default, arbitrary waveform generators use High-Resolution Clocking to generate a waveform if the sampling rate that you choose is not an exact integer division of the maximum frequency of function generator. When High-Resolution Clocking is used, the sampling rate you specify can actually be coerced to a slightly different value than specified.
The problem with this is that if your specified sample rate is coerced into a non interger it will not be evenly divisible into other frequencies. When synchronizing multiple devices using NI-TClk, the algorithm will attempt to choose a TClk frequency that all sampling rates can be divided into evenly. Having an actual sampling rate that has been coerced into a non devisable value throws off the NI-TClk algorithm resulting in error -250016.
Could you try to disable High-Resolution Clocking and use Divide-Down Clocking instead. You can do this in LabVIEW using the Clock Mode property of the niFgen Property Node, and setting the value to NIFGEN_VAL_DIVIDE_DOWN.
Please let me know if this helps.
Cameron T
Applications Engineer
National Instruments

Error -200022 from PXie 6556 cards

I am running into trouble when running my application to synchronize 3 PXIe 6556 card. How could I fix it?
Error:
ni HSDIO Initiate.vi<ERR> Driver Status (HEX 0xBFFA4014)
Resource requested by this session has already been reserved by a different session.
Property: RefClk.Source
Reserved Value: None
Requested Value: PXI Clock Line
Status: -200022
Thanks for your help.
AnDong
Attachments:
Write_Read Test from HWS file_for_3_card_Test_DIO_output.vi ‏93 KB

Hi,
Does your signal generation operation take longer time than what you have specified in the input terminal:
http://zone.ni.com/reference/en-XX/help/370520K-01/hsdioviref/hsdio_wait_done/
Try changing the timeout value and run the code with "Highlight Execution", see where the error occurs.
Br,
/Roger

Analog,digital and pfi triggering of PXI 6133 card

Hello,
i am using PXI-6133 card. i observed that there are three type of triggering options(i.e., analog, digital and PFI) available on each card. i want to know the difference? and also best one.
regards
chandu

Hi chandu,
Analog triggering is based on the value of an analog
signal. For example you can trigger when your analog signal goes above or below
a specified value. Digital triggering happens on a rising or falling edge of a
digital signal. For either type of triggering you must have a trigger source
that is the signal you are triggering on. For digital triggering on your card this
can be any PFI line. For analog tirggering it can be any analog input channel.
A detailed explanation of the triggering capabilities of your PXI-6133 can be
found in the S-Series User Manual. Triggering is discussed in Chapter 13. Also
a more great summary of triggering in general can be found in the Developer
Zone article, Tips and Techniques in Data
Acquisition Triggering - NI-DAQmx. What triggering is better depends on your
application and which one is more suited to your trigger signal. If you have a
digital trigger source then digital triggering will work great. If your trigger
source is an analog signal than you will probably need to use analog triggering.
Let me know if you have any questions and have a great weekend.
Thanks,
Nathan
National Instruments
Digital Hardware Engineer

How many PXI Ethernet Cards supported in LabVIEW RT?

How many ethernet ports does LabVIEW RT support. If I put in several cards (such as PXI-8231, PXI-8232, or PXIe-8234) into a PXI chassis, then would I be able to configure and use them all?

Hello kmcdevitt,
It should be fine to have as many ethernet cards as you need in the PXI chassis. There's a global limit depending on the number of interrupt lines available on the motherboard (or PXI chassis), but it's up to around 16, depending on the controller. You would set them up using the Advanced Ethernet Settings section in MAX, as explained in this LabVIEW Real-Time Module Help article. I posted the 2011 help but this works for a few versions back, what version of LabVIEW RT are you using? Hope this helps!
Regards,
Deborah Y.
LabVIEW Real-Time Product Marketing Manager
Certified LabVIEW Architect
National Instruments

Finding PXI 6071 cards in PXI system

Similar Messages

Maybe you are looking for