Skip to content

Interface the drivetrain class #2

Description

@Lock-The-Door

The drivetrain code constantly freaking out is really concerning.

To prepare in advance, we should create a drivetrain interface with the same existing functions already implemented so we can easily swap out of the okapi lib if we need to.

As of writing this, the only important part of the class is the drive function which takes in two controller values to implement arcade drive and a getVelocity function which returns the current velocity.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions