04-11-2007 05:28 AM
04-12-2007 02:47 AM
Hi,
I don't know if this can help you, but in last days I had some problems similar to yours with property nodes.
Please try to do the following things:
From Labview, go to Tools >> Options... from here select the category "Block Diagram" and disable (remove the check) the option "Enable automatic error handling dialog" (see the screenshot atached below). Otherwise you can simply create an indicator and connect the error output of the property node, that gives you the error, to this indicator.
Let me know if this change solve the problem.
Have a nice day
carlo>
04-12-2007 03:11 AM
Thanks for your interest, but i don't understand... why care about what i do with the error message AFTER the error has occurred??
However, automatic error handling is already disabled in my VI, the error is logged to a text file and not popped up in a window
04-12-2007 04:34 AM
Hi,
Analyzing your error it seems that the problem is the path of the library. Can you check if the path is correct for the target pc on which the executable should work? If so, and the problem persists, can you create a simple vi that only do the deploy of the library and that give the same error so I can take a look to it?
Bye
carlo>
04-12-2007 06:15 AM
04-13-2007 03:27 AM
Hi,
Doing some researches, the only things I found, related to your problem are:
1. The document you found (One possibility is to follow what said in it and check if this solve the problem, even if in your library there's no I/O server).
2. I also found a specific bug related to "Shared Variable bound to an item(SV or I/O server)". It is said that:
If one creates a library and within this Library creates a Variable bound to the I/O server over the "Browse>>Project Items Dialog" resulting in a path like "My Computer\Lib1.lvlib\IOServer\Group\Item" the "Error 1 Occured at Invoke Node in PRC_Deploy.vi" effectively occurs (obviously creating a new vi and use "Deploy Library.vi" to programatically deploy the Libraries created).
While if one creates a library and within this Library creates a Variable bound to the I/O server over the "Browse>>Network items" resulting in a path like "\\host\Lib1\IOServer.Group.Item" the error doesn't occurs.
a possible workaround then is to use this second method, or it is also suggested to put the I/O server into the same library to deploy.
I hope this help
carlo>
04-16-2007 02:11 AM
04-16-2007 04:46 AM
Hi,
I tried your executable and I saw the error you mentioned but unfortunately you sent me an "*.exe" and so it is difficult to me to debug your example application.
It should be useful if you can run the exe on a pc (different from the one you used to develop the vi and build the executable) on which you have Labview, so we can better understand if the problem concern the lack of software or something else.
Best Regards
carlo>
04-15-2008 07:03 PM
04-16-2008 01:13 AM