Quote:
Originally Posted by sanddrag
Can you elaborate on the problem and fix? We had issues too, where our controller would reboot or something upon field connection, causing our arm's encoder position to be lost prior to the start of the match.
|
The issue Code Orange had with their robot was related to a timing issue in Cheesy Arena during autonomous. There was a specific WPILib timing function that was not receiving the right inputs from the FMS (the GetMatchTime function). Most cases I've seen that use that function use it during teleop to detect the end of the match, which was correct. However, this has been fixed in Cheesy Arena, so Beach Blitz and Capital City Classic should not have this issue.
Regarding the e-stop issue, we are still working with FIRST to try and detect the cause and institute a fix. Our plan during Beach Blitz if we see it is to immediately replay the match, as the issue pops up right at the beginning of the match.
__________________
All statements made are my own and not the feelings of any of my affiliated teams.
Teams 1510 and 2898 - Student 2010-2012
Team 4488 - Mentor 2013-2016
Co-developer of
RobotDotNet, a .NET port of the WPILib.