search

prusa3d / Prusa-Firmware-Buddy

Firmware for the Original Prusa MINI, Original Prusa MK4 and the Original Prusa XL 3D printers by Prusa Research.
Other
1.13k stars 219 forks source link

[FEATURE REQUEST]Signed firmware for Bondtech modifications #767

Closed ogland closed 2 months ago

ogland commented 4 years ago

Josef recently wrote this: "Recently when concern was raised about the appendix and firmwares for modded printers I offered to provide signed firmwares for well tested and safe modifications."

So now I'd like to cash in on this. Since the buddy firmware right after release of the Bondtech extruder and heatbreak removed the possibility to save esteps (and PID values?) this modification is somewhat crippled. As it is the most tested and safe modification that requires signed firmware, it should exist.

So a custom SIGNED firmware with esteps 415 (1/16 microsteps) is hereby requested.

As a sidenote I'd also like the heatsink cooling fan speed to not be limited, which it seems to be right now. Please at least unlock a secret menu where we can set it to full speed.

derenma commented 3 years ago

You need to track the commits to the firmware, honestly.

On Fri, May 28, 2021, 3:00 AM Czarnyszarf @.***> wrote:

Well, you ain't wrong. Prusa has been working on this issue, and I have been following most of the code updates like a hawk. I am speculating that most of the issues will be resolved after the next board version. … <#m-4653218443366706441>

Where I can find info about that new board and what's happening ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/767#issuecomment-850267225, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWE53VVDBXDWIJZOLYRQD3TP5LS3ANCNFSM4PZCWA2A .

BogdanH59 commented 3 years ago

Correction related to my previous post. Explanation: Per Prusa documentation, appendix on board must be removed (yeah, I know) and jumper must be used. Because new board is missing one of three pins (and printer doesn't boot if jumper is used on remaining two pins), I assumed one can't load custom (non-signed) firmware anymore. As it turned out, custom firmware can be loaded without using jumper. Prusa should mention that in documentation though.

pkg2000 commented 3 years ago

@BogdanH59 Prusa has updated their documentation with a note on this. It will see a larger overhaul to make it more future-proof in terms of hardware revisions.

matthewlloyd commented 3 years ago

Anyone following this issue may be interested to know that I just released custom firmware that adds a menu option to configure e-steps, with presets for the Bondtech extruder with and without reversed wires, amongst other goodies:

http://github.com/matthewlloyd/Llama-Mini-Firmware#readme

enganear commented 3 years ago

Thanks!!!

Stephen Chapman Author - The Stonehenge Rift

On Sun, Jun 27, 2021, 8:17 PM Matthew Lloyd @.***> wrote:

Anyone following this issue may be interested to know that I just released custom firmware that adds a menu option to configure e-steps, with presets for the Bondtech extruder with and without reversed wires, amongst other goodies:

http://github.com/matthewlloyd/Llama-Mini-Firmware#readme https://github.com/matthewlloyd/Llama-Mini-Firmware#readme

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/767#issuecomment-869248207, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOENPB4VXUKRIHGRALIZ6DLTU65QJANCNFSM4PZCWA2A .

ogland commented 3 years ago

Cool @matthewlloyd

How did you fix the eeprom desync that made Prusa disable saving to eeprom in the first place?

matthewlloyd commented 3 years ago

How did you fix the eeprom desync that made Prusa disable saving to eeprom in the first place?

I couldn't find any specific details on the mysterious EEPROM desync (just the patch notes where they say Marlin EEPROM was causing "synchronization issues," and this issue where they say the values "were written inconsistently") so it's hard for me to say.

What I can say is that I didn't reenable Marlin EEPROM settings in Llama, I just followed Prusa's convention of moving the relevant settings into a proprietary section of the EEPROM. So I expect the llama has pronked right over whatever issues there were. :llama:

PippoAe commented 3 years ago

I'd love to see a menu that allows to change settings if the bondtech extruder is installed.

JohnnyDeer commented 3 years ago

Finally we released FW with promised hidden menu. We are sorry it took so long to develop this function. All you need to know is in the release notes. You can find new RC and try it here https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/v4.3.3-RC. Thank you all for patience.

ogland commented 3 years ago

That's great! Do consider adding a feature to use the heatsink fan at 100% too, since many users are having issues with heatcreep.

BogdanH59 commented 3 years ago

Great news indeed! Even I already removed appendix (lost warranty), I still think added features might be useful for me one day.

I assume, many who upgrade the extruder also decide for (Bondtech) heatbreak upgrade. It's known that in this case different PID values are required. That means, to have exact PID values on startup, one still needs modified firmware (or run PID G-code after power on, or after factory reset). Yes, we can run PID calibration which will be kept in memory (until reset)... But as Bondtech heatbreak has became a "standard" upgrade, it would be nice to have an Heatbreak: Prusa / Bondtech option in HW Settings. In my opinion this option would be more useful than Extruder direction (in case there's limited space on display).

anttikarhu commented 3 years ago

Hoping to see support for the Bondtech heatbreak in the official firmware in the future :)

Workarounds of modifying Prusa Slicer printer profiles or running some gcode after every boot both work, but are just workarounds. Using default profiles is easy to use and maintain, and running custom gcode is easy to forget :)

enganear commented 3 years ago

Install the Llama firmware, it already has the ability to store PID values in addition to esteps.

Stephen Chapman Author - The Stonehenge Rift

On Mon, Sep 13, 2021, 2:38 PM anttikarhu @.***> wrote:

Hoping to see support for the Bondtech heatbreak in the official firmware in the future :)

Workarounds of modifying Prusa Slicer printer profiles or running some gcode after every boot both work, but are just workarounds. Using default profiles is easy to use and maintain, and running custom gcode is easy to forget :)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/767#issuecomment-918471484, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOENPBYR7KMFHDXVQXTITYLUBZALZANCNFSM4PZCWA2A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

derenma commented 3 years ago

I like warranties, customer support and that Prusa has dozens of printers to test software updates on. That's just me though.

Was considering buying a second buddy board to mod though...

On Mon, Sep 13, 2021, 7:28 PM enganear @.***> wrote:

Install the Llama firmware, it already has the ability to store PID values in addition to esteps.

Stephen Chapman Author - The Stonehenge Rift

On Mon, Sep 13, 2021, 2:38 PM anttikarhu @.***> wrote:

Hoping to see support for the Bondtech heatbreak in the official firmware in the future :)

Workarounds of modifying Prusa Slicer printer profiles or running some gcode after every boot both work, but are just workarounds. Using default profiles is easy to use and maintain, and running custom gcode is easy to forget :)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/767#issuecomment-918471484 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AOENPBYR7KMFHDXVQXTITYLUBZALZANCNFSM4PZCWA2A

. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675

or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/767#issuecomment-918718079, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWE53TJMKE4LBHWHNKSKUTUB2QLBANCNFSM4PZCWA2A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

JustAnother1 commented 3 years ago

@derenma Why not mod now and buy a second buddy board once you need support?

Aquaerics commented 3 years ago

I think it's a shame that it took so long. I have one of the first batch prusa minis. At the start they said you get weekly firmware updates for the new feature. Than they forbid to use the normal gcode feature to store the steps and the PID values. And now it takes month to get a fancy menue to change it. Normaly they should fixed the gcode storing and it would be easy for everyone. I had breaked my board to get this feature. And now i have to press the reset erverytime to start right. So i'm not amused that it took so long. I think prusa should update the mini that the print quality is the same or better than the mk3. Since it has the newer hardware base.

derenma commented 3 years ago

I am not speaking for Prusa, but there were quite a few underlying issues that needed to get resolved.

There were some massive EEPROM read/write issues as well as some USB driver issues that had to get resolved first. These two subsystems had to be fixed first. I think.

Development work generally does not work out as expected.

On Thu, Sep 16, 2021, 11:08 PM Aquaerics @.***> wrote:

I think it's a shame that it took so long. I have one of the first batch prusa minis. At the start they said you get weekly firmware updates for the new feature. Than they forbid to use the normal gcode feature to store the steps and the PID values. And now it takes month to get a fancy menue to change it. Normaly they should fixed the gcode storing and it would be easy for everyone. I had breaked my board to get this feature. And now i have to press the reset erverytime to start right. So i'm not amused that it took so long. I think prusa should update the mini that the print quality is the same or better than the mk3. Since it has the newer hardware base.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/767#issuecomment-921494664, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWE53VCJLUDR3YI7MRG4R3UCLEMPANCNFSM4PZCWA2A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Aquaerics commented 3 years ago

I'm a software developer too. So i think bug fixing is very important. For the MK3 there were many mechanical updates. For the prusa they took time to get a new level sensor. But they should have noticed it first that the old one did not work as expected. It's seems that the cost range was the only thing that matters to design the mini. For me it woud be better if it cost 200 euros more, and than it can print like the mk3 or better. So it had bondtech extruder and a good printer head out of the factory. There are many cool feature in the mini, so why don't make it a realy good printer?

Czarnyszarf commented 2 years ago

Any updates on this ?

cnEUL commented 2 years ago

the new firmware supports the bondtech extruder. i am using it and it works.

Czarnyszarf commented 2 years ago

I know, I mean heatsink fan speed

Eldenroot commented 1 year ago

Any update from devs for Bondtech heatbreak? Please!

Or release your upgrade kit with these two upgrades---

@Prusa-Support @JohnnyDeer

Prusa-Support commented 1 year ago

Sorry for the late reaction, I was reviewing a few aspects with the rest of the team.

For clarity now, allow me to sum up your current requests.

Honestly, I'm not sure if these features are necessary.

Regardless of this, I'm taking notes and passing them along to the developers. The issue will stay open, and our developers will do their consideration about these quite popular requests.

Michele Moramarco Prusa Research

Eldenroot commented 1 year ago

@Prusa-Support - Hi, thank you for your reply!

I think that Prusa firmware should support these:

These two are missing and I think they are useful.

Add them into "secret" menu makes sense and will not be confusing for newbie and "normal" users

image

BzuciakCZ commented 1 year ago

Thanks for update Michele, 100% fan speed would be sooo coool!

We could use E3D Revo Micro original fan or Noctua silent fans without having to source 5V fan power from other pins of the mainboard.

I believe it is small code change with great impact.

Regards, Zbynek

On 27. 10. 2022, at 16:03, Prusa-Support @.***> wrote:

 Sorry for the late reaction, I was reviewing a few aspects with the rest of the team.

For clarity now, allow me to sum up your current requests.

Support for Bondtech/custom heat-breaks, in a similar fashion as customizable extruder settings. Compatibility with custom PID settings. I guess this would also address Bondtech/custom heat-breaks incompatibility problems. An option to enable 100% hotend fan speed (probably something like AltFan on MK3). Honestly, I'm not sure if these features are necessary.

To address the first two points, our tests proved our MINI thermal regulation to be suitable for custom heat-breaks (see Buddy FW 4.3.3), rendering specific heat-break settings and custom PID settings unnecessary (nonetheless, we got other similar requests #1341, #2401). To address the last point, heat-creeps are most often caused by factors other than the hotend fan running at regular, safe and adequate speed as per our defaults (not 100%). Regardless of this, I'm taking notes and passing them along to the developers. The issue will stay open, and our developers will do their consideration about these quite popular requests.

Michele Moramarco Prusa Research

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

ogland commented 1 year ago

I would also like to add to this to please lower load/unload speed slighly since it seems that it's slightly too fast for the motor/mcu to handle when using Bondtech esteps. Maybe even a load/unload length and speed option in hwmenu.

Prusa-Support commented 1 year ago

Thank you again for your suggestions. Our developers will look into this. Also please notice we are talking about the use of 3rd party components so, in the meantime, you may consult with the author of the mod or the parts vendor. You can even get in touch with other adopters of the mod among the community on forums (may our forum.prusa3d.com), as they may have tips, workarounds and experience in general to share.

Michele Moramarco Prusa Research

ogland commented 1 year ago

@Prusa-Support the only workaround with good UX for all these issues would be custom firmware, but that breaks warranty so not really a viable workaround.

Prusa-Support commented 1 year ago

True. As a company, we can't take legal responsibility for the use of third-party components, and we can't even vouch for them. The software and the product remain Open Source though, so modfing the firmware is legit but you do it at your risk.

Michele Moramarco Prusa Research

ogland commented 1 year ago

@Prusa-Support exactly, so the only real and simple solution in good UX would be to add these simple features to the menu. I don't really see a single reason not to do that, but I can see many reasons for not removing them in the first place.

Starving the heatsink cooling may be good for noise, but as we can see in forums and groups many are having heatcreep. So I think it's worth testing 100% speed at least :)

BzuciakCZ commented 1 year ago

100% true Olof!On 10. 11. 2022, at 14:55, ogland @.***> wrote: @Prusa-Support exactly, so the only real and simple solution in good UX would be to add these simple features to the menu. I don't really see a single reason not to do that, but I can see many reasons for not removing them in the first place. Starving the heatsink cooling may be good for noise, but as we can see in forums and groups many are having heatcreep. So I think it's worth testing 100% speed at least :)

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Czarnyszarf commented 1 year ago

I appove this, it was a year already..please do something with that!

FabianMPunkt commented 1 year ago

Is there any update on the 38% fan speed situation yet? Since this issue is still open, my guess is that the dev team still has this on their list? I really hope we can get an adjustable fan speed, the same way we can adjust E-Steps. That would make it possible to install a much quieter Noctua fan, and still get enough cooling to prevent heat-creep.

github-actions[bot] commented 3 months ago

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

github-actions[bot] commented 2 months ago

This issue has been closed due to lack of recent activity. Please consider opening a new one if needed.