LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

shared varaible communication

I am trying to connect to my compact field point using a shared varaible. I have done this successfully on my office computer, moved my compact field point into the test area and am trying to run the same softeware on my lab computer. I get the error something like "could not read shared varaible, likely its not been deployed properly." I am using the first release of labview 8.0.

I have tried the following:

-disableing the windows firewall, then rebooting (winXP)
-deleting the shared varaible, and making a new one.
-avoiding putting spaces in the varaible name

I have full communication, and am using the same MAX setup on both computers.

If others could give me a list of things to try that would be great. Have the subsequent two updates to labview8.0 fixed this?

Short list of things I have not tried:

-using a hub with two ethernet cables, i am using a Xover cable, worked fine in office

Thanks for your help,
Kevan -
0 Kudos
Message 1 of 2
(2,252 Views)

Hi Kevan,

Here are some steps you should try if you have not done so already:

  • Run a VI without shared variables from within the same project and verify that front panel communication is working properly
  • Verify IP address settings on the lab machine (set to static IP, if so, is it the same as your office machine?)
  • How many network interfaces are installed on the system?  If multiple, disable the one not connected to cFP
  • What is the actual error number that appears?
  • Verify as well that the gateway and dns settings for the lab machine match that of the office machine - this has been known to cause some odd behavior
  • Manually deploy the library before running program by right-clicking on the library in the project window and select Deploy All.  Additionally, if the library was not set to Autodeploy, this would also explain the situation.
  • Change the hosting location of the library containing the shared variables (i.e., drag from cFP target to your PC in the project window)

One of the above should expose the issue, if not solve it outright.  Please post back once you've had a chance to give it a try.  Have a great weekend!

Cheers,

Matt Pollock
National Instruments
0 Kudos
Message 2 of 2
(2,230 Views)