LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

exe doesn't work

Thanks for helping narrow down the problem.

Do your VIs start running at all? How have you confirmed that no communications have occurred? Do you start with some sort of Initialize VI for your data generator? Does it get called? Or are you crashing while just trying to load your VIs? Do you see a front panel? Does the 3rd party DLL get called?

You can use the Task Manager in Windows to monitor your memory usage, but I would expect it to use about the same memory as in the development environment.

Brian
Message 11 of 21
(1,817 Views)
After building the exe, what are the DLLs in the exe folder?

-Joe
0 Kudos
Message 12 of 21
(1,817 Views)
My application.exe ran, I can see the front panel. My application has an initialization and then start the DG2040, and when the DG2040 starts, a green button on the instrument should lit up. The green light didn't lit up when I ran my application. I saw the front panel, it ran for like 2 or 3 seconds and then crash. I didn't even get to the DLL part at all. But when I copied this part of the code onto another VI and made an execution, the DG2040 lit up, then the 3rd party DLL get called and everything is great.
0 Kudos
Message 13 of 21
(1,817 Views)
No DLL In the exe folder. In the system folder I have visa32.DLL, and then I have some 3rd party DLL that the program uses, but I have already registered them.
0 Kudos
Message 14 of 21
(1,817 Views)
did you check if you have different versions visa32.dll on the same system? It's possible the development system loads one version and the runtime loads another.

-Joe
0 Kudos
Message 15 of 21
(1,817 Views)
The VI on the laptop runs, so shouldn't the exe runs on the laptop also. It's the same laptop, it shouldn't load different DLL, right?
0 Kudos
Message 16 of 21
(1,816 Views)
Not necessarily.
0 Kudos
Message 17 of 21
(1,816 Views)
Oh, so how do I check? I know I have one in the system folder. Should I just do a search for visa32.dll?
0 Kudos
Message 18 of 21
(1,816 Views)
Once you searched the files, right click on each one, it should show the DLL version. Then compare with the computer where the executable worked.

Also, make sure there is enough time during application startup to properly initialize everything (values, constants, globals, daq parameters, etc).

-Joe
0 Kudos
Message 19 of 21
(1,816 Views)
Thanks for trying to help. I have checked, and it's the same version. Do you have any other suggestion? Also I have put some indicator lights in there to see where it breaks, and it looks like it breaks where it tries to communicate with the DG2040 Data Generator. But then I open the DG2040.exe, and it communicates fine.
0 Kudos
Message 20 of 21
(1,816 Views)