Félix Boisselier

> hi just downloaded shake and tune last week for my vzbot 330 awd with octopus max ez and beacon. i can complete the belt analysis no problem but when...

Hello, thanks for the PR! It's a good starting point. But there's a couple of changes that are needed to align it more with current Klippain logic and simplify the...

> Should I include rehoming the z axis in the `tilt_calib` action if the `probe_type_enabled` is `cartographer_touch` or would you suggest a different approach? No, this is not necessary. In...

Thanks Elpopo, that's indeed a pretty good and clean way to do it. Do you want to PR it to Klippain for integration? Le mar. 21 janv. 2025, 13:59, elpopo...

I'm coming back on the topic since a some time on Shake&Tune... Did you solved your issue? Usually the error with IFCNT is indeed a bad wiring or bad configuration...

Hello, I'm pretty sure this is not Shake&Tune related since I don't use the dateutil library... Can you share a klippy.log with the error to validate its origin?

Hello, Was this issue solved ? I think it's due to an incorrect matplotlib version or something like this. Probably that running the install script of Shake&Tune again should fix...

Ok, you're right! I think the problem is that more and more plugins are designed for Klipper, and we all reuse the Klipper virtual environment. Each plugin has different requirements...

Hello, there's this PR under work to allow this: https://github.com/Frix-x/klippain-shaketune/pull/154

Hello, thanks for the PR! I'm pretty open for this change as it will indeed allow to split and simplify the logic :) However, let's keep it simple: 1. Can...