Help printer automatically disconnects after 3 seconds of linking

This is a part of Klippy.log

Args: ['/home/pi/klipper/klippy/klippy.py', '/home/pi/printer_data/config/printer.cfg', '-l', '/home/pi/printer_data/logs/klippy.log', '-I', '/home/pi/printer_data/comms/klippy.serial', '-a', '/home/pi/printer_data/comms/klippy.sock']
Git version: 'v0.11.0-143-gc54d83c9'
CPU: 4 core ?
Python: '3.9.2 (default, Feb 28 2021, 17:03:44) \n[GCC 10.2.1 20210110]'
=============== Log rollover at Thu Nov 23 17:23:55 2023 ===============
Args: ['/home/pi/klipper/klippy/klippy.py', '/home/pi/printer_data/config/printer.cfg', '-l', '/home/pi/printer_data/logs/klippy.log', '-I', '/home/pi/printer_data/comms/klippy.serial', '-a', '/home/pi/printer_data/comms/klippy.sock']
Git version: 'v0.11.0-143-gc54d83c9'
CPU: 4 core ?
Python: '3.9.2 (default, Feb 28 2021, 17:03:44) \n[GCC 10.2.1 20210110]'
Building C code module c_helper.so
Start printer at Thu Nov 23 17:24:13 2023 (1700760253.8 82.2)
Unable to open config file /home/pi/printer_data/config/printer.cfg
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/configfile.py", line 158, in _read_config_file
    f = open(filename, 'r')
FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/printer_data/config/printer.cfg'
Config error
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/configfile.py", line 158, in _read_config_file
    f = open(filename, 'r')
FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/printer_data/config/printer.cfg'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/pi/klipper/klippy/klippy.py", line 175, in _connect
    self._read_config()
  File "/home/pi/klipper/klippy/klippy.py", line 134, in _read_config
    config = pconfig.read_main_config()
  File "/home/pi/klipper/klippy/configfile.py", line 279, in read_main_config
    data = self._read_config_file(filename)
  File "/home/pi/klipper/klippy/configfile.py", line 164, in _read_config_file
    raise error(msg)
configparser.Error: Unable to open config file /home/pi/printer_data/config/printer.cfg
webhooks client 281473575896832: New connection
webhooks client 281473575896832: Client info {'program': 'Moonraker', 'version': 'v0.8.0-29-g80920dd'}
webhooks client 281473575896832: Disconnected
Restarting printer
Start printer at Thu Nov 23 17:25:53 2023 (1700760353.7 182.1)

The upper computer is Orangepi3LTS

 __  __       _                 _ _  ____   _____
|  \/  |     (_)               (_) |/ __ \ / ____|
| \  / | __ _ _ _ __  ___  __ _ _| | |  | | (___
| |\/| |/ _` | | '_ \/ __|/ _` | | | |  | |\___ \
| |  | | (_| | | | | \__ \ (_| | | | |__| |____) |
|_|  |_|\__,_|_|_| |_|___/\__,_|_|_|\____/|_____/


Version 1.1.0, based on Armbian 23.02.2 Bullseye
Running on OPi 3 LTS with Linux 5.15.93-sunxi64

The configuration file and path have been checked and are correct
Why is there such a mistake

klippy (3).log (53.1 KB)

1 Like

Hello @badpoi !

You may tidy up your post.

For code snippets please use the feature “preformatted text” in the editor tool bar.

Format

Especially for the section with the slashes and bars at the end.

The forum bot marked your post as spam.

1 Like

Have a look at my answer here Ender 3v2 Neo Custom - #4 by hcet14. I wrote it just a couple of minutes before.
You got the same problems as @JosevdG
If you solved your problem, you could help JosevdG.

Thank you for your reminder. It has been corrected

1 Like

thank you, I’ll take a look tonight

dmesg.txt (32.8 KB)
I cannot understand what is displayed when I run sudo dmesg - e .
Can you help me read it

When I run ls/dev/serial/by id/*, it shows


pi@mainsailos:~$ ls /dev/serial/by-id/*
/dev/serial/by-id/usb-Klipper_stm32f407xx_44545-if00

Both your ls command and the dmesg is looking fine and the klippy.log you posted indicates that Klipper is successfully connecting to the board.

Your error is Lost communication with MCU ‘mcu’, which has a different source than what you are looking at: Timeout with MCU / Lost communication with MCU

Unfortunately, this error can be tricky to hunt down, but is 99.99786% related to your hardware.

Thanks, I have solved this problem by replacing the data cable

1 Like

Seems like this figure should be slightly higher now.

1 Like

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