We have had more problems with the Rio this year than we’ve ever seen before. In our first competition, a Roborio 1 that had been working fine decided that on boot, on the field, it would start crashing while loading code over and over again. Power cycling did not fix it, and it required us to connect to the Rio via USB and redeploy code once in the pits.
We’ve seen it happen twice now in two days - and this is with a different robot and Rio 1. The robot can be fine. We change a battery, or power cycle, and it goes into this boot loop.
I’m concerned it might happen at our competition (again) and we are planning on having multiple roborios with code deployed that we can drop in.
Has anyone seen similar behavior?
The only thing I can think of that we are doing that we haven’t done is using labview to open config files. In the past we always used text files. But that doesn’t seem like it should cause this problem, and it works fine 98% of the time.
Want to share your code in case we can repeat the issue?
What firmware is on that RIO 1?
No. We have no problem deploying code initially. We can run indefinitely on that code without a problem. Then, on some random power cycle, it will start crashing over and over. Because of the crashing, the roborio cpu never enters a state where we can connect over wireless/ethernet, and forces us to connect via USB. Even then, it will take 3 or 4 tries before we can get in between the ‘reboots’ to deploy code.
1 Like
It has the newest firmware. We are uploading our latest to github.
I’m sure it’s the newest.
There are however two current versions.
One for the roboRIO 1.0 (6) and another for the roboRIO 2.0 (8)
They will both work on a RIO 1 to a point. It’s the point where it stops working that can be aggravating.
Which version of the firmware are you running?
Verified just now, roborio version 4. (Not roborio 2).
This one.
Hopefully that’s v4.0 of the image not the firmware.
In this picture the Image is v4.0
The firmware is version 6.0.0f1
We want to look at the listings on the left side.
The project is missing some dependencies:
- SWERVE_DRIVE_ODOMETRY.ctl
- PathPlannerTrajectory.ctl
- SWERVE_DRIVE_KINEMATICS.ctl
- Util_GetTime.vi
- etc
Is there a vendor library I need to download?
Jsimspso’s trajectory library. We use it because it has easy access to the FPGA high precision timer (which we didn’t know how to access until he released it). We also were using it for trajectory running early on, and plan on returning to it once the season is over for more development.
Sure enough! Firmware version 8 on a roborio 1.
installing the correct firmware and reimaging it now.
1 Like
It’s such a simple thing sometimes… 
Be careful, there are still bugs out there…
My controls lead is currently complaining because the firmware aren’t labled as roborio 1 and roborio 2. I told him to read the directions next time =).
Well, that was short-lived. Reimaged, reformatted, and on the third reboot it’s back in a boot loop.
I’ll try running your code here.
Added Jim Simpsons library, but still missing:
- PathPlannerTrajectory.ctl
Sound familiar?
It may be due to a specific version of the trajectory library.
There are two installs on that path planner page. I believe you need both.
Both 2020 packages.
Did you create this auton scripts file? Can you send me a sample one to load?
/home/lvuser/Auton ScriptsLabVIEW
I’m getting a bunch of errors when running it that I have to track down.
Some are just the specific CAN IDs missing since I don’t have all your devices, or set to the same CAN IDs.
Others are missing RefNums
How are you rebooting to get the error? Power cycle or the DS “Reboot roboRIO” button?
The scripts are csvs located in the disabled/auton/scripts directory or near there. The configuration files are on the disabled/config directory I believe.
We power cycle (main breaker) and it sometimes happens, sometimes doesn’t. We have seen it 3 times in two days.
