LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

building the application, the vi calling std deviation and variance shows a broken arrow.

Solved!
Go to solution

In Labview 2017 running in windows 10, building the application, a .vi which calls std deviation and variance shows a broken arrow.

0 Kudos
Message 1 of 18
(3,440 Views)

Can it find lvanlys.dll?

 

0 Kudos
Message 2 of 18
(3,410 Views)

It would help of you could include significantly more detail. It's not really clear what you did.

 

My best guess is that you did not build any installer and copied the exe somewhere else. Typically, the builder will also create a "data" folder in the same place as the exe. Keep that folder next to the exe and see if it help.

0 Kudos
Message 3 of 18
(3,400 Views)

I made a project and then I built the relative application. While in the project all is working ok, when I produce the application (running on the same PC) the subvi STD Deviation & Variance (taken from functions : mathematics\probability & statistics) doesn't work (Arrow Broken). If I replace the vi with its contents (LabView 2017 allows this operation) then all is OK.

0 Kudos
Message 4 of 18
(3,362 Views)

Compress the folder containing your Project and attach the resulting .zip file.  You did something wrong.  We can "guess" what it was, or you can provide us data and we can "figure out" what it was and tell you, without guessing.

 

Bob Schor

0 Kudos
Message 5 of 18
(3,358 Views)

I think that the problem arises because the vi is called as a subvi of a test vi loaded as in the following:

C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\Utility\victl.llb\Preload Instrument.vi

C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\Utility\victl.llb\Run Instrument.vi

what do you think? can it be?

 

 

 

 

0 Kudos
Message 6 of 18
(3,353 Views)

Wow, these are some old tools (~1998 according to the revision history, full of stacked sequences and sequence locals. Yuukkk!). Why do you think you need any of this? Just curious.

 

Since you are running VIs by reference, can we assume that you correctly "always include" all needed files when building? Anything that is called by filename cannot be automatically determined as dependency by the builder.

0 Kudos
Message 7 of 18
(3,345 Views)

Hallo! I "Always Include" NI_AALBase.lvlib but  the application isn't still working. Anyway, since I solved the problem using the content of the vi... I Thank you and go on working on my job.

0 Kudos
Message 8 of 18
(3,321 Views)

"Mean" is not part of "base". It requires lvanlys.dll.

0 Kudos
Message 9 of 18
(3,312 Views)

I used "std deviation and variance.vi" not mean.

0 Kudos
Message 10 of 18
(3,308 Views)