-
Notifications
You must be signed in to change notification settings - Fork 62
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
Gcode Curve Support? #28
Comments
No, it doesn't support these. |
Would you be willing to add them? G02 and G03 are just circular arcs, so they should be fairly easy to implement. The difference in print quality just from Arc Welder is pretty spectacular, and that is just from approximating the original curves. |
Honestly I can't really see segments in the lines. Why would you want G02 and G03 if the results from this script are already nice and sharp? Also, I think it's more work than you may think. |
Here are a few reasons:
and, finally and most importantly,
Does that make sense? |
I expect that not all 3D printers support these gcodes. Moreover, a lot of the time what comes out of Inkscape or other svg drawing programs will be splines, not actual arcs, so I think the utility will be limited to cases where the user took care to ensure there are arcs. But most importantly, I think this is just begging for bugs. Getting these gcodes right is finicky, and there are multiple cases to get right, and I think it's safer to just deal with lines. You can get whatever precision you want by upping the precision in the generator. Granted, it will make the files bigger. |
I was searching for a gcode exporter for Inkscape so I can print smooth lettering/etc. and came across your project. I don't code well enough to be able to parse your code, but does it support the G02/G03/G06.X commands that generate curves for the hardware to interpret? That would both make the resulting gcode MUCH smaller while making the fabricated part match the original artwork MUCH better.
Here is the video that introduced me to the commands: https://youtu.be/18uYYXecH5g
The text was updated successfully, but these errors were encountered: