danielbrownmsm / ftc-3638-2021 Goto Github PK

so that it's standardized and makes a lot of sense to the casual reader (read: me in another year or two wondering what the h*ck stuff is)

make sure to preserve the sign

So it talks more about our robot, code structure, control loops, and team

So that we can turn off the arm+claw servo to reduce power draw and not brown out.
Also so the arm rests fully down because the arm servo's 1 is still ~25 degrees higher than it needs to be so then we can have it drift all the way down

Should hold encoder constants and other constants things

So our code doesn't freakin crash for a method we don't call.
The error is a TargetPositionNotSetException thing

so we can drive good in auto

That sets all motors to float, disconnects the servos, the whole shebang. Not sure when we'd call this tho

Uses vision/color sensor to move the wobble goal to the correct box, then goes back and moves the other wobble goal to the correct box, then parks on tape. Points: 35

so we have documentation

Moves the wobble goal to the correct position using either vision or color sensors, then parks on tape. Points: 20

Add @params and @returns and all that to all javadoc comments

Use the gyro

It should update telemetry and stuff. And also set the arm to its target. And probably other stuff as well. Linking #16

Just some assert()s in Robot.init() after everything's been set up

dpad calls setArmTarget(constants.kArmUp or whatever); and then in the loop we robot.periodic() which then sets the arm to (target - current) * kP

So that we don't brownout and lose power. Maybe limit it evenly among all motors while driving?

Values to add:

• arm position (down, neutral, wobble height)
• claw position (open/close)
• robot direction (turning right/left, moving forward/backward/left/right/diagonal left up/diagonal left down/etc.)
• distance until reach goal
• other stuff

Moves the wobble goal to box C (or B, whichever) because 33% chance of getting it right. Then parks on tape for 5 points. Possible points: 20, probably only get 5 though

As well as any blocks code, plus the blocks offline editors

Moves the wobble goal to one box, then goes back and gets the other wobble goal and moves that to another box, and then parks on tape. Points: max of 20, min of 5. Chance of 20: 66%.

Drives a distance in inches, so add some conversion methods and stuff

so we can knock powershots and then later middle goal

It should drive to the line and stop for 5 points. Maybe add a color sensor on the bottom?