06-06-2023 01:44 AM
Hi,
I downloaded a VI file and tried to run it . When I opened the file, the labview sent me a warning list showing 'Dependency loaded from new path'. The detailed information is shown below.
\Users\daigujilab\Downloads\6517B_Current_measurement_VI_cds.vi (6517B_Current_measurement_VI_cds.vi)
- The VI expected to be at "C:\~~wafer_mapping_automation~~\subvis\keithley\keithley_6517\Keithley 6517\Public\Initialize.vi" was loaded from "C:\Program Files\National Instruments\LabVIEW 2021\instr.lib\Keithley 6517\Public\Initialize.vi".
- The VI expected to be at "C:\~~wafer_mapping_automation~~\subvis\keithley\keithley_6517\Keithley 6517\Public\Configure\Measurement\Configure Measurement Function.vi" was loaded from "C:\Program Files\National Instruments\LabVIEW 2021\instr.lib\Keithley 6517\Public\Configure\Measurement\Configure Measurement Function.vi".
What shoud I do to fix the problem? Do I need to change the location of my VI file?
Thanks!
06-06-2023 02:56 AM
The keithley library is loaded from a different location ("C:\~~wafer_mapping_automation~~\subvis\", not "C:\Program Files\National Instruments\LabVIEW 2021\instr.lib\".
You should decide if you want the library to be in instr.lib, or in a local directory. It's probably best to make it the same everywhere you're working on the project, or you'll be getting the warning each time the location switches.
A save all should store the new location and you shouldn't be getting the warning (unless the location changes again.
If you do want to store the library locally, you probably want to store it relative to the project, and put it in SCC. If you use an absolute path, it should be the same, or you'll get the warnings (there's not much special about instr.lib, it's just a defined absolute path).