PXIe-1073 not detected

I'm trying to install a PXIe-1073 chassis on a new Dell system running Windows 7 x64. I have the latest version of Labview, NI-DAQmx, etc. The PCI express controller shows as properly installed in the Device Manager ("PCI standard PCI-to-PCI bridge"). The chassis and installed DAQ card are not detected in MAX.
I am actually transferring this system from an older computer. I recall having exactly the same problem before, and I'm fairly certain I solved it by installing the "MXI-Express BIOS Compatability Software". There was never any way to actually identify the "PXI System" as anything other than "External PC" even when it was working properly.
After installing the current version of the MXI-Express software, I rebooted and was able to load MAX briefly before Windows BSODed with an error involving "niraptrk.dll". This proceeded to occur every time I tried to load Windows. I was able to start in safe mode, but attempting to uninstall any NI software gave me an "error 1601". I was finally able to load the last known good configuration and uninstall the software.
When I checked MAX again, the chassis was still unrecognized, but there were multiple broken entries for the DAQ card installed in it, so I assume it was detected at some point. It looks like the MXI-Express software worked, but it's obviously unusable if it causes the computer to BSOD every time Windows starts. Why is the computer unable to recognize the chassis without it? What else can I do to solve the problem?

Hello Bob_mcbob,
After looking over this issue, I think we have a problem with the Windows installer on your machine. I have found a KnowledgeBase about the Error 1601 stating that this is a Microsoft Windows installer error and that the installer will need to be reinstalled. The Knowledgebase explains how to do this.
As for the BSOD, do you have any more information that it provided when this occurred like the address line, etc? Did you do something in MAX before it crashed?
Since accessing MAX now gives you a BSOD, I think it would be best to uninstall/reinstall the drivers to fix the issue. What cards do you have in this system?
Jim St
National Instruments
RF Product Support Engineer

Similar Messages

NI PXI-1033 not detected if turned on after PC

Hi,
I noticed that MAX does not detect the presence of the NIPXI-1033 if it is turned on after the PC.
There is a programmatic solution to resynchronize the device? My application using C # and C + +.
thanks
Roberto Guerzoni
Solved!
Go to Solution.

Thank you Roberto
It is normal what happens. Your PC has to see the device during the boot up. It is a BIOS matter.
Have a great weekend!
Antonios

PXI cards not detected

I'm using SignalExpress with a NI PXIe-1062Q chassis and the following cards:
PXIe-8360
PXI-4071 DMM
PXIe-6556 waveform generator/analyser
PXI-4110
All cards are detected by NI MAX. However when I create a waveform in SignalExpress, it's unable to see my hardware. It can see the 4071.
I'm following the correct startup procedure of booting the chassis first, then booting my PC.
Any suggestions?

Hello AidanFrost,
The reason for this could probably be that you may not have the correct drivers installed. Which drivers do you have on you computer at the moment ?

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

PXIe-1073 sytem not detected

I connected a PXIe-1073 system (PXIe-6363 and PXI-2567 connected) to the PC (running Windows 7) and the PC does not detect the chassis. It started happening when I recently upgraded to LabVIEW 2013 and NI-DAQmx 9.7.5.
I also installed the MXI BIOS compatibility software Ver 1.4, changed the DIP switch1 to ON position on the MXI express card 8361 and rebooted the computer. That did not solve the problem.
Then, I upgraded to PXI Platform services 3.2.3 and restarted the computer. I still don't see PXI system recognized in NI MAX. When the computer was restarted, the 8361's MXI card's switch 1 was still in ON position.
Any ideas on how to fix this issue ?
Thanks
Jeet

Hi Matt
Sorry for delay in replying.
After a lot of uninstallation/installation/repair of different driver versions, i have currently got the following software (see attached pic): NI-DAQmx 9.5.5, Ni PXI platform services 3.2.1.
In the picture, you can see that all my cards are detected in NI-DAQmx devices as Dev1, Dev2 etc.
My PXIe-1073 is not detected or listed in MAX. I expect to see chassis controller detected and all the cards listed under the chassis controller as "PXI2slot2" device or "PXI2slot4" device etc.
The attached pic shows NI-MAX and device manager snap shot.
Please advise.
Thanks
Jeet
Attachments:
nimax dev man.jpg ‏316 KB

PXI-8532 DNET card is not detected in MAX

Hi all,
I'm using NI PXI-1031(4 slot PXI chassis). I have the following cards in the respective slots
Slot 1= PXI-8106 Controller
Slot 2= PXI-6259 card(AI)
Slot 3= PXI-6509 card(DI,DO)
Slot 4= PXI-8532 Card(DNET)
In MAX(Measurement & Automation Explorer), I was expecting all the above cards(PXI 6259, 6509 & 8532) to be detected under Devices and Interfaces. But only the AI and DIO cards are detected in MAX under Remote Systems>>PXI>>Devices and Interfaces.
PXI-6259 (PXI1 Slot2)
PXI-6509 (PXI1 Slot3)
The device net card, PXI-8532 is not detected in MAX. Does MAX shows/detects the DNET card?
In MAX, I selected Tools menu>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, I pressed OK. A message appears that no device is found.
Can any one help me how to detect the DNET card in MAX and do the DNET port configuration?
DNET driver version - 1.6.4
Thanks,
Raja
Solved!
Go to Solution.

Dirk,
Thanks for the reply. After updating the new driver, I am able to detect the DNET card PXI-8532 in MAX
New driver - NI-Industrial Communications for DeviceNet 2.1
But Im not able to configure the Device Net port. In MAX, I selected the menu option Tools>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, a message appears that no device interface is found.
By default, the DNET0 port is configured for the card in MAX. So I tried to communicate from LabVIEW using DNET0 port.
After installing Devicenet 2.1, an additional function palette has been added for DNET in LabVIEW.
Old DNET function palette - Instrument IO>>DNET
New DNET function palette - Industrial Communications
My original application was written with old function palette VIs which corresponds to DNET 1.6.4 version. In the download link that you shared has a description about the driver compatibility. The description says still the DNET card PXI-8532 is compatible with NI-DNET 1.x LabVIEW VIs.
With the old DNET VIs, I tried to establish communication with DNET interface port "DNET0". But it shows error while opening the interface.
Error Code ="-1074388957" - The Interface is invalid or unknown. Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
With the new DNET VIs(DNET 2.1.0), Im able to open the DNET interface successfully. But my original application was written in Old DNET VIs (DNET 1.6.4).
1. Do you know why the DNET 1.6.4 LabVIEW VIs are not working with PXI-8532 DNET card?
2. Can you help me how to configure DNET port in MAX for PXI-8532 DNET card?
Thanks,
Raja
LV 2009, Windows XP

NI Scope Sorf Front Panel will not detect NI PXI-5122

Hello,
I am trying to use NI Scope Soft Front Panel 2.7f0 to acquire simple waveforms;
however it will not detect my NI PXI-5122. I have confirmed that the digitizer
works under MAX 4.2.1 and can see waveforms under the test panel. I have
installed NI Scope 3.3.1 on my machine and have updated the driver on the PXI
to version 3.3.1. Any ideas on what is wrong?
~Buck

It is unclear from your post whether or not the 5122 is on the same physical device as you are running the soft front panel (SFP). The SFP only works on local devices. It does not have the capability to attach to RT or remote systems (MAX does). However, if you are running Windows on your PXI controller or are using MXI to control the chassis, there is another issue.
This account is no longer active. Contact ShadesOfGray for current posts and information.

MXI3 (NI PXI-8330) board not detected. Not powering up, no link light.

MXI3 (NI PXI-8330) board not detected. Not powering up, no link light. Cable looks fine. Any ideas?

PeteMan,
I will need to know in more detail how your system is behaving to give you better tips, so please feel free to send me more information.
For now, let me send you a couple of troubleshooting tips:
Cable connection
Make sure both ends of the copper cable are well connected to the PCI-MXI-3 and the PXI-MXI-3 boards. Be careful when disconnecting the copper connectors. you need to push down the plastic connector so it does not get damaged. Damaged connectors could result in bad MXI-3 links.
If the connector has not been used properly, it could be broken (this rarely happens). Make sure you are not connecting the cable backwards.
Power - Up order.
It seems you are controlling your PXI chassis using a PCI-to-PXI extender (copper cable). Make sure you are powering up the PXI chassis BEFORE powering up the PC.
PXI is built on top of the CompactPCI spec, so it uses the PCI high speed bus. The MXI-3 extender is really a PCI-to-PCI bridge toyour computer, so for your PC, all the slots in the PXI chassis look like more PCI slots. In other words, your computer suddenly has more PCI slots.
It is very important to power up the PXI chassis first before powering up the computer, because at power up the PC enumerates all PCI slots. If the PXI chassis is OFF during boot up, the slots in the PXI chassis will never get enumerated and your PC will never see the board installed in the PXI chassis.
Normal Power up LED sequence
Each MXI-3 board has four LED light on its front panel: two green lights (POWER and LINK) and two orange lights (Tx and Rx). When you power up the PXI chassis you should see one green light and one orange light ON steadily (POWER and ). Then, when you power up the PC, both green lights shoudl be ON steadily and the orange lights shoudl flicker.
If you do not see this behaviour at power up, most probably one of your boards its damage.
If you have another MXI-3 extender kit, try to set up the system mixing the boards from the two kits to try isolate which board is the one that is damaged.
Run the MXI-3 Optimization Software
The MXI-3 Optimizaton Software makes sure that the link between the PC and the PXI chassis has been set up properly. It will show you an error otherwise.
MXI-3 Software Version 1.15 for Windows 95/98/NT/2000/ME
The PC powers up fine if the PXI chassis is OFF, but if I turn on the PXI chassis first and then try to power up my PC, my PC does not boot
There are several things that could be causing this behaviour:
It could be that your PC has an old BIOS that has issues detecting PCI-to-PCI bridges. You could try upgrading the BIOS.
A part of the hardware could be damaged. If you have a main-stream computer (like a DELL or HP PC, for example), test your MXI-3 extender in it to make sure that the hardware is in good conditions. Main-stream computers tend to use new Motherboards with good BIOS.
There are more tips in the following KnowledgeBase:
KB 267FAS5P : MXI-3 Troubleshooting Guide
Hope this helps,
Claudia Lorente
Applications Engineer
National Instruments
http://www.ni.com/ask

Pxi cards on 1000b cahssis not detected under windows 98

my mxi-3 card is being detected on windows startup (mxi-3 optimization software is running correctly) but all other pxi cards on my 1000b pxi chassis are not detected.

Anis,
Well, I always prefer to try the simplest things first. In this case, that would be fully powering down the chassis and the computer. Then powering on the chassis first, and a few seconds later, powering on the computer. If this doesn't help, then you would probably want to try any or all of the following troubleshooting steps to try and isolate the problem:
- Try removing all but the mxi-3 and one other card from chassis and then try booting up.
- Try placing the pci mxi-3 card in a different slot in the computer.
- Try uninstalling and reinstalling all the NI software on your computer. (better yet, format and reinstall).
- Try the pci mxi-3 card in a different computer.
- Try a different set of mxi-3 cards (if available)
- Check
device manager to see if there are any errors or warnings.
So those are the things that I would try. If after all that you still have no luck connecting you may have a hardware problem and need to RMA (Return Materials Authorization) your hardware.
Please post back with what you find.
Regards,
Jed R.
Applications Engineer
National Instruments

Can i use PXIe-1073 with an embedded PXIe controller PXIe-8108

I have a PXI express chassis PXIe-1073 with an integrated controller MXI-Express controller PCIe-8361. I now want to use the chassis as a standalone system with an embedded controller.
(a)Can i use PXIe-1073 chassis with PXIe-8108 embedded controller
(b)Can i use a windows based laptop to control the PXIe-1073 via the PCIe-8361 integrated controller.

Hello kanad,
The PXIe-1073 is a MXI-integrate chassis. This means that the MXI card that would normally go into the controller slot (slot 1) is built into the chassis. The PCIe-8361 or Expresscard8360 are placed into the desktop or laptop, respectively, and connect to the chassis. The cards in the PXIe-1073 then appear as if they are part of the desktop of laptop.
Since the controller is built into the chassis, the PXIe-1073 does not have a slot 1. Controllers, such as the 8108 can only be plugged into slot 1. Therefore, the PXIe-1073 can only be controlled by the desktop or laptop MXI link. It cannot run standalone with an embedded controller.
Consider reading page 1-3 and 1-6 in the manual below:
NI PXIe-1073 User Manual and Specifications
Regards,
George T.
Applications Engineering Specialist
National Instruments UK and Ireland

How to determine what card is in what slot of a PXIe-1073 unit programmable

How can i programmable determine what card is in what slot of a PXIe-1073 unit I have a PXI-4063 and a PXI-2503 in a 1073 chassis. I use the DAQmx Device Product Type to to find the 2503 matrix card but it woun't return the 4065 product type.

Hi cjp1,
The KnowledgeBase article Programmtic PXI Slot Detection walks you through the steps to do this. There is also a community example called Read PXI an PXIe Card Serial Numbers Programatically that demonstrates the type of LabVIEW architecture you can use to do it.
You should first ensure that all of your modules can be identified and self-test in MAX.
In case the above hyperlinks don't work, you can copy-paste the addresses below:
http://digital.ni.com/public.nsf/allkb/2342900AED02975A86256BD800764C8B
https://decibel.ni.com/content/docs/DOC-20207
Jeff Munn
Applications Engineer
National Instruments

PXIe 1073 Input Grounding

Hello,
I was wondering how the grounds from the hybrid slots of a PXIe 1073 chassis are connected within the chassis. I'm using 3 PXI 6255 cards, though I don't believe that makes a difference. What I'm looking for is whether they are tied together or not, or similar information. Thank you.
Solved!
Go to Solution.

BVeezy wrote:
UPDATE: I was incorrect. Please refer to the following KB:
http://digital.ni.com/public.nsf/allkb/02A451C0A88A3EAE8625702F0059C98E
Regards,
Brandon V.
Applications Engineer
National Instruments
Yeah, I discovered that not long ago. Every ground on DAQ cards are tied to the chassis ground. It is just that each type of ground (DGND, AGND) have their own planes on the card itself. And chassis ground will be going to Earth Ground, in case that matters to you.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

MXI-3 interface not detected?

Hello to you all,
I was using PXI/PCI 8335 with PXI 1000B chassis. Everytime I run the MXI-3 optimization it says MXI-interface not detected.
I checked the LEDs.
For PXI-8335, the PWR and RX were both solid on, one green and the other orange. For PCI-8335, the PWR and TX (nor sure it's TX or RX, just the one in the same row with PWR) were both solid on, one green and the other orange.
No LINK light.
The whole system was powered in proper sequence and the fibre optic cable was fine.
So there seems to be something wrong with the cards.
I was wondering is there any way to know particularly which one of PXI-8335 and PCI-8335 doesn't work well without replacing them one by one, since I don't have any extras?
Like, does the LED tell other information except they are not linked?
Thank you in advance.
Yaqiong

Yaqiong,
In general you can't differentiate between a bad transmitter on one side or a bad receiver on the other, so it's often hard to tell which side is bad.
In your case, it sounds like one side or the other has a broken transceiver. Power and RX on both sides means the boards aren't communicating at all, meaning a transceiver is bad, or a cable is bad in both directions, or a cable is not plugged in or is plugged in backwards. If you power it up without a cable you should get the same LED behavior -- PWR and RX, the two LEDs next to each other.
If that's the case (same LEDs without a cable as with a cable), you should be able to tell which card is bad if you connect both ends of a half cable to one card (a loopback). On a working card connecting RX to TX will "link" to itself according to the LEDs (at least it did for me on both the PCI and PXI card). On a broken card you'll get something else.
- Robert

Pxie-1073 trigger

Can the PXIe-1073 drive/monitor the PXI trigger lines?

Hello Robert,
I have not seen any software that can monitor and display the information of the PXI Trigger Bus that is in the backplane of the PXI. A workaround is using an external card that can be used to export this lines to the front panel of the PXI. Some of the cards that can help with this are the 6652 or the 6653 timing and synchronization cards.
On the following link you should be able to see an example on how to export a Trigger to a PFI line:
https://decibel.ni.com/content/docs/DOC-2350
Also, I would like to show you some articles that speaks how to manipulate the trigger lines:
Using PXI Timing and Triggering Functionality
http://digital.ni.com/public.nsf/allkb/BD37A128B1DF27F3862570FC0072359D
Routing PXI Trigger Lines Across the Buses of Multisegment PXI Chassis
http://digital.ni.com/public.nsf/allkb/CA9A49FA50393C4186256DC200774E2B
Signal Routing for PXI Devices - NI Digital Waveform Generator/Analyzer Help
http://zone.ni.com/reference/en-XX/help/370520J-01/hsdio/hsignal_routing_pxi/
I really hope this answer properly your question. If not, please let me know so I can see how I can assist you further.
Regards,
Luis C.

IPod Touch, not detected in Windows or iTunes...

First of all, hello to everyone...
i want to say that i read a lot EVERYWHERE about my issue and still i couldnt find a solution...
the problem is easy, i have a 3rd gen ipod touch, OS 4.2.1 now fully working... but, it's not detected in windows or itunes, as simple as that, and as u all have read in lots of other posts...
my ipod is now working because i took it to an apple store and they charged it in a MAC and they had no problem at all. the MAC detected the ipod, with all its content and my ipod's name...
but when i took it home -this has been hapenning since maybe... 5 MONTHS!-, i plug it in my PC and nothing happens...
ok, first of all, my spec... win vista home premium 64 bits, last version of itunes...
i tried ALL the solutions provided in APPLE official support page, and nothing happens... that means:
1- completely uninstall itunes and then reinstalling it... i ALSO FORMATED my entire hard drive twice!!!!
2- tried all USB ports and even an entirely different PC and nothing happened
3- bought 3 different IPOD to USB cables and nothing happened
4- tried setting ipod to restore, that way itunes SOMETIMES detected the ipod but i coulnt restore because of different error codes, so i had to take it several times to apple store to "unblock" it...
the only way it works -detection and charge- is with MAC computers or dock systems such as an iHome my gf has thats the way im charging it now, but otherwise it wont work...
i would really appreciate any help, since idont know what else to do!!
thx in advance!!

HI I was having some other problems getting my itouch to restore because it was not being recognized in itunes and kept erroring out. Now it has finally restored after I updated all kinds of drivers and removed and reinstalled itunes and apple software a million times,(yes this is all after installing itunes 8.1 and paying for an itouch upgrade as well) Now itunes says it cannot do anything with the ipod because it is getting an invalid response from the device. So it won't put anything back on my itouch or even show that I have plugged it in. I emailed tech support, If I find anything out I'll let you know, will you do the same for me?

PXIe-1073 not detected

Similar Messages

Maybe you are looking for