Klipper issues installing/flashing

Basic Information:

Printer Model: Ender 3 v2
MCU / Printerboard: v4.2.2 with GD32F303

klippy (7).log (542.2 KB)

So, I have been messing with my printer trying to install klipper and have run into a few issues. When I go into mainsail I encounter “mcu ‘mcu’: Unable to connect
Once the underlying issue is corrected, use the “FIRMWARE_RESTART” command to reset the firmware, reload the config, and restart the host software.
Error configuring printer”. I am not sure if this is because the klipper firmware was not flashed correctly on to my printer or some other issue. I have tried the provided configuration for the SD card as well as many other combinations and the only thing that changed was the screen getting stuck at the creality logo and the cr touch turning red. I am not sure if this means the firmware was flashed or just an error.

Just as another tidbit of information, when I do the command “ls /dev/serial/by-id/” I am returned “usb-1a86_USB_Serial-if00-port0”. I am also doing this all on an orange pi 5 plus.

Hopefully someone has some new insight into this issue as I have searched every depth of the web looking for a solution. Thanks!

Hello @ma1z !

So you should fill in this

into the appropriate line:

[mcu]
serial = /dev/serial/by-id/<your-mcu-id>

https://www.klipper3d.org/Installation.html#configuring-klipper

Where exactly would I fill this in to? I already have that written in the config file here. Am I suppose to put it somewhere else?
image

Your screenshot looks correct. If it still does not work, post a new klippy.log

[quote="ma1z, post:5, topic:1
klippy (5).log (70.5 KB)

I had it like that before and was still getting the error. I assume klipper is not flashed properly on the printer. I am able to easily flash to marlin but when I attempt to flash to klipper it either doesn’t work or I just get a blank creality screen as if it is frozen.

mcu 'mcu': Starting serial connect
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/<your-mcu-id>: [Errno 2] No such file or directory: '/dev/serial/by-id/<your-mcu-id>'
webhooks client 548214661008: New connection
webhooks client 548214661008: Client info {'program': 'Moonraker', 'version': 'v0.8.0-243-g84a8538'}
[mcu]
serial = /dev/serial/by-id/<your-mcu-id>

You had not and you still have not. Look at your log and if you ask yourself which file you have been editing, I do not know but the file you should be editing is:

/home/orangepi/printer_data/config/printer.cfg

Okay so I edited the file you referenced to include /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 but the klippy.log has not changed.

image

Did you reload the config?

Klipper has to know that you changed something.

Type save_config in the terminal

In any case: We always need a fresh and new klippy.log.

Screenshots are completely useless for any diagnosis.

No I did not do that but I just tried it and it doesn’t seem like it changed anything within the klippy.log file. I should be typing this under console right?
klippy (14).log (435.1 KB)

Your log changed. Now the error is

serialhdl.error: mcu 'mcu': Serial connection closed

This points to a board that is not correctly flashed. Follow the instructions on top of klipper/config/printer-creality-ender3-v2-neo-2022.cfg at master · Klipper3d/klipper · GitHub and repeat the process.

I’ll attempt to flash it again, but I have tried those instructions, and it doesn’t seem to be flashing on to the printer. Do you happen to know what the screen should look like if the flash was successful? Should I flash marlin back on it before attempting the flash because right now it seems to be stuck on the creality logo.

Did you happen to succeed flashing your printer? I’ve run into the same issue, it seems: LCD screen gets stuck on the Creality logo (not blank screen, as expected) and the only way to get it back is to re-flash Marlin.

Looks like at least a few other threads with the same issue, one as recently as yesterday, so I’m finding it hard to believe it’s a problem where all of us aren’t following the (very simple) instructions in the repo.