Can not run Inertiaproject in VeriStand 2017

[larboc]

Will Inertia work on labview/veristand 2017? I am running into this error when trying to go through the "moment of inertia" Youtube video.:

"

Error 1126 occurred at Open VI Reference in Custom Devices Storage.lvlib:Initialize New Custom Device.vi

Possible reason(s):

LabVIEW:  VI version is too early to convert to the current LabVIEW version.

An error occurred loading VI 'Inertia RT Custom Device.lvlib:Inertia RT Initialization VI.vi'.

LabVIEW load error code 10: VI version (16.0) is too old to convert to the current LabVIEW version (17.0).

VI Path: C:\Users\Public\Documents\National Instruments\NI VeriStand 2017\Custom Devices\WTI\Inertia RT\Inertia RT Configuration.llb\Inertia RT Initialization VI.vi"

I tried opening that .vi by itself and get a similar error.

[larboc]

I installed LV2016 and VS2016 and am now getting this error when I try to add a custom device, in the same spot on the youtube tutorial as last time.

Error 1003 occurred at Open VI Reference in Custom Devices Storage.lvlib:Initialize New Custom Device.vi

Possible reason(s):

LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it.

VI Path: C:\Users\Public\Documents\National Instruments\NI VeriStand 2016\Custom Devices\WTI\Inertia RT\Inertia RT Configuration.llb\Inertia RT Initialization VI.vi

[RandallCrandall'sCandleHandle]

Hey larboc,

Can you open the VI in LabVIEW 2016 without error? I'd like to see what happens if you try that. Also, what software do you have installed on your computer? It's possible that this error is showing up because you're missing something like LabVIEW RT, causing the VI to be broken.

Cheers,

Ryan C.

[larboc]

I never got anywhere with this so I uninstalled all NI software, and then installed:

Labview 2016

Real time 2016

Veristand 2016

DaqMX2016

Inertia 16

I get a new error now when trying to add "inertia RT" under custom devices in system explorer.

Error 1003 occurred at Open VI Reference in Custom Devices Storage.lvlib:Initialize New Custom Device.vi

Possible reason(s):

LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it.

VI Path: C:\Users\Public\Documents\National Instruments\NI VeriStand 2016\Custom Devices\WTI\Inertia RT\Inertia RT Configuration.llb\Inertia RT Initialization VI.vi

I've never gotten inertia to run past this point, I've been limping along with a homemade vi for the past 2+years I've owned an inertia license.

[larboc]

I'm suspicious that it has to do with all my Labview software being installed on the 😧 drive, but inertia installs to the C: drive (No option to select installation directory with Inertia).

I copied the vi.lib file from the installation on the c drive to the d drive and then opened the suggested .vi's from the errors. As they opened with missing file errors I directed them to the files in the new location. Seems to be able to open now and get past where I was hanging up in the example.

[larboc]

Next hangup, I've added a single AI channel in from the PXI chassis to a copy of the example project (which worked before I added the channel) and I am getting this error when I try to deploy.

Running Project C:\Users\Public\Documents\National Instruments\NI VeriStand 2016\Projects\Inertia 2016 Example\Inertia 2016 Example.nivsproj

• Start Date: 1/23/2018 10:15 PM
• Loading System Definition file: C:\Users\Public\Documents\National Instruments\NI VeriStand 2016\Projects\Inertia 2016 Example\Inertia 2016 Example3.nivssdf
• Initializing TCP subsystem...
• Starting TCP Loops...
• Stopping TCP loops.
Waiting for TCP loops to shut down...
• TCP loops shut down successfully.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The VeriStand Gateway encountered an error while deploying the System Definition file.

Details:
Error -307660 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi

Possible reason(s):

NI VeriStand: Timeout occurred while deploying a new system definition file.
=========================
NI VeriStand: NI VeriStand Gateway.lvlib:VeriStand Server Wrapper.vi >> NI VeriStand Server.lvlib:NI VeriStand Server.vi

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
• Unloading System Definition file...

I'm not sure what to check.

[larboc]

Figured that out, I went back and installed all available software in MAX. Onto the next hickup...

[larboc]

All the DAQ cards except for one added successfully to veristand. The PXIe-8430/8 card did not show up however, and it looks like it's not supported by DAQmx? I need to use 3 channels of RS232 to control some relay boards in existing hardware (worked with the homespun system before, and still shows up in MAX).

Any suggestions on how to use the 8430 card with veristand?

[RandallCrandall'sCandleHandle]

Hey larboc,

You are correct, the 8430 card is not supported by DAQmx. We don't have built-in support for RS232 in VeriStand, but I recommend taking a look at the Instrument Custom Device that is posted on GitHub:

https://github.com/NIVeriStandAdd-Ons/Instrument-Custom-Device

This adds support for NI-VISA, which is our driver that supports RS232 and the 8430.

Cheers,

Ryan C.

[larboc]

Thanks, I've been working through that this morning, I'm struggling a little trying to figure out how to build it and get it to work in veristand without a bunch of errors. It calls for a bunch of software to be installed in the readme and I think I have them all added now. 

I am currently trying to work through this error, I can't find this file. I'm assuming I need to build something to generate it.

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.

VI Path: C:\Users\Public\Documents\National Instruments\NI VeriStand 2016\Custom Devices\Instrument Addon\Windows\Instrument Addon Configuration.llb\Initialization VI.vi