Error -732156 When Using Scan Engine and EtherCAT Custom Device

Issue Details

I am trying to configure an NI-9145 or NI-9147 chassis using the Scan Engine and EtherCAT custom device in VeriStand 2024. When attempting to auto-detect modules in the custom device, I see the following error:

Error -732156 occurred at SEECD System Explorer.lvlib:Generate Application Call Error.vi

Possible reason(s):

Unable to launch process to perform hardware configuration.

Complete call chain:
SEECD System Explorer.lvlib:Generate Application Call Error.vi
SEECD System Explorer.lvlib:Call Get HW Config.vi
SEECD System Explorer.lvlib:Main - Auto Detect Modules.vi

The same error with the call chain shown below can also be observed when trying to download an FPGA bitfile into the EtherCAT chassis. 

Complete call chain:
SEECD System Explorer.lvlib:Generate Application Call Error.vi
SEECD System Explorer.lvlib:Call Get HW Config.vi
SEECD System Explorer.lvlib:Host - Find Path.vi
SEECD System Explorer.lvlib:Host - Find Slave Path.vi
SEECD System Explorer.lvlib:FPGA - Download (ECAT).vi
SEECD System Explorer.lvlib:FPGA - Select Bitfile (ECAT).vi

I have tried repairing all NI software components along with reinstalling software, but with no success. How can I fix this issue? 

Solution

This issue is caused by a bug affecting the Scan Engine and EtherCAT Custom Device 24.x when used with VeriStand 2024. The error occurs due to a missing Registry Key in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\National Instruments\LabVIEW Run-Time\22.0 that contains a Path variable providing the location for nNIBlueBus_nCrioFixed_nRefnum.dll.

This has been resolved in the Scan Engine and EtherCAT Custom Device 25.0.1 (2025 Q1 Patch). To upgrade the version of this custom device please note the following:

• Uninstall the custom device from NIPM first, otherwise you will get a message saying "A newer version of the package or one of its dependencies is already installed. No operation will be performed". You need to ensure to uncheck the "Products Only" box to find it in NIPM search.
• The patch package version shows the wrong version number, it should be 25.0.1, but it shows as 25.0.0.2. This seems to be safe to ignore.

If using earlier versions of the Custom Device, follow these steps to solve the issue:

1. Open the Registry Editor by typing regedit in the Windows search bar and pressing Enter.
2. Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\National Instruments\LabVIEW Run-Time\22.0.
3. Right-click on the 22.0 folder and select New > String Value.
4. Name the new string value Path.
5. Double-click on the Path string value and enter C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2022\ as the value data.
6. Click OK, verify that the key and value data appear as shown in the image below, then close the Registry Editor.

Additional Information

The error might also be thrown if you are trying to use the Auto-Detect function on an empty chassis. Make sure the chassis has modules properly inserted, refresh the VeriStand environment, and try auto-detecting the modules again.