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 skeleton for climb mechanism #28

Open
james-ward opened this issue Jan 8, 2025 · 3 comments · May be fixed by #33
Open

Create skeleton for climb mechanism #28

james-ward opened this issue Jan 8, 2025 · 3 comments · May be fixed by #33
Assignees

Comments

@james-ward
Copy link
Contributor

Add a basic component and state machine. Can be blank for the time being, but it will get us ahead of schedule later.

@LucienMorey
Copy link
Contributor

The climber component will likely comprise 7 methods at the very least.

  • The constructor
  • something to deploy
  • something to retract
  • something to check if we have deployed
  • something to check if we have retracted
  • something to read out the current position
  • the execute method

There may be more if we incorporate some sensing into how we have grasped the cage, but lets not get ahead of ourselves just yet.

The state machine can go through deploying and retracting states in its most basic form. This may turn out to be a little clunky once we better understand the mechanism but at least we have a starting point. See if you can work out what the end conditions for deploying and retracting are 😉

@auscompgeek auscompgeek linked a pull request Jan 15, 2025 that will close this issue
@LucienMorey
Copy link
Contributor

We now have duplicate PRs dealing with this.

We need to decide which one of these things we are keeping and close the other.

@Hik-ari @DannyPomeranian

@65-7a
Copy link
Contributor

65-7a commented Jan 19, 2025

we've chosen to use @Hik-ari's #33, but need to move the motor code from #62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants