Archived:Error Deploying NI 951x to CompactRIO in Scan Interface Programming Mode

Updated Nov 26, 2025

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Reported In

Hardware

  • NI-951X
  • cRIO-9074

Software

  • LabVIEW
  • LabVIEW SoftMotion Module
  • LabVIEW FPGA Module

Driver

  • NI-RIO

Issue Details

I receive the following error when deploying a CompactRIO-9074 project using the NI 951x in slots 5-8.  I am using software version 2018.

 

This module cannot be deployed to this slot in Scan Interface programming mode. Only the first 4 slots have the high-speed interface support that this module requires. You can resolve this issue either by relocating the module to a slot supported in Scan Interface programming mode, or by using LabVIEW FPGA programming mode instead.
How can I fix this?

Solution

The NI 951x drive interface modules must be connected to CompactRIO slots that support high-speed interface (HSI).

  • Newer cRIO chassis, such as cRIO-903x/cRIO-904x/cRIO-905x/cRIO-9065, support HSI in all 8 slots.
  • Older model chassis, such as cRIO-902x, cRIO-907x, cRIO-908x, NI 9144, and NI 9148, have HSI support on slots 1 through 4.
    • The NI 951x modules will work in slots 5-8; however, you must use LabVIEW FPGA to compile a custom scan engine bitfile for your CompactRIO. That custom bitfile will provide HSI support for the slots you wish to use with the NI 951x module(s).
    • However, these targets will still be limited to four 951x modules total in the chassis, so this should only be used if the modules must be located in these slots for other design reasons.
    • Follow the steps listed in the How Do I Use the 951x Series Motion Modules in a Hybrid Configuration on my CompactRIO? article to correctly structure the project and create the custom bitfile. Note that unless you are working with modules in FPGA mode, there will be no modules or code running under the FPGA. The resulting blank bitfile should be loaded to the FPGA upon system startup using the initialization process described in Correcting SoftMotion Scan Engine Errors -2147138411 and -77055.

Additional Information

The requirement for older controllers is due to FPGA resource limitations.