02-23-2010 07:27 AM
muks,
I think that link applies if I'm reading in a file, which I don't think I'm doing.
02-23-2010 07:35 AM
Paulie,
The problem is seen on the same PC I developed the VI.
I'm not sure how to see the value of the reference in the exe version. I put a probe on the vi and got some values(see below). How do I do the same in the exe?
Thanks for your help again,
Richard
Refnum (in hex): 0x7BB00009
Type: Network
ToString(): Aerotech.Ensemble.LabVIEW.Network
HashCode (in hex): 0x03C22AB2
02-23-2010 07:38 AM
Richard,
the 3rd party VI is using a .NET interface for the motion control. If the error is created by the property node following the constructor, i guess that the "Network" Object is throwing an error when trying to access the controllers. Since the error is most probably passed on from the node into LV, you will receive a message which might not suite the original error.
I suggest you to make sure that the .NET assembly used in the VI is properly accessable from the LV RTE as well (Is it e.g. part of the GAC?)...
hope this helps,
Norbert
02-23-2010 08:46 AM
Norbert,
I think you've got it. There were some other dll's that weren't in the right place. I assumed the Application Builder would get everything it needed to create the exe. When I added the 'missing' files my simple vi runs as an exe. I just need to confirm with the real thing.
Thanks for everyones help,
Richard
02-23-2010 10:24 AM
The way to see some values in an exe is to add some controls (on your Panel) connected to the desired 'wires', and to built it again (I don't know the terminology in English) - it is not elegant but it's fast and easy. Or to you can add some message boxes + a number to string vi.
It is nice that you found the problem. Good luck with your further work.