SharpAI
/

what have teams discussed about swerve drive in ftc

Teams and documentation discuss several aspects of swerve drive in FTC, ranging from hardware implementation to software kinematics and community showcases.

A swerve drive system requires a high number of encoder inputs, specifically needing two encoders per module: a quadrature encoder for the drive motor's position and velocity, and an absolute encoder for the steering motor's angle . For example, an OctoQuad can be configured to manage these inputs for a four-module swerve drive by reading four relative quadrature encoders and four absolute pulse-width encoders .

Several community discussions and technical resources cover FTC swerve drive topics:

  • A reveal of an independent suspension coaxial swerve drive is shared on Chief Delphi 1.
  • The utility and effectiveness of swerve in FTC is debated in a thread discussing whether FTC swerve is useless 2.
  • A swerve showcase comparing FTC and FRC implementations by team ARES, FTC #23247, is available on Chief Delphi 3.
  • Technical implementation details for swerve drive kinematics are hosted in the FTCLib documentation 4.
  • Swerve drive odometry is also covered in the FTCLib documentation 5.
  • Calibration procedures for swerve modules are detailed in the REV Robotics documentation 10.
Was this right?

Generated from indexed documentation and can be wrong — check the source beside each claim. Follow-ups are not saved. Unofficial, not affiliated with FIRST. Quotes Game Manual 0 (CC BY-NC 4.0) and FTC Docs (BSD 3-Clause). Built by Sharp Face Robotics.