03-31-2019 03:13 AM
03-31-2019 02:57 PM
You should really attach your code instead of pictures, otherwise some people around here will get grumpy.
For your Error 1 - that invoke node is failing and thus the reference returned is probably invalid. So the " to more specific" call fails - you wouldn't get this unhandled error if you had following standard error handling practice and wired the error out of the invoke node and then into the more specific node ....
For your root cause (the .NET Exception) - its hard to say. It might be something simple such as checking that the filepath you are passing to the invoke method is correct and specifies the right type of file etc. The developer of that assembly did not do a great job of communicating errors appropriately to the caller.
04-01-2019 03:14 AM
Thank you for your reply. And sorry for not attaching the code.
Here is the code that I use.
I wire the error out and then the error messages don't pop up.
But when I run the "Autolab Complete Example (A).vi" in project, the program is still stuck in the SubVI "Load Procedure.vi".
04-01-2019 01:41 PM - edited 04-01-2019 01:42 PM
OK, so you are running the example code provided with the LabVIEW API. At this point your best bet is to contact the supplier of the Autolab SDK since they will be best placed to help you. It doesn't appear to be a LabVIEW-specific issue.