Releases: FIRSTTeam102/Robot2026
Releases · FIRSTTeam102/Robot2026
Team102-2026-PAWAR
FMA District Centennial Event
Competition code used at the Warrington PA event (PAWAR)
Overview
Our overall results were ok, but not great. Qualification performance was consistently good, as was robot reliability. We did have a strange electrical issue and had to recover the PDH at the end of the first day, but were able to recover -- this is likely related to our issues with the Intake motor burning out.
We ended as the 17th ranked team, and were selected as the final team in Alliance 8. We lost both our Playoff matches (Alliance 1 - overall winner, Alliance 5).
Good
- Shooting directional accuracy was really good
- Reliability and durability of the robot was surprisingly good
- Intake was consistent; impacts did not damage it in a way that reduced functionality
- Drive team performance very good, especially when switching to defense
- Robot was able drive Saturday after complications Friday night
- Consistent autonomous when aligned properly
- Interaction with judges was good
Needs Improvement
- Overall shooting distance accuracy wasn't as consistent as we'd like; need to tune speed of the flywheel / zone configuration
- Cameras at the front of the robot are blocked when the hopper is full
- Auto paths could get thrown off by an impact to the robot; need to learn to monitor and continuously update the path
- We need to be able to empty the hopper completely, and faster (shoot faster)
Lessons Learned
- When setting up a SPARKMax, or adding a new one to the robot, make sure to factory reset the configurations
- Consider setting the SPARKMax configurations IN SOFTWARE so that we can overwrite previous configurations
- Power monitoring -- particularly for brown-outs -- should be standard practice; any brown-out should prompt a check of all electrical components
- Consider setting power limits on all motors to control temperature, and reduce burnout