Is it just me or are the settings really noisy ?
I've been running my own installation of Klipper since I got my v-core-pro back in 2020. Decided it needed refurbishing and decided to give RatOS a shot ... so many cool new features but oh my word is the printer noisy ... so much wine at rest when the motors are enabled, and the z motors sound like they are grinding (definitely not) something but only sometimes - It seems when the bed is lowering, but they are fine when it is raising. I appreciate it is due to changes in microsteps, stealthchop, and interpolate based on 5 years of tuning that I wasn't using. I haven't actually done any printing as many more things to do but they require physical rework that I can't do just now, hopefully in a few weeks, so I don't know if I'm going to get a better/more reliable output.
10 Replies
I suppose I should say I'm using the performance settings (I mean who wouldn't ?) 🙂
Hi, I`m facing the same issue after installing ratos 2.1. drivers are very noisy when engaged but not moving (after homing) . I have silent mode, and current lowered to 0.5Amp on steppers it is better but still noisy. Had no issue with 2.0.1 configuration Octopus 1.1, TMC2209 + LDO 2504ac
Performance is optimized for speed, they’re quieter at 200 mm/s and above. “Standstill stealth” removes the whine on standstill without any downsides, unless you have questionable drivers. If you want silence at low speeds you’ll need to significantly lower the current or enable stealthchop.
The “grinding” on z is resonance from your leadscrew couplers
Couple of ways to fix, one is lowering max_z_velocity
You can also tighten them or swap to ones that don’t make as much noise at medium speeds.
0.5A? The 2504AC’s barely work at that current.
Stealthchop eliminates noise under 135 mm/s (but resonates above)
If you drivers are making sounds at standstill with stealtchop, something not related to RatOS is very wrong.
Yeah ... to be honest I was just surprised at the difference ... I've only gone up 0.1 A ( I was running at 1.5 before ). Define questionable drivers 🙂 I know I had the stealthchop threshold at 1 previously but the "use with caution" made me question that choice so it is disabled
combination stealthchop and standstill made the trick, thanks
You can't have both. Stealthchop overrides standstill, it's the same setting, different values (
stealthchop_threshold).
So i'm guessing you were just missing stealthchop before
questionable as in FYSETC (their 2209's are just broken..) or TwoTrees and what have we.. Bottom of the barrel type stuff.
Usually people buy BTT, never had an issue with standstill stealth on any of their drivers.yeah pretty sure mine are BTT ones
Solution
flip that switch!
And I've been running at threshold 1 for a few years now 🙂 I was just using installing RatOS as an excuse to start fresh with all the learnings of the last few years
Excellent that's exactly what "Standstill stealth" is, so you already know it works 👍 🙂