Quote:
Originally Posted by Greg McKaskle
I'm glad you were able to capture this. I wasn't able to post last night, but the logs you posted seemed to indicate a crash. If the battery trace doesn't go away, the robot it connected to the field. The CPU goes low because the thread the code was in was terminated. Hopefully you can use practice matches and some code walkthroughs or some clever debugging to track it down.
Greg McKaskle
|
After removing the SmartDashboard we (Team 1280) performed beautifully for our next seven matches at Silicon Valley. We did not have any further crashes, either on the field or tethered in the pits.
GRT (Team 192) did get their problem resolved at Silicon Valley as well. Their symptoms were different from ours. The report I heard was they had an IP address conflict - they had an on-board laptop with the same IP address as their Axis camera. This is 2nd-hand information but I heard it from a very reliable source.
One note for those looking at their radio firmware as a potential root cause. We ran 1.21 in Silicon Valley and continued to have our issues. As Greg said, we continued to log our battery voltage and CPU usage from the robot on the driver station so communication with our robot through the field was not our issue. It wasn't until we removed the SmartDashboard that we ran consistently.
Silicon Valley is our last competition for the season so we won't have any additional information to provide this year on our performance. I hope everyone else experiencing issues is able to get theirs identified and resolved! Best of luck to the teams still competing and those headed to St. Louis!