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.

Sign up for GitHub

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

Jump to bottom

Motion profile state produces no motion #1

Open
JonathanZwiebel opened this issue Jan 27, 2017 · 1 comment
Open

Motion profile state produces no motion #1

JonathanZwiebel opened this issue Jan 27, 2017 · 1 comment
Assignees
@JonathanZwiebel
Labels
bug

Comments

@JonathanZwiebel
Copy link
Owner

When using the Drivetrain in the MOTION_PROFILE state, the motion profile command is only run for fractions of a second. FIRSTHelpNow was contacted and was able to isolate the issue to our structure.
@JonathanZwiebel JonathanZwiebel self-assigned this Jan 27, 2017
@JonathanZwiebel
Copy link
Owner Author

Believed issue is that output velocity is too slow. The motion profile generator took input values as RPM when desired unit may have been tics/minute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JonathanZwiebel JonathanZwiebel

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JonathanZwiebel