Basic Information: Printer Model: Creality CR-10S MCU / Printerboard: BTT SKR 1.4 Turbo and Raspberry Pi 3 klippy.log Describe your issue: klippy.log (8.8 KB) I cannot seem to connect to my printer anymore after I reinstalled my Raspberry pi 3. Config files worked fine before reinstallation, …

Try: nano /home/pi/printer_data/systemd/klipper.env Replace /home/pi/printer_data/comms/klippy.sock by /tmp/klippy_uds sudo service klipper restart

klippy.log.zip (1.0 MB) I apologize for the delayed response, please find my klippy.log attached. Since I managed to print 2 succesful prints, I suppose my hardware should be okay… klippy(3).log (37.4 KB) Here is another klippy.log, from my test today. Printer is turned on, klippy doesn’t want t…

I’m not sure what you are reporting. The klippy(3).log above does not contain any Klipper errors. On the contrary, it shows a successful start. As for the zipped log and the EOF error there is not much more to say about unfortunately: Your host’s Linux is reporting that the data stream from the MC…

That’s unfortunate… My Fluidd interface keeps reporting “Klippy is not connected” and I cannot do anything, let alone start a print… :frowning:

[image] Esumontere: My Fluidd interface keeps reporting “Klippy is not connected” Provide the output of cat /etc/default/klipper and cat /etc/systemd/system/klipper.service

cat /etc/default/klipper cat: /etc/default/klipper: No such file or directory cat /etc/systemd/system/klipper.service [Unit] Description=Klipper 3D Printer Firmware SV1 Documentation=https://www.klipper3d.org/ After=network-online.target Wants=udev.target [Install] WantedBy=multi-user.target [Se…

and: cat /home/pi/printer_data/systemd/klipper.env

KLIPPER_ARGS="/home/pi/klipper/klippy/klippy.py /home/pi/printer_data/config/printer.cfg -I /home/pi/printer_data/comms/klippy.serial -l /home/pi/printer_data/logs/klippy.log -a /home/pi/printer_data/comms/klippy.sock"pi@klipper:/etc/default $

[image] Sineos: nano /home/pi/printer_data/systemd/klipper.env Hey, that seemed to solve the issue, I can connect to the printer again! Would you mind explaining what that edit did exactly?

The klippy.env contains arguments to tell Klipper where to put its log, where the printer.cfg is etc. Among these arguments is also the path where Klipper puts the interface to moonraker - a so called socket. This is given by the -a argument As far as I’m aware, moonraker accepts two socket locatio…

So if I understand correctly, the connection between klipper and moonraker was faulty, not the connection between moonraker and my printer? Interesting :slight_smile: Thanks a lot!

Klipper not connecting after new installation

General Discussion

Jamiekay January 22, 2023, 4:19pm 24

Hi Sineos, I did start a new thread (502 bad gate way) the one you have not responded to after threatening my privlages in this group.

Topic		Replies	Views
Klipper Internal error on command:"G1" General Discussion	34	538	August 2, 2025
Klippy not connected? after updates General Discussion	28	13025	June 4, 2025
Cant' detect MCU - Tried Everything! Please Help General Discussion	17	1137	March 26, 2024
Sudden MCU Shutdown During Print General Discussion	23	3082	February 13, 2024
'mcu': Unable to connect General Discussion	24	1957	August 1, 2024

Klipper not connecting after new installation

Related topics