[Help] Can ping, but DS says "No Robot Communication" only W7, ok from XP

[Joe Ross]

What anti-virus are you using?

[gnunes]

Long shot...is the laptop fancy enough to have two network ports? If so, have you set the DS to use the correct one?

Either way, I would hit the Choose NIC... button on the DS Setup tab, just to see if there is anything illuminating there.

[fovea1959]

Joe Ross: hadn't thought of that. Running AVG Free 2013; disabled it, no joy.

gnunes: only one ethernet port. double checked, wireless is disabled, wired enabled on correct port, ping and FTP work.

So still in same place: Communications lights on diagnostics panel shows "Robot" with a green light, I can ping and ftp the robot, but DS stills says "No Robot Communications". If I put a bad team number into the DS, then the "Robot"light goes red (as it should), and if I have the correct team number in the DS, but disconnect the cable, the "Robot" light goes red (as it should). I definitely have TCP/IP connectivity between the W7 box and the robot (green Robot light on diagnostics panel, ftp and ping work).

Who knows the difference between the green Robot light and the "Communications" light?"

I'm about to give up and start over with the 2013 DS in a little over 2 weeks; maybe the problem will go away then (or FIRST will be able to tell me how to get more troubleshooting information).....

[Greg McKaskle]

Ooh, ooh, I know...

The Diagnostics page LEDs in that column mostly refer to ping results. The No Robot Communication message, and the light on the left permanent panel labeled Communications are much more of a summary and indicate whether the protocol is succeeding.

My guess is that the cRIO is not running the FRC Communications task and is not responding to control packets. Image the cRIO. You can verify this further if needed by using netconsole or the serial cable to view the console trace. You could also identify if that task is running or not. But since most folks don't have a null-modem serial cable laying around, I'd reimage and see if the issue is resolved. Be sure to click the format checkbox in the imaging tool.

Greg McKaskle

[fovea1959]

cRIO is running the task; swapping my XP machine in makes everything work perfectly. It's something on the W7 box...

[Mr. Lim]

Is there any chance you are also using both a wireless and wired network connection?

Do both have the same domains, or do they both start with 10.xxx.yyy.zzz and you have a subnet mask set at 255.0.0.0?

It might be confused about which network connection to use to connect to the cRIO.

If so, try disabling your wireless, and go wired only.

Strange, because if you can ping it, it should be fine.

How are the ping times? any dropped packets?

Maybe you can try a "tracert" and see if anything fishy is going on.

[Mark McLeod]

It still sounds like the FRC port traffic for the Driver Station is being blocked (or the port is locked up) by something on the Win7 machine (for your own security, of course).

You might scan from another machine to see what ports the Win7 machine has open using something like Angry IP Scanner

You've already eliminated the usual culprits - Windows firewall, anti-virus, extra NICs, intermediate router firewalls.

No other network related applications on the Win7 machine?
Perhaps booting Safe Mode with Network would eliminate the possibility of a third-party driver causing the conflict.

[Kevin Fort]

Does the cRIO show up in the imaging tool on the Win 7 machine?

If your wireless card is currently disabled try enabling it - if it is currently enabled try disabling it. We fixed most of the problems with this in the updates after week 1 of the season last year and it was mostly with the imaging tool but still worth a shot at this point.

[Greg McKaskle]

One other thing I've seen affect this is having multiple IPs on a single NIC. Open the control panel and get to the IPv4 properties. That dialog contains an Advanced button. If you happen to have multiple IP addresses set, delete all but one.

You can also see this if you use ipv4 or perhaps netshell.

Greg McKaskle

[Mr. Lim]

Does your W7 machine support Gigabit Ethernet?

Try going to Device Manager and manually configure the speed of your Ethernet down to 100Mbit Full-Duplex.

I've had machines be able to ping, but not actually send reliable packets via Ethernet if auto speed/duplex negotiation is on, and I don't have cabling which can reliably support Gigabit speeds. It tries Gigabit speeds, it sortof works, but then stalls.

[Secretspy97]

Your netmask should be 255.255.255.0 not 255.0.0.0.

[fovea1959]

just trying to stay focussed on underlying problem: netmask is not the problem, else ping, ftp, etc, would not work.

frc documentation states clearly that 255.0.0.0 is correct (ref: http://www.usfirst.org/uploadedFiles...adio_Rev_A.pdf, http://www.usfirst.org/sites/default...20System_2.pdf)

in any case, either netmask 255.0.0.0 or 255.255.255.0 will work for 2 clients, 10.xx.yy.2 a nd 10.xx.yy.6.

[Secretspy97]

I believe that 255.0.0.0 is for configuring your radio not to communicate with your cRIO;
The 2012 control system says that you need to change it to 255.255.255.0 as stated by FIRST in http://www.usfirst.org/sites/default/files/uploadedFiles/Robotics_Programs/FRC/Game_and_Season__Info/2012_Assets/Getting%20Started%20with%20the%202012%20FRC%20Cont rol%20System_2.pdf(page 16, bullet 6).

You are currently just pinging the radio not the cRIO.
You can see if this is true by connecting directly to the cRIO and then try to ping it.

I know that it is possible for a windows 7 computer to work because I currently use a windows 7
computer to deploy code to our robot. I had the same problem and this fixed it.

[connor.worley]

Originally Posted by Secretspy97

You are currently just pinging the radio not the cRIO.
You can see if this is true by connecting directly to the cRIO and then try to ping it..

OP can definitely ping and FTP to the cRIO.

[Secretspy97]

Can you deploy code to the cRIO?