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

Suggestion suggestion: Motor subsystem implementations with supervised mode #66

Open
dandeduck opened this issue Mar 22, 2021 · 7 comments

Comments

@dandeduck
Copy link
Member

Add some subsystems or interfaces (or options for existing things e.g. rotateable) that will allow built in guaranteed supervised behavior. e.g. don't cross certain angle or speed. (could just receive a supplier)

I can implement it if you think that it's a good idea.

@tomtzook
Copy link
Member

Sounds interesting. Do you have any examples from the past few years where it could have being useful?

@dandeduck
Copy link
Member Author

It's useful for both automated and manual control schemes. These things are anyway used in manual mode (controlling an arm or driving) and in automated mode we also need to supervise it somehow. Specifically in 2017 we had arm that wasn't limited mechanically enough so it was also limited by code. It's useful to use both anyways

@tomtzook
Copy link
Member

Okay sure go ahead

@dandeduck
Copy link
Member Author

Ok, but should I just do supervised moveables, and systems? and drives? or did you have something else in mind/.

@tomtzook
Copy link
Member

I don't really have any ideas. But maybe something will come up after you open something.

@dandeduck
Copy link
Member Author

I don't really have any ideas. But maybe something will come up after you open something.

passive aggressive? ok I'll do something

@dandeduck
Copy link
Member Author

oops

@dandeduck dandeduck linked a pull request Mar 25, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants