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

[ARC SUPPORT not true] (Failure with G2/G3) #33

Open
electric-m opened this issue Feb 9, 2021 · 8 comments
Open

[ARC SUPPORT not true] (Failure with G2/G3) #33

electric-m opened this issue Feb 9, 2021 · 8 comments

Comments

@electric-m
Copy link

Bug Description

Installed to Hex File on a Anycubic Mega-S in wanted to use the Arc Welder plugin which needs Arc Support.
G2/G3 commands give out an error, which should mean that Arc Support isnt enabled at the firmware.
I checked the Code in the Configuration_adv.h file at line 1631 and it looks like it should be enabled.
Are there any additional steps, that need to be made?

@electric-m
Copy link
Author

@FormerLurker
Copy link

What version of Marlin is this fork based on? There have been quite a few updates to the interpolation algorithm recently that fix several glitches.

@electric-m
Copy link
Author

What version of Marlin is this fork based on? There have been quite a few updates to the interpolation algorithm recently that fix several glitches.

I am only able to see that the base is something like 2.0.x, which isn't really helpful.
I found out though that a blank G2/G3 command leads to a connection error.
However if I specify a movement with G2/G3, it is carried out correctly.

The compressed Gcode is printed pretty good, but compared to the original, there are slight imperfections.
Gcode looks weired in gcode.ws as well.

@FormerLurker
Copy link

I don't want to get too much off-topic, but most viewers don't support arcs. Those that do often have issues, like low resolution. Try simplify 3d or the PrettyGcode viewer in OctoPrint.

The imperfections could definitely be due to missing fixes in the upstream branch. If I have some time I'll take a look at the version history for the interpolation code and will see what I can find.

@electric-m
Copy link
Author

Right, S3D showed the Gcode correctly, according to the corresponding STL.
I must admit though, that I probably did not choose an ideal model to test arcs.
It's a mostly suqare nameplate with letters in it.
What model would be suitable to make some tests?

@FormerLurker
Copy link

What model would be suitable to make some tests?

The letters should be an OK test. I like using (surprise surprise) benchy to test quality, but some of the detailed miniatures of people/superheroes/monsters, etc are typically a good torture test since they are mostly random organic shapes.

@electric-m
Copy link
Author

electric-m commented Feb 11, 2021

I will print two Benchys. One without Arcs, another after Arc Welder applied.
Am I supposed to actually see a difference when viewing the Gcode in S3D?
Because I think I cannot.
Benchy gets compressed by about 38%, but the toolpaths look pretty much the same to me.

Benchy-no-arcs

NO ARCS -------------------------------

Benchy-AW

AFTER PROCESSING WITH AW

@FormerLurker
Copy link

Benchy gets compressed by about 38%, but the toolpaths look pretty much the same to me.

This doesn't appear to be related to this issue. However, the whole point of arc welder is that you shouldn't be able to tell the difference between the toolpaths of the welded and original file. This may or may not translate into quality improvements. However, if the firmware is bad at generating arcs, then the quality will suffer.

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

2 participants