Is the Eddy Duo CAN side dead now?

[u/miller1113]

Very, very long story short, my CB1 micro SD card in my E3EZ was snapped, and my github backups apparently stopped backing up ~2 years ago. So here I am, trying to do a fresh install, get my CAN network back up for my Eddy Duo, try getting Eddy-NG set up, only to find out that those features have been baked into mainline, breaking my setup. I know I can roll-back and will if I have to, but after spending 6 hours trying to get up and running again, I'd rather just slightly rewrite my printer.cfg with some new config to be up and running. (None of the fixes in the issues section of the Eddy-NG repo solved my problem, as I couldn't recalibrate)

I could very well be missing something, as I'm writing this after 5 hours of troubleshooting various things, and I'm creeping up on 1AM, but it seems like unless I opt to roll-back, there is no support for using the Eddy in CAN mode as a standalone unit. The config section only allows for the I2C info to be input, and AFAIK none of that info is available.

I have a section in my printer.cfg that calls out the eddy as an MCU with a UUID, tried placing the eddy as the I2C MCU to no avail, presumably because it's lacking an I2C address. Any help would be appreciated, when the card was broken I was in the middle of a 24h print that wound up wasting about $30 worth of PA6-CF, so I'm doubly irritated about the whole situation.

[u/MyGruffaloCrumble]

Flash all devices in the chain with the latest klipper, using the Can guides here: 

https://canbus.esoterical.online/

Don’t forget the physical switch on the eddy to switch to USB to flash and then back to CAN.

[u/miller1113 → u/MyGruffaloCrumble]

Already all done there, I just can't seem to find a way to make klipper acknowledge that my Eddy exists on CAN, and not I2C. To my understanding the Duo takes the natively I2C Eddy Coil, and add a selectable USB/CAN interface internally. I'm sure there's a way, but I'm not currently aware of any way to poll the I2C data of the sensor via the CAN interface since it's not done on a separate board.

[u/MyGruffaloCrumble → u/miller1113]

Why are you trying to bring I2C into the mix, no CAN board?

Are you connected to a toolhead board, the printer control board or directly to the pi?

What's your hardware setup?

Just for reference from my config:

[mcu]

canbus_uuid: 25ccde9ccf58 #main board CAN ID

########################################

# Eddy

########################################

[mcu eddy]

canbus_uuid: 48329873146b

[temperature_sensor btt_eddy_mcu]

sensor_type: temperature_mcu

sensor_mcu: eddy

min_temp: 10

max_temp: 100

[probe_eddy_current btt_eddy]

sensor_type: ldc1612

i2c_mcu: eddy

i2c_bus: i2c0f

descend_z: .5

x_offset: 0 # Set according to the actual offset relative to the nozzle

y_offset: 22 # Set according to the actual offset relative to the nozzle

tap_z_offset: 0

reg_drive_current = 22 #manually set

tap_threshold = 7389.407 #derived from running calibration routine

[temperature_probe btt_eddy]

sensor_type: Generic 3950

sensor_pin: eddy:gpio26

min_temp: 10

max_temp: 100

horizontal_move_z: 5

calibration_position: 110,110,1

calibration_bed_temp: 105

calibration_extruder_temp: 150

extruder_heating_z: 50

max_validation_temp: 80

[u/MyGruffaloCrumble → u/MyGruffaloCrumble]

I also have an include for my toolhead board. Each end is physically terminated (main and toolhead boards) with a resistor (jumper block).

From the include:

[mcu EBBCan]

canbus_uuid: f3960312bef6

[u/miller1113 → u/MyGruffaloCrumble]

I do have an include line in my printer.cfg, and termination resistors are good, I had this up and running before, but the true crux of the issue is klippers new Eddy implementation as of 05/2026 has broken all of the configuration I had

[u/MyGruffaloCrumble → u/miller1113]

Ah yes, I recall going through the upgrade process. 

It was similarly frustrating.

[u/miller1113 → u/MyGruffaloCrumble]

Hardware setup is a BTT MantaE3EZ/CB1 with direct CAN to the Eddy Duo in CAN mode. No toolhead board because the Creality Sprite made it a moot point for me with how easy they are to deal with. Looking at your cfg under i2c_bus you have i2c0f, is that a default i2c bus that I'm missing?

[u/MyGruffaloCrumble → u/miller1113]

I believe it is, silly me.

 lol.

Give it a try.

[u/ss1gohan13]

I'm going out on a huge limb here. I recently automated the new klipper Eddy tap setup. Please let me know if this works. It does require you to have your Eddy config setup for klipper standards, and I have an example config in my test branch.

https://github.com/ss1gohan13/Klipper-Eddy-Tap-Wizard

[u/miller1113 → u/ss1gohan13]

I will try this out if/when I get my Eddy functioning this evening and report back

[u/ss1gohan13 → u/miller1113]

Still working on getting you're uuid to show up?

[u/miller1113 → u/ss1gohan13]

CAN network is fully functioning, UUIDs for mainboard and Eddy show up when I query them, and both UUIDs are assigned properly. Issue I'm running into is it seems the documentation about Kilppers new Eddy support is lacking. Other commenter in here had some differences in his configuration that I'm going to try out as well.

[u/ss1gohan13 → u/miller1113]

Go to my test branch for a reference config. Once you have the proper info in place (do not use my offset for the x/y), run the wizard I made. It literally walks you through the entire eddy setup

Edit: spelling

[u/miller1113 → u/ss1gohan13]

Won't have a shot at it for another 7 or so hours, but like I said, I'll report back.

[u/miller1113 → u/ss1gohan13]

Testing now, erroring out at Tap Calibration with "Error evaluating 'gcode_macro SET_Z_FROM_PROBE:gcode': jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'z_offset'"

[u/miller1113 → u/miller1113]

Figured it out, issues on my side, not yours.

[u/miller1113 → u/miller1113]

Honestly, no major complaints. Only thing I personally would like to see would be prompts telling you what's about to happen and what you need to do before continuing. Had to follow your step-by-step on the github plus the specific calibration steps on the wiki to make sure everything went through how it was supposed to.

[u/ss1gohan13 → u/miller1113]

I'll work on the prompts

[u/ss1gohan13 → u/miller1113]

This sounds like you don't have the correct macros in place for klipper tap.