LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

executable doesnt work

I created an executable from a vi that worked fine.  However, when I created the executable, the executable doesnt work.  Also, someone else brought an executable from their machine to my machine that worked on their machine an it didnt work on my machine either.  One of the things i noticed on my oscilloscope from the executable that was brought to my machine by my co-worker, was that the communication rate slowed way down.  When running the vi itself, the communication rate was at the correcte baud rate, but ran as an executable, the rate was way out of spec and will not work against my target hardware.
0 Kudos
Message 1 of 4
(2,681 Views)
When you say that the executable "doesn't work" can you say a bit more about that? What exactly are the issues that you are running into?

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 4
(2,669 Views)
simply, I created a vi on my machine and when running the vi, the program will communicate with my unit under test, but when ran as an executable it will not.  A co-worker of my brought an executable from his computer and ran it on my computer and it didnt work, but it worked on his machine.  The problem seems to lie in the com port/ baud rate setting area.  Because, when viewing the communication on the scope, the vi's waveform has a much higher baud rate than the executable's. 
0 Kudos
Message 3 of 4
(2,662 Views)
Have you tried running your exe on your co-worker's machine?  If that works, you may need to update your VISA Run-Time Engine (I am assuming you are using serial communication for this...).  You can get the RTE here.
0 Kudos
Message 4 of 4
(2,635 Views)