Problem printing circles

3DOeste

I just looked at your config.g and I don’t think low jerk values are your problem. I think I’m using the same values...

dc42

I assume you are printing from SD card. The usual reason for this type of issue is that the XY jerk is set too low for the print speed.

OBELIKS

@t3p3tony I will try Cura tomorrow. I don't like setting it up, but I will try. But I know that S3D gives more or less the same results. It's a bit annoying, that the old Anet board gave me no problems like that. But I hope we can get this sorted out.

T3P3Tony

@obeliks try @dc42 and @3DOeste 's suggestions of increasing Jerk first.

OBELIKS

@dc42 I actually went from 20mm/s to 15mm/s just to check. It is also true that it was even worse with my old configuration (I havent stored it. I will check, but I think it is gone). Then the circles were flat on top and bottom.
What jerk setting would you suggest?

dc42

@obeliks said in Problem printing circles:

@dc42 I actually went from 20mm/s to 15mm/s just to check. It is also true that it was even worse with my old configuration (I havent stored it. I will check, but I think it is gone). Then the circles were flat on top and bottom.
What jerk setting would you suggest?

The default value of 600mm/min works well for many users, but some users increase it to 900 or even higher.

OBELIKS

I have them at 900 st the moment. I will make a test tomorrow with 1200 and 600, so we can see the difference. And with Cura.

deckingman

@t3p3tony said in Problem printing circles:
...................

quite small moves

Can you try using another Slicer as a test to see what difference it makes? I note this is Slic3r Prusa edition version 1.40.1, so maybe try Cura to see the difference?

@deckingman I know there is no pressure advance involved but is this related to the issues you are seeing?

There are certain similarities for sure - although I only see it with pressure advance enabled. I've discovered that increasing extruder micro-stepping to 256x from 16x is a work around for my issue, so it would be interesting to know if doing the same has any effect on the OP's problem.

OBELIKS

That is another thing that I have problems with. If I try to give command "M350 X256 Y256 Z256 E256 I0" I get something like "Drive E0 does not support 256 microstepping"
I will try this and the rest when I get home from work.

deckingman

@obeliks said in Problem printing circles:

That is another thing that I have problems with. If I try to give command "M350 X256 Y256 Z256 E256 I0" I get something like "Drive E0 does not support 256 microstepping"
I will try this and the rest when I get home from work.

That's weird, but try this. Leave everything in your config.g as is but add M350 E256 at the end of your drive section (after the M84 command). This will mean that the steps per mm are first calculated using 16x microstepping, then when you add that line, the micro-stepping will be changed x 256 and the steps per mm for "E" will be automatically recalculated.

You're not using external stepper drivers are you?

OBELIKS

No.
I will try this also. But this should work from gcode console also?

Catalin_RO

@dc42 RRF configurator default max jerk is 15mm/s, hence 900mm/min! Maybe 600mm/min is the default firmware value, but any config.g file generated with the configurator will have it overridden. I'm going to experiment a little bit with the idea, by increasing from the current 300mm/min in 50mm/min steps.

deckingman

@obeliks said in Problem printing circles:

No.
I will try this also. But this should work from gcode console also?

Yes

OBELIKS

@deckingman said in Problem printing circles:

@obeliks said in Problem printing circles:

That is another thing that I have problems with. If I try to give command "M350 X256 Y256 Z256 E256 I0" I get something like "Drive E0 does not support 256 microstepping"
I will try this and the rest when I get home from work.

That's weird, but try this. Leave everything in your config.g as is but add M350 E256 at the end of your drive section (after the M84 command). This will mean that the steps per mm are first calculated using 16x microstepping, then when you add that line, the micro-stepping will be changed x 256 and the steps per mm for "E" will be automatically recalculated.

You're not using external stepper drivers are you?

So first this one, as I said, if I put this in to G-Code Console, I get this error (bug?):

M350 E256
Error: M350: Drive E8 does not support 256x microstepping

But it works if I put it in to config.g exactly as you suggested:

M350
Microstepping - X:16(on), Y:16(on), Z:16(on), E:256:256:16:16:16:16:16:16:16

The result was slightly better. But there were still audible judder.
Setting them all to x256 also did not help more.

Setting jerk to 1200 or even 1800 makes no real difference.

I will test Cura later

deckingman

@obeliks said in Problem printing circles:

So first this one, as I said, if I put this in to G-Code Console, I get this error (bug?):
M350 E256
Error: M350: Drive E8 does not support 256x microstepping
But it works if I put it in to config.g exactly as you suggested:
M350
Microstepping - X:16(on), Y:16(on), Z:16(on), E:256:256:16:16:16:16:16:16:16

.....................

That error message does rather look a bit like a bug as you don't have a drive E8. Anyway, it doesn't seem to have resolved your problem but it was worth a try.

DocTrucker

Similar issue to something I experienced. Tested with and without pressure advance and as was and increased Jerk. Increased jerk smoothed things out, pressure advance had comparitively little effect.

https://forum.duet3d.com/topic/5834/core-xy-judder-slowdown-on-circle/18

OBELIKS

Before I waste any more of our time, is there any option to make a fresh start on the board?
Would the erase button do that?

JoergS5

@obeliks Erase is not good, because you erase the firmware. You should update your config files with your original files which you created with your online configurator. Through DWC.

OBELIKS

Someday I will try the nuclear option, and I will push the erase button.
But for now I found a workaround, if anybody else has these problems.
In Slic3r go to Print settings -> Advanced and under resolution put in 0.1mm.
I will do some more tests, but this cured the problem.
Mostly. Printer runs smoother, but there is still some ringing on circles.
So I would like to see a better solution someday.

And just to be clear,

Jerk settings were at 1200mm/min at start, I then lowered them to 900mm/min to check, and later even went to 1800mm/min. This did nothing.
I changed microstepping to x256, this helped a bit, but not enough.
Cura seems to do OK, but I do not like it. I will try to set it up.
I generated and uploaded config from the configurator a couple of times, no difference.

If you have any more ideas besides that, please tell me. I will also try with a different SD card, just to eliminate this from the list of possible problems.

But from my observations, DuetWifi just can't handle the Slic3r files with full resolution. At least for me. It looked like it needed some time to catch up with what was passed on. That is also the reason I was thinking of erasing the whole firmware. Maybe something was not uploaded right.

deckingman

@obeliks said in Problem printing circles:
..............................

But for now I found a workaround, if anybody else has these problems.
In Slic3r go to Print settings -> Advanced and under resolution put in 0.1mm.
I will do some more tests, but this cured the problem.
Mostly. Printer runs smoother, but there is still some ringing on circles.
So I would like to see a better solution someday.
....................................

But from my observations, DuetWifi just can't handle the Slic3r files with full resolution..................................

Now that is a very interesting observation. Maybe, just maybe, it might also explain the problems I've been having with curves and pressure advance. I'm stuck in the middle of something that prevents me doing any printing right now but I'll try this at the first opportunity. I haven't played around with the resolution option with Slic3R, leaving it set to the default 0 which effectively disables any simplification. For anyone else not familiar with slic3r, the pop up description of the resolution option in slic3r is quote:

"Minimum detail resolution, used to simplify the input file for speeding up the slicing job and educing memory usage. High-resolution models often carry more detail than printers can render. Set to zero to disable any simplification and use full resolution for input. (default: 0)."

End of quote.

Strange choice of words in that quote...........