(My Labview built executable) has encountered a problem and needs to close.

[gdecker]

All,

I've built a labview executable that interfaces with GPIB and the Texas Instruments EV2300 via USB.

The VI runs beautifully on the development machine, and I built the VI into an executable and it runs fine on the development machine.  So I built an installer that installs the Labview 2010 runtime environment on the target computer.  I ran the installer on a production line computer that I know can run GPIB and the EV2300, but when I try to start the executable I get an error that says "(your application) has encountered an error and needs to close." 

I can get labview executables that don't talk to GPIB or USB to run on the target machine, so it's not the runtime environment.  And I have VB6 applications that can run the GPIB and EV2300 interfaces without a hitch.

I'm not doing anything weird with the file paths in my program, just creating paths from strings using the canned VI for converting strings to paths.  In the course of the program, I read a few text files and write one.

Is there anything I need to know about how to build an application with an installer?  I need to get this up and running so the test program can run on a production line.

[RTSLVU]

---

I can get labview executables that don't talk to GPIB or USB to run on the target machine, so it's not the runtime environment.  And I have VB6 applications that can run the GPIB and EV2300 interfaces without a hitch.

---

Sounds like a VISA problem. Download and install the latest VISA runtime on the target machine.

[JÞB]

---

@RTSLVU wrote:

---

I can get labview executables that don't talk to GPIB or USB to run on the target machine, so it's not the runtime environment.  And I have VB6 applications that can run the GPIB and EV2300 interfaces without a hitch.

---

Sounds like a VISA problem. Download and install the latest VISA runtime on the target machine.

---

Ditto that!  At least One of the installed drivers on the target does not have LabVIEW 2010 support.  Check MAX and NI.com to resolve all the drivers on the target that have no support for 2010.

And yes, you may need to re-qualify the pre-existing exe's- if their code changes to use the new drivers If you are in a heavilly regulated industry.   If so, It might be easier to build in an older LabVIEW version.  Very sad- but it might even be simpler to incorporate the Unit Test Framework to handle regession testing of older code with newer drivers.

Worse-  What if the exe's were built with a legacy version of LabVIEW that is no longer supported by the latest Drivers?

Time to start thinking of life cycle maintenance plans- with a 5 year upgrade required!

[RTSLVU]

---

@gdecker wrote:

 So I built an installer that installs the Labview 2010 runtime environment on the target 

---

Did your installer include the VISA runtime along with the LabView runtime?

[gdecker]

Here's some new information:

The target computer will load a program that uses just the GPIB instruments without the USB driver.  But a program that just uses the USB driver and none of the instruments gives me the same error.

The USB device is an EV2300 from Texas Instruments.  It works with other software that I've written in other programming languages on the same machine, and it works with the software provided by Texas Instruments.  I'm not sure what's different between the two USB driver installs, since they both came from the same installer.

The implementation of the driver in my software was to import the .DLL into an activex structure within the VI.  I don't know if that's relevant.

EDIT:

Is there something I need to know about making an executable that uses activex?

[RTSLVU]

I have had simmilar issues with LV programs using ActiveX methods running fine on the development station and crashing on the target.

Neither I nor NI support was ever was able to solve them. In the end NI said it's a Windows/MS/ActiveX issue.

Therefore I have abandoned using ActiveX methods all together.

---

@gdecker wrote:

The implementation of the driver in my software was to import the .DLL into an activex structure within the VI.  I don't know if that's relevant.

EDIT:

Is there something I need to know about making an executable that uses activex?

---

[gdecker]

Are there alternate methods for using a DLL within a VI then?  I need to be able to interface with this USB device.

EDIT:  Bear in mind that I don't have access to the header file for the DLL I'm using.  I had to pull it out of the Windows directory it was in, and there are no .h files to be found associated with the DLL I'm using.

[gdecker]

I would also like to add, appropos of nothing, that it is incredibly frustrating to try and search for solutions to this problem and find that most of the sites Google points to that pertain to using the EV2300 module with labview are forum posts here and at TI that I created, most of which were never resolved.

I know I'm not the only person ever to try and use Labview with the EV2300, but it seems everyone who's actually done it doesn't let on that they have.

[RTSLVU]

Anytime I have had to go through a DLL I used the Call Library Function Node

I have attached an example of a vi that cam with an NH Research electronic load.

I has been a long time since I had to build VI's using the Call Library Function, but from what I recall it was not that difficult to get them setup...

[gdecker]

Okay, we'll call rewriting all the VIs I made that use activeX, and the program that calls them, plan B.

Is there anything special I need to know about how to build an executable and installer when I'm using ActiveX?  It's a feature included in Labview, so there must be a way to make it work.