1062Q not listed under "Identify chassis"

[Efrain_G]

I see Fedor,

In case that you decide to try using Windows 7 again, I would recommend you a couple troubleshooting steps:

First, one of the main reasons why a chassis is not identified in MAX is when the software installation of your drivers does not run properly. Repairing MAX, and DAQmx will take care of this problem.

1. Select Start > Control Panel > Add Remove Programs
2. Select National Instruments Software and click on the Change button.
3. You can then select MAX, Traditional DAQ, and DAQmx by using Ctrl + left mouse click.
4. Next click the Repair button to repair the installations of these products.

If this does not fix the problem, I recommend you to download the latest version of the NI PXI Platform services which is 2.5.6. You will find it on this link:
http://joule.ni.com/nidu/cds/view/p/id/2084/lang/en

[Valkrie]

I too am having a very similar problem, but do not have the luxury of falling back to another PC.

In trying to configure our new PXIe in DAQmx, I can select the PXIe System (8108) but cannot identify our PXIe Chassis (1065); it simply is not present in the drop-down menu and cannot seemingly be loaded (all attempts to select "National Instruments PXIe-1065.ini" file from my C:\, from NI.com, and from the CD that came with our HW all result in a "File was not a valid chassis.ini file. Browse for another chassis.ini file?" error message). 

I'm running LV2009SP1 on an XP machine with DAQmx 9.2.2 and PXI Platform Services 2.5.6, so this PXI and chassis should be supported.

I've tried repairing both the DAQmx and PXI Platform installations to no avail. I've also tried to run the corruption removal tool suggested in the post above, but cannot replace my config3.mxs file as it claims to be in use (despite reboots, removal of internet access, and task manager investigations, I cannot figure out what is using this file). I have attached a copy of this file, though I don't know that it is corrupted (or how to tell).

Any help in this matter would be most appreciated.

Thanks,

Val

[Fedor]

Val,

After talking back and forth with NI, it is possible that my particular motherboard is not compatible with MXI card in some way - the PC does not see PXI cards neither in windows device manager nor even during BIOS boot. 

Does your device manager see any of the PXI cards?

[Efrain_G]

Hi Valkire,

I am sorry to hear that you are experiencing this problem. I believe your issue might be slightly different form Fedor's because apparenlty you are trying to control your PXIe 1065 using the PXIe 8108 controller. Is that correct? It turns out that Fedor is using an MXI Express bridge to control his PXI chassis with a PC.

Fedor,

After doing some further reseach I found that there might me a couple reasons why your motherboard was not compatible with the MXI-Express BIOS compatibility software. These are the presence of multiple PCI/PCI Express root bus devices, which adds complexity to the system. And also that there is a maximum limit on the bus number range set by the BIOS, which limits the amount of hardware that can communicate through the PCI Express bus.

There is in fact a utility that you can execute on your system that can be used to analyze the system's PCI/PCI Express root bus devices. You will find more information about this here.

[Valkrie]

Correct, I have an 8108 controller. I now understand why I couldn't initialize in DAQmx's My Systems, though I was trying to do so because I could not expand any of the items (Data/Devices/Scales/SW) under the PXI in DAQmx's Remote Systems - a separate issue of PXI connectivity and one which I now have my local NI rep helping to diagnose and solve.

Thank you both for your responsiveness.

-Val