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

Infeasible cartesian motion causes unhandled exception #49

Open
dmcconachie opened this issue Sep 7, 2017 · 1 comment
Open

Infeasible cartesian motion causes unhandled exception #49

dmcconachie opened this issue Sep 7, 2017 · 1 comment
Labels
bug

Comments

@dmcconachie
Copy link
Contributor

We need a graceful way to catch and report problems unfeasible Cartesian motions. Right now we get a "CommandInvalidException" when a joint axis is reached, which we are not catching and handling.
@dmcconachie dmcconachie added the bug label Sep 7, 2017
@dmcconachie
Copy link
Contributor Author

Not sure if we should add more information to the motion_status message, or if we should introduce a new channel for error reporting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dmcconachie