05-19-2009 10:01 AM
I created an executable on labview 8.6 and ran it on a laptop which is connected to an HP 35670A Signal Analyzer via GPID to USB and the executable runs fine(active light flashes), but when i transfer the executable with an installer to another laptop without labview and run the executable while attached to the analyzer the data screen is blank and the active light on my GPID cable does not light/flash. I do not know why the executable would run on one laptop and not the other.
Things I have tried:
1. I verified the GPIB Cable works and also tried another GPIB cable which also has the same problem when connected to the deployment laptop.
2. I made sure the address of the GPIB is the same on both machines.
3. I have the drivers for the analyzer and all the other drivers installed on both machines.
4. Created a test program to verify the GPIB and the Analyzer are seeing each other, which verified they are(active light flashed and addresses match).
5. Installed a evaluation version of labview 8.6 on the deployment laptop to see if some necessary files were not transferring.
6. Installed microsoft .net framework on deployment laptop.
I am stumped as to why the executable works on the computer with labview but not at all on the computer without labview. Any ideas or suggestions would be greatly appreciated.
05-19-2009 10:23 AM
05-19-2009 10:26 AM
I had a ver simular issue with the executables.
the computer without labview still need the run time engine for it to work,
you can add this durring the creation of the executable in the options pages, after then it should work.
06-25-2009 07:58 AM
Alright, I packaged the executable with the installer, that contained Visa RTE, RTE, and NI 488.2. Transferred the installer over to the deployment laptop, installed it and ran it and still got no results (laptop still did not initialize). Any more suggestions would be helpful.
06-25-2009 08:03 AM
Sounds like you're not paying proper attention to error indications. Does your code have error checking? If so, it should stop and report the error, or log it to a text file or something, so that you can see that you got "error 999 when trying to send command" or something.
Otherwise, you're flying blind.
Blog for (mostly LabVIEW) programmers: Tips And Tricks
06-25-2009 08:06 AM
5. Installed a evaluation version of labview 8.6 on the deployment laptop to see if some necessary files were not transferring.
Blog for (mostly LabVIEW) programmers: Tips And Tricks
06-25-2009 08:08 AM
06-25-2009 08:25 AM
The code works perfectly fine when it's on the development laptop, so I am assuming the code is correct.
But you're making assumptions about what auxillary files / drivers / whatnot are needed.
All I'm saying is that, since you're already installed the eval version on the laptop, you try and run the source code there, and it might tell you what's missing.
Also, what about the error checking question?
Blog for (mostly LabVIEW) programmers: Tips And Tricks