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

Wrong bounding box calculated, caused by G2 in ZX plane (OK in CNCjs) #36

Open
Billiam opened this issue May 4, 2022 · 0 comments
Open

Comments

@Billiam
Copy link

Billiam commented May 4, 2022

The X/Y min/max range can report incorrectly for shopfloor tablet on some files, and I've tracked it down to vertical arc lead out moves:

Here's a minimal example, extracted from a facing operation:

G90 G94
G17
G21

(Face)
S16000 M3
G54
G0 X146.905 Y0.418
Z15
Z5
G1 Z0.435 F1000
G18 G3 X146.27 Z-0.2 I-0.635 K0
G1 X142.986
X-0.244 F1430
G17 G2 X-0.244 Y2.396 I0 J0.989
G1 X142.986
G18 G2 X143.621 Z0.435 I0 K0.635 F1000
G0 Z15
G17

Shopfloor tablet reports this having file having a range of: X: -1.23 - 146.91, and Y: 0.42 - 146.91.
CNCJS correctly reports this as X: -1.233 - 146.905, and Y: -0.418 - 2.396

The last curve: G18 G2 X143.621 Z0.435 I0 K0.635 F1000 ends up getting converted to start coordinates of x: -0.2, y: 142.968, z: 2.396 by the G2 handler, causing the wrong bounding box for the Y axis.

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