Diagnostics Custom Device installation problems

[AldhairGarza]

Hi everyone,

in the last couple of days i've tried to install the Veristand Add-on https://github.com/NIVeriStandAdd-Ons/Diagnostics-Custom-Device but I got a couple of problems. I solved the most of them but i got an Error at the very End.

I installed all the dependencies, The NI Veristand Hardware Discovery zip file came without a .vipb file VI Package Build Specification. So I did it by myself with the default options.

I got a reference problem so i switched the Company name to NI, that solved the problem.

The Diagnostics-Custom-Device didn't came with a  .vipb file either, so i made it be myself with the default options.

After approx. 40 Minutes, an error occurs.

Apparently a file is missing and I dont know if i did something wrong in the installation process or where can I download it.

Do you have any idea of what could be wrong? or what could i try? I am using Veristand 2016 and I run the VIPM as administrator in a Windows Administrator Account.

Thanks.

Regards.

[AldhairGarza · Accepted solution]

I got a Solution in case somebody is also new to this Custom Devices on GitHub.

Normally the dependencies got a .vipb file which plays the role of the .exe in any Programm Installer.

And with that the VI Package Manager Pops-up and does almost all the work and at the End you obtain something like this:

One of those dependencies had not any .vipb file so I made it by myself, checking the other .vipb files. Which wasn't that much difference from the default options. And it caused no problems.

When I finished installing all those Dependencies I tried to Install the Diagnostics Custom Device. But the folder didn't have a .vipb file. My Mistake was to create one as I did with the Dependencies. 

The correct way to do it is to search for the lvproj files in the Source Folder, which contain the builds inside and then execute(build) them from there.

They look something like this, and you just need to build them.

And also depending on your Target you need to Build also the Build Specifications from those too. (PXI, CRIO, etc) 

That solved the problem for me.