LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO-9104 running .vi across subnets

Solved!
Go to solution
I have a .vi that I am running from my computer with Labview version 8.2 and a cRIO-9104 that runs another .vi connected across an ethernet switch.  My problem is this: when I am connected to the same switch and am assigned the same IP scheme as my cRIO, I am able to run the program with no issues.  However, when I try to connect to the same cRIO on a different IP scheme my program spits out an error.  I can successfully ping and deploy the program on the cRIO across the different subnets; it's just when I go to launch the program on the computer that it throws the error.  The error being: code:-1950679022 source:LVVAR_RTSinglePointRead bool.vi.  This is the error from the program on the cRIO.  Thanks in advance for your help.
0 Kudos
Message 1 of 13
(3,824 Views)

Hello,

 

Are you using shared variables in your VI? Take a look at these Knowledge Bases:

http://digital.ni.com/public.nsf/allkb/AB40E0B788E946188625723600311EF1?OpenDocument

 

http://digital.ni.com/public.nsf/allkb/D358BABAE2F61F1A862571570056867D?OpenDocument

 

http://digital.ni.com/public.nsf/allkb/B9366256C53D95CA8625725A007C0287?OpenDocument

 

Let me know if these solutions apply to you.


Thanks,

 

Anna K.

National Instruments
0 Kudos
Message 2 of 13
(3,803 Views)

Try changing the subnet masks on both (your PC and the cRIO) such that the mask only has bit set where the IP addresses overlap.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 3 of 13
(3,798 Views)
I looked at these three links and put the .ini file with the LOGOS on my cRIO.  However the situation is the same. It almost seems like this is a timeout error.  Like I said before it only occurs when I switch to the connecting computer's IP to an external IP.  I don't think it is a firewall issue because I can communicate with the cRIO and deploy the .vi. 
0 Kudos
Message 4 of 13
(3,777 Views)

Are you using shared variables?

Are you deploying your program as a stand alone application?

When you move the connecting computer to an external ip address, is the ip address of the crio still listed as 192.168.bla.bla in the project explorer? 

 

 

 

---------------------------------
[will work for kudos]
0 Kudos
Message 5 of 13
(3,773 Views)
Yes I'm deploying shared variables.  No it is not a stand-alone application.  One application is deployed on the cRIO (from Project Explorer) and the other is opened from the computer (from Project Explorer).  No when moving to an external IP the cRIO is listed as an external IP address. The cRIO is assigned a static IP.
0 Kudos
Message 6 of 13
(3,764 Views)

subnet mask?

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 7 of 13
(3,762 Views)
Did you fill in the gateway address. That is the address the box will use to have it route the system across the subnet.
0 Kudos
Message 8 of 13
(3,760 Views)
Sorry about that Ben, do you mean if I have a subnet mask that is 255.255.255.0 to change it to something like 255.255.254.0?  Right now the IP scenario is cRIO = IP: xxx.xxx.132.280 (external IP), subnet: 255.255.255.0, gateway: xxx.xxx.132.1.  The computer is 192.168.1.70 (internal IP), subnet 255.255.255.0, gateway: 192.168.1.1.  Like I said I am able to communicate with the cRIO this way.
0 Kudos
Message 9 of 13
(3,750 Views)
Solution
Accepted by topic author samf48
After speaking to NI's tech support the solution to this issue is to use data sockets in conjunction with shared variables.  This article: http://digital.ni.com/public.nsf/allkb/474BC0745F63B7378625754D0069ECE8 explains how to do this.
0 Kudos
Message 10 of 13
(3,683 Views)