-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MK2.xS printer community build and support #4604
Comments
Yes indeed. I have recently upgraded my old MK2 to MK2+magnetic bed. |
@vsky279 Thanks for the answer. So you have a MK2 with a MK52 12V bed and a steel sheets, or do you have a different solution for the magnetic bed? |
That's correct. MK2 + MK52 12V bed and a steel sheets. |
The idea is to make it possible to compile the current firmware for different types of MK2S with partial upgrades of MK2S -> MK2.5S
So making it possible to en/disable each of these upgrades enables the community to use the MK2S with any combination of the upgrade parts above. Somebody may want to have IR Sensor, SuperPINDA and MK52 12V bed and would be able to create a new variant to do that. I personally will NEVER change the MK42 bed on my MK2S+IR sensor as it is perfectly good and even for some prints better as there is no sheet that may be pulled up at the corners when filament cools down to fast. |
I had this setup also but get's alwas a leveling error. |
@Hobo2k I don't have a firmware for the MK2.0-MK2.4. This is ticket to look for volunteers and see if there is any demand for it. |
Yeah, a demand for MK2S with the MK52 bed 😉 But I thought, that @vsky279 had a FW for this setup, if I understand his post correctly 😃 |
@Hobo2k Felix, you can try to use one of these compiled firmwares. Better approach would to compile your own as probably you don't need some features that are implemented in this fw. i.e.
You can clone your own branch and remove these commits if needed. |
this! i have an mk2s in process to convert in mk2.5s+ and plus disable mmuX for use the free serial port as esp3d serial port thnx @vsky279 i take look you firmware about support esp3d and the experimental Flashair branch (also i have a unit for all my printers out of prusa) -> sems the flashair is just implemented in firmware, i I thought that branch adds a new features like configure the wifi SSID, webdav, DHCPD, wifi modes, etc in the sd_wifi/config file... i picked the ESP3D commit. thanks @3d-gussner what is the " PAT9125" thing? -> ok, is the old mk3 optical sensor xd, i missread the PAT as patent thing xddd greetings |
Question MK2.5S+ with Einsy board is still considered as MK2.x? i've switch today to this configuration (powerpanic include, all in 12v excepts motors and board iself). but i got fail calibration Z or XYZ in Z step. firmware is a bit messy (hardcoded values in random code) for figure out what happen any throughts? greetings EDIT: FIXED! now calibrates Z and XYZ without problem |
I will be trying to port as many features as I can to my setup.
|
Prusa Research will NOT follow up these issues!
The maintainers of the "Community made" feature should/will react.
Which Community made feature do you want to address?
I have seen few users working on getting the MK2S printers working with the current firmware.
I would suggest to define few things:
Printers with own variants:
MK2.0S = commenting out the FSensor is quiet challenge and I would drop this one as the FSensor can be disabled in MK2.1S
MK2.1S = MK2S + IR sensor
MK2.2S = MK2S + IR sensor + Hotend fan tacho
MK2.3S = MK2S + IR Sensor + Hotend fan tacho + SUPERPINDA
MK2.4S = MK2S + IR Sensor + Hotend fan tacho + SUPERPINDA + BondTech gears and extruder body
No MK2.x as the PAT9125 isn't available anymore.
Difference to MK2.5S would be the MK42 bed vs. MK52 bed and Sheets
As the MK2/S are EOL this would be a community driven firmware and the owners would be responsible to test, maintain and provide support for these.
What is your request/question/suggestion?
Anyone interested? Please leave a 👍 or 👎 to vote for it.
@GilesBathgate @matz9x @vsky279 I have seen that you were working on a custom firmware for your own printers, would you be interested to work on this?
The text was updated successfully, but these errors were encountered: