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.

lennertvdkort commented 4 years ago

Couldn't agree more! Yes i know you can modify the Gcode. But the filament change is also affected by the esteps.

enganear commented 4 years ago

Yes, please. The Bondtech upgrade unlocks a lot of functionality for the Mini. Please release a signed firmware for it.

mobileagellc commented 4 years ago

Yes, please!

bhbloom commented 4 years ago

Yes please

LC3DPS commented 4 years ago

Pretty please! 🙏 Thanks in advance Prusa

andrej-petrovic commented 4 years ago

yes please !

andresfjs commented 4 years ago

Yessss please.

philippbeckmann commented 4 years ago

An even better solution would be to support advanced settings via a new dedicated M-code or the GUI.

darkspector commented 4 years ago

+1

derenma commented 4 years ago

I think I have seen a PID value save setting in the recent commits, and that is probably going to hit in 4.3.0. Maybe. Absolutely don't quote me on that.

I totally agree with the Bondtech upgrade. The flexibility, strength and reliability is absolutely amazing. The stock extruder is perfectly fine, but it cannot handle filament that exceeds +/-0.03mm'ish. When doing draft prints, print quality absolutely does not matter and would rather burn through my awful spools in that regard. Tension adjustment of the stock extruder is, eh, not very good, but it works.

In Prusa's defense, EStep adjustment is a dangerous feature for new printer owners due to the abundance of bad information on the internet. Also, there should be no obligation for Prusa to compensate for out-of-spec filament. This is a company that deals in quality and precision, so why should they have to think about garbage filament?

Edit: The BondTech upgrade for me was a last resort fix. There are going to be other issues that crop up due to this upgrade and I believe I have found one or two already. The BondTech extruder is strong enough to separate the press fittings from the PTFE tube over time if there is a partial clog in the nozzle, so there is that. Oh, this is partially caused by the low tolerance of the inside diameter of the PTFE tube. Hundreds or thousands of retractions will create just enough pressure in the tube for it to work itself out of the press fitting given the increased strength of the new extruder. The extruder is intrinsically tied to the capabilities of the hotend, so there is a ton of room for error in that regard. The small E3D hotend absolutely cannot handle filament that out of spec which the BondTech extruder is capable enough to ram through it with serious consequence. This can be partially mitigated in the slicer by reducing the number of retractions, this is not a fix but rather a time extension on the inevitable issues that are going to crop up. (This can be corrected by a planned maintenance cycle, maybe.)

My particular Mini will be used at my office (after quarantine) for use by people that have no prior experiance with 3D printing. The Estep adjustment problem will absolutely cause issues for these people. I am considering reverting back to the stock extruder for just that reason. Everything must absolutely work correctly in an out-of-box state or I will spend more time fixing peoples prints for the dumbest reasons.

At the end of the day, I completely respect Prusa for removing M500 but it was a very heavy hammer approach for experienced users. I totally get it. I have been thinking about this problem for a month or so and my opinion attempts to be completely objective and of course, subject to error.

BzuciakCZ commented 4 years ago

+1 for it

No need of official Bondtech support, but return of M500 for ESTEPS would be great pain killer for Bondtech upgrade users. Not to mention, lot of those users choose that upgrade as a last effort dealing with notorious heatcreep problems due to factory hotend assembly issues.

Future collaboration with Bondtech on future development of MINI would be beneficial for both parties and mostly for customers themselves.

I like my MINI, it was a good printer (after pushing default heatbreak into heatsing) and is great printer after Bondtech upgrade.

ogland commented 4 years ago

The only (official) reason Prusa removed M500 was that they were having issues with eeprom not working properly. It wasn't due to some UX ease thing. Esteps can be altered anyway. And even if M500 worked, you could still restore factory settings if some noob messed it up.

The mini doesn't have an e3d hotend unfortunately. It would be great if the stock heatbreak would work as good as e3d heatbreak.

JohnnyDeer commented 4 years ago

Hi @ogland, thank you for suggestion. We are considering a solution to this issue.

cnEUL commented 4 years ago

Any way, it would be very useful to have m500 support again. Please make savings to eeprom possible again. I had much problems with the original extruder and now i am using Bondtech. It works great. So also i would prefer to support such hacks. But any way it would be also a good idea to heve better extruder / heatbreak from factory. I love the mini, it is simple to use, small und fast. Also the GUI is very usefull. Come on...

josefprusa commented 4 years ago

Hello everyone. That offer was in respect to the Bear project which is community project. With commercial products there will be some different rules. We will not sign anything which is not thoroughly tested in house for every release, which adds costs. This is all in the making but we will require the producer to have similar customer support to ours with some SLA in order to do it and some other things.

Regardless the esteps and this issue, we will make similar hidden menu for the new platform as we are doing for the 8bit, which will solve this request.

ogland commented 4 years ago

@josefprusa Fantastic! That sounds completely reasonable and very understandable. That reply is 11/10.

BzuciakCZ commented 4 years ago

@josefprusa Understood, this is a good solution. Does it mean M500 will be still limited on Mini? (I need it currently only for ESTEPS anyway.)

PeterDHabermehl commented 4 years ago

PLEASE please please let us enable M500 at least in custom build firmware. I totally understand your intention and I also can accept breaking the appendix. But then at least the fw should build with EEPROM_SETTINGS enabled. I would like to set E-Steps, Extruder loading/unloading max. speed, and PID values. I don't want to take you responsibility on what I do, so I would break the appendix. But the build has to work with EEPROM_SETTINGS enabled. Thank you so much and kind regards Peter

ogland commented 4 years ago

@PeterDHabermehl You should read in the patch notes WHY they disabled it. It's not as easy as just enabling it.

bobc commented 4 years ago

Looking at the code, Prusa already stores several values in EEPROM, adding new ones is quite easy. I don't understand Prusa's reluctance to maintain features that already exist in Marlin and people widely rely on.

ntmaster26 commented 3 years ago

Please please !! :)

dcs3473 commented 3 years ago

Yes Please...

d-zalewski commented 3 years ago

New Mini owner with BondTech extruder and is upgrade. Please make this happen.

bergh-io commented 3 years ago

Yes, we need this :) Any info about if, and if so when, this might me released?

JohnnyDeer commented 3 years ago

Work on hidden menu for BondTech upgrade is in progress, will be in one of next releases.

Pcgrande87 commented 3 years ago

yes please !

sayeghr commented 3 years ago

Is there any update on this issue? I’d really like to upgrade my extruder but am concerned the software doesn’t support it.

Pcgrande87 commented 3 years ago

@sayeghr yes I made a firmware,

sayeghr commented 3 years ago

@sayeghr yes I made a firmware,

What do you mean?

padigree commented 3 years ago

Would be glad if this could implemented soon. It's a confusing to use different start g codes for every prusa I have, also it's difficult to sync this on every machine I slice with..

padigree commented 3 years ago

Are there any news if it could be implemented in the next firmware?

Czarnyszarf commented 3 years ago

Any updates? Commits about this feature?

stickybyte commented 3 years ago

As I had seen in the source code, there seems to be a new menu item called „EEPROM“ (See commit https://github.com/prusa3d/Prusa-Firmware-Buddy/pull/991). Could be the menu @josefprusa talked about? Maybe he can give more infos, if the feature will be part of the next release. I need it too...

Czarnyszarf commented 3 years ago

Im more intrested in hotend PWM fan speed - it may be the solution for Bondtech heatbreak problems.

Also it would improve cooling on modified minis with v6 hotends , they run pretty hot due to inadequate cooling

s-taylor commented 3 years ago

🙏 pretty please allow this. 3d printing is really a hobbiest discipline, and it's expected that people are going to tinker with their printers. Prusa knows this and supports this, they still provide customer support for modded printers so it's a logical step to support this. People are honestly more likely to generate bad prints and contact support because this feature is not baked in.

Czarnyszarf commented 3 years ago

any updates ?

padigree commented 3 years ago

2 1/2 more months are gone..

PeterDHabermehl commented 3 years ago

Break the appendix...-- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 17.02.21, 11:19 schrieb padigree notifications@github.com:

2 1/2 more months are gone.. —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

SteeeveAT commented 3 years ago

Just to push this up, and in hope Josef will realize this soon.

Czarnyszarf commented 3 years ago

bump

SHAXperiment commented 3 years ago

Totally agree. Changing the E-Steps would be amazing. +1

jayseeee commented 3 years ago

Any news on this M500 issue? I also want to be able to change the esteps and the PID values and store them into EEPROM.

BzuciakCZ commented 3 years ago

metoo Waiting so long to be able M500. No need special firmware for me. Just be able to store ESTEPS and PID.

Aquaerics commented 3 years ago

we want the UPDATE now :-)

BzuciakCZ commented 3 years ago

Hi guys. I just got an compromising idea. What about create support for post-start gcode, in which we can put our own initial values. Something like AUTOEXEC.gcode :-) Firmware and EEPROM will remain intact and if you mess something in that gcode, you simply remove USB stick and restart.

This might be useful not only for Bondtech modifications, but for many more features bound to certain USB stick with distinct AUTOEXEC.gcode

I hate running my start gcode manually each time I want to load filament after printer start.

What do you think of this?

derenma commented 3 years ago

@BzuciakCZ I like that idea in general! Even if M500 is never enabled (and I think I have seen the code changes for it, but not sure) your idea could be useful in a number of ways, for sure. Thumbs up!

Czarnyszarf commented 3 years ago

Still no updates? It's disappointing

BogdanH59 commented 3 years ago

I got my MINI+ about two weeks ago, which I've upgraded with Bondtech extruder & heatbreak during assembly. Reason being, I just wished MINI to give best possible results and to avoid unnecessary hassle in the future. But sadly, later I realized one can't upgrade MINI in a comfortable way, because it's impossible to store necessary G-code into EEPROM. And even worse: because latest MINI's are delivered with modified board, it's also impossible to use custom firmware anymore. Not that I'm really interested in custom firmware by itself -but I could at least store G-code. Yes, MINI works as expected, but so do many other cheaper 3D printers. Needless to say that I'm a bit disappointed in this regard. I think this issue should be solved by Prusa as soon as possible.

derenma commented 3 years ago

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.

On Mon, May 24, 2021, 11:57 PM BogdanH59 @.***> wrote:

I got my MINI+ about two weeks ago, which I've upgraded with Bondtech extruder & heatbreak during assembly. Reason being, I just wished MINI to give best possible results and to avoid unnecessary hassle in the future. But sadly, later I realized one can't upgrade MINI in a comfortable way, because it's impossible to store necessary G-code into EEPROM. And even worse: because latest MINI's are delivered with modified board, it's also impossible to use custom firmware anymore. Not that I'm really interested in custom firmware by itself -but I could at least store G-code. Yes, MINI works as expected, but so do many other cheaper 3D printers. Needless to say that I'm a bit disappointed in this regard. I think this issue should be solved by Prusa as soon as possible.

— 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-847559296, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWE53R3WA3OBBOUM3UR4JLTPM33FANCNFSM4PZCWA2A .

Czarnyszarf commented 3 years ago

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. …

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