I guess you got me wrong. The TMC2209s are ok, it was working before!
The new TMC5160s! Take one out and try. Does Klipper come up? If not, try the other one alone.
No I am understanding and have done what you asked. I only have 2 5160s to try. I have isolated them to the point that either they are both bad or none are bad.
Does Klipper come up with just one TMC5160?
Same error with or without a driver in the slot.
-Reflashed Pi
-Reflashed and updated MCU
-Reinstalled Klipper to latest official
-Tried new 5160 drivers which arrived today
-Tried config in hardware SPI as BTT recommends for their drivers instead of software SPI as FYSETC recommends for their MCU
Still get the same error, latest log attached.
latestlog.log (124.0 KB)
Did you try different spi_speed settings? Like here Fysetc Mini 12864 Panel (RGB) on Spider V2 - #7 by jjarosz
I do not have a display like that, running Klipperscreen display directly off the Pi. And according to the Spider 2.3 documentation that I could find the SPI bus number 4 is just the tmc drivers.
But, tried that anyways and it did not help.
Of course.
I would start over following FYSETC-SPIDER/firmware/Klipper/printer.cfg at main · FYSETC/FYSETC-SPIDER · GitHub
I have started over multiple times. As stated I even reflashed everything and started over again fresh.
Is there something you are seeing incorrect about my config? Ive had a few others look at it, and none are coming up with anything wrong.
As I mentioned I have tried it with baseline Spider 2.3 config as well as config recommended by BTT for the drivers.
No, I think you tried everything. I have no clue!
Hopefully, someone else has a brilliant idea.