LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can a VI publish on a remote server?

I'm trying to perform a small expirement - I would like a control in a VI on one computer to publish and subscribe to another control in a different VI on a different computer on the same LAN.(and vice versa) The idea is to be able to manipulate both controls from either computer.(each control should track the other)

I have a VI on computer A and a VI on computer B. Both computers are on the same LAN.
Each VI consists of a single numeric control.
I setup the control on VI A to publish and subscribe to dstp://computerA/new.
I setup the control on VI B to publish and subscribe to the same URL, dstp://computerA/new.
Datasocket server is running on A.
The control on B reflects all changes on A,as I ha
d hoped. However changes in B are not reflected on A. My guess is this is because there is no datasocket server running on B. What I was hoping was that I could publish remotely - have computer B publish on computer A's datasocket server.
So one might say "Start a datasocket server on computer B too." The problem is, when you right-click a control in a VI and select Data Operations>>Datasocket Connection and then choose the connection type to be Publish and Subscribe - you have to Publish and Subscribe to the same location. as above, this would be dstp://computerA/new So if I want to subscribe to the dataitem new on remote computer A, I can't publish locally anyway.
Is what I'm trying to do w/ datasockets even possible? If it can be done and you know how, please help. If you don't think it can be done this way but have a better approach, that info would also be much appreciated! Also if you have any questions feel free to email me.

Thanks,
Jim
dingler44@postmark.net

0 Kudos
Message 1 of 2
(2,517 Views)
One problem I see is that they are both writing to the same connection and at the same time. Multiple servers shouldn't make any difference. And instead of using front panel DataSocket, use the separate write and read VIs. Maybe you would want to put continuous reads in each VI but only publish when there is a change?
0 Kudos
Message 2 of 2
(2,517 Views)