PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

PXIe DAQmx cards not shown in chassis

Solved!
Go to solution

I have a PXIe-1071 chassis, with controller 8822 and 2 pxie-6363 cards in slots 2 and 3. The controller is connected to a PC via Ethernet.

In NI MAX, I can see the chassis and controller in the remote system, and the 2 cards also appear in the list (in "devices and interfaces"), but are not shown as part of the chassis (it says the slots 2 and 3 are empty). See attached picture.

 

All equipment is brand new. I have installed DAQmx drivers with same versions on both PC and remote system (24.8.1). The remote system runs Linux RT 2024 Q4 and labview real time 24.1.

 

What are the steps to have the chassis recognise the cards correctly?

 

Screenshot 2025-08-01 102440.png

0 Kudos
Message 1 of 7
(332 Views)

It looks like you have the correct drivers but something is missing.

Please upload NI MAX Reports for both host PC and remote system here.

-------------------------------------------------------
Applications Engineer | TME Systems
https://tmesystems.net/
-------------------------------------------------------
https://github.com/ZhiYang-Ong
0 Kudos
Message 2 of 7
(304 Views)

Thanks for the reply. Here are the two NI MAX reports. I am not sure what to look for exactly in those.

Download All
0 Kudos
Message 3 of 7
(284 Views)

I have exactly the same problem with my system: an 8844 controller (Windows 11 OS, LabVIEW 2025 Q1) communicating with an 8822 controller (NI Linux RT LabVIEW 2025 Q1). Here is an image:

SiffleurExpress_0-1754994175394.png

 

The problem appeared after an update, which I was initially happy to see because, before that, nearly all of my modules in the 8822 were showing errors in NI MAX — even though they actually worked. I was able to use all of my modules in LabVIEW, including the 6363. Here is what I was getting before when I double-clicked on a module in NI MAX (this is no longer the case, as you can see in the first image):

SiffleurExpress_1-1754994175395.png

 

I tried some simple steps, such as placing the module in another slot, reinstalling DAQmx first for the 8844 and then for the 8822, and disabling the firewall on both systems, but nothing seems to work.

0 Kudos
Message 4 of 7
(253 Views)

I have a similar situation too. Was anyone able to sort it out? 

 

Thanks in advance!

0 Kudos
Message 5 of 7
(181 Views)
Solution
Accepted by topic author BNPL

I opened a ticket with NI, and here’s what I received by email regarding the possible cause and solution : 

"

PCIe Link-Up Failure

  • The PXIe-8822 controller may fail to establish PCIe links with certain modules (like PXIe-6363) if they are placed in chassis slots that connect directly to the controller rather than through a PCIe switch.
  • This is a known issue with PXIe-8822/42/62 controllers and modules using Kintex-7 FPGA PCIe IP (which includes PXIe-6363).

PXIe-8822/42/62 May Be Unable to Link Up with Module with Kintex-7 PCIe Gen2x8/Gen2x4 FPGA IP


Driver or DAQmx Version Mismatch

  • Even if DAQmx is installed on both systems, mismatched or incompatible versions can cause modules to appear but not function correctly.
  • Some users resolved similar issues by reinstalling DAQmx and LabVIEW RT modules, ensuring version alignment across host and target.

 PXIe-6363 Multifunction DAQ Card Not Showing Up in NI-MAX


Recommended Steps:

  • Check Slot Configuration
  • Verify DAQmx Version Compatibility
  • Reset NI MAX Database
    • Sometimes NI MAX gets corrupted. Resetting the database can help: Open NI MAX → Tools → Reset Configuration Data.
  • Reinstall Software Stack
    • If the above steps don’t help, consider:
      Reinstalling LabVIEW 2025 Q1 and DAQmx on both systems.
      Re-uploading RT and FPGA modules to the 8822 via NI MAX.
       


I kindly suggest to take a look at the mentioned articles and troubleshooting steps above to find a solution to the issue. 

"

For me, the solution that worked was to reinstall NI Linux RT and all the software by following method 1 from: 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YHhPCAW&l=fr-FR

Hopefully, the other method works for you, but if it doesn’t, simply reinstalling Linux should do the trick.

Message 6 of 7
(137 Views)

Thanks for the feedback. I could also solve the problem by reinstalling the Linux RT image and all drivers. I am immensely grateful for the help!

0 Kudos
Message 7 of 7
(14 Views)