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.
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.
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 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.