stand-alone application problem

[matt26]

Hi all

I’ve been having some trouble with building a stand-alone application. The problem is that the system works on the development machine, but when I build the .exe file and deploy, the UUT drivers that I made for this app keep failing.

1st of the UUT drivers uses Property and method nodes(Active X), 2nd UUT driver uses call library function,  and the 3rd UUT driver uses VISA VI’s to communicate to the instruments.

 The errors I’m getting are:-

1. VISA Flush I/O Buffer in Measure.vi->drv.vi->daqdrivers.vi->Ruska QSM.vi Error -1073807346
2. Unknown System Error in DG700 component.vi->DG700 Read.vi->drv.vi->daqdrivers.vi->Ruska QSM.vi Error 97

The application is required to talk to a reference instrument (which works), and to talk to a UUT at the same time and log that data to a file.  I’ve installed the run-time engine, NI-VISA, MAX, 488-2 software onto the PC which the application will be deployed on.

Any help with this problem will be apreciated.

Regards

Matt

[ramses64]

Hi,

does your .exe work on a the development machine ?

Regards,

[matt26]

Hi

The .exe dosen't work when trying to communicate to a second device on either machine, but operates correctly when only the reference device is there. I can communicate with the UUT in MAX. I'm using multiple buses to communicate( reference is GPIB, UUT are Serial and USB).

Regards

Matt

[matt26]

Hi

I've retested the UUT drivers on their own, and 2 of them work as an .exe on the developer machine, so I don't understand why its not working in the original app. Any ideas?

Regards

Matt

[Andy.G]

Hi Mat,

Im a bit confused as to what machine you have tested on and what works on what. Could you please give me a full run down on what you have tested on which PC and the software installed on them. Thanks!

[Mark_Ramsdale]

Hi,

I looked up the first error,

-1073807346 =  VISA:  (Hex 0xBFFF000E) The given session or object reference is invalid. 

Are the COM setings the same in both systems ( COM 1,2 ...N)?  Is there a way to run and IDN or some similar call to verify the com is set up. 

Can you describe the setup/error conditions a bit more.

[matt26]

HI Andrew

The software installed on the developer machine are:-

1. LabVIEW 8.6.1 Base package
2. LabVIEW Signal express v3.0
3. NI-488.2 version 2.2.7.3
4. NI-DAQ
5. VISA
6. MAX version 4.6.2
7. NI Spy
8. Datasocket
9. IVI
10. USB –Serial driver (for converter cable)
11. DM2 USB device Driver (DM2)
12. Teclog2 (DG700)

The software on the Target Machine are:-

1. Run-Time engine 8.6.1
2. LabVIEW Signal express v3.0
3. NI-488.2 version 2.2.7.3
4. NI-DAQ
5. VISA
6. MAX version 4.6.2
7. NI Spy
8. Datasocket
9. IVI
10. USB –Serial driver (for converter cable)
11. DM2 USB device Driver (DM2)

The NI Variable Engine doesn’t appear to be installed on the target machine, is that required?

The target machine works with the reference device, which is GPIB, but throws an error when trying to communicate with a UUT device.

The developer machine can run each of the drivers individually in development mode and as an executable, but each time I include them in the application, it throws an error, (the error isn't always at initialise, it can occour when trying to read from teh device).

The reference equipment is a Ruska unit with GPIB connector.

The UUT is changeable, there sometimes won’t be a UUT there- but the UUT are an DM2 (USB), DG700 (Serial), FCO510 (serial). The FCO510 uses VISA, the DG700 uses Active X, and the DM2 uses a dynamic link library.

Regards

Matt

[MoReese]

The VISA flush port error may be because the program can no longer see the Com port.  Do you have it hard coded in the program or can you control it from the fp.  Check your com settings on the target system and ensure your Com ports are mapped out the same.  You are using Com ports and not USB, correct?  USB will be assigned to whatever is available on the machine and will most certainly be different from one machine to the next.

[matt26]

The comm port setup is controlled by a dialog box. I double checked the comm port setup, and found a tunnel that should have been a shift register. So now the VISA driver works, but I'm still unable to connect to the other 2 drivers that use active x and call library function. These 2 drivers seem to poll the ports to make a connection, so they dont use the VISA comm port.

[matt26]

It seems to be working now, I added another place for the application to look in for the active X control and the DLL, as per the document at http://digital.ni.com/public.nsf/allkb/862567530005F09C862565C50068363D . Thanks for all your help.