We missed our first match since 2009 on Friday, because of corrupted code crashing the Rio.
We found the problem after placing the robot on the field. My drive team were told that if we had a Rio 2 we could put in a new SD card and reboot (which would have required removal of a belly pan and inversion of the robot). But we could not take the 2-3 minutes to tether and deploy code because of the no tethering rule. We have a Roborio 1. In fact we have 6 or 7 of them, and this seems like a fairly inequitable rule set up for many teams who have a very substantial investment in Rio 1s.
Was the rule applied correctly? Can it be improved?
I am confused a bit. I missed the no tethering rule. We tethered and deployed code twice in cue week 1. Were we in violation of something? That I missed?
On a solution based note, if you are running CAN almost exclusively, swapping the whole Rio should not be too difficult if you design for it moving forward. You could back up the same way. I know it is of small consolation though.
Oh, I guess I understand that. In that event, there may not be time to swap a Rio then either. I am truly sorry and cannot think of another workaround save for a change of the rule to level the playong feild.
Nope, it’s been like this at least since I started in 2017. Look at R704 this year, it details what ports are open between the driver station and robot on the field.
To simulate this at home, check the “enable firewall “ checkbox when flashing your radio.
Did whoever told you that you could replace the SD card know that you had to remove the belly pan to do so? That would seem to fall under H301.
It would also depend on you having an SD card with your latest code on it, which would require that you have a second roboRIO 2 or were swapping cards in your main roboRIO frequently, which has its own host of problems.
You need permission from either a FTA or a referee to tether on the field. Otherwise, it’s a yellow card.
Though, this seems strange. Whomever was telling them this was almost certainly the FTA and has to know they can provide permission to tether to push code.
You’re likely remembering pushing code wirelessly at your shop. You CAN do this. You cannot push it through the FMS at an event. You must tether at events to push code. It’s the difference between the radio config you do at home versus at an event.
Is there any reason the rio is so enveloped or is that just where it fit best with this year’s design? Though, as others mentioned, it sounds like the FTA didn’t notice this when suggesting they’d be ok with the time to swap the SD card versus the time to deploy code.
Etcher does allow you to copy an image. So, if you had recent code on an extra SD card, you could technically swap them and participate in the match (assuming your workflow allowed for this; no changed CAN Ids/dio assignments).