-
Notifications
You must be signed in to change notification settings - Fork 9
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
Acceleration #5
base: master
Are you sure you want to change the base?
Acceleration #5
Conversation
…en-controldev into acceleration Conflicts: tasks/GenericRawToMotion2D.cpp
} | ||
|
||
/* handle the translational part */ | ||
uint8_t stop_translation_button = rcmd.buttonValue[_stop_translation_button.get()]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that not every input device necessarily provides buttons, so this options should be optional and deactivated on default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, that's why they are just used with acceleration mode enabled. Maybe it's a good idea to check the length of the button vector before?
…ogen-controldev into acceleration Conflicts: tasks/GenericRawToMotion2D.cpp
With the acceleration mode enabled, one can accelerate or decelerate with the analogue inputs, which is better suited for controlling comparably slow walking robots or when moving over great disrances