Jump to content

do NOT push the UPDATE ALL button!


Dirk

Recommended Posts

Klipper pushed a large update, which seems to be the BTT branch of Klipper that supports the BTT Eddy probe.

This has as consequence that ALL probes that have a klipper plugin, like Beacon and Cartographer, have to follow the same routine that the BTT Eddy probe requires.

This has as consequence that these probes did not function as soon as the update was applied. Luckily the programmers quickly reacted and within a few hours there was already an update from Beacon and Cartographer.

HOWEVER, with such a huge update, which cost BTT almost a year to (have) develop(ed),  issues still may arise.

So do like I did, and wait a bit longer before updating... Do not fix something that works perfectly. 

 

301059869-2b35e7a5-d2b7-4f50-9db7-5e4202ad85ed.gif.c6a3eeae1e260b0f1f0f34111719c8b7.gif

 

And if you already did update, and you have a completely useless printer and are considering going back to TAP or Klicky, run this command in your SSH, which will reset all updates from github back to the time before the BTT-Klipper.

 

 
cd ~/klipper
git reset 6cd174208bd9bbd51dc0d519a26661fb926d038a --hard
 
After this, a reboot (power recycle) may be necessary.
 

 

 

  • Like 4
  • Thanks 4
Link to comment
Share on other sites

17 hours ago, Dirk said:

Klipper pushed a large update, which seems to be the BTT branch of Klipper that supports the BTT Eddy probe.

This has as consequence that ALL probes that have a klipper plugin, like Beacon and Cartographer, have to follow the same routine that the BTT Eddy probe requires.

This has as consequence that these probes did not function as soon as the update was applied. Luckily the programmers quickly reacted and within a few hours there was already an update from Beacon and Cartographer.

HOWEVER, with such a huge update, which cost BTT almost a year to (have) develop(ed),  issues still may arise.

So do like I did, and wait a bit longer before updating... Do not fix something that works perfectly. 

301059869-2b35e7a5-d2b7-4f50-9db7-5e4202ad85ed.gif.c6a3eeae1e260b0f1f0f34111719c8b7.gif

And if you already did update, and you have a completely useless printer and are considering going back to TAP or Klicky, run this command in your SSH, which will reset all updates from github back to the time before the BTT-Klipper.

 
cd ~/klipper
git reset 6cd174208bd9bbd51dc0d519a26661fb926d038a --hard
 
After this, a reboot (power recycle) may be necessary.
 

Thankyou for the information I have got a lot of my parts coming in the mail and was going to update them all is there a version number that is working right I am using voron tap 

Link to comment
Share on other sites

Safe to update if you do it correctly:

 

I have just updated my micron and VZBot with a beacon probe.

Important if you have a beacon probe, to first update beacon software to the latest release (v2.0.0-10-g0946c7cd), then flash the beacon probe with the latest firmware by ssh-ing into the Raspi and issuing the following command:

./beacon_klipper/update_firmware.py update all

This will update the beacon firmware to:

 

mcu beacon(beacon)
Version: Beacon 2.0.1
Load: 0.00, Awake: 0.00, Freq: 32 MHz,

 

and then only update klipper to v0.12.0-237-gfcf064ba.

On the machines with the cartographer probes - Update the cartographer software first, then update klipper.

On the machines with Voron TAP - update as per normal

On the machines with klicky type probes - update as per normal

Following the above all my machines/printers are fully functional.

 

  • Like 1
Link to comment
Share on other sites

After I placed this post, Klipper again pushed a few updates that did change some more probe code.

Breaking again the backwards compatibility at the cost of supporting BTT hardware.

This makes me wonder if BTT is paying klipper programmers to do so.

I saw a new update for beacon and cartographer after this klipper update. 

I doubt you need the BTT Eddy functionality. So I am almost sure the updates do not do anything for beacon and cartographer users. 

But sure, if you want to be up to date always, update 🙂

Link to comment
Share on other sites

23 minutes ago, Dirk said:

Breaking again the backwards compatibility at the cost of supporting BTT hardware.

"You have to break some eggs to make an omelette" o.O

23 minutes ago, Dirk said:

This makes me wonder if BTT is paying klipper programmers to do so.

I guess I can't fault the developers for wanting to make some money.. 🤑

26 minutes ago, Dirk said:

But sure, if you want to be up to date always, update 🙂

The buttons are all calling to me!!

2024-06-15-101201_509x494_scrot.png.c44c1f21a058cba48561ad5a20b0db9d.png

I know it will probably be a royal pain, but I do want to try the BTT Eddy on my Vorpal 180... I just don't know when I'll find the time.

  • Like 1
Link to comment
Share on other sites

I doubt it will be a problem for BTT Eddy.

The klipper version has been BTT, has become mainline. Breaking with Beacon d Cartographer and probably also Mellows new probe.

But again, even Klipper has pushed a new fix for the updates they pused a couple of days ago.

I know Beacons programmers work on compatibility asap. But I also know Cartographer has only one programmer who has also other obligations (like a full time job).

So if you want to test your Eddy probe, check out the information from BTT and update. And good luck 🙂

I doubt the instructions from @KrauTech will still work though...

 

Edited by Dirk
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...