Klipper won't connect to ERCF easy brd serial device

General Discussion
1

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: ERCU easybrd
Host / SBC: android TV box- flashed with Klipper
klippy.log: klippy-2.log (777.6 KB)

I have a working printer and am attempting to add an ERCF MMU.
Im using an ERCF easybrd V1.1 (see below GitHub link). I am able to successfully flash it per the instructions and Klipper recognizes the serial device when listed with one of the following:

ls /dev/serial/by-id/*
ls /dev/serial/by-path/*
ls /dev/serial/ttyA*

I am attempting to use the current version of happy hare, I have added the serial alias under [mcu mmu] in the cfg file as I believe is appropriate:

[mcu mmu]
serial: /dev/serial/by-id/usb-Seeed_Studio_Seeeduino_XIAO_1858C9A250583833312E3120FF06213E-if00 # Change to canbus_uuid: 1234567890 for CANbus setups
#serial: /dev/ttyACM1 # Change to canbus_uuid: 1234567890 for CANbus setups
#serial: /dev/serial/by-path/platform-xhci-hcd.1.auto-usb-0:1:1.0 # Change to canbus_uuid: 1234567890 for CANbus setups

Ive tried all thee of these. In any case I get the

image
image527×266 16.1 KB

error, which switches to the red “mcc ‘mmu’: Unable to connect” red error after some time. (it seems I can only provide one image.)

I have tried re-flashing the ercf easybrd mmu, Im not sure what else to do. It is clearly able to communicate as I am able to flash it and the Klipper box does recognize the usb serial device.
At this time I am simply not including any of this ercf mmu stuff in my printer.cfg and continuing to use my otherwise perfectly good printer.

…any ideas?

Thanks

2

I’m not sure that I fully understand your report and the topics around:

From your log:

[mcu mmu]
serial = /dev/serial/by-id/usb-Seeed_Studio_Seeeduino_XIAO_1858C9A250583833312E3120FF06213E-if00
restart_method = command

This indicates:

  • You have connected the board via USB
  • The MCU on the board is not at all or not correctly flashed with a Klipper firmware

Depending on the intended connection scheme (CAN or USB), you have to flash the board with a Klipper firmware that is built to support this connection scheme and enter either the correct serial: path OR the correct canbus_uuid:

1 Like
3

Thank You, going back through my setup I found the below from when I flashed the MCU:

image
image1892×960 83.5 KB

I managed to miss this before, it looks like I did not correctly flash the MCU.

4

Welp here we go again.

I believe I have correctly flashed the MCU per the instructions. See log attached from the ssh terminal.

Same result… Could this be a bad MCU? I dont remember running into this issue on previous klipper installations.

log.txt (52.9 KB)

5

Not sure that I can meaningfully support, as I only used a SAMD Arduino once. Looking through my old files, it was something like:

  • Architecture: SAMD21/SAMD51
  • Processor: SAMD21G18 (Arduino Zero)
  • Clock: Internal clock
  • Bootloader offset: 8KiB bootloader (Arduino Zero)
  • Communication: USB

and flashed with:

bossac -i -d -p /dev/ttyACM1 -e -w -v -R --offset=0x2000 out/klipper.bin

after putting it in bootloader mode. Possibly it needed root rights to flash.

If the device does not come back with something like:

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

it has not been flashed correctly.