Basic Information:
Printer Model: Voron Trident
MCU / Printerboard: 2 x BTT SKR Mini E3 V2, BTT EBB2240, FYSETC ERB
Host / SBC: Raspberry Pi 3
klippy.log
Long time user of this fantastic code, many thanks to all involved. I’m completely stumped at the moment.
I built a Voron Trident using two BTT SKR Mini E3 V2 MCU boards and a BTT EBB 2240 tool head board. About a year ago, I began adding an MMU using a FYSETC ERB V1 (RP2040 B2) MMU MCU. Klipper v0.12.0-526-g3fcbc0b4 was installed on the host and all four MCU boards and there were no issues. I am using USB connections throughout (no CAN bus).
When v0.13 was released, I compiled and uploaded 0.13 firmware for all the boards, and ran into a problem - the three BTT boards worked with no issues. After uploading the v0.13 firmware to the ERB using the BOOTSEL method, it appeared as expected in the LSUSB output. After the printer was power cycled, the ERB did not connect and was not listed by LSUSB. When I restored the v0.12 firmware, the ERB was again connecting as expected. Things worked nicely with v0.13 on the RPi and BTT boards, and v0.12 on the ERB.
With the most recent v0.13 update, some code has been deprecated and the STEPPER_STEP_BOTH_EDGE feature is missing from v0.12, so it was time to update to v0.13. I compiled and uploaded v0.13.0-557-g54c7b65d. Again, the ERB refused to connect to the RPi after power cycling, and is not listed by LSUSB.
Two Klippy logs are attached. The one dated 2026-02-16 is with v0.12 on the ERB, the one dated 2026-02-28 is after updating ERB to v0.13.
Any advice or guidance is appreciated.
John
Klippy Logs.zip (499.0 KB)