08-14-2025 07:52 PM
Hi all,
I am part of a research team working with radar waveform simulation using the USRP-2944 / X310 software defined radio. We connect the SDR to a host PC via PCIe, and we use LabView 2018 (x64) to write to the FPGA and read the data. Until recently, this has worked well with no issues; we built the code around the Simple Tx/Rx Streaming example project, so it was straightforward to get everything running.
However, at a time during which we made NO changes to the VIs or the LabView project, the connection stopped working for no discernible reason. Specifically, the LabView program hangs when trying to run the simulation. It does not fully "freeze" in the sense that Windows marks it as "Not Responding", but the pause and abort buttons cannot be interacted with, and LabView must be closed via task manager. I did some investigating using breakpoints and probes, and identified the culprit as a VI very early in the execution order that attempts to establish connection and load the bitfile onto the device (specifically getDeviceInfoFromScs.vi). This VI is not customized in any way, and is one of the VIs included in the original Simple Tx/Rx Streaming example.
Fast forward a week, and after digging through this roadblock with what feels knowledge-wise like a plastic spork, I guess my main goal in writing this post is to get some advice on where else to even look. I am relatively new to LabView and could use the guidance, as I am more of a software person still learning the ropes of hardware integration. Thank you for reading!
Troubleshooting attempts thus far:
Other potentially helpful clues I've stumbled upon:
Solved! Go to Solution.
08-17-2025 07:28 PM
Hi,
You can install a different NI-USRP driver that supports LabVIEW 2018.
NI-USRP driver 2018, 2019, 2020, 2021...
09-05-2025 03:32 PM
Hi again,
I resolved this issue! Dropping by to post further symptoms I encountered, along with what ended up fixing everything.
Further symptoms:
Solution:
It turns out the issue was with the NI MAX utility: either a file was corrupted or it was no longer compatible with some update that my IT department pushed, I'm still not sure. Regardless, I first wanted to see if the issue could be fixed without requiring a fresh uninstall/install of LabView, so I was aiming to use the "Repair" capabilities of the NI Package Manager. However, NI MAX could not be repaired with the package manager while the Configuration Manager was running. My solution got everything fixed while working around these constraints.
Here are the steps I followed (Windows 10):
This fixed NI MAX, but now my USRP was not being enumerated properly, likely due to the Configuration Settings being changed/repaired. So I had to remind Windows where to find the RIO drivers for it using the Device Manager:
After one final reboot, it enumerated properly and everything is back to normal!
Good luck and happy LabVIEWing? USRP-ing? National Instrumenting?
Happy verbing.