Sub Vis are not executable! Dependendcy is broken?

[TEgerland]

Here's a brief text in English based on the issue you're experiencing with LabVIEW:

---

I am encountering a problem with a LabVIEW program that is designed to conduct measurements. This program, comprised of numerous sub VIs, has previously worked flawlessly on a laptop. However, upon transferring it to a desktop computer, I am encountering an error message: "Dependency loaded from new path."

Upon launching the program, I am prompted to manually locate and implement certain sub VIs from the directory. Strangely, this prompt only appears for two sub VIs, despite there being more than two in the directory. The sub VIs that are not prompted are the ones causing errors. Specifically, the error message reads: "Root Cause: Dependency is broken" (see attached image).

Additionally, there is an error indicating that the VIs cannot access the referenced item. Furthermore, I am receiving notifications that the sub VI is not executable (see attached image).

I have attached the somewhat chaotic code for reference. Any assistance with resolving these issues would be greatly appreciated.

Best regards,

Tobias

Due to file limitations of 10Mb I loaded the file to gdrive. I cant compress this file under 16 MB. So feel free to have a look at this file:

https://drive.google.com/file/d/1ZNv562MXe6umWJ2ZlbPSb5giQc2GoLH6/view?usp=sharing

[wiebe@CARYA]

Agilent ENA Series.lvlib:Write.vi is a private VI. You can't use it directly in your code. Only VIs in Agilent ENA Series.lvlib can use it.

You can

1 Either modify (a copy of) the library, by

  1.1 making the VI public or by

  1.2 adding your VIs in the library or

2 Only use VIs in the library

3 Copy the contents of Write.vi (although it probably uses a reference that's also protected or private).