-
Notifications
You must be signed in to change notification settings - Fork 4
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
[BUG] Toolpath generation #59
Comments
Current gcode:
Correct Gcode:
|
If that's a 2d contour pocket using clipper then there should be a transition cut from one contour to another as well instead of a full retract like here Can't triage based on this though whether it's from your changes or whether the current implementation is just unreliable. Looks like there is NO test for this feature though, my bad. |
Yeah I have been playing with the code yesterday and removed various functions from router.py to see their effect and I finally understood what shift_edges() does. Wouldn't a better strategy be to always transition on wire corners (or the start point to be more accurate since arcs and splines won't have corners)? So this is the previous design but with the bug I introduced fixed: This is a second one that uses the shift_edges() function: In my head this seem like a better presentation: The Am I missing something? @voneiden |
Don't quite follow that one, closest point should be the shortest path, no? Anyway, my assumption has been that horizontal ramping is going to require being able to start the next contour/path from an arbitrary point so from that perspective the current implementation serves as preliminary work. |
I just checked the state of the code for the changes that I did so far and I noticed a couple of bugs.
Toolpath generation introduces:
The text was updated successfully, but these errors were encountered: