TestStand access to LabView .EXE control variables

[Dennis_Knutson]

I'm not absolutely sure about the path. You could try just the path to the exe. The other option would be to append the name of the top level VI to the path. I haven't worked with the ActiveX server of LabVIEW 8.x executables.

[harlemite]

Actually, it's not reading/writing variables in my .exe, it's using the VI... How do I make it reference the .exe?

Sorry, got a bit excited thinking it was working, close but no cigar.

[harlemite]

I tried using the path of the .exe and got the following error:

Details: An exception occurred calling 'GetVIReference' in '_Application' of 'VRBGUI3 Type Library'
LabVIEW : LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
Source: LabVIEW

Error Code: -17811; ActiveX automation server exception.

[DRock]

harlemite,

After you've registered your exe as an ActiveX server, I think you should be able to attain a reference to the underlying VI by passing in to the path input in TestStand something like <rest of path>\\GUI.exe\\GUI.vi.  This seemed to work when I played with things on my machine.  Don't forget the double \\ !

[harlemite]

So if I edit variables in the underlying VI of the EXE (which is working, thanks a lot), is this still adjusting the variables in the EXE or just the VI? Basically, are the boolean switch values I have in the EXE stored in different parts of the memory that the boolean switches in the VI or do they all point to the same location (in which case, it's exactly what I want)? I just want to make sure that this works properly as a stand-alone EXE with TestStand ActiveX modification capabilities, wherein TestStand uses the EXE in the exact same behavior as if a user opened the EXE file.

[DRock]

harlemite,

Try changing the name of the VI on your machine from which you built the EXE.  Use the same TestStand setup that was working (same names, paths, etc) and try to adjust the variables.   Does it still work? 

Mine does, so this indicates to me that the VI has nothing to do with it and that it is using only the EXE (which we did NOT change in our test above).