Deploying Shared Varaiables in Executable

[pmac]

I am running two executables. One is running on a tpc-2106 Touch Panel Monitor using the Labview PDA Module. The other is being deployed on a FP-2010 controller. They are communicating over ethernet using network published shared variables. The FP-2010 is the host and the tpc-2106 is the client.

The tpc-2106 executable is essentially monitoring and displaying status and data that it receives from the executable on the FP-2010. If I run the FP-2010 vi in the development system everything works fine, however when I build the executable and deploy it on the FP-2010 the observed data and status on the tpc is not always correct and largely unpredictable. If I start up the debugger any incorrect data that I'm observing on the tpc display becomes corrected.

In the build properties the shared variable library is "Always Included" and the destination is "Support Directory".

I'm using Labview 8.5, Windows xp SP2.

Has anybody seen this before or have an idea as to what might be causing this?

Thanks,

pmac

[Kevin_H]

Hey pmac,

We do have a KnowledgeBase article that might be worth taking a look at. 

How do I Deploy Network Shared Variables from a Compiled Executable?

Take a look at that, and let me know if you have any questions!

Regards,

Kevin H

[pmac]

Kevin H,

Yes, I have seen that KnowledgeBase article.

As it turns out, the source of the problem was not shared variables but, believe it or not, a value property node. 

Using shared variables to "probe" the FP-2010 exe and display it on the tpc front panel, I was able to determine that a boolean value property node that was wired to a case structure selector was not getting updated. Once I replaced it with a local variable everything worked perfectly. I don't know why this is the case but I did talk to another engineer who said he had a similar issue with value property nodes in an executable. So I guess this is something to keep in mind when building executables.

Thanks for your suggestion,

pmac