06-08-2020 12:16 PM
Hi,
I need to access third party simulator t software through labview. I used automate open function in LabVIEW. Then when I try to select the object type, it's not listed.
Is it the right approach? Or I'm missing something. Please let me know in detail.
06-08-2020 07:08 PM - edited 06-08-2020 07:11 PM
When you say object file do you mean a file with the ending .obj? Automation Open requires a. .ocx or .dll file and not all .dll files support an Automation interface. Neither does an .ocx need to provide an Automation Interface, it could also contain an Active X container instead.
As to your request for a detailed answer, your question is so vague and provides no detailed information, that a detailed answer is impossible.
06-08-2020 10:52 PM
The steps I did are as follows:
1. I placed automation refnum.
2. Then I need to select ActiveX class.
3. Selecting "browse"
4. " Select object from Type Library" window appears.
5. From " Type Library" drop down list menu , I am supposed to select the 3rd party simulator type library.
But it's not listed there in the "type library" drop down menu.
How to get that ?
06-09-2020 03:15 AM
That Listbox simply enumerates all REGISTERED ActiveX Automation servers on your computer. If you can't find the one you are looking for there are some possible reasons:
1) Your component wasn't registered in Windows. The fact that you have an application that can use this component does not mean that it has to be registered. An application can also explicitly load a component by path. You can do this in LabVIEW by clicking the Browse button besides the drop down box and navigating to the actual ActiveX Automation server DLL and selecting it.
2) The name under which a component appears is whatever the component developer decided in its infinite wisdom. Some are very creative in the naming of their installed component. Why I'm not sure, maybe an attempt to hide it from nosy users?
3) Your component may not be a full blown ActiveX Automation server. It could be either an ActiveX container (which you would need to use in LabVIEW through the according ActiveX container control on the front panel) or it could be only exposing a COM interface. The COM interface is the binary invocation technology an ActiveX component uses for its implementation but it is not enough to make a component ActiveX compatible.
06-10-2020 12:21 AM
Hi, I tried with option 2 and 3.
Also I tried manually by browsing the .DLL files as you mentioned in option 1.
Still I'm not able to get it.