11-12-2004 12:09 AM
11-15-2004 07:18 AM
11-16-2004 03:11 AM
11-16-2004 03:21 AM
03-09-2007 03:20 AM
03-12-2007 03:55 PM
Hi Andreas,
It sounds like your VI is actually running but encountering an error. You could test this by setting a breakpoint in your VI and checking if it runs. If you are able to debug your VI, I would then step through the VI (specifically into the DIAdem Open Reference VI) and attempt to find where the VI starts.
When I drilled into the DIAdem Open Reference VI, I found that error 8808 occurs when the VI is unable to obtain a reference to the open instance of DIAdem. This occurs when LabVIEW attempts to access the bInterfaceLocked property which requests the status of the OLE interfaces from DIAdem. If the bInterfaceLocked property returns the value True (1), the OLE DIAdem interface is locked. It appears that this would cause an error in the LabVIEW VI.
Since you are using this script with the CScriptStart command, I believe you are getting this error because DIAdem has not fully initialized. This would explain why the script works when called directly from DIAdem (after the OLE has been initialized) but not as a "link."
Matt M.
NI
03-13-2007 12:35 PM
03-14-2007 12:36 PM
Hi Andreas,
Thanks for the example. I was able to replicate your problem with it.
I have forwarded this along to my R&D contacts and they are going to take a look at it. I will get back to you when I have more information.
Regards,
Matt M.
NI
03-16-2007 09:22 AM
Hi Andreas,
When I looked at your code, I was able to drill down into the VIs and find where the error (8808) was being caught and thrown by LabVIEW. LabVIEW was evaluating whether the bInterfaceLocked property was true of false. If it is locked, then LabVIEW throws the error.
I talked to my R&D contacts and they said that this this property is not locked once DIAdem is loaded; however, it is locked during the initialization of DIAdem. The reason for this lock is that com provides an interface immediately if the interface exists and is available. While the interface exists during the start of DIAdem, it is not available (this is true for some other DIAdem functions and variables as well) and then the error is thrown.
We have filed a CAR for this issue. This means our R&D will consider including a fix in future editions of DIAdem.
Matt M.
NI
03-16-2007 10:51 AM