"mcu" unable to connect

General Discussion
1

Basic Information:

Printer Model: RatRig Vcore 31
MCU / Printerboard: Octopus Pro + SHT42
klippy.log
klippy.log (345.4 KB)

Fill out above information and in all cases attach your klippy.log file. Pasting your printer.cfg is not needed
Be sure to check our Knowledge Base and in particular this and this post

Describe your issue:

Not MCU
Not MCU2560×1033 135 KB

LsUsb
LsUsb849×289 6.05 KB

Extract Octopus Pro in RatOS

Hi,

I want to try to make the klipper configuration in 1 file, not in many as I have now.

For this I decided to start from scratch, reinstalling RatOs…

But the first one on the front, RatOs (a version of Mainsail with many Macros) does not find the MCU, when Rpi sees it via USB, and a few hours ago, Fluidd saw it…

Does anyone know why this could be?
…

2

Use the command:

ls /dev/serial/by-id/*

and replace the serial: ... with the correct output

3

i have sended

ls /dev/serial/by-id/*

the console responds…

/dev/serial/by-id/usb-Klipper_stm32f429xx_3A0039000D50304738313820-if00

the correct line would be?

[mcu]
serial: /dev/usb-Klipper_stm32f429xx_3A0039000D50304738313820-if00

That “name” change would have been because the firmware it has installed is different from the one provided by RatRig. In the RatRig the name is changed…

I suposse…

4

As it is described here:

https://www.klipper3d.org/Installation.html#configuring-klipper

it needs the full path.

5

This is wrong. Just copy paste the exact console output from the command you ran.