Error 7 When Building Executable With the ADCS Toolkit in LabVIEW

Updated Dec 18, 2023

Reported In

Software

  • LabVIEW
  • Automotive Diagnostic Command Set Toolkit

Issue Details

I'm trying to build a LabVIEW executable which uses functions from the Automotive Diagnostic Command Set Toolkit (ADCS), my VIs runs fine in the LabVIEW Development Environment, but I get the following build error:
 
LabVIEW cannot find a file that is a dependency of a Startup, Exported, or Always Included VI.

File Not Found: C:\<Program Files>\National Instruments\<LabVIEW version>\vi.lib\Automotive Diagnostic Command Set\Diagnostic Transport.llb\ISOTP Send CFs.vi

The missing file might be referenced by one of the libraries included in the build or by the file - VI_Name.vi. To fix this issue:

- Open all Startup, Exported, or Always Included VIs, recompile them (CTRL+SHIFT Click the Run arrow) and save them to update their dependencies.
- Open all libraries included in the build and verify the existence and locations of referenced files. Also, try building with the additional exclusion option, "Remove unused members of project libraries", checked.

Error 7 occurred at AB_Engine_HandleLinkErrors.vi -> AB_Engine_Update_Source_from_Linker.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.
 
image.png

Solution

This issue has been reported in LabVIEW 2022 or newer. The Application Builder will fail to link the correct files to properly create the executable. You can use the following workaround to avoid the issue:
  1. Get a copy of the Automotive Diagnostic Command Set folder:
    • Locate the folder to copy in this location: C:\Program Files\NI\LVAddons\adcs\1\vi.lib
    • As another option if you have a previous LabVIEW version installed (i.e, LabVIEW 2021, 2020...) you can find the folder to copy at C:\<Program Files>\National Instruments\<LabVIEW version>\vi.lib. Where <Program Files> will be Program Files if you are using the 64-bit version of LabVIEW, or Program Files (x86) for the 32-bit version, and replace <LabVIEW version> with the corresponding LabVIEW version.
    • You can also download the file attached in this article, Automotive Diagnostic Command Set.zip, and decompress it in your computer.
  2. Take the copy of the Automotive Diagnostic Command Set folder and paste it in the target's version vi.lib folder, for LabVIEW 2022 the path would be: C:\<Program Files>\National Instruments\LabVIEW 2022\vi.lib
  3. Make sure to close all LabVIEW windows, except the project file. This is to avoid getting an error stating that an item is already in memory.
  4. Retry building the executable.

Additional Information

Starting in 2022 Q3, NI released select drivers and toolkits that function with a minimum LabVIEW version (e.g. LabVIEW 2022Q3) and all future versions of LabVIEW. This included changing the installation of support files to a version-independent LabVIEW directory, the LVAddons directory. For more information refer to:
Extending Compatibility Between LabVIEW and NI Drivers with Addon Support.

However, this error is a known issue in LabVIEW 2023 Q3.

Attachments

Automotive Diagnostic Command Set.zip

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.