Printer Model: enderwire
MCU / Printerboard: skrv1.4
Host / SBC orangepi02w
klippy.log
Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
klippy (2).zip (6.1 KB)
Enderwire conversion skr v1.4 ,tmc 2208, noisy with stealthchop active?
Hello @mattfly !
Maybe a chance to attach klippy.log to your next post?
new to klipper working on that now
Sorry?
See [tmc2208] and Setting “spreadCycle” vs “stealthChop” Mode how to properly configure your TMCs
before converting the printer, using the skrv1.4 and btt2208 drivers
the machine was quiet…so must be klipper???
What exactly is the added value of this comment?
I have provided you the link to the correct config since your current config uses spread cycle.
I have tried it both ways…no change in stepper volume or sound
marlin 2.0 same board same drivers before the conversion …dead quiet.
stealthchop threshhold at 0 or 999999 makes no difference.
Try increase the run_current on all steppers.
0.3 A and 0.5 A are way too low. What you hear is skipping steppers.
Start at about 0.8 A
set to .8 on x y z no change . I would like to home in stealthchop and have the threshold working . This is my 5th printer including voron 2.4 . The stepppers are not in stealthchop mode. and not skipping steps.
Can you make a short video clip on what is happening?
The problem is no matter how threshold is configured…stealthchop is not working. The printer prints fine just loud.
There are no issues known around this topic and I run this board in one of my printers as well.
Most likely a local issue on your side. Post a new klippy.log so that we can check your current settings.
Viewing the klippy log … stealthchop threshold not appearing under the TMC driver settings although it is in the printer config…set to 999999
What prevents you from uploading a new klippy.log?
Ok figured it out was changing the wrong printer.cfg file. Works now thanks for the help