Basic Information: Printer Model: Voron 2.4R2 MCU / Printerboard: Spider 2.3 Host / SBC 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” Categ…

Ok. So You have the drivers installed and config adapted. Walking through your log, I noticed, that you got that issue while still running the TMC2209: lines 33848ff [tmc2209 stepper_x] uart_pin = PE7 interpolate = False run_current = .95 sense_resistor = 0.110 line 34165: TMC stepper_x failed …

[image] EddyMI3D: Walking through your log, I noticed, that got that issue while still running the TMC2209: lines 33848ff That is not used in the last part of that huge klippy.log. That’s why I asked for the two printer.cfg(s) above.

Yes, but the issue occurred, for what reason ever.

[image] EddyMI3D: Yes, but the issue occurred, for what reason ever. Of course, that’s why [image] hcet14: It might be helping to post your working printer.cfg with just TMC2209 drivers and your new printer.cfg for the mixed setup. Guessing around is boring :wink:

I would have definitely done that from the first post if the instructions on here didnt basically tell you not to put the config here but to use the klippy log. Here is the current config, youll notice the 2209 commented out, which were the working settings before switching. printer.cfg (17.9 KB)

I use Moonraker and it regulary has me update Klipper. I did have an issue a couple months back that many Voron users had with an update. It basically caused my mcu to disappear and some issues with adxl. The workaround was I believe was using the version you are mentioning which fixed that issue. …

To rule out an issue with the board, you may revert one of the axes to the previous driver.

I did that, and it just changes the error to stepper y. And back to stepper x if I swap them. It prints good with both 2209 so i think the board is fine.

You might try just one driver. The drivers were never tested, they are new. It happened before, that a driver is defect and disturbs the hole SPI bus.

Yes that is what I did, one of the new 5160 drivers and one of the 2209s. Then swapped the 5160 drivers and tried that. I see others have had issues like mine, but the resolution never seems to get updated on the post whether it be on discord, reddit, etc.

Unable to write tmc spi error after switching to 5160 drivers

General Discussion

hcet14 May 1, 2024, 11:34am 25

Did you try different spi_speed settings? Like here Fysetc Mini 12864 Panel (RGB) on Spider V2 - #7 by jjarosz

Topic		Replies	Views
Klipper state: Shutdown Running TMC5160 BTT Octopus 1.1 General Discussion	10	3590	July 22, 2022
Unable to write tmc spi 'stepper_x' register General Discussion	4	1835	March 11, 2024
MKS Robin Nano V3.1 With TMC5160 General Discussion	4	324	September 20, 2025
Suddenly unable to write to TMC 5160 spi General Discussion	2	819	February 4, 2024
BTT Octopus Max EZ and EZ5160 SPI problems General Discussion	20	4456	March 3, 2024

Unable to write tmc spi error after switching to 5160 drivers

Related topics