MCU returned is not same by katapult and klipper

General Discussion
1

Basic Information:

Printer Model: Custom core xy
MCU / Printerboard: Manta 8P
Host / SBC: CB1
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 followed the guide ( Reddit - Please wait for verification ) to connect eddy duo with ebb42 via CAN. but I get below observations.

I see only Klipper here, no katapult.

Also the MCU returned is not same by katapult and klipper.

Can someone help me here.

image
image1557×1358 420 KB

…

config-20260530-174321.zip (8.8 KB)

klippy (20).log (234.9 KB)

2

What’s wrong with the official instructions?

3

Thanks, I executed the steps as mentioned in the manual but stuck at point no 5.3>>3>>3.

Could not find UUIDs.

biqu@bigtreetech-cb1:~$ ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
Total 0 uuids found

For finding the UUIDs, what should I connect eddy through? USB or CAN?

4

I don’t have an Eddy duo (I bought the plain coil for this very reason) but as I understand it you need to:

  1. Build klipper.bin for the Eddy with CAN enabled in make menu.
  2. Connect the the Eddy in USB mode (mind the switch on the Eddy)
  3. Flash the firmware
  4. Unplug the Eddy, switch to CAN mode
  5. Wire the Eddy to the toolhead
  6. Find the UUID

NOTE: The toolhead board is simply an electrical junction point and is not “involved” in the communication with the Eddy.

Any Eddy Duo owners have any other advice?

5

Thanks…

Some questions…plz let me know if anything is wrong in the commands and steps sequence.

  1. Build klipper.bin for the Eddy with CAN enabled in make menu.
    2. Connect the the Eddy in USB mode (mind the switch on the Eddy)
    → Switch to be in USB side?
    3. Flash the firmware
    → flash with the command : make flash FLASH_DEVICE=2e8a:0003"
    4. Unplug the Eddy, switch to CAN mode
    → connect the Eddy duo to Ebb42 using CAN wires with switch on CAN side?
    Wire the Eddy to the toolhead
    5. Find the UUID
    → with command : “python3 ~/katapult/scripts/flashtool.py -i can0 -q”

I see below result:

biqu@bigtreetech-cb1:~/klipper$ python3 ~/katapult/scripts/flashtool.py -i can0 -q
Resetting all bootloader node IDs…
Checking for Katapult nodes…
CANBus UUID Query Complete
biqu@bigtreetech-cb1:~/klipper$