VI server control exe

[Neil.Pate]

Hi,

I need to be able to pass tiny bits of data between separate compiled applications. DataSocket seems like overkill, and so its easier to directly change the values of the control using a VI server approach.

My problem is, things work fine in the developement environment, but once compiled the behaviour is different.

I seem to be having a little bit of hassle with the VI server. Attached is an example. The "Get All Control Values" works fine in both development and application, but "Set Control Value" only works in the development mode.

Am I being silly here? I think the server is configured properly as I am able to read control values, and changing the port number gives (as expected) an error message.

(Using LV 7.0 and W
in2k)

Any help would be greatly appreciated.
Thanks
Neil

[rolfk]

nrp wrote:

> I seem to be having a little bit of hassle with the VI server.
> Attached is an example. The "Get All Control Values" works fine in
> both development and application, but "Set Control Value" only works
> in the development mode.
>
> Am I being silly here? I think the server is configured properly as I
> am able to read control values, and changing the port number gives (as
> expected) an error message.

Your problem here is probably that the Application has removed the front
panels during the build to your subVIs. Make sure that the front panels
are not set to be removed in the Application Builder settings for the
VIs you want to invoke the "Set Control Value" method on.

Rolf Kalbermatter

[Neil.Pate]

Rolf,

thanks for your speedy reply. In my very simple test case the target VI is the only one being built into an executable, and so the front panel is always on (not removed). For some reason the show panel is set to "no" and I cannot seem to find where to change this, but the app runs fine. I can see the front panel and interact with it, so it must be something else wrong.

Any other suggestions??

[Jon Bowers]

I am not sure that VI Server will work as you wish because it refers to the vi as a layer under the executable. You might try building the exe as an activeX server then useing activeX call to get the data you require.

Regards

Jon Bowers
NIUK