Lost MCU path after hardware change

General Discussion
1

Basic Information:

Printer Model: Ender 3 v2
MCU / Printerboard:STM32F103 chip, 4.2.2 board
Host / SBC: Laptop with Linux mint on it
klippy.log
klippy.log (25.5 KB)

Describe your issue:

After my last workshop Computer fried because of a dang spider i resorted to using a laptop laying around. I installed Mint clean, and got rid of ModemManager just in case. i used a script that’s floating around to see if my problem is linked to the debian bullseye bug, but it doesn’t seem to be the case.
Basically i reflashed my printer and also changed my cable to a longer one. It is specifically made for data transfer so it should be fine?
However i cannot find my MCU serial when i try to use it.

2

According to your log, you have configured your MCU as being connected via serial and not via USB. Is this intended? If not, follow the documentation to get a proper USB connection path.

3

Hello it’s not intended indeed lol do i need to modify my printer.cfg or did i make a mistake when flashing the printer?

4

I cannot tell. Please systematically follow Installing Klipper with KIAUH

5

I have re-followed the installation from scratch but i still can’t find my MCU, when i do this command : ls /dev/serial/by-id/* it says i have no such folder or directory.
I have removed modemmanager and Brttly, and when running the debian bullseye bug it tells me it’s not this because it’s no on deb11 anyways…
Also for the serial connection configuration, i have followed the configuration suggestion in the config_exemple file for the ender3v2 i have

Edit: i have managed to find the path, however when using it i still cannot connect to my mcu, by id or by path neither work X_X

6

Please attach a corresponding klippy.log whenever you change something or encounter an issue. Without this log it is impossible to see, where things might go wrong.

7

Ah yes sorry i forgot to do it here it is now:
klippy.log (33.9 KB)
moonraker.log (30.5 KB)
I also added my moonraker log just in case

8

For this board, and according to your log, your firmware build settings seem correct.
In any case, verify that the board really is what you think and also systematically follow Issues flashing the printer board

9

Sorry for the lack of answer i was away for holidays. As Soon as i cam home i uninstalled everything and redid everything from scratch and i still cannot manage to connect to my MCU T_T
here are the new logs:
klippy.log (54.9 KB)
moonraker.log (22.1 KB)

10

According to my experience, just redoing the stuff the same way as before only very rarely changed anything.

The error in your log is still the same and the only guidance, I can offer is that I’m pretty sure that your topic has its root cause within one of the points listed in Issues flashing the printer board

11

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