What drivers need to be installed on a target in order to run an executable that uses USRP VIs?

[FlamingYawn]

I'm having trouble running a build executable using the USRP VIs on a target machine.  What drivers do I need to install to get this to work?

[CoffeeBreak]

Hi Robert,

When you say that you are having trouble running an executable with NI USRP VIs, what specific symptoms are you seeing when trying to run the executable?

What USRP model are you using?

In order to use the USRP Vis, I believe you will need the NI-USRP 1.2 driver and the LabVIEW Run-Time Engine that matches the version of the LabVIEW development environment used to build the executable.

It should be noted that the NI-USRP driver does not show up in NI Measurement and Automation Explorer (MAX), but you can double check if it is installed by going to Control Panel >> Programs and Features >> National Instruments Software on the target machine. 

[FlamingYawn]

Thanks for your help, Sam.

My VIs aren't runnable because they are missing dependencies, including usrp.dll.

I'm using USRP-2930 with LabVIEW 2013 and TestStand 2013.

So the NI-USRP 1.2 driver needs to be installed on the target machine as a separate install, even though it appears to be a development install?

Whenever I deploy code to a target machine, I build the executable (which includes any code dependencies, including certain dlls, which it puts in the "Data" directory by default) and then build an installer, which optionally includes all the necessary drivers and LabVIEW Run-time Engine.  I've never run into anything that falls outside this process, like it appears the NI-USRP driver does.  It doesn't seem to get pulled into the executable as a dependency and doesn't show up in the list of includable installers when building an installer in LabVIEW.

I'll try out the NI-USRP 1.2 driver install on the target machine and see if that fixes the problem.

This situation creates a further problem when trying to create a deployment install from TestStand.  Since the dependencies aren't automatically pulled in, TestStand detects that the VIs are now broken and aborts the install.  How do I get around that problem?

Thanks again,

Robert

[CoffeeBreak]

Of course, I am happy to help Robert.

I have searched through our internal resources and it is known that the NI-USRP driver cannot be included in the additional installers tab of the LabVIEW Application Builder. Therefore the NI-USRP driver will need to be installed on the target machine. From past service requests, the most common method to install the NI-USRP driver has been to create a batch file for the driver.

As far as the NI TestStand troubles that you are encountering, I think if you follow this troubleshooting step we can provide a proper work-around to adding the proper dependencies for NI TestStand. Navigate to: NI TestStand Deployment Utility >> System Source Tab >> Check “From Directory” box >> Include the folder C:\Program Files (x86)\National Instruments\NI-USRP\lib >> Check “Include Subdirectories” box. Let me know this helps resolve the problem.

I also wanted to make sure to let you know that NI-USRP 1.2 is the only USRP driver version that supports the USRP-2930 so please make sure you use this version.