Printer Model: Custom Core XY
MCU / Printerboard: Fystec Cheetah V3
Host / SBC BTT Pi 2
klippy.log - no klippy log - printer still in final build stage
Describe your issue:
I’m just finishing a core XY build and I’ve seen the Eddy coil is available for a handful Australian pesos and considering incorporating one into the design. The main reservation I have it that in it’s current state it requires a BTT version of Klipper and I’m not totally sold on the idea.
The BTT Pi 2 already uses it’s own version of Klipper from what I understand so maybe it’s not a major issue in that respect but I was considering purging the BTT version of Klipper and trying to run a standardised version of Klipper on it to remove all the AI (Obico) stuff they’ve tacked onto their Klipper install. I’m not using the AI functionality so that just seems like an unnecessary overhead I could do without.
Would it create any issues in respect to support on here if I have issues configuring it or would I have to rely on support from BTT?
…
Hi @Mendax I was running Klipper on a RPI 4 with my E3 V3 SE. I have repurposed the RPI for my Voron 2.4 build and have replaced with a BTT Pi 2.
I haven’t had any problems running a vanilla version of Klipper, I’m currently running v0.12.0-263-g0087f04c which just updated tonight.
I installed the klipper version of the Pi 2 image and then just installed Kiauh and uninstalled the embedded Klipper / Moonraker / crapware and started fresh.
The main reasons for choosing the BTT was the 24v option and the $20 saving. With all the hassle of trying to get the UART and GPIO running, I can tell you it wasn’t worth it.
If I had my time again I would just go for the genuine RPI, and may still go that way anyway. Seems like there is plenty of Pi stock here in Oz.
Most of the Eddy relevant code is already present in Klipper and remaining piece is shortly before getting merged, which would bring it to feature parity with the BTT version. See https://github.com/Klipper3d/klipper/pull/6602
Essentially the BTT version is a “draft implementation” of the Klipper code.
Thanks for the replies guys, that’s useful information from both of you.
The main appeal of the Eddy coil for me with this build is its speed advantage during its bed mesh routine. The new build has a 310 x 310 bed and a regular probe seems to take ages . Not having moving parts seems like a plus too. I might try one and see how it goes.
I almost bought one of these yesterday and I noticed the Eddy coil variant which works with the EBB36 doesn’t have temperature compensation, only the Eddy variant does and it’s a USB connection. So they recommend to use it with a probe which defeats the purpose of what I wanted it for - as a replacement for a probe.
The CAN version might be worth the wait. The Eddy Current has the thermistor populated on the coil board but the LDC board doesn’t connect it to anything. I hacked my Eddy Current to use the included thermistor with my EBB36 as the mcu. All the parts are in Klipper now except for one gotcha during initial calibration.
