probe: remove the old eddy current support

[rogerlz]

The existing support for eddy current sensors is pretty old and unmaintained.

as stated here, we aren't currently working on it, but we will definitely review a good implementation.

[HeavilyModdedEnder3]

Removing it without replacing it will break all BTT Eddy user's Kalico installments (if they update, which of course they will)

[rogerlz]

Removing it without replacing it will break all BTT Eddy user's Kalico installments (if they update, which of course they will)

Yes, thats expected. Due to the how old the code is, I believe there is no one running Kalico and BTT Eddy. And if there is, I would prefer them to know that is it outdated, unsupported and potentially unsafe.

[Bradford1040]

rogerlz I am a Mercury one owner and use BTT EDDY and had it working with Danger Klipper, before the switch, I pulled my rig apart as I was reprinting everything and building a tradrack, got a little overwhelmed so have taken a bit of a break on that machine, but I do believe there are many others that are using the EDDY with Kalico/Danger.

I was just looking around at different updates tonight, and noticed your comment, just bringing up that there are people that use Kalico that are not active on github nor watching to see what is truly happening, they just hit update when they see they have one.

No real reason to reply to me, I was just voicing an opinion about things, I am able to get what I need to work working via my own fork, but others don't and having EDDY working with Kalico IMHO is important to those that can't afford say a Beacon

[rogerlz]

rogerlz I am a Mercury one owner and use BTT EDDY and had it working with Danger Klipper, before the switch, I pulled my rig apart as I was reprinting everything and building a tradrack, got a little overwhelmed so have taken a bit of a break on that machine, but I do believe there are many others that are using the EDDY with Kalico/Danger.

I was just looking around at different updates tonight, and noticed your comment, just bringing up that there are people that use Kalico that are not active on github nor watching to see what is truly happening, they just hit update when they see they have one.

No real reason to reply to me, I was just voicing an opinion about things, I am able to get what I need to work working via my own fork, but others don't and having EDDY working with Kalico IMHO is important to those that can't afford say a Beacon

thanks for the feedback. I will keep it and will add a disclaimer to the documentation that it is outdated and should be used with caution.