LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can’t read data on shared Variable From remote PC

I have read and think I understand the articles on ni.com about using shared variables over a network.

 

I want to take data from my development machine (D---175) running LabView 8.6.1 Professional and display it using a separate VI on a client machine (WIL---18).

Client machine has LabView runtime 8.6.1 installed.

 

I created a project with two sets of variables (server and client). The client variables are bound to the server variables.

 

I set the build so that the shared variable is in the support folder.

 

When I run both VI’s on the development machine everything goes fine.

When I run the server side VI and the executable on the development machine everything goes fine.

When I run the server side VI on the development machine and the client side executable on the client machine: NOTHING happens. The executable loads fine. I browse to the location where the shared variable is located and the program runs, but there is no data. Everything stays Zeros. I don’t get any error messages (on the client machine), nothing seems to be wrong except I don’t see my data.

 

The distributed systems manager (on the development machine) sees both computers. I am deploying the variables on both computers. BUT I get an error listed on the value field (no known value, connectiong, disconnected, process failure)

DSM.jpg

 

I applied the following fix with no difference (I re-ran the build after the fix)

http://joule.ni.com/nidu/cds/view/p/lang/en/id/1255

   

My IT department tells me there are no firewalls between machines on our intranet. 

What else could I try to trouble shoot this?

0 Kudos
Message 1 of 7
(3,809 Views)
Why are you using VI on one machine and executable on the other ? why r u not using executables or vis on both machine?
Message Edited by gak on 08-22-2009 01:57 AM
Gaurav k
CLD Certified !!!!!
Do not forget to Mark solution and to give Kudo if problem is solved.
0 Kudos
Message 2 of 7
(3,795 Views)
Also instead of taking variables at both machine and binding them, you can use datasocket and have your variables on one machine only. it will be much simpler.
Gaurav k
CLD Certified !!!!!
Do not forget to Mark solution and to give Kudo if problem is solved.
Message 3 of 7
(3,793 Views)
do you deploy your all shared variables at the program initialize?
0 Kudos
Message 4 of 7
(3,775 Views)

Hi

Keep your code at the server machine and keep the shared variable there. On the client machine use datasocket functions instead to reach data in the server computer (Its quite easy). It doesnt work with executables and shared variables ,there are no support for some commands you need, if I remember right.

 

Regards

Hans

Message 5 of 7
(3,763 Views)

gak wrote:
Why are you using VI on one machine and executable on the other ? why r u not using executables or vis on both machine?

I only have Labview on one machine. The other has just the run time environment. I could go with two exe's but it would only be an added step.

0 Kudos
Message 6 of 7
(3,721 Views)

ronke wrote:
do you deploy your all shared variables at the program initialize?

 

Yes. I used the files from here (http://zone.ni.com/devzone/cda/tut/p/id/5715) as a starting point.
0 Kudos
Message 7 of 7
(3,714 Views)