cRIO connection issue-can't deploy code

[integr8]

We are using labview to program our robot and our code looks like it works and no issues are detected when we build the code, but when we try to deploy the code the dialogue box comes up and says:

>>Initializing...
>>Calculating Dependencies...
>>Checking items for conflicts. This operation could take a while...
>>Waiting for Real-Time target (RT CompactRIO Target) to respond

At this point a new box comes up with this error:
>>Failed to connect to real time target
and gives me only one option to cancel.
When I do it says:

>>Current Operation Cancelled

I don't know what the problem is though. We've tried doing something with the network, but when we ping the ip of the cRIO it says that it's connected. We also don't believe it is a hardware issue so any help would be appreciated.

[Tom Line]

Have you verified that you have the correct IP address set in the Project Explorer window in labview? It should that 10.17.18.2 (insert your team number in place of 17.18). If it sawys 10.XX.XX.2, you haven't configured it for your project.

[integr8]

Yes we have checked that and it says 10.13.7.2

[Jasmine Zhou]

Is the firewall on your computer disabled? If not, try turning it off. We had problems last year with connecting to the cRIO, but we use C++ so yours might be a labview-specific issue.

[integr8]

We just tried your solution, Jasmine, and we got the same result as before.

[Alan Anderson]

When you reimaged your cRIO this year, did you choose the LabVIEW option?

[ehochstein]

Have you verified the IP address on your computer is 10.13.7.5? What is your subnet mask set to?

Connected wired first, make sure your wireless and IPv6 are turned off.

[Mark McLeod]

Things to try, some of them already mentioned:

• Disable all other Network connections leaving only the one you are using for the cRIO.
• Turn off all firewalls and anti-virus programs
• Verify the remaining connection has an FRC valid IP address, i.e., 10.13.7.5 (for Ethernet) or 10.13.7.9 (for wireless), Check the Advanced button for multiple IP addresses and delete any extras.
• Start the Driver Station to see the Diagnostic tab ping verifications
• Try connecting your laptop directly to the cRIO vis Ethernet cable
• Type ipconfig /all in a command window to verify what your network connections are.
• Close the Dashboard if it is open and reboot the cRIO. There is currently an issue if the Dashboard is trading data with an existing program on the cRIO.

[integr8]

I have just changed the IP from 10.13.7.10 to 10.13.7.5 and out subnet mask is set to 255.0.0.0 and the default gateway is set to 10.13.7.4. I have also just turned off the IPv6. We are still getting the same issue but now we no longer have communications or robot code in the frc driver station.

Also we are connected directly to the cRIO via Ethernet cable if that makes a difference.

[ehochstein]

I just want to ensure that your wireless adapter is disabled or at least not connected to a network. Also set your subnet mask to 255.255.255.0 for programming.

[Alan Anderson]

The "Failed to connect to real time target" error suggests either a network problem or a misconfigured cRIO. If you can ping the 10.13.7.2 address, the network is probably okay, but you should double-check by using the ipconfig command. Can you copy and paste the results of ipconfig /all here so we can help you narrow down the problem?

Originally Posted by Mark McLeod

• Close the Dashboard if it is open, then reboot the cRIO. There is an issue if the Dashboard is trading data with an existing program on the cRIO-the traffic volume can drown out the file transfer.

The issue isn't the volume of data being transferred. It's a bug in the Network Tables server that keeps the cRIO program from being terminated when there's a current client connection. Closing the Dashboard is the suggested workaround until a software update is released. Rebooting the cRIO is not necessary.

[integr8]

When I pinged ipconfig/all this is what came up

Windows IP Configuration

Host Name: (my name)
Primary Dns Suffixblank)
Node Type: Hybrid
IP Routing Enabled: No
WINS Proxy Enabled: No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix: (blank)
Description: Realtek PCIe GBE Family Controller
Physical Address: 08-2E-5F-7B-6B-38
DHCP Enabled: No
Autoconfiguration Enabled: Yes
Link-local Ipv6 Address: fe80::dc16:faef:92f9:7b3d%12(Preferred)
IPv4 Address: 10.13.7.5 (Preferred)
Subnet Mask: 255.255.255.0
Default Gateway: 10.13.7.4
DHCPv6 IAID: 25219439
DHCPv6 Client DUID: 00-01-00-01-18-4a-43-38-08-2E-5F-7B-6B-38
Dns Server:
fec0:0:0:fff::1%1
fec0:0:0:fff::2%1
fec0:0:0:fff::3%1
NetBIOS over Tcpip: Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State: Media disconnected
Connection-specific DNS Suffix: (Blank)
Description: Teredo Tunneling Pseudo-Interface
Physical Address: 00-00-00-00-00-00-00-E0
DHCP Enabled: No
Autconfiguraton Enabled: Yes

Tunnel Adapter isatap.{A66FC120-4B59-4ABA-A50D-275EF46A6B6B}:

Media State: Media disconnected
Connection-specific DNS Suffix (blank)
Description: Microsoft ISATAP Adapter #4
Physical Address: 00-00-00-00-00-00-00-E0
DHCP Enabled: No
Autocnfiguration Enabled: Yes

[Mark McLeod]

You probably want to turn IPv6 service off.

[Alan Anderson]

I suspect you didn't actually copy and paste that, because there are misspelled words and inconsistent lines, but I'll trust that the content accurately reflects what you got.

With the possible exception of the IPv6 support, everything looks the way I'd expect it to for a properly-configured system. The next step in my troubleshooting script is to verify that the cRIO is correctly imaged. Run the 2013 cRIO Imaging Tool and tell us what it says (a screen capture would be helpful).

[integr8]

We turned off IPv6 and ran the cRIO imaging tool and an error message came up that said:

"No CompactRIO Devices were found

Verify an Ethernet connection between the CompactRIO device and the computer, and then turn Windows Firewall Off while imaging the CompactRIO device."

The windows firewall is off but I'm not sure if the computer is connected correctly to the cRIO.