Failed Reset and Self-Test using a PXI-6683H on NI Hardware Configuration Utility

Updated Jun 1, 2026

Reported In

Hardware

  • PXI-6683H
  • PXIe-8398

Operating System

  • Linux

Issue Details

I am using a PXI-6683H on a Red Hat Enterprise Linux 9.4 system in a PXIe-1095 chassis with a PCIe/PXIe-8398 remote controller. The device is detected in NI Hardware Configuration Utility; however, I encounter errors when running Self-Test, Reset operations, or when attempting to use the device in LabVIEW.

When attempting a Reset, the following error is returned:

There was a problem resetting the device.

Miscellaneous operation failure.

misc error.png 

 

When attempting a Self-Test, the following error is returned:

The self-test failed.

The trigger has not occurred for the requested buffer, so data cannot be fetched relative to the trigger.

trigger error.png

 

When I attempt to use the module in LabVIEW, the example returns the following error:

Error -107411864 occurred at niSync Initialize (Default).vi

Possible reason(s):

Driver Status: (Hex 0xBFFA4016) The specified device was not found.

LV error.jpg

Solution

This issue occurs when the PXI-6683H is incorrectly associated with the NI-QPXI expert instead of NI-Sync, which is typically caused by Input–Output Memory Management Unit (IOMMU) being enabled on the system. This prevents proper communication between the driver and the hardware. To resolve this issue, verify the device association and disable IOMMU if necessary.
 
  1. Verify the primary expert assigned to the device:
    1. Open a terminal.
    2. Run the command: lsni -v
    3.  Locate the PXI-6683H in the output.
    4. Confirm that the Primary Expert is set to NI-Sync. If the Primary Expert is listed as NI-QPXI, proceed to the next step.
       QPXI.jpg
  2. Disable IOMMU in the system configuration:
    1. To disable the IOMMU in RHEL, follow the instructions at How Do I Disable IOMMU on RHEL 10? - NI.
    2. When modifying the kernel parameters, use iommu=off instead of passthrough (pt).


 

 

Additional Information

NI typically recommends setting iommu=pt for compatibility with PXIe/PCIe devices. However, for PXI/PCI devices such as the PXI-6683H, IOMMU must be completely disabled using iommu=off.
 
Newer Linux kernels enforce stricter PCI handling, which can prevent proper device enumeration when IOMMU is enabled. This may cause the device to be incorrectly associated with the NI-QPXI expert instead of NI-Sync. Disabling IOMMU ensures proper driver association and communication with the hardware. 
 
If you are using an MXI connection (such as PCIe/PXIe-8398), system topology and PCIe slot configuration can also affect device detection. In some cases, improper enumeration over MXI may lead to similar symptoms. Verifying the PCIe slot placement or moving the MXI card to a different slot may help resolve detection issues. For additional troubleshooting steps, refer to the MXI-Express Compatibility and Connectivity Troubleshooting Guide - NI 

Related Links

 

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.