Ringing/echo after migration to duet3d, rootcause lookup

morf

I've just replaced titan with stock extruder but same pattern is visible So I guess it has nothing to do with extrusion

Phaedrux

What does it actually look like while printing? Those vibrations seem extreme.

Can you post your config file as well just in case something is really off.

morf

@phaedrux said in Ringing/echo after migration to duet3d, rootcause lookup:

What does it actually look like while printing? Those vibrations seem extreme.

Can you post your config file as well just in case something is really off.

Hmm it looks kinda normal no wobbling, oscilations etc.
I attach the config.g

I really hope I missed something 0_1546643162195_config.g

Phaedrux

After a print if you run M122 do you see anything for hiccups or steperrors in the move section?

Wyvern

What slicer? What G-code flavor are you running? This looks exactly what happened to my stock Anycubic delta, the cause was a bug in cura, (3.5?) 3.4 and 3.6 worked fine, one thing I noted is the stock G code flavor was different than the others, not sure if that was the cause.

You should run Reprap flavor.
https://imgur.com/a/eRt4M3E

dc42

What are your E steps/mm? If they are less than about 400, try increasing extruder microstepping to 64 or 128 in the M350 command. If the M350 command comes after the M92 E command then you won't need to adjust the steps/mm, it will be done automatically.

morf

@dc42 said in Ringing/echo after migration to duet3d, rootcause lookup:

What are your E steps/mm? If they are less than about 400, try increasing extruder microstepping to 64 or 128 in the M350 command. If the M350 command comes after the M92 E command then you won't need to adjust the steps/mm, it will be done automatically.

M350 X128 Y128 Z128 E32 I0                            ;  NO interpolation
M92 X640 Y640 Z640 E812                              ; Set steps per mm

Regarding slicer i use simplify3d with Reprap firmware setup:

This is YT video during the print
https://youtu.be/h0db7zNWiL4

DaveA

Not too sure what this does in the grand scheme but you have relative extruder moves enabled in config.g but not checked in S3D. I always assumed that these needed to track together.

dragonn

S3D includes at the start of g-code proper command to switch to relative/absolute dependent on the checkbox. So I don't think this should cause any problem.

DaveA

OK, if the checkbox in S3D is unchecked is it not going to produce absolute extruder moves and if there is an M83 in config,g is the printer not going to expect relative moves?
Maybe this doesn't work as I thought.

Answered my own question. I didn't realize that S3D would output the M82 as a result of the checkbox. Learned something new.

dc42

@morf said in Ringing/echo after migration to duet3d, rootcause lookup:

M350 X128 Y128 Z128 E32 I0                            ;  NO interpolation
M92 X640 Y640 Z640 E812                              ; Set steps per mm

Using XYZ microstepping of 128 may lead to processor overload (although probably only in faster travel moves), so I suggest you reduce it to either 16 with interpolation, 32 or possibly 64. Your extruder microstepping and steps/mm look good.