ActiveX with LabView error 0x80070002

[twowheels]

trying to use LabView to control another program which has a COM interface.  I can select the Interface from the Ref control and I can see the methods associated with it but the Invoke call always returns an error and the errors are different. 0x8007002, 0x8003000E(??)    I need more detail on how LabView uses the registry to attach to the COM object.  I have read a bunch of various docs but still don't have a clear picture of what steps occur. The program is a seperate .EXE running in it's own address space not a .dll.   Any COM Automation wizards out there?

[Andy-K]

Hi twowheels,

If I understand correctly, you want to use Labview to open an ActiveX connection to a separate program that then has a COM interface communicating with a device.  The specific errors you are getting are unique to the program you are running with ActiveX.  Is the device you are using virtual or an RS232 connection? Also, what operating system are you using and have you done a hyperlink communication with the COM device to insure communication is happening?  Are you getting errors when performing an invoke call not related to the COM interface?  If possible, could you give details on your application goals for the purpose of narrowing down what the issue could possibly be?

[twowheels]

when I refer to COM, I am talking about the COM Automation API(as in OLE, ActiveX, etc.), not RS-232 communications.

I am trying to Invoke methods which are exported in the Type library for the program I am trying to control via LabView.  Without debug version of LabView's ActiveX interface I can't be certain what parameters are incorrect when trying to open a COM connection(not RS232) to the object and then be able to Invoke methods. The documentation for required registry entries and the general details of communication via COM Automation has required some searching on my part.   I was looking for some advice from someone who was an expert on COM objects and interfaces.   Most of the material I find always refers to remotely controling microsoft office products. not interested in that.

[Andy-K]

Hi twowheels,

I am sorry for the misunderstanding with the COM interface.  Which methods in the Type library are you trying to access?  One possible method for finding out the correct way to reference the functions is to find someone else’s code that calls the method correctly and rebuild the process in Labview.  I hope this is helpful and I understand the situation now.