Klipper, linux on loptop, MCU, lsusb, CH340

General Discussion
1

Printer Model: Ender 3 S1 Pro
MCU / Printerboard: STM32F401
klippy.log

Hello, I don’t know where the problem could be. I’m trying to run Klipper on my laptop using Ubuntu Server. I’ve followed a few YouTube tutorials, and I’ll provide the links later. I’ll start explaining from the beginner .

From the YouTube tutorials, I first tried “Ubuntu Mint,” where I encountered my first problem. I couldn’t find [mcu] using the command /dev/serial/by-id/* or ls /dev/serial/by-path. I tried fixing this problem by following online posts. I attempted other Linux distributions, including Ubuntu Desktop, but encountered the same problem.

Then, I tried Ubuntu Server, and finally got a result after running the command /dev/serial/by-id/*. I found /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0. I placed my USB ID into printer.cfg, but nothing happened. I don’t know where the problem lies. Can somebody help?

I’m going to create an FAQ to make it easier for you to understand what I did.

How do I flash my printer’s motherboard?

I flashed my motherboard using these tutorials: Link 1 and Link 2

Did I try using a different cable to connect from the laptop to the printer?

Yes, I tried four different cables, and only one of them worked

What do I get if I run the command “lsusb”?

When I plug in my printer, it detects 'QinHeng Electronics CH340 serial converter

In one video I saw, the guy got a different result from me when he ran the command “lsusb” What I want to say is that when he connects to the printer and runs “lsusb”, he gets the motherboard chip name, while I get “QinHeng Electronics CH340 serial converter”.

I thought there might be a problem with the USB port, but now I’ve tried plugging in my keyboard and mouse. After the lsusb command, I could see the keyboard and mouse names. Maybe here could be the problem. ?

2

Nice idea, but there are some Linux basics that you have to learn yourself. Even just putting an Ubuntu server on a laptop seems strange to me.
lsusb shows you the recognised devices on the bus, i.e. the interface of the board may of course only be visible when it is plugged in, i.e. with and without checking.
In /dev/serial/by-id/… there are links pointing to a /dev/tty… where your user must have write permissions. If you have not used pi as a user, further challenges will await you.
Nevertheless, you can get it to work on an Ubuntu server, I have the same on an Odroid C4.
You don’t need a special cable, just no charging label with only + and - on it

3

Unless you have an over-riding need to use modemmanager you should remove it. On my system, it prevented attached usb devices from displaying their presence in /dev/serial/by-id

[edit] or rather tell systemd not to load it if you are running a linux where systemd has been forced upon you.

4

I propose to start over and follow Installing Klipper with KIAUH. You can skip the first chapter and start with “OS Sanity Checks and Fixes”.

Also Issues flashing the printer board might contain relevant information for your case.

5

Find the problem. That was my problem, a little bit stupid . I used “ls /dev/serial/by-path” to find the ID for the connection. There, I found the ID “pci-0000:00:14.0-usb-0:2.1:1.0-port0”. But in printer.cfg, I wrote it like this: “/dev/serial/serial/by-id/pci-0000:00:14.0-usb-0:2.1:1.0-port0”, where it should have been “/dev/serial/by-path/pci-0000:00:14.0-usb-0:2.1:1.0-port0”. Yeah, that was… I’m using /dev/serial/by-path because I’m using a USB hub for the connection. I’m going to try running three printers on one laptop.

6

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