1062Q not listed under "Identify chassis"

[Fedor]

I was trying to upgrade my PXI setup from WinXP to Win7-64bit. Everything works fine with XP machine, but not with Win7 one.

The 1062Q chassis is controlled over MXI cable by external PC. I installed all the relevant drivers, and I identified PXI controller as "external PC" in MAX, but when I try to "identify" the chassis, there's no 1062Q option in the longish list. The 2 DAQ modules I have in the chassis, PXI-6133 and PXI-5105, show up in MAX, but remain "grayed" and can't be accessed.

What I could be doing wrong?

[Efrain_G]

Do you have PXI Platform Services Installed? Which version?

[Fedor]

Yes, I've installed v. 2.5.4 from this link: http://joule.ni.com/nidu/cds/view/p/id/1632/lang/en

[Efrain_G]

I see. Your version of Platform Servces does support Windows 7 and your 1062Q chassis. You might find this Troubleshooting Guide in our website useful:

http://digital.ni.com/public.nsf/websearch/484f81e6570ad803862569ed007aaa41

[Fedor]

The problem is that when I bring up "identify chassis" pop-up menu, there's a list of about a dozen NI chassis models to choose from, but no 1062Q.

[Efrain_G]

Have you seen any abnormal behavior on your chassis, like a red LED trun on? Is this a MXI Express bridge? Can you see your bridge connection on the Device Manager?

[Fedor]

It is a MXI express bridge, the link and power lights on the pxie-8370 are both green.

[Fedor]

also, when I try to open "C:\Program Files (x86)\National Instruments\PXI\Hardware Descriptions\Chassis\National Instruments PXIe-1062.ini" in MAX under "Identify chassis", I get a message "File was not a valid chassis.ini file. Browse for another chassis.ini file",

which sounds kind of bogus error.

[Efrain_G]

That is interesting. This could be an actual problem with MAX. Let's try to fix any MAX database corruption errors. Please take a look at this Knowledge Base:

What is the Process For Removing MAX Database Corruption?

[Fedor]

I was not able to resolve it in Windows 7 64 bit after all. Due to pressing project needs to  have the system up and running, I rolled back to WinXP 32-bit, where it found all the hardware on it's own.