No connection with klipper

General Discussion
1

Basic Information:

Printer Model: Creality Ender 3v2
MCU / Printerboard:basic ender board
logs-20240324-204555.zip (13.6 KB)

after starting the server, information about the lack of connection with the klipper is displayed

obraz
obraz787×282 29 KB

klippy.log (17.4 KB)

2

Was the printer running before? The more information you share, the easier is finding a solution.
What did yo do with the printer, before this message was displayed?

3

The printer has not yet been used with klipper

4

Post the klippy.log as initially required.

5

I’ve posted klippy logs

6

Are you running Klipper on a notebook? Under what OS exactly?
What guide did you follow to install Klipper, Moonraker, etc?

The Klipper ecosystem is not working properly and Klipper can’t connect to your MCU as the serial seems to be wrong.

7

ubuntu, use kiauh

8

does the operating system matter?

9

As your setup is not running everything can cause that issue.
On what platform is Klipper running? The mentioned i5-4300U suggests a mobile platform.
I’m not a Linux expert but maybe there are missing rights for the involved components here.

10

Yes it does. Especially, Ubuntu desktop versions tend to have some quirks that spoil Klipper.
Your error is not related Moonraker but Klipper itself and can have multiple reasons (the OS being one of them). See Issues flashing the printer board

11

I will try it on Ubuntu server

12

This error may be due to incorrect CPU model selection in make menuconfig?

13

Yes, incorrect settings during make menuconfig might be causing this as well. Again, one reason among quite a few. See the link above.

14

write f303 on the board’s processor and there is no such choice in makeconfig

15

GD32F303 uses the STM32F103 settings. What is the complete marking on the board? Creality v…

16

creality v4.2.2

17

Yes, this is known to have a GDF303 chip. The correct settings are:

  • STM32F103
  • 28KiB bootloader
  • Serial on USART1 PA10/PA9
  • Make sure to rename klipper.bin to firmware123.bin, where 123 is changed whenever you flash
19

that’s exactly what I did before

20

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.