BTT Manta V2 + CB1

[zacf]

Basic Information:

Printer Model: Homebrewed
MCU / Printerboard: Mant m8p V2
Host / SBC: CB1
octoprint-systeminfo-20240716161603.zip (44.2 KB)
klippy.log (1.2 MB)

klippy.log

Hi,

Got a new brain for my printer after an accident…
Manta m8p V2 with CB1.
I Installed the minimal image for the CB1 and updated it (2.3.4 Bullseye with Linux 5.16.17-sun50iw9).

Kilpper is unable to connect to the mcu.
The terminal say:

Trying port /dev/ttyACM0, baudrate 115200
Connecting to port /dev/ttyACM0, baudrate 115200
Could not open port /dev/ttyACM0, baudrate 115200, skipping
Trying port /dev/ttyACM0, baudrate 250000
Connecting to port /dev/ttyACM0, baudrate 250000
Could not open port /dev/ttyACM0, baudrate 250000, skipping
…

octoprint.log say:

2024-07-16 16:02:30,447 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyACM0, baudrate 115200
2024-07-16 16:02:30,486 - octoprint.util.comm - INFO - Connecting to port /dev/ttyACM0, baudrate 115200
2024-07-16 16:02:30,592 - octoprint.util.comm - INFO - Failed to connect: Port /dev/ttyACM0 is busy or does not exist
2024-07-16 16:02:30,593 - octoprint.util.comm - INFO - Serial detection: Could not open port /dev/ttyACM0, baudrate 115200, skipping
2024-07-16 16:02:30,593 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyACM0, baudrate 250000
2024-07-16 16:02:30,596 - octoprint.util.comm - INFO - Connecting to port /dev/ttyACM0, baudrate 250000

Running ls /dev/serial/by-id/ return the board:

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

Running dmesg -w I get:

[ 3.585182] usb 2-1.4: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
[ 3.594652] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.601987] usb 2-1.4: Product: stm32h723xx
[ 3.606185] usb 2-1.4: Manufacturer: Klipper
[ 3.610465] usb 2-1.4: SerialNumber: 12345

And:

[ 8.387797] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 8.388507] usbcore: registered new interface driver cdc_acm
[ 8.388528] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

I don’t see anything else attached to ttyACM0.
I also noticed this (not sure if it’s related):

[ 8.389819] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 8.391187] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
[ 8.466195] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid

I’ll appreciate any help.

[EddyMI3D]

Hello @zacf !

I seems you mix up the connection of Klipper to the MCU and the connection of OctoPrint to Klipper.

As for the klippy.log, in the last sequence of the log, the connection from Klipper to the MCU is fine.

Yo have to try a different port for the connection of OctoPrint to Klipper

In OctoPrint Settings → Printer → Serial Connection.

In Additional serial ports there may be a port /tmp/printer Choose that one to connect to Klipper.

BTW: How did you install Klipper and OctoPrint to the CB1?

If /temp/printer does not work, you may try /home/pi/printer_data/comms/klippy.serial but depending of your installation the path may be a bit different.

This one you have to insert into that field I mentioned before.

[zacf]

@EddyMI3D

/home/pi/printer_data/comms/klippy.serial

Thanks for your reply.
I installed Klipper and OctoPrint with Kiauh.
I restored a backup of OctoPrint upon first login to it.

Adding /home/pi/printer_data/comms/klippy.serial didn’t help.

Is there a way to find the correct serial port?

Thanks

[zacf]

Thanks @EddyMI3D. You’re a lifesaver.
BIQU had to act like smart@$$…
The root user for the CB1 image is BIQU and not pi.
/home/biqu/printer_data/comms/klippy.serial did the trick.

Thanks!