Recently, one of our roboRIOs has had an issue with getting it running. We code in Java, and we can successfully upload code to the RIO. However, for whatever reason, the Comms light on the roboRIO alternates between red and green, and on the Driver Station, the status indicator alternates between “Teleoperated Disabled” and “No Robot Code”.
In my efforts to find a simple solution, I tried many different methods of updating the roboRIO. I ran the RIO in Safe Mode, updated the firmware to the latest version (version 3.0), reimaged the RIO (FRC_roboRIO_2017_v8.zip), and installed the Java 8 JRE to the RIO. Sadly, none of these methods solved the problem.
I have checked on the forums for any threads related to my problem, and the most recent thread that was even close to it was for a cRIO from 2012. If anybody else has experienced this problem and has any potential solutions, I would greatly appreciate the help.
We’ve had the same issue in the past when our vision thread caused a crash. The roboRIO ends up trying to continuously restart crashing code, causing the cycle between disabled and no robot code.
Have you tried checking the driver station logs? That might help narrow down the cause of your issue.
I’ll look into it once the team meets again. I’ll send an update if I find anything, thanks for the suggestion. Understand that I think the problem is with the roboRIO, because this has happened with multiple different Java projects, so I don’t think the problem is linked to the code.
I can confirm that we have also had this issue due to robot code continuously crashing in init(). Perhaps try deploying some of the default code projects and see if the problem persists?
Thanks for the help guys! I checked the driver station logs and it turns out the code was calling a Gyroscope that wasn’t connected to the roboRIO. I reinstalled it and it started working. You gotta stress the small stuff!