search

ni / niveristand-fpga-addon-custom-device

VeriStand FPGA Addon custom device
MIT License
7 stars 16 forks source link

Build Error for FPGAAddon CD #169

Closed vskconsultants closed 1 year ago

vskconsultants commented 1 year ago

Environment used : LabVIEW 2020 , Veristand 2020 R6 32 bit Operating System : Windows 10 64 Bit Release version : FPGA Addon Custom Device 20.6.0
https://github.com/ni/niveristand-fpga-addon-custom-device/releases/tag/20.6.0 Dependencies Installed : As mentioned for release 20.6

Issue :

I am able to build the Windows ( Configuration/Engine Release) and Liunx x64 ( Engine Release). Once I try to deploy system definition file with no other custom devices or other modules ( simple system def file), gets an error "VI Broken RT Driver.vi" as below :

_**Deployment Error
LabVIEW: (Hex 0x3EB) 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.
=========================
NI VeriStand:  Open VI Reference in Custom Devices Storage.lvlib:Open Device Reference (HW Interface).vi->Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi->NI VeriStand Engine.lvlib:Initialize Inline Custom Devices.vi->NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi->NI VeriStand Engine.lvlib:VeriStand Engine.vi->NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi<APPEND>
/c/ni-rt/VeriStand/Custom Devices/FPGA Addon/FPGA Addon Engine Linux64.llb/RT Driver VI.vi**_

So I changed the settings in the build specification under Source File Settings and uncheck "remove front panel or remove block diagram" and rebuilt the custom device and try to redeploys and get following error.

image

I am using LabVIEW 2020 32 bit, Veristand 2020 R6, so I don't see any issue with different OS or 32/64 bit difference which can cause this issue.

Please suggest.

buckd commented 1 year ago

@vskconsultants Is there a reason you need to rebuild the libraries instead of using those from the latest release?

VeriStand custom device builds are a little tricky and often require some additional settings on your build machine outside of just what is in the build specs. Usually, issues like this arise from not having some LabVIEW.ini keys set. The most common one is _NI_AppBuilder_SDistExcludeEditTime=True. If you are not making any source changes, I would recommend you use the release from this repo. If you do need to build your own version, try setting that INI key, restarting LabVIEW, and then build.

vskconsultants commented 1 year ago

@buckd Issue resolved, thank you very much