Hey Chief Delphi! I am in desperate need of your help! On our Roborio, the comm light is red but the driver stations says that the robot is connected. When I attempt to deploy code, the consul says the code is getting to the Roborio but when i go back to the driver station the robot code light is red. I have tried reimaging the Roborio and that doesn’t seem to help anything. I don’t know what else to try. Any help is appreciated! Thanks!
Have you tried statically setting the IP address of your RoboRIO?
While RoboRIO-3181-FRC.local would work for resolving its IP address, it seemed like the driver station really wanted the RoboRIO to be 10.31.81.2
Once we statically set the address to .2, everything was much happier.
Which language are you using?
When you say it shows that it deployed successfully, what message are you seeing exactly?
I’m not sure if this could cause this type of issue, but did you also update the firmware on the Roborio? There is both firmware and an image for it.
Try turning off the windows firewall on the computer running the driver station.
If you are using C++ or java, open the RioLog to see if there are any error messages. You can also open a console window to the roborio from the driver’s station app by clicking on the gear over the box on the right hand side and selecting “View Console”. See if there is anything in the console about code starting up and then terminating.
On the driver’s station diagnostic tab, is the robot light green? That is the same as typing ping roborio-TEAM-FRC.local from a command prompt, which you can also try for fun. (substitute your team number for TEAM)
Clearify for Johnny (I’m working with him right now)
We are working in C++. I was able to get an older version of the code uploaded, deployed and working, but the new version (which has quite a bit more in it) builds successfully, deploy’s succussfully (With a message that says ‘Build Successful total time: 11 seconds.’ Both the COMM light and the driver station diagnostic lights are red.
Firmware is up to date with 3.0.0
We’ve tried re imaging the roborio with no avail.
We have not tried statically setting the ip address yet (I’ll do that now)
Though we are still trying to figure it out, any help is greatly appreciated!
Do you think it may have something to deal with the actual code? I think this is doubtful, but older code we have seems to be working.
Have you tried deploying the code without having the driver station program running? We ran into a problem like that this year also, and it seemed that always closing the driver station before deploying the code helped. If that’s not the problem you are having, I would suspect a problem with the robot code that you are building or possibly with the toolchain versions on the PC that built the code (I know you checked that already…)