PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

PXIe-8130 in PXIe-1065 Chassis

Hello,

 

I have a PXIe-8130 controller in a PXIe-1065 chassis.  MAX does not recognize neither the controller nor the chassis.  When I try to id the controller, I cannot find the correct .ini file.  I manually found the .ini files here:

 

C:\Program Files (x86)\National Instruments\PXI\PXIe System Modules

 C:\Program Files (x86)\National Instruments\PXI\Hardware Descriptions\Chassis

 

on the system, but MAX does not recognize these files even when I rename the controller file as "cntrller.ini"

 

I've updated MAX to V4.8 and DAQmx to V9.3.  Interestingly, MAX sees the PXI-5412 Fgen card and the three PXIe-6368 cards in the chassis.

 

Has anyone seen this sort of thing before?

 

Thanks

0 Kudos
Message 1 of 15
(6,565 Views)

Hey Munk,

 

First, you should change that filename back to the way it was.  Next, is there an unidentified PXI system in your "Devices and Interfaces" (see image below)?  If so, you can right click and identify as the controller you have (8130).  MAX won't recognize the controller as a typical card, so this would be the way to identify it.

 

Regards,

Jake

Regards,
Jake G.
National Instruments
Applications Engineer
0 Kudos
Message 2 of 15
(6,560 Views)
Hello Jake, Actually, I made a copy of the "National Instruments NI PXIe-8130.ini" file and saved it in another location. I did the right-click on the "PXI System (Unidentified)" entry, but I do not see the 8130 controller listed. I went down to "Other" and navigated to the "National Instruments NI PXIe-8130.ini" and also the renamed "cntrller.ini" file but MAX tells me that this is not a valid init file. This 1065 chassis has been loaned to us by our NI rep, and the original plan was to install a 8360 MXI card and connect the chassis to a PC. I was trying to run the 8130 in the chassis to do some development offline since the original PC intended for this task is not available. In the past, I have never had an issue with MAX correctly discovering controller/chassis/modules. Could we have a hardware fault on the chassis?
0 Kudos
Message 3 of 15
(6,555 Views)

Hi,

 

At the moment I am experiencing the same problem but for a NI PXI-1042 chassis and a NI PXI-8361 controller.

 

I also manually looked for the ini files. But I needed to put the marker on show all files. Then the ini files became visible.

 

Now, when I choose my 8361 controller it says it is already in the system , so it asks if i want to overwrite it. Then I click yes but an error shows up.

 

Properly the controller files are corrupted now but I have no idea how to change that.

 

Grts

Stieve

0 Kudos
Message 4 of 15
(6,547 Views)

Hi,

 

Today I phoned with an support engineer and he mailed me the following link :

 

http://joule.ni.com/nidu/cds/view/p/id/2071/lang/en

 

This is a program that makes your BIOS able to talk to a pci card. But BE WARNED it can make things worse if used incorrectly.

 

So read the manual very carefully :

 

http://ftp.ni.com/support/softlib/PXI/MXIe%20Compatibility%20Software/1.3/readme.html

 

It fixed my problem, but I am not sure it will help you.

 

Kind regards

Stieve

0 Kudos
Message 5 of 15
(6,515 Views)

Thanks Commodore!

 

Also, the problem described in this KnowledgeBase does not directly apply, but the steps outlined here may help. You can find the KB in the link below. By deleting the data folder, it will force MAX to relink everything in there including the configuration files.
Chassis Not Described in pxisys.ini File
http://digital.ni.com/public.nsf/allkb/C4DA5EEE704F30138625752F0079883B?OpenDocument

If this step does not yield any results, then we will need to either repair or remove/reinstall PXI Platform Services. Here is a link to the location on ni.com so that you will not have to worry about any network mapping.
PXI Platform Services 2.5.1
http://joule.ni.com/nidu/cds/view/p/id/1381/lang/en

Beyond that, you may want to try reimaging your system.

 

Regards,

Jake

Regards,
Jake G.
National Instruments
Applications Engineer
0 Kudos
Message 6 of 15
(6,512 Views)
Hello, Thank you so much Commodore and Jake! I really appreciate the valuable help on this forum. I checked that I had PXI Platform Servies 2.5.6 installed in the system, and it is there. An possibly important point that I didn't mention earlier is that the PXIe-8130 controller used to be in a PXIe-1075 chassis. That chassis came down with a serious case of "power-supply-itis" and is back at NI for repair. We received the PXIe-1065 chassis as a loaner until the 1075 chassis is repaired/replaced. I just swapped the controller and modules from one chassis to the other. I will try the steps you suggested Jake and let you know what I find. Thanks again, Tad
0 Kudos
Message 7 of 15
(6,507 Views)

I seem to have bumped into another problem here.

 

I am getting this error :This chassis has been identified but is not described in the pxisys.ini for this system.

This chassis was not present in the system during PCI enumeration.

 

In other words in don't have the driver for the chassis. Reason is because i bought the chassis on e-bay.

 

Is there any place i can find the PXI-1042 chassis drivers ?

 

Grts

Stieve

0 Kudos
Message 8 of 15
(6,503 Views)

Nevermind my last post, i already solved it.

 

It is very important to power the chassis before the PC. And I powered the PC first and then the chassis.

 

So be careful with that.

 

Grts

Stieve

0 Kudos
Message 9 of 15
(6,501 Views)
Hello, I did not mention that I'm running Windows 7 64 on the 8130 controller, so I don't think that PXI Platform Services 2.5.1 works. I have version 2.5.6 installed. I tried the steps to reset MAX , pxisys.ini and pxiesys.ini files but MAX still doesn't recognize the chassis or controller. I started trying to reinstall the PXI platform services, but that may require re-installation of other software components. I have some tests I MUST try to do before I re-image the system. Thanks, Tad
0 Kudos
Message 10 of 15
(6,494 Views)