LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Exe works on my computer, but not on others..

Solved!
Go to solution

Hello,

 

I've made a .exe file from my vi to test my application (measure).

 

My vi remote a spectrum analyser, read the datas and spread them on the screen (xy graph). Before, these datas pass thru Create Limit and Limit testing vi, so I've got 3 plots : Signal, Failures (over the limit) and Limit (the pattern).

 

So I created the exe and it works well, just like the vi.

 

But the problem is that when I copy the build folder (exe+ini+aliases+data folder) on another computer, the program works, but there is a problem : I've just got the Signal plot on the screen. Failures and Limit just don't appear, as if the limit vi didn't work.

 

There is many exe on the computers I tested it, and they all works fine... is it a runtime engine problem ? I don't think so because the computer got labview 2009 so it should have the latest version.

 

Anyone got an idea ?

 

Thanks in advance

 


J.D.
French Labview beginner
N'oubliez pas de complimenter les bonnes réponses - Don't forget Kudos for good answers
0 Kudos
Message 1 of 28
(4,564 Views)

It doesn't sound like a runtime engine problem because it wouldn't work at all (i think).

 

Trying to guess now. Are the things that don't work in a sub-VI? if yes have you included them on the .exe build?

Can you put some indicators on the main VI appart from the graph to see if you are getting anything there?

Have you got an error out cluster on your front panel to display any errors if they occur?

0 Kudos
Message 2 of 28
(4,552 Views)

Dimitrios a écrit:

It doesn't sound like a runtime engine problem because it wouldn't work at all (i think).

 

Trying to guess now. Are the things that don't work in a sub-VI? if yes have you included them on the .exe build?

Can you put some indicators on the main VI appart from the graph to see if you are getting anything there?

Have you got an error out cluster on your front panel to display any errors if they occur?


Yes they are in a sub-vi (polymorphic), which is in the dependancies of the project explorer (it is done automatically).

This sub-vi gives over things like a boolean indicator, which doesn't work neither.

 

There is an "error" that may be a problem : my waveform parameter dt is set to -1 because it isn't constant. But it should not be a problem as there is a Labview example using this, and it works fine as a vi and as a .exe on MY computer.

 

How can it be possible that a .exe works on my computer and differently on others? incredible..


J.D.
French Labview beginner
N'oubliez pas de complimenter les bonnes réponses - Don't forget Kudos for good answers
0 Kudos
Message 3 of 28
(4,542 Views)
It's hardly incredible. Unless you install all of the necessary drivers, etc. on the different pc, your exe will not work correctly. You don't think the exe includes all hardware drivers, do you? You have not provided nearly enough information to determine what is missing. First, it's generally a bad idea to just do a copy. You should really create an installer. You mention using a spec analyzer. What type of connection are you using? Does it require NI-VISA, GPIB?
0 Kudos
Message 4 of 28
(4,530 Views)

It has happened to me many times.

Once it was a path that was different.

Another time it was the the DAQ device which had different name.

Or i had to add VI's manually on the Source files

When you build the executable have you added these VI's on the 'Always included List' of the "Source Files". If not try it to see if that makes a difference.

0 Kudos
Message 5 of 28
(4,526 Views)

I know that a exe doesn't include everything, but I thought labview would build the exe including the dependencies of the vi.

 

Previously, the futur user of my program never had a problem with this : the guy who created the application gave him the build repertory, an it worked...

 

How can I create an installer please ? The network analyser is connected via NI GPIB (analyser)- USB HS (computer). So it uses GPIB communication, and the VI uses VISA protocol to communicate with the analyser.

 

The point is that the communication with the analyser isn't a problem as the Signal is transmitted well with the .exe, the only problem is that limit polymorphic VI (i think). But how can I know ? Smiley Surprised


J.D.
French Labview beginner
N'oubliez pas de complimenter les bonnes réponses - Don't forget Kudos for good answers
0 Kudos
Message 6 of 28
(4,518 Views)

http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/build_installer/ 

 

But try to add the Vi's on the list it might be just that.

 

Message 7 of 28
(4,514 Views)

You create an installer just the way the LabvIEW help explains. In your project, right click on Build Specifcations and select New>. When you built the exe, did you not notice the 'Installer' option right below 'Application (exe)'?

 

There is the possibilty of a lot of dependencies that the app builder has no possible way of knowing. Even when known, those dependencies might be something that you have to specifically add as part of the installer.

Message 8 of 28
(4,512 Views)

Dimitrios -> there is only the main VI in the Source files, and I can't add anything...

 

here are 3 screens of the options

 


J.D.
French Labview beginner
N'oubliez pas de complimenter les bonnes réponses - Don't forget Kudos for good answers
Download All
0 Kudos
Message 9 of 28
(4,503 Views)
You need to add them on your project file.
0 Kudos
Message 10 of 28
(4,465 Views)