Klippy won't connect

Basic Information:

Printer Model: Ender 3 V2
MCU / Printerboard: 422
Host / SBC: BTT Pi2
klippy.log
klippy(1).log (1.8 MB)

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

Describe your issue:

… Printer was down for about a month, just plugged it all up and now Klippy wont connect.
I updated all the modules that needed updates, I ran make menuconfig and reinstalled klippy.bin on the ender 3, still wont connect.

I’m not sure what I’m missing so I’d appreciate any help on figuring this out

Your printer board does not correctly connect to your host. Either:

  • Board not correctly flashed
  • Wiring / cable issue
  • Issue on the Linux side. Check with the dmesg command
  • Dead board

Thanks for replying.
I reflashed to Marlin and plugged in the screen to check that the board is working (it booted up fine).
Turns out I had my thermistor and heater cables plugged in the wrong way round (ie thermistor into heater and vice versa), this is the only wiring that would have changed so there shouldn’t be any other possible wiring issues internally and I’m using the same USB that worked for me before (also been trying with three other cables with the same results).

Still getting the same issue.
What should I look for in the dmesg command? It returns a looot of info

I tried running “ls /dev/serial/by-id” which wouldn’t work

When I checked the directories using Cyberduck, the /dev/serial folder is entirely missing.
So it seems to be a linux issue?

No idea how this happened. Looking for fixes now

Follow How-To Trouble-Shoot, Chapter 3, and attach the dmesg.txt file.

This is due to the points already listed in my first answer. Carefully work through Issues flashing the printer board.

dmesg.txt (88.1 KB)
from what I can tell, it’s as if the printer isn’t plugged in at all

PS I plugged in a mouse just to see if lsusb would return a response, it did.

Unless there’s something I’m not seeing, its as if the USB cable has stopped working or the USB port on the mcu board or has