I’m not sure how many people have had issues at the Bayou Regional, but we haven’t been able to have a single good match at the Bayou where we haven’t disconnected from FMS. They verified that our router remains connected, but they are saying our cRIO keeps dropping off.
We have replaced everything, and I mean everything regarding the control system. Electrically we’re good. Our best guess is that the cRIO is crashing mid match.
Here’s the thing we cannot get past. Our code works perfectly tethered and on the practice field using wireless. We can beat the heck out of our robot, and it remains connected. CPU usage hovers around 40%, memory around 40%, we have tons of flash space free. When we put our robot on the field, we’re always the last to connect to the FMS, we’ve had it drop and reconnect multiple times while the field is being setup. The field management bypassed us one match and told us we couldn’t play because they couldn’t keep a connection.
My question is why? I know we weren’t the only ones with the issue today. Kryptonite had the same problem during the same match we were in one time. Another team came to talk to FTA after the award ceremony about the same issue. FTA still claims that they don’t see any issues with their system. Maybe they don’t see any, but if our code runs perfectly everywhere but the field, that makes me believe there is a problem on the side of the code we cannot touch (cRIO Image, and FMS).
We can sometimes make it through autonomous, and during the match, our robot will come in and out of communication. We finally remained connected for at least half match in our last match of the day, and we did great.
I hate to see our kids’ work that they spent 6 hard weeks working on go to waste because of a dumb bug or glitch with the cRIO image.
I know there was a team update on ‘lightening’ code, but we’re not running anything more complicated that what we ran in 2008 on a PIC18 microcontroller, which is way less powerful than the cRIO we’re given today. We tried lightening the code during the day between matches, and we finally finished right at 7PM today. We have one match left, and it’s the only match we can try to redeem ourselves. We have no closed loop control, and I’m calling it our dumb code, because all it does is take joystick output and apply it to motors. Nothing neat, no safety interlocks, no special features. All of the hard work we worked on is useless now because of a problem that we cannot diagnose outside of the FMS system.
Honestly, I’m exhausted. We’ve spent 2 days now working on this problem. Our CTA, MJ, looked through all of our code, witnessed it working in the pit, and agreed with us that our code works. We have sat in every match so far. We have a very capable robot, and we know it. It’s so hard to accept that we basically missed every match this year for a 12 year old team.
I would also like to add that I have over a year of professional LabVIEW experience. Our code can be found here: http://www.chiefdelphi.com/forums/showthread.php?t=103902