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

Possible bug in interpreter with rotary axis find_ends #32

Open
ArcEye opened this issue Aug 2, 2018 · 0 comments
Open

Possible bug in interpreter with rotary axis find_ends #32

ArcEye opened this issue Aug 2, 2018 · 0 comments

Comments

@ArcEye
Copy link
Collaborator

ArcEye commented Aug 2, 2018

Issue by dkhughes
Fri Dec 29 22:45:44 2017
Originally opened as machinekit/machinekit#1339


This is kind of an edge case thing, but I found it digging through the interpreter files.

When the rs274 interpreter calculates the end point for a non-wrapped rotary axis in a G53 move, it does not include a tool offset value. For every other case, including the wrapped rotary condition, the tool offset is included.

A tool offset A, B, or C value seems strange, but if this type of tool offset is supported then I think the nonwrapped rotary case should be updated to include the angular tool offsets as well. Or, the wrapping case should be updated to ignore the angular tool offsets and be consistent.

Any thoughts? Does anyone know if this behavior is by design and what reason there would be for the disparity?

Here is a link to the code in question:

https://github.com/machinekit/machinekit/blob/master/src/emc/rs274ngc/interp_find.cc#L196

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

No branches or pull requests

1 participant