Would a PXIe card work in PXI chassis?

Hi,
I planned to add another 4472B to the existing PXI chassis but noticed that PXIe 4492 is recommended to replace 4472B. I am wondering if PXIe 4492 would work in a PXI chassis (PXI-1056).
Thanks!
XR

The PXI and PXIe have different connectors. So the short answer is "no". If you had a PXI chassis with hybrid slots, either PXI or PXIe cards could go in those slots.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

Which is better, many PXI cards or fewer PXI cards with more SCXI cards?

I have a pretty basic question. Which is "better", using multiple PXI cards for analog inputs or a single PXI card and multiple SCXI cards? For example, if I have say 100 channels to sample (all at the same rate), I could use 2 6225s at 80 ch each. Or I could use 1 6220 and 4 SCXI 1100s (32 ch each). What are the pros and cons with either approach? Keep in mind sample rate probably isn't an issue (less than 1 kHz) but it is the same for all channels.
Thanks.

The pros/cons will depend on your application now and in the future. I recommend contacting your local NI sales representative. Synchronizing across a PXI system is easy to do via the backplane. There are PXI/SCXI combo chassis available, you could use PXI multifunction DAQ cards and then SCC for signal conditioning for thermocouples for additional functionality later. There are many possibilities that may be best discussed with your sales representative.
Regards,
h_baker
National Instruments
Applications Engineer
Digital Multimeter Resources

Would this storage card work in the Media Card slot of my W700?

Hi,
I'm interested in buying this Lexar 133x SDHC Card:
http://lexarmedia.com/products/lexar-professional-133x-sdhc-card?category=213
Basicallyl, I want to use it as another storage drive (as opposed to putting in my camera or other device). So after I insert it, I want to be able to format it and use it as another storage area. Would this card work?
The reason I'm gravitating to that card is that is that I see in the specs that is minimum 20MB/sec read transfer rate and it does not take up one of my USB slots.
However, even if it does work, would I be better off with their Echo ZX plug-and-forget it USB drive when they ship it?:
http://lexarmedia.com/products/lexar-echo-zx-backup-drive-0?category=90
If both work, which would be faster as a storage drive?
Thanks.

It is a SDHC card so it should work on the card reader of the W700.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Does anyone know of a compact PCI to PXI card adaptor?

We wish to place a Compact PCI card into our PXI-1006 chassis. We are using windows 2K.

Reida,
No adapter is necessary. You can use any CompactPCI or PXI card in a PXI chassis.
Regards,
Greg Caesar

Can my current cards work with a newer system?

I have an old system that was created in Windows 3.11 and is running LabView 3.5 with AT-MIO-A6E- 10 and PC-TIO-10 cards. I would like to upgrade the system, would my softaware/cards work on anything newer (i.e. windows 98 and up)

Hello;
The current version of Labview is 6.1. This new version won't be able to open a VI that was coded with such old version of Labview. You will probably need to recode your VI on version 6.1.
Regarding the DAQ devices, the AT-MIO-16E-10 and PC-TIO-10 are supported by the latest version of the NI-DAQ driver (6.9.1), which also supports all the new OSs (W98/NT/2000/XP).
Regards
Filipe A.
Applications Engineer
National Instruments

Simultaneously triggered acquisition: Multiple PXIe-7962R + NI-5734 cards, across multiple PXIe-1085 chasses

Hi all,
I need to do high-frequency, high-channel-count acquisition.
Specs
Signals: 10 MHz, 60 channels
Controller: PXIe-8135 (Windows 7)
Chasses: PXIe-1085 (2x)
Input cards: PXIe-7962R FlexRIO base with NI-5734 digitizer (15x)
Description
Each FlexRIO card will store data in circular buffers, and continuously monitor the voltage levels. When any one channel exceeds the user-defined threshold, all 60 channels need to be triggered simultaneously to pass waveform data (200 μs pre-trigger, 300 μs post-trigger) to the host OS for logging.
In other words, every FlexRIO card needs the ability to fire the trigger, which is then received by all 15 FlexRIO cards (the card that fires the trigger also needs to receive the trigger).
Question
Can I achieve this with only a single PFI line? Or do I need some other technique?
I've found some examples, but they only show single-source and single-card triggering, e.g. https://decibel.ni.com/content/docs/DOC-30182 uses one analogue input to trigger the acquisition of 2 channels on the same card.
Any advice would be much appreciated. Thanks!

Assuming you are using LV 2013 or 2014 you should download version 1.3.4 of the FlexRIO Instrument Development Library (FIDL). This will install 5734 Acquisition Engine examples which use the MultiRecord Library to stream data to the DRAM in a circular buffer, allowing you to recover pre-trigger samples. The example also demonstrate how to implement the Syncrhonization Library that synchronizes triggered acquisition to within a single sample period across multiple devices.
Getting the example to work across two chassis' may be difficult, but I believe it is possible. Though to do so you will need a timing and sync module in each chassis to distribute the triggers and reference clock that the sycnrhonization library requires.
National Instruments
FlexRIO Product Support Engineer

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

Using PXI-6682(H) in PXI Express chassis to replace backplane clock

I have a PXI-6682H in a PXIe-1075 which I use for event timestamping. I also have a PXIe-6672 card in the timing slot.
I would like to replace the 10 MHz backplane clock to use the 6682 as a GPS disciplined oscillator and synchronize multiple PXI chasses.
I understand from the block diagram in the manual that the PXI-6682H does not possess the connection to directly replace the backplane clock as the PXI-6682 does in a PXI chassis.
Is there any way for me to replace this clock? Perhaps using an external connection? If so could you briefly explain how this would work and what software steps would be required?

Hello Gregoryng,
It might work since the PXIe-6672 and the PXIe-6674T are both timing and synchronization modules, but the best option would be the PXIe-6674T, which is able to work with other protocols such as GPS while the other cannot. It seems that in the video they use GPS.
I think the PXIe-6672 will not work for this with the PXI-6682H, but you can give it a try.
The one in the video seems to be a PXIe-6674T.
Regards.
Ernesto.

PXI-1052 not detecting SCXI chassis

Full disclosure: I've submitted a support request on this too, but knowing that it may take some time to go through I thought I'd ping the discussion boards for any ideas people here might have as well.
I have a PXI-1052 PXI/SCXI combo chassis with a PXI-6289 card serving as the SCXI controller. Up to this point, the chassis has been controlled by a PXI-8105 embedded controller running WinXP. We are changing this. The PXI-8105 controller is being removed and instead we will use an MXI card (PXI-8360) to allow us to control the chassis via an external computer running Win7 32-bit.
With the chassis on and connected, using the Win7 computer I can see the PXI slots and the cards in them are correctly identified by model number. However, I cannot see the SCXI portion of the chassis, and when I try to manually add an SCXI chassis I am told that there is no DAQ device installed to serve as the SCXI controller. In addition, the PXI-GPIB card which is also installed is acting a little strangely. It allows me to scan for instruments, and it sees all of my GPIB instruments OK, but I don’t see a GPIB bus defined separately under Devices and Interfaces the way I did on the old controller—the instruments just show up listed under the PXI card.
I have read the Knowledgebase article on auto-detecting SCXI instruments, but it doesn’t seem to offer anything helpful. Everything works fine if I put the old controller back in and use it again, so this isn’t an issue of a bad card/chassis or the wrong card or a blown fuse or SCXI power not being on/set correctly or the DAQ being in the wrong slot. (The ONLY hardware difference is the controller being replaced by MXI; everything else is exactly the same.) All NI software on the Win7 machine is installed and up-to-date, and I even reinstalled everything just to make sure I hadn’t gotten a bad install. It seems to me like it must be either a driver or a configuration issue, but I’ve combed through the Windows Device Manager and the settings for all cards involved and can’t find any differences.
Screen shots attached. Any ideas?
Solved!
Go to Solution.
Attachments:
Win7.png ‏109 KB
winXP.PNG ‏73 KB

Hello Sara_J,
I'm going to post to the forums with my suggestions from my email so that if we find the answer it will be available to the community as well.
As long as the 6289 is showing up incorrectly you're not going to be able to use the SCXI side of the chassis. The problem looks like your 6289 is not being associated as a DAQmx device. The alias it has in MAX is showing it as a generic VISA device. You'll have to manually associate the 6289 in device driver. Normally it would show up under Data Acquisition Devices with the NI logo in Device Manager. Since its not showing up correctly it may be located elsewhere, most likely under a PCI Standard PCI-to-PCI bridge (this is how the MXI card looks in Device Manger).
Once you find it, right click and select Update Driver Software...>>Browse my computer for driver software>>Let me pick from a list of device drivers on my computer. You should then be able to pick the appropriate driver from the list.
If this does not fix the issue then I believe there may be a corruption in your installation of DAQmx. You can download the newest version (9.9) here: http://www.ni.com/download/ni-daqmx-9.9/4707/en/ .
Jonathan L.
Applications Engineer
National Instruments

Exe not working in PXI RT Target

Hello all,
I wondered yesterday while I am working with my PXI RT system.
My system having following components.
PXI RT Controller 8108
PXI Chassis 1042
LabVIEW 2009
LabVIEW RT 2009
NI MAX 4.6.2
The following observation on my system.
1. While running VIs in Host and RT system it works fine but after making a build for RT target and set as startup exe, it wont work at all. I am communicating with host and RT using shared variable libraries and it is deployed in RT target.
2. There is no any error while building an exe or after deployng RT exe and run the host exe, but neither I get any data from RT not I can control from Host.
3. As I serch for Remote device in MAX. I can identify my PXI chessis and the cards installed on it but while I am expanding the "Software" segment it doesn't show any software installed but by selecting "ADD/Remove Software" a new window popups and the list of Installed componets appears.
I don't know why its happening, Please Advise.
Awaiting a Reply.
Malhar Chaniyara
Application Engineer.
Greetings from India.
Greeting from India,
Malhar

This problem may be also caused by the policies keys. You can use the followling method to remove the policies keys:
Remove Group Policy
================
1. Click Start, type REGEDIT in the Start Search bar and press Enter.
2. Locate the following key in the left pane:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft]
3. Highlight “Microsoft” folder and click "Delete".
4. Repeat to delete the following keys:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Group Policy]
[HKEY_CURRENT_USER\Software\Policies\Microsoft]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies
If some keys do not exist, please ignore them.
If the issue persists, you can run an in-place upgrade to repair the system.
In-place Upgrade
=============
1. Insert the Windows 7 DVD in the computer's DVD drive.
2. Click Start and choose Computer.
3. Please find the "setup.exe" file in the DVD-ROM and double click it.
4. Click Install now.
5. When we are prompted to input the product key, please click Next without inputting any key. The setup wizard will prompt and ask if you agree to install Windows Vista without the key. Please choose to confirm.
6. When you reach the "Which type of installation do you want" screen, click Upgrade to upgrade the system files of Windows 7.
Thomas Lins

Why are my PXI cards not recognized by Windows or MAX?

I have a PXI-1045 chassis connected to a PC through MXI-4. When I turn the chassis and PC on with a PXI card in slot 2, the message "Windows could not load the installer for DAQDevice. Contact your hardware vendor for assistance." appears, and the PXI card is not recognized (it is scene by Windows as an unidentifiable PCI Devices, though I have a DAQmx installed).
More details:
Windows XP
LabVIEW 8.0 installed
TestStand 4.0 installed
Latest DAQmx 8.XX installed
NI Scope installed
NI CAN installed
MXI-4 PCI card installed in PC and recognized by Windows (as PCI-PCI bridge, and MXI-4 Device)
I identified PXI chassis 1045 in MAX and on subsequent boot up saw that MAX complained about pxisys or some other ini file (in the chassis status area of the screen) so I configured it as 'other' then put in the PXI-resorce CD and selected the ini file for PXI-1045, MAX no longer complains about pxisys and instead says the chassis is configured properly
If I have nothing but the PXI MXI-4 card installed in the PXI system and boot up the chassis then the PC, I get no errors
If I have a card in slot two (I've tried PXI-6509 Industrial Digital IO, PXI-2569 Relay Module, and PXI-5102 Digital Oscilliscope) and boot the chassis then PC, the message "Windows could not load the installer for DAQDevice. Contact your hardware vendor for assistance." shows up when Windows boots and Windows sees a PCI Device but can't identify any drivers for it.

Hello,
Can you post a screenshot of the problem? Are you switching on the chassis first or the PC? Please make sure that you switch ON chassis and then boot the PC. This typically happens when you have a corrupted installation. I would suggest downloading the latest version of driver from here and re-installing it.
Please uninstall all the driver software from computer before installing the new software.
http://digital.ni.com/softlib.nsf/websearch/d31d46fffb745eca862571490053eab8
Thanks,
Kalyan
Applications Engineer
National Instruments

ADLINK PXIe-3985 Controller - NI PXIe-1062Q Chassis Compatibility

Hello forum members!
we recently purchased a PXIe-3985 ADLINK PXIe Embedded controller to be installed in a NI PXIe-1062Q PXIe chassis. In our system is also present a NI PXIe-6672 Timing Module, installed in the chassis timing slot (4). Windows 7 installation, NI MAX toolsuite and NI PXIe-6672 Timing Module driver installation worked fine, but we discovered that the CPU is not able to recognize the TIMING SLOT. We cannot generate any PXI STAR signal with our NI PXIe-6672 Timing Module because it appears that the TIMING SLOT is recognized as normal peripheral slot. The PXI trigger lines and clocks are working well and usable, but not the PXI STAR signals.
I also tried to install the PXIe Chassis in the NIMAX toolsuite as explained in the PXIPLATFORM _50-17049-100_200.pdf document from ADLINK.
basically in the NIMAX device and interface tab I right click and try to add the pxie chassis.
First it is not understandable how can I find the bus identifier root of the chassis. There is a PXI bus tree, but no evidence of the PXI bus related to the chassis.
Furthermore even if I select one PXI bus, the NI PXIe-1062Q PXIe chassis is not listed and trying to load the corresponding .ini file from C://programs/nationl instruments/PXI/PXIe Chassis/ returns the error “Could not import Chassis information. Error Code 0xFFFB380E”
is the ini file working at all for my PXIe chassis? is there another procedure that I must follow to have my timing controller working or the chassis installed?
We definitely need this capability to test our equipment and I would like to know if there are known incompatibility issues between these three devices:
PXIe-3985 ADLINK PXIe Embedded controller
NI PXIe-1062Q PXIe chassis
NI PXIe-6672 Timing Module
And in case if there is an update or workaround which solves the issue.
The system has Win7 32bit installed.
Many thanks to every answering user

Hi emanuele83,
which version of PXI Platform Service do you use?
Can you please upgrade to a current version?
Here is a download link:
PXI Platform Services 14.1 - National Instruments
http://www.ni.com/download/pxi-platform-services-14.1/5230/en/
This may solve the issue.
Best regards,
Andi

Accessing a SWTICH and DMM cards in a PXI System remotely

Hi everybody,
I use a PXI system with a NISwitch PXI-2503 and NiDMM PXI-4070. The embedded controller PXI-8176 is running WinXP.
From a client machine I want to access remotely this cards. Via VISA Server it is possible to interact with the Switches using NI's driver NiSwitch. On the ther hand, I did not succeed so far to access remotely the DMM using the driver software NiDMM. I receive always the following error:
"Error -1074135030 occurred at niDMM Initialize.vi
Possible reason(s):
Error: (Hex 0xBFFA000A) Failure loading driver module."
My Software Versions are:
Labview 7.1, VISA 3.1, NI-DAQ 2.10, NiSwitch 2.20, NI-DMM 2.2.1
I have read that there are some incompatibilities between VISA and RDA conc
erning the TCP-IP port, but this problem should be solved in the versions I currently use.
Anybody out there who knows a workaround?
Thanx for any help in advance
Hannes Schmidt, Swiss Federal Institute of Technology, Lausanne

Hannes,
Unfortunately I don't think anybody here knows of a workaround because the application is not one that anybody has recently tested using NI-DMM. The easiest work around to me would be to use LabVIEWs remote front panels to do the acquisition. The only reason why using this might cause a problem is if you need to save data to file on a remote PC. So the only consideration to work with is to save the file on the host PC and then grab the file saved using FTP or something along those lines. That may be a much easier work around than trying to figure out what is going on with the low level DMM driver call. Hope this helps. Good luck with your application.
Best Regards,
Jeremy Ross
NI - Applications Engineer

Document "Is my PXI card hybrid slot compatible?"

Hi, I would like to ask for some clarification and make a suggestion for Document 4S3F9Q9G, "Is my PXI Card Hybrid Slot Compatible (PXIe-Ready)". In this document, there is a series of statements about the compatibility of various card types with various slot types.
Link: http://digital.ni.com/public.nsf/allkb/50C189CF7BF8884B86257515007184F4
I know that the document only intends to say whether any type of card is compatible with a PXI Hybrid Slot, it almost answers the question of what all cards are compatible with what all slots, which is the more general question I am trying to answer as I try to juggle devices and chassises.
Knowing basically nothing about the PXI standards, I attempted to produce a compatibility matrix from these statements alone, and I'd like to see if I arrived at the correct conclusions. I'm not sure if I used the conventional nomenclature, but it should be clear from the statements why I used those terms. See the attached PDF.
There are the pictures at the bottom where you can play a game of hocus focus to figure out which cards fit in which slots, but I think it would be much clearer with a matrix.
So my suggestions for the document are:
add/edit the statements provide information about "blank" cells
add a completed compatibility matrix for quick reference.
Indicate on the matrix, or reference, the standard symbols indicating slot types, used below the slots of a PXI chassis
Thanks,
-Gregory Ng
Attachments:
pxicompatibility.pdf ‏36 KB

Great to hear that it looks correct. I assume that you mean that I have not introduced any erroneous information.
But the reason that I submitted this message here, rather than directly on the page, is because I believe that my matrix is incomplete, and so I was hoping for some expert feedback on that and a quick commentary about why.
For example:
- Will the PXI system timing slot accept standard connector PXI cards, 32-bit compactpci cards, or hybrid compatible cards?
- Is it possible to plug a PXI standard connector module into a PXI hybrid slot?
Just for completeness, the text and matrix don't answer these questions, but I don't actually care about them.
- Is it possible to plug a PXI system timing module into a PXI hybrid slot?
- Will a standard PXI slot accept system timing cards, 32-bit compact pci cards, or hybrid compatible cards?

How to use PXI Star Trigger for PXIe-5663 in PXIe-1075 chassis

HI all,
I have this sytem configuration:
PXIe-8135 controller. Windows 7 64-bit, RFSA 2.7.5. NI-SYNC 3.4.1
PXIe-1075 chassis
PXIe-5663 (2x)
PXIe-6672 Timing & Sync Card (slot #10)
I want to trigger the recording of my Digitizer with an external trigger.
The External Trigger is connected to PFI0 of the PXIe-6672 Timing card.
Then, the PXIE-6672 card routes the trigger to the backplane of the PXIe-1072 (Destination "NISYNC_VAL_PXITRIG0")
The PXIe-5663 are triggered with “NIRFSA_VAL_PXI_TRIG0_STR” as the source.
The trigger fires my PXIe-5663 correctly, but the timing is not tight (> 5ns).
I would like to use the PXI Star trigger instead, I think that I should be able to acheive much better synchronization with this.
But NI-RFSA won't let me do this:
When I try to call
"niRFSA_ConfigureDigitalEdgeStartTrigger(rfsa_session, NIRFSA_VAL_PXI_STAR_STR , NIRFSA_VAL_RISING_EDGE)", I get the error:
"Specified Route Cannot Be Satisfied, Because the Hardware Does Not Support It"
I don't understand why the PXIe-5663E would not be able to use that Route.
Any idea?
Regards,
Serge
Serge Malo, ing.
Concepteur logiciel
Software Developer
T (514) 842-7577 x648 | [email protected]

That explanation isn't quite right. Usually, even PXIe modules have a connection to PXI_Star. The PXIe standard added the PXIe_DStar trigger buses, and it also preserved the PXI_Star bus from the PXI standard.
However, there is an additional twist in this situation. I'm assuming that your PXIe-5663 includes a PXIe-5622 as the digitizer. It turns out that a synchronization technique called NI-TClk has eliminated the need for our more recent digitizers to rely on triggering from PXI_Star. I was able to find some documentation that includes this information, here and here. Given that, I think you have two options that should result in better synchronization.
The first option is to use TClk; I found an example program that demonstrates using TClk to acheive phase coherent signal acquisition across two 5663s. The second option is to use cables of matched length to connect two PFI front panel terminals of the timing board (6672) to the PFI1 front panel terminals of the digitizers (5622). The timing board would accept the external trigger on PFI0 and then issue triggers on PFI1 and PFI2 with around 500 ps of skew (manual, page A-4) . The digitizers would use NIRFSA_VAL_PFI1_STR as the trigger. I hope one of these solutions will meet the demands of your particular application.
I will also follow up with the owners of the RFSA product documentation to see if we can include a note about why PXI_Star is not supported in some cases.
James Blair
NI R&D

Would a PXIe card work in PXI chassis?

Similar Messages

Maybe you are looking for