Quote:
Originally Posted by nathannfm
It looks like I missed the back story here. If it's not too painful would someone from 2169 mind recounting their season of swerve and what problems you had with it for other teams who are dead set on at least trying swerve as an off season project so they may learn from your season?
|
We used the "Wild Swerve" modules from Team 221 robotics parts. We did not order them prior to build season. I think they were ordered by the end of week 1. Arriving mid week 2, we assembled them and attached them to our drive base. Our programers were coding prior to receiving the modules, confident in their code. We implement the code, not up to snuff. We keep editing and revising, problems arise left and right (using 3D printed encoder mounts was one of said issues.) We focused so much on our swerve that other mechanisms suffered. We over complicated the code, and the start up routine for each match (we had a "hard zero" button to "reset" the encoder values to 0) and in the end we didn't move for half our regionals. My advice is do your trouble shooting and learning before the build season, and only implement swerve for the build season if you already have a polished code for it, and have designed and planned the mechanical implementation of the drive before kick-off.