After upgrade mcu Unable to connect

General Discussion
1

Basic Information:

Printer Model: Voron 2.4r2
MCU / Printerboard: Octopus v1.1
klippy.log

Describe your issue:

So I have decided to upgrade to the voron tap, btt sb 2240 can bus with the U2C board. I did do an update thinking that I might need that with these extra mods being installed.
Since the update I am unable to connect to the mcu. After I flashed the octopus I can get connected until i reboot the printer. Also having troubles with a hand full of other things, but first thing is first. I have tried to re-flash my octopus through usb using CanBoot ( Katapult ) and as well as winscp with Micro sd card many times with no luck. I have re installed Klipper and Mainsial on my raspberry pi 4, I have gone through the trouble shooting and it seams its over my head. I feel like my issue is in this Printer.cfg area…

Very new to this, any help would be greatly appreciated.

serial: /tmp/klipper_host_mcu
[mcu]

Obtain definition by “ls -l /dev/serial/by-id/” then unplug to verify

##--------------------------------------------------------------------
serial: /dev/serial/by-id/usb-katapult_stm32f446xx_2B0040001750344D30353320-if00
restart_method: command

klippy (48).log (215.8 KB)

2 
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-katapult_stm32f446xx_2B0040001750344D30353320-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-katapult_stm32f446xx_2B0040001750344D30353320-if00'
  • The error is pretty clear: there is no /dev/serial/by-id/usb-katapult_stm32f446xx_2B0040001750344D30353320-if00
  • Also since this serial contains katapult, it is a strong indication that you obtained it when the board was in bootloader mode

Reboot / Reset your board, then try again with ls -l /dev/serial/by-id/*

1 Like
3

Thankyou sir for your time… Greatly appreciated.

4

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