Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a standard for testing #10

Open
fruzyna opened this issue Nov 15, 2022 · 0 comments
Open

Create a standard for testing #10

fruzyna opened this issue Nov 15, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@fruzyna
Copy link
Member

fruzyna commented Nov 15, 2022

We've had selfTest() for a while but never use it. Should we document a standard way to use it or create something automated?

@fruzyna fruzyna added the enhancement New feature or request label Nov 15, 2022
fruzyna pushed a commit that referenced this issue Jan 18, 2023
* Beginning to climb

:)

* make climb have code

* fixing typos

* fixing more typos

* fixing bugs still

* Praying to the software gods

* doing last commit properly this time

* pleeeeeeseee

no errors???

* getting better?

?

* work? please?

* :(

* ('~')

* (*~*)

* I give this 1/100 chance of working

* Cleanup, comments, and minor bugfix

- resetState in climbControl now calls reset state in climbMotion
- now pressing dpad stops autoclimb (so no fighting for control of the robot)
- remove extra constants
- ton of comments

* Compliance with coding standards

* Making changes

Still need to make one motor a follower.

* Make left climb motor a follower

* Fix followers, remove unnecessary encoder-related code

* Solenoids work and climb quickly.

* fix follower in WS outputs

* Retract speed is now a constant

Huge changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant