Driver station has no robot communication

[johnhenry]

we are not a rookie team, but we have been out of completion for a couple of years. We started out with a brand new control system this year. We have upgraded firmware and imaged the PDM, roboRIO, PCM, and the radio. After wiring everything up all system status lights appear as they should be. We created a test program via Robot Builder and downloaded that to the roboRIO successfully. When we start the Driver Station with an Ethernet tether we get NO ROBOT COMMUNICATION message. We can ping the robot via Ethernet and USB cables. We can get into the Web Dashboard of the roboRIO via USB and all addresses appear correctly.

What are we missing???

[rich2202]

What are the IP Address of:

1) RoboRio
2) Radio
3) Driver station

Is your team number displaying correctly on the Driver Station?

[johnhenry]

RoboRio - 10.38.51.34
Driver Station 10.38.51.70
Radio not sure.


The team number is in the driver station and it recognizes local PC power and joysticks, just not the robot. It gives some warnings, I don't have a copy with me, that says some connections are bad, but some are good, so it appears like it is trying.

[Mark McLeod]

Disable your Windows firewall (Disable McAfee type firewall management tools)
Disable any anti-virus
Disable the network connections you aren't using.

Once you get it working you can add these back in one-by-one to see what was causing the problem.

[johnhenry]

I'm pretty sure I've disabled everything listed, but I'll try again. Does the robot code need anything in it to get things rolling? We are just using a basic shell created by Robot Builder. I've also tried some of the sample programs, but always end up with the same results.

[Mark McLeod]

If you don't have user code or if your user code crashes, then you still should see the Driver Station Communications indicator go green (and the Robot Code indicator stay red).

If you can get that far (Communications=green) then you can worry about your user code.

Your IPs are fine (the radio IP doesn't matter-it's just routing if it's even in the network chain).
Check the diagnostic tab to see it the Driver Station is also pinging everything.

[johnhenry]

I get the same green lights as shown and when I plug in the USB cable the eNet Link light turns on as well. I didn't realize I can add pictures. I will get some of those and post them this evening.

[Mark McLeod]

If your Communications light is on then it's just a user code (or a code downloading) problem.
Networking sounds fine.

What language are you using?

[johnhenry]

I'm using Java. I guess we have a terminology issue on Communications. I have the two green lights for Robot Radio and Robot, but the lights for Communications and Robot Code under the battery level are both red.

[Mark McLeod]

Just an aside, but did you put the Java runtime onto the roboRIO?

[johnhenry]

Yes. Figured that one out after a different series of error messages. I think it was when I was trying to install the software the first time after getting the image installed on the roboRIO. Seems imaging removes the JRE. Been learning a lot, but need one more detail hidden somewhere.