Klipper Internal error during connect: [Errno 19] No such device

Hi All,

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: BTT Octopus
klippy.log is attached

I have a Raspberry PI4 connected to an Octopus stm32f446

I imaged the Pi with the combined OS and Klipper off of the Pi site with the Pi imager

I performed the following actions:
sudo apt-get update
sudo apt-get -y dist-upgrade


make menuconfig
enable extra low level configuration options
processor model stm32f446
bootloader offset 32 Kb
crystal 16 Mhz
communication interface usb (pa11, pa12)

make - compiles the firmware for the btt octopus

copy the klipper.bin to the sd card and rename it to firmware.bin
flashed the octopus and checked file is renamed to FIRMWARE.CUR


ls /dev/serial/by-id - on the Pi
usb-Klipper_stm32f446xx_4C0031000151303530353135-if00

used
/dev/serial/by-id/usb-Klipper_stm32f446xx_4C0031000151303530353135-if00
to configure klippers printer.cfg file

in the klipper web interface i get the following error
“Internal error during connect: [Errno 19] No such device”

Needless to say i have tried different usb cables,
If the usb cable is disconnected using “ls /dev/serial/by-id” correctly does not find the port

I have treid many different options including reloading the Pi from the ground up as well as watched many youtube videos and read many pdfs.

Any solutions would be appreciated

…

Hello @CSteveP !

where?

i up;oaded it, maybe the wrong place, let me check

klippy.log (65.1 KB)
here is klippy, i hope

You wrote all the 2000 line of printer.cfg by yourself? Respect!

Have you checked the can subsystem for a correct setup?

i can dream, no, not at all, it was just the best one i could find
i have a lot to learn still

i am not using CAN at this stage

I appears you put a lot of macros into your printer.cfg just by random choice.

[mcu pitb]
canbus_uuid = 0a754ef78da4

...

[mcu sb2040]
canbus_uuid = 62aff65e7dcf

Please start with a simple printer config

Thanks for your advice, If you could point me in the right direction i would happily use a simple printer cfg file

Honestly: With a blank printer.cfg, the Klipper documentation and a pinout schematic of the printer board.

Of course, this is a steep learning curve, but it gives you the most insight of how Klipper works, how the printer.cfg can be optimized and give you the ability to choose just those macros you really need.


The Klipper documentation starts here:

https://www.klipper3d.org/Overview.html


There are also examples for to start with:

For Voron:

but compare the pin assignments to your actual board.


A pinout schematic can be this:

but take care to get the proper version.


And if you get stuck, you can ask for help here.

Thanks,

I will try the suggested printer config fille suggested and let everyone know how it turns out.

1 Like

Hi EddyMI3D,

Thanks for the response.

I noticed that this printer.cfg file is for dual RAMPS controller boards (maybe old hardware) because they are not used on the standard Voron 2.4 build. The standard build uses the Octopus board.
I am not very familiar with the changes required.

I did try the config file and modified both “serial:” values to the single USB ID that i have.
I now says the ERROR is “mcu ‘z’: Unable to connect” probably because it is already connected with “mcu” connection.

I think the cfg file needs modification?

Can you post the printer.cfg? Please as file or between code braces:

Format

You can find the “Voron official” Klipper configs here: Voron-2/firmware/klipper_configurations at Voron2.4 · VoronDesign/Voron-2 · GitHub

Edit:
Also refer to the official Voron documentation: Software Configuration | Voron Documentation

1 Like

Hi EddyMI3D,

Thanks
I used the file you referenced for me

Hi Sineos

Thanks

I used one of the files you sent me to.
I think i have a small success SHUTDOWN “MCU ‘mcu’ shutdown: ADC out of range”.
For me this implies that the Pi is talking on the USB link.
I probably do not have the correct thermistor values set, so i will go and have a look at them.

Also check that the thermistors are properly connected and at the right ports/pins (the ones defined under the respective sections in your config files).

This is less the consequence of wrong thermistor values but more likely a wiring / connection issue, e.g. wrong thermistor port or loose / damaged wiring or connectors.

Post a fresh klippy.log if the error persists