Installation problem

[Andre1i]

Hi. When trying to add UPD-Custom-Device to Veristand, an error occurs:

_Error 7 occurred at Open VI Reference in Custom Devices Storage.lvlib:Initialize New Custom Device.vi
Possible reason(s):

LabVIEW: File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.

Nonexistent GPIB interface.

VI Path: C:\Users\Public\Documents\National Instruments\NI VeriStand 2017\Custom Devices\UDP-Custom-Device\Windows\UDP-Custom-Device Configuration.llb\Initialization VI.vi

Built Application or Shared Library (DLL): Make sure all dynamically loaded VIs were properly included in the build specification for the application or shared library.

LabVIEW Real-Time: VIs built into executables cannot be accessed through VI Server calls. Use Source Distributions to dynamically call VIs on Real-Time targets._

I think I am going wrong with the installation process. Is there an instruction on how to properly perform the installation process and add a custom device?

[ryanvallieres]

Hey Andre1i;

Are you using the NI Packages to install the custom device? From the looks of it, you're using Veristand 2017, which corresponds to this release:

https://github.com/NIVeriStandAdd-Ons/UDP-Data-Link-Custom-Device/releases/tag/2017-1.4.5c.060

If you're using this already, can you verify you have files present in the target directory?

[Andre1i]

Hi ryanvallieres. Thanks for the quick response.
Yes I am using Veristand 2017 and 2017 release. But i can't find these files in the release: UDP-Custom-Device Configuration.llb\Initialization VI.vi
Do I need to use NIPackageManager for the Installation?

[ryanvallieres]

Yes, it is suggested that you use the NI Package Manager for installing the UDP Custom Device. The NI package will place the .llb files in the correct locations on disk.

If you cannot use this, rebuilding the custom device from the source code would also install the UDP Custom Device to the target directory.

[Andre1i]

Hello again.
When I try to use NI Package Manager following happens:

I couldn't find a solution to this problem on the internet.
So I would be very grateful if you could explain how to rebuild the custom device from source code.

[ryanvallieres]

Wow, that's an exciting new error that I've never seen before. I'm sorry you're having so much trouble working with the packages.

To rebuild from source, I'd suggest the following:

• Make sure you have all the dependencies required to build the custom device.
• Run the build specification(s) in the project.

The build specifications have post-build actions that should populate the Veristand directory with the build outputs and support for the custom device.

A note on the dependencies, you're going to need quite a few:

• Veristand Development Tools (https://forums.ni.com/t5/NI-VeriStand-Add-Ons-Documents/VeriStand-Development-Tools-VIPC/ta-p/3632685)
• Veristand Data Library (https://github.com/NIVeriStandAdd-Ons/VeriStand-Data-Library)
• a few other OpenG toolkits (see VI Package Manager for these)

[ryanvallieres]

According to one of my colleagues, the Veristand Development Tools have since moved to here:

https://github.com/ni/niveristand-custom-device-development-tools

Good luck!