We have a program, Merlin, to control our Instron Test Machine. I want to create a program that retrieves the data from the Machine, however, direct communication between the Machine and LabView is not possible. I should be able to acquire the data through the Merlin software using OLE/ActiveX but have ran into problems. I've tried using the ActiveX Automation reference to gain access to the methods needed. As I build the VI, create the object and use the Invoke Nodes to select the methods, all seems right; the methods are available for me to select. However, when I run the VI I get error 3005 (TIFF attached below). I've also attached a TIFF of my VI diagram.
Since this didn't work, and I couldn't figure out how to fix it, I tried another approach. We currently have a Visual Basic Application that retrieves the data from the Merlin software. Since we know that the VB can gain access to the methods, we have been trying to write an ActiveX DLL in VB 6.0 that will create the objects and present the data to LabView. This would essentially be a wrapper DLL containing only the methods and properties needed for the particular application. I registered the DLL with windows and ran the VI, which looks almost the same as the previous VI except the units input on the invoke node was coded within the DLL. I get error -2146827864 when I run the VI, see attached TIFF for actual error. A previous postee, post, got the same error and was able to solve it but didn't adequately explain his solution so that I could apply it to my situation. I am only marginally familiar with VB (and I am quite happy to keep it that way), so my boss, the creator of the original VB program, is writing the DLL for me. However, he doesn't have much experience with creating DLLs. I have successfully created from an example, a simple DLL that works when used in LabView and my boss created a simple DLL that would open the Merlin Program when called by the Open Automation.VI within LabView. The DLL didn't have any callable properties or methods, just opened the Merlin.exe file. Therefore, I know that this should be possible but there is something wrong with the way the VB DLL is created that makes it incompatible to LabView.
I need a solution to correct the error for either one of the methods that I've tried. I know this isn't a VB forum but since I know so little about VB, I doubt I could explain it so that VB experts could understand (to help with that method).
I've tried to thoroughly explain the things tried and their results but should more information/clarification be needed please don't hesitate to reply to my post.
Thank you is advance for any help provided.
Tessa
NTA Testing Laboratories
