@Ro3Deee @josefprusa @RawBearToe83 @Prusa3D I have replied to you in the PR 🤠 Prusa-Firmware-Buddy#5616
80 views
@josefprusa @RawBearToe83 @Prusa3D Here's your PR. Commit 6d9739fba is what broke it. Prusa-Firmware-Buddy#5616
3 likes · 488 views
CORE One "Endstop early trigger" errors when homing since 6.9.1? There's a workaround until Prusa fixes it
If your CORE One (with or without INDX) keeps showing "Endstop early trigger" while homing, or the homing calibration fails, and it started with firmware 6.9.1 or later (including 7.0 and 8.0), you might be hitting this known issue: Prusa-Firmware-Buddy#5520
In short: Prusa lowered the motor current used during homing to stop belts slipping on some printers, but on other printers (often older motors, especially upgraded MK4s, but also some newer motors it seems) it is now too low.
Until Prusa releases an official fix, there is a workaround: firmware 8.0.0 with a setting to raise the homing current, plus a homing calibration that finds a working current by itself. Downloads for the CORE One and the CORE One INDX (but see safety note below about downloading binaries), and simple instructions to build it yourself on Windows, are here:
Prusa-Firmware-Buddy#5520
Please note it's unofficial firmware (but it's just a very few changes to the official firmware), and installing any custom firmware means you have to break the "appendix" seal on the printer's board first (but Prusa expressly says that this does not void the warranty). Also note that building it yourself (which isn't that hard; instructions are in that issue comment) is safer than trusting someone else's binary download.
5 points · 6 comments
@MarcoPiraccini @gonecozycrafts @c13m3n7_3D @broblas @SameOldShane Prusa-Firmware-Buddy#5525
2 likes · 30 views
@NomadsGalaxy @gonecozycrafts @c13m3n7_3D @broblas @SameOldShane I don't see the source code (or tags) yet on gh. github.com/prusa3d/Prusa-Firmware-Buddy/releases
2 likes · 16 views
Firmware 7.0.0 and upwards GitHub release
Important edit: Due to issues with the published source code, the GitHub release has temporarily been made private again. The development team has been alerted and will address the issue first thing tomorrow morning. We’ll republish the release once everything is verified.
Edit2: It's out again
Hey everyone.
After a bit of wait, the firmware is now finally available on GitHub. Take note that firmware 7.0.0 has an important security update that we recommend updating towards (or above). For more information about this, please see the attached security report to the GitHub 7.0.0 release notes.
Important extract from these notes for those that are concerned about how we will handle this in the future:
>We released firmware 7.0.0 and 8.0.0 without publishing their source code at the same time. We did it to give people time to update before the fixes could be studied in the code. That was the wrong call. The Buddy firmware is licensed under GPLv3 and its source belongs next to every binary. Withholding it also gave little protection, because binaries can be analyzed.
>From now on, source code for every firmware release, including security releases, is published on the same day as the binary. When we need time to prepare a security fix, we keep the work private before the release, not after it.
7.0.0: github.com/prusa3d/Prusa-Firmware-Buddy/releases/…
8.0.0: github.com/prusa3d/Prusa-Firmware-Buddy/releases/…
Edit: There was apparently a mistake with the release and the source code is not correctly pointed to. We will fix it as soon as possible. Sorry for that.
98 points · 27 comments
Endstop early trigger after Core One+ Gen2 Upgrade
Just upgraded my Core One+ (Former Mk4S) to Gen2.
Since then i can‘t go further than firmware 6.8.1, else i get the „endstop early trigger“ messages while doing the home calibration.
Gantry is square and belts are tuned to near perfection. But even changing the tension in both directions didn‘t help.
Seems like other people got the same problem:
Prusa-Firmware-Buddy#5520
Did anyone solve this or do i have to wait for a working firmware?
3 points · 11 comments
@davidthepurple @xiphmont the enclosure stuff looks kind of complicated, including temperature checks for stuff that can overheat. not sure this is the right thing, but extended pause can reset the timer too github.com/prusa3d/Prusa-Firmware-Buddy/blob/1ce2…
6 views
Mentions
@Ro3Deee @josefprusa @RawBearToe83 @Prusa3D I have replied to you in the PR 🤠 Prusa-Firmware-Buddy#5616
@josefprusa @RawBearToe83 @Prusa3D Here's your PR. Commit 6d9739fba is what broke it. Prusa-Firmware-Buddy#5616
CORE One "Endstop early trigger" errors when homing since 6.9.1? There's a workaround until Prusa fixes it If your CORE One (with or without INDX) keeps showing "Endstop early trigger" while homing, or the homing calibration fails, and it started with firmware 6.9.1 or later (including 7.0 and 8.0), you might be hitting this known issue: Prusa-Firmware-Buddy#5520 In short: Prusa lowered the motor current used during homing to stop belts slipping on some printers, but on other printers (often older motors, especially upgraded MK4s, but also some newer motors it seems) it is now too low. Until Prusa releases an official fix, there is a workaround: firmware 8.0.0 with a setting to raise the homing current, plus a homing calibration that finds a working current by itself. Downloads for the CORE One and the CORE One INDX (but see safety note below about downloading binaries), and simple instructions to build it yourself on Windows, are here: Prusa-Firmware-Buddy#5520 Please note it's unofficial firmware (but it's just a very few changes to the official firmware), and installing any custom firmware means you have to break the "appendix" seal on the printer's board first (but Prusa expressly says that this does not void the warranty). Also note that building it yourself (which isn't that hard; instructions are in that issue comment) is safer than trusting someone else's binary download.
@MarcoPiraccini @gonecozycrafts @c13m3n7_3D @broblas @SameOldShane Prusa-Firmware-Buddy#5525
@NomadsGalaxy @gonecozycrafts @c13m3n7_3D @broblas @SameOldShane I don't see the source code (or tags) yet on gh. github.com/prusa3d/Prusa-Firmware-Buddy/releases
Firmware 7.0.0 and upwards GitHub release Important edit: Due to issues with the published source code, the GitHub release has temporarily been made private again. The development team has been alerted and will address the issue first thing tomorrow morning. We’ll republish the release once everything is verified. Edit2: It's out again Hey everyone. After a bit of wait, the firmware is now finally available on GitHub. Take note that firmware 7.0.0 has an important security update that we recommend updating towards (or above). For more information about this, please see the attached security report to the GitHub 7.0.0 release notes. Important extract from these notes for those that are concerned about how we will handle this in the future: >We released firmware 7.0.0 and 8.0.0 without publishing their source code at the same time. We did it to give people time to update before the fixes could be studied in the code. That was the wrong call. The Buddy firmware is licensed under GPLv3 and its source belongs next to every binary. Withholding it also gave little protection, because binaries can be analyzed. >From now on, source code for every firmware release, including security releases, is published on the same day as the binary. When we need time to prepare a security fix, we keep the work private before the release, not after it. 7.0.0: github.com/prusa3d/Prusa-Firmware-Buddy/releases/… 8.0.0: github.com/prusa3d/Prusa-Firmware-Buddy/releases/… Edit: There was apparently a mistake with the release and the source code is not correctly pointed to. We will fix it as soon as possible. Sorry for that.
Endstop early trigger after Core One+ Gen2 Upgrade Just upgraded my Core One+ (Former Mk4S) to Gen2. Since then i can‘t go further than firmware 6.8.1, else i get the „endstop early trigger“ messages while doing the home calibration. Gantry is square and belts are tuned to near perfection. But even changing the tension in both directions didn‘t help. Seems like other people got the same problem: Prusa-Firmware-Buddy#5520 Did anyone solve this or do i have to wait for a working firmware?
@davidthepurple @xiphmont the enclosure stuff looks kind of complicated, including temperature checks for stuff that can overheat. not sure this is the right thing, but extended pause can reset the timer too github.com/prusa3d/Prusa-Firmware-Buddy/blob/1ce2…