Trouble with katapult

General Discussion
1

Basic Information:

Printer Model: mercury zerog
MCU / Printerboard:kraken
Host / SBC btt pi
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:

So I’m installing a ebb36 following the esoteric canbus guide and can’t get back to klipper from katapult
…

2

Hi ten57,

katapult is only the bootloader (needed for CAN implementation).
After you flashed successfully katapult, you have to flash (over CAN) klipper.

Here are general instructions for flashing katapult and klipper via CAN:

And here is the instruction for flashing klipper via CAN specialy for EBB36:

I know, the articles are in german, but I hope it helps you.
It is extremely important that you set the correct bootloader offset for the EBB36 when compiling klipper.

3

Stick to these guides. They are excellent.

As mentioned by @KosstAmojan, you probably forgot or not correctly flashed Klipper.

Installing Katapult will delete the entire flash memory and as long as no Klipper firmware is installed the board will only come up in Katapult / Bootloader mode.

4

And, very important, have you set the 120Ohm resistor for the CAN bus?
If not, you get no or not a stable connection to the toolhead for flashing.

5

I believe i got klipper back but now it won’t connect to mcu

6

Could you upload a klippy.log?

7

Did you set the right can_uuid in printer.cfg?
for both, board and toolhead ? Something linke

[mcu EBBCan]
##  uncomment mcu communication type you use
##  for serial: obtain definition by "ls /dev/serial/by-id/*" then unplug to verify
##  for CAN: obtain can uuid by ""~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py <can interface>""
# serial: /dev/serial/by-id/usb-Klipper_Klipper_firmware_12345-if00
canbus_interface: can0    # default is "can0"
canbus_uuid: 2e12ab8ec8ce

And

[mcu]
##  uncomment mcu communication type you use
##  for serial: obtain definition by "ls /dev/serial/by-id/*" then unplug to verify
##  for CAN: obtain can uuid by ""~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py <can interface>""
# serial: /dev/serial/by-id/usb-Klipper_Klipper_firmware_12345-if00
canbus_interface: can0    # default is "can0"
canbus_uuid: 34943f8a8f6b
8

Do I replace my original mcu, with that

9

klippy (5).log (606.3 KB)
i was at work so couldn’t post klippy

10

Standard way is to use serial connection for board mcu and eddy mcu (snippet from your klippy.log):

[mcu]
serial = /dev/serial/by-id/usb-Klipper_stm32h723xx_0C0013000C51323532393433-if00

[mcu eddy]
serial = /dev/serial/by-id/usb-Klipper_rp2040_50445061304E4E1C-if00

You flashed katapult (can bootloader) and klipper on your board and eddy, so you have to set your mcu connections with CAN bus in your printer.cfg.

If you use the esoterical can guide look here:

11

And as I see, your klippy.log says, you have the eddy connected via I²C and not via CAN:

[probe_eddy_current btt_eddy]
sensor_type = ldc1612
z_offset = 2
i2c_mcu = eddy
i2c_bus = i2c0f
12

what do i change the eddy to and ive made the changes you suggested and still unable to connect

13

First: what kind of “eddy” do you have?
There are 3 eddy’s:

  1. Eddy Coil (only I²C; no USB or CAN connection)
  2. Eddy USB (only USB, for direct connection to a Pi, no CAN, no I²C connection)
  3. Eddy Duo (USB or CAN; no I²C connection)

Do you compile klipper for the Eddy with the right settings?
USB:

CAN:

384601845-e60728d1-98c9-42ef-89f1-c04a19966559
384601845-e60728d1-98c9-42ef-89f1-c04a19966559690×196 6.74 KB

The sample printer.cfg on the BTT EDDY github is only for the I²C or USB connection.

Here is a thread on github which seams to solve the can setup problem:

14

duo im lost i tried flashing it its not coming up when i ls /dev/serial/by-id/*

15

And that’s good => if you have a Duo with the switch to CAN (instead of USB) and flashed katapult (CAN bootloader) and klipper via CAN, because you don’t have a serial device anymore.

Or do you want the Eddy Duo connect via USB with the SBC (f.e. BTT Pi)?

You should only have the “can bridge device” as serial device (plus the on-board-devices from the Pi).

16

im not getting anywhere i cant flash klipper back to main board

Screenshot 2025-06-10 055148
Screenshot 2025-06-10 055148945×226 8.1 KB

17

Yes, you CAN (and without Obama :wink: )

as your picture shows: OpenMoko, Inc. Geschwister Schneider CAN adapter.
that’s the CAN bridge adapter (example : Dedicated USB CAN Device | Esoterical’s CANBus Guide )

follow the esoterical CAN guide:

18

is it supposed to stay saying OpenMoko, Inc. Geschwister Schneider CAN adapter.

19

That’s the CAN Interface.

20

Maybe this would help: it’s a step-by-step guide for the Octopus Pro board

and here one for the BTT Manta M8Pv2:

The configuration of the klipper firmware is different, but the steps should be the same for the Kraken board.