-
Notifications
You must be signed in to change notification settings - Fork 41
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
Prusaslicer 2.3.0 path problem #60
Comments
Please upload the original and the welded gcode to gist.github.com, and drop a link here, thanks! |
Hope this helps. |
Looks like your visualizer doesn't correctly render arc commands. Here's how simplify3d sees your welded gcode file: So far the only slicer I know that correctly renders arc commands is simplify 3d. The OctoPrint gcode view and the pretty gcode plugin also do this correctly. ncviwer.com can mostly do it correctly, though it does have a few issues, but it will give you a general idea. |
Can you try sending a 'G2' command (empty, with no parameters) to your printer via the OctoPrint terminal and see how it responds. It may disconnect, but it won't cause any problems. Paste the response in here, thanks! |
I will after work today. Cannot access my machine at the moment. |
There's an issue logged for this at the cura github page. Hopefully it gets fixed. |
G2 says "unknown command" |
Arcs are disabled in your firmware. You will need to enable arc commands before you can use arcwelder. |
Sorry for the delay. I have tried and tried and I still get broken arcs. I cant speak to the arcs being disabled in Marlin but I have successfully printed 6 parts through Octoprint/arcwelder with no firmware changes. All Gcode viewers show broken arcs from Prusaslicer standalone Arcwelder. At this time I do not believe it is viewer problem I believe it is an issue with the standalone executable I'm using with Prusaslicer. |
Finally had a chance to check myself on simplify and sure enough! |
I have sliced a few files and I am left with this. I am not able to solve.
The text was updated successfully, but these errors were encountered: