Basic Information:
Printer Model: Modified RatRig V3.1
MCU / Printerboard: BTT Octopus
Host / SBC Linux PC
klippy.log (60.5 KB)
klippy.log
Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there
Describe your issue:
I have a PC running Linux Mint as an alternative to using a Raspberry Pi
I have the printer homing and was working on getting everything working correctly. I was tring to get a relay to via the fan out out on the Octopus board. While doing this I think I damaged the board because the MCU was no longer able to communicate.
I have replaced the BTT Octopus board and installed the firmware. I have not connected the relay to eliminate causing the problem again.
I am able to get the serial id. via the command prompt: ls /dev/serial/by-id
serial: /dev/serial/by-id/usb-Klipper_stm32f446xx_290029001850535556323420-if00
I have another PC that I loaded Linux onto. Installed klipper. I get the same problem. Unable to connect to MCU.
In the klipper log is see this
mcu ‘mcu’: Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-Klipper_stm32f446xx_05001C001350535556323420-if00: [Errno 2] No such file or directory: ‘/dev/serial/by-id/usb-Klipper_stm32f446xx_05001C001350535556323420-if00’
The Klipper_stm32f446xx_05001C001350535556323420-if00’ does not match the current ID. Klipper_stm32f446xx_290029001850535556323420-if00
I do not know why this information is in the log. Please know that I have not reviewed klipper logs much so the information is new to me.
I have read every post I can find but have not been able to find a solution. Any help would be greatly appreciated.
…