frc5687 / frc5687/2018-switchbot

Rework center 1 cube auto using Talon Motion Profile Control Mode

Open
#17 0 comments 0 reactions 1 assignee Claimed by @deslobodzian View on GitHub
Dominant language
Java
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Talon Motion Profile Control Mode is a slightly more complex approach to motion planning, but it's faster and smoother because the computation is offloaded to the Talon SRXs. More information is available on the [CTRE website](https://github.com/CrossTheRoadElec/Phoenix-Documentation/raw/master/Talon%20SRX%20Motion%20Profile%20Reference%20Manual.pdf). The trajectory can still be generated using Pathfinder, or it can be generated using the CTRE spreadsheet. The key difference here is that the generated profile is sent to the Talons instead of using a DistanceFollower.

The basic task is the same as #16 :
Currenty, the center auto is handled using a series of straight runs and in-place turns by buildCenterLeftCube and buildCenterRightCube. For this task, you should start by creating duplicates of those two functions (buildCenterLeftPath and buildCenterRightPath) and replace the initial approach steps (Attack1, left 22deg, Attack2, and face switch) with a single Pathfinder trajectory. This trajctory can consist of just two waypoints: 0,0,0 and -48, 134, 0.
More about Pathfinder can be found on Jaci's wiki.
For background on motion planning, please watch Team 254's video.
The example in our AutoDrivePath class uses Pathfinder, but it should be a good starting point in combination with the examples from the CTRE documentation.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.