Prusa Slicer Horrible movement noise. A350

Hi All,

I’m hoping someone can help me out with some horrible stuttering movement amd sounds that are happening with my ol’ A350. I wanted to try out Prusa Slicer after having some issues with others. So I downloaded the current version 2.9.4, and used the built in Snapmaker 2 profile with Dual head.
I adjusted filaments and tried to print a small thing for starters.

The start g-code functions at the beginning went normally. The head zipped around the bed and started to do its heating, priming, and tracing the bed perimeter bla bla bla. All that was just fine.

But once it started to print, as you’ll see In the video, the travel and print movements are horribly stuttery and sound absolutely awful. (plz ignore the bed mess and image blur, I haven’t been able to finish calibrating and phone’s camera is cracked :/…)

I taped a piece of spring steel onto the head to help visualize the stuttering on at least the Z-axis.

This hasn’t happened in any other slicer that I’ve tried. I’ve rebooted, and tried previous G-Code from other slicers and those print just fine. Tried the Prusa again and got the same result.

I went back into Prusa and changed some of the max speed settings thinking that it was just forcing it to go to fast or something and enabled “Emit limits into G-Code” since it wasn’t by default. and still no change.

I’m barely a lvl 1 g-code/firmware user. So I am out of my depth and at a loss on why this may be happening. More than happy to upload any other info that would be helpful.

I couldn’t tolerate listening to my dude sound like this, so I stopped after the first layer. It looks “good” but you can see odd movement lines and artifacts in the layer as evidence of whatever this was.

Thanks in advance, and Happy New Year!

Also, in case you’re curious why I’m trying Prusa. I’ve gone through the big players and run into problems with them;

1 - Luban - Terribly limited in functionality and options. Also crashes for me.
2 - Cura - My preferred slicer, but I’m getting missing Z-Steps issues exactly like Snapmaker 2.0 Printing Defects - Z Feed Rate too high - Skipping Z steps · Issue #13420 · prusa3d/PrusaSlicer · GitHub that I can’t figure out. And I thought Prusa slicer would help as it was patched in the ticket in the link.
3 - OrcaSlicer - honestly, overwhelming for me. Settings layout is confusing. It also seems to ignore some of my changed settings. (not fully given up on this one yet!)
4 - Snapmaker ORCA - Unstable for me, crashing and pathing issues, printer freezes up mid print with it’s g-code files.
5 - Simplify3D - I’m a cheap bastard.

Hi,

I dont think it is slicer related. For me it looks and sounds like a faulty y axis. I would suggest to disassemble the machine and check the y axis, especially the sliders there: https://wiki.snapmaker.com/en/Snapmaker_2/troubleshooting/slider_comes_loose

Thanks for the reply!

I thought so too! But I went back and tried it with the other slicers after this came up. Their g-codes don’t cause this. It’s been quiet and smooth if I use Luban, Cura or even Orca. Tried Prusa again, and right back to this again. Took a video of it running that same model but from SMOrca (with wife’s phone for better camera!) and it sounds fine. It’s got to be a setting in Prusa somewhere, but I have no idea what.

Run the same print again please and increase the working speed in the live menu.

I think to hear sometimes also noises when y axis movement is switching from back to front.

Post your machine settings please.

Enter M503 in the terminal console and copy the output here.

As I see you checked the emit settings to gcode, this would not save the settings so after restart the old value (whatever it is) would be active again.

I agree with the possibility of an faulty axis.

I also hear a clicking extruder but not really sure about..

Here’s the M503:

I’m glad you guys mentioned the rails, I’m tempted to go through the steps here to check for backlash/rail slop issues. https://wiki.snapmaker.com/en/Snapmaker_2/Linear_module#step2-adjust-the-nut-to-eliminate-the-backlash.

A great suggestion! :slight_smile:

M503
ok
others < G21 ; (mm)
others < M92 X159.87 Y160.67 Z401.04 B888.89 Current E676.35, BACKUP SINGLE E212.21, BACKUP DUAL E676.35
others < M203 X120.00 Y120.00 Z20.00 E45.00
others < M201 X1100.00 Y1000.00 Z500.00 E3000.00
others < M204 P800.00 R1100.00 T1000.00
others < M205 B20000.00 S0.00 T0.00 P0.05 L3.00 C0.05 J0.25
others < M206 X-32.00 Y-23.00 Z0.00
others < M218 T1 X26.00 Y0.00 Z-1.576
others < left_z_compensation: 1.00 right_z_compensation: 1.00
others < M420 S1 Z0.00
others < G29 W I0 J0 Z43.84486
others < G29 W I1 J0 Z44.21514
others < G29 W I2 J0 Z44.52683
others < G29 W I3 J0 Z44.74003
others < G29 W I4 J0 Z44.91208
others < G29 W I5 J0 Z45.13026
others < G29 W I0 J1 Z44.07301
others < G29 W I1 J1 Z44.44829
others < G29 W I2 J1 Z44.74626
others < G29 W I3 J1 Z44.93577
others < G29 W I4 J1 Z45.12154
others < G29 W I5 J1 Z45.23748
others < G29 W I0 J2 Z44.06429
others < G29 W I1 J2 Z44.42709
others < G29 W I2 J2 Z44.68517
others < G29 W I3 J2 Z44.84475
others < G29 W I4 J2 Z44.97566
others < G29 W I5 J2 Z45.12278
others < G29 W I0 J3 Z43.99446
others < G29 W I1 J3 Z44.31364
others < G29 W I2 J3 Z44.58668
others < G29 W I3 J3 Z44.72257
others < G29 W I4 J3 Z44.80236
others < G29 W I5 J3 Z44.89463
others < G29 W I0 J4 Z43.87976
others < G29 W I1 J4 Z44.12912
others < G29 W I2 J4 Z44.30989
others < G29 W I3 J4 Z44.43457
others < G29 W I4 J4 Z44.53930
others < G29 W I5 J4 Z44.61909
others < G29 W I0 J5 Z43.65160
others < G29 W I1 J5 Z43.83114
others < G29 W I2 J5 Z43.96953
others < G29 W I3 J5 Z44.08922
others < G29 W I4 J5 Z44.20641
others < G29 W I5 J5 Z44.27998
others < M301 E0 P150.00 I1.00 D30000.00
others < M301 E1 P13.00 I0.10 D17.00
others < M851 Z0.00
others < M900 T0 K0.03
others < M900 T1 K0.02
others < Z1.00
ok

Nothing really obvious here, it should be also more acceleration possible..

Would you mind to share the GCode that causes the awful noises?

Absolutely! Here it is. I tried it again by slowing down some speeds and making those changes i screenshot earlier if you want to see that too. This was the first, and the one from the videos.

Snapmaker_Mount(1).gcode (808.5 KB)

The GCode motions look sane and fine to me - what may be a problem are these lines at the beginning of the GCode:

M201 X1100 Y1000 Z500 E3000
M203 X150 Y150 Z40 E45
M204 P1100 R1100 T1100
M205 X5 Y1 Z1 E3

These modify the motion parameters, and may be a reason for the noises. I never played with these parameters, and @xchrisd seems to find them OK for M201-M204, so M205 might be a problem? Dunno, worth a try. My suggestion would be to remove these lines (which I’d deem not necessary anyhow) from the GCode (use normal text editor), and try again.

I am not sure if the M205 XYZE counts because it`s not there in the settings:

One thing i thought about is the “corrected” steps of the linear modules, could it cause such noise?

Would be worth a try to run factory settings, instead of this?