New Firmware Version for the mk2.5
“New XYZ calibration with image processing”
i wonder what that would be?!
New Firmware Version for the mk2.5
The firmware works fine but my Orballo MK42 only reaches 94°C :-/
Kfazz is your port based on FIRMWARE 3.1.4 (10. 4. 2018) ?
I have a clone with ramps and MK42. It will work? I have not got the filament sensor. I assume if I change the calibration points of the MK52 for my mk42 will work, correct?
The TMC2130 drivers will work? I’m thing upgrade.
when i look at the kicad files the mk52 has only 4 calibration points
but i am in a similar situation. I am currently upgrading my 2 printers to the mk3 frame
one with a mk42 bed
the other with a mk3 later when it is awailable @ orballo printing a 24v mk52 on the other printer.
A good upgrade is the Prusa Steel from Orballo https://orballoprinting.com/estructura/8-estructura-prusa-i3-steel-p3steel.html the frame is compatible with the mk42 heatbed
For 60€ you get a steel mk3 frame / i paid 40 for 2 wooden frames.
The orballo steel is sturdier than wood frames.
So this https://github.com/kfazz/Prusa-Firmware/tree/MK3_Ramps
is what y’all are talking about or where can I find the latest version of the “RAMPS Prusa Firmware”?
Also, a bit of a OT question (I promise it’s just a little one! ): I just got the electronics (Mega 2560 + RAMPS) and LCD for my MK3 clone and I just noticed that I also need an adapter for the screen. Any way I can already test its functionality (and the Prusa interface that I was soo looking forward to test!) by wiring it via breadboard or something like that?
Thank you in advance!
Does someone knows where the calibration points are defined in firmware ?
Woah this looks like exactly what we were looking for. This is modified prusa mk3 firmware that will work on the ramps board right? It looks like it doesnt support the full-graphics smart controller lcd though? I’ll def be trying this out!
I have just upgraded to a Mk42 heatbed and installed the firmware, however It is not working at all. I have Ramps 1.4.
When the printer is on, the Z motors are constantly enabled, with Y and X disabled. When I connect through repetier I get:
09:08:04.730 : No start signal detected - forcing start
09:08:14.855 : Printer reset detected - initalizing
09:08:14.872 : ~??~??f???f???
09:08:14.872 : echo: External Reset
09:08:14.872 : echo: Last Updated: May 4 2018 09:05:27 | Author: (none, default config)
09:08:14.872 : Compiled: May 4 2018
09:08:14.872 : echo: Free Memory: 2186 PlannerBufferBytes: 1360
09:08:14.872 : echo:Hardcoded Default Settings Loaded
I cannot control the printer manually at all. No motor movement or heat.
When I use S3D, i get a constant message of READ:Echo:Busy:paused for user
My printer has worked with Marlin before this. Is there something simple that I’m missing? Baud rates do match on firmware and repetier.
Which firmware exactly did you install? This one? https://github.com/slippyr4/Prusa-Firmware This firmware is preconfigured for the mks board, not ramps control board. So it could be that none of the marlin pins are lining up with your board and that is why its having issues.
Has anyone been successful in getting mk3 firmware onto their ramps/mks + tmc2130 boards by chance? If you have, please let us know how you did it and exactly what firmware you ended up using.
i did nothing change and use a ramps 1.6
only the steps for the extruder
but i have to change some parameters now because i now using a non standard mk3 frame
Hi, I have just built a Prusa i£ clone and am using a rumba board, TMC 2130 driver for X and Y Pinda probe and MK 42 bed. Now, will this firmware work with the above? Will changing the board type to Rumba suffice? As is plainly obvious I am a bit of a novice sp p-lease be gentle…
Has anyone figured out how to get the mk3 firmware working on the ramps clone? If you have, please let us know how you were able to get it working, and what changes to the firmware you had to make. I have seen quite a few forked versions that claim to work but I havent found any yet that compile successfully.
Has anyone used original Pinda probe on a clone
const bool X_MIN_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop. const bool Y_MIN_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop. const bool Z_MIN_ENDSTOP_INVERTING = false; // set to true to invert the logic of the endstop.
have changed in MESH_BED_CALIBRATION.CPP
//#define BED_ZERO_REF_X (- 22.f + X_PROBE_OFFSET_FROM_EXTRUDER) #define BED_ZERO_REF_X (- 20.0f + X_PROBE_OFFSET_FROM_EXTRUDER) //#define BED_ZERO_REF_Y (- 0.6f + Y_PROBE_OFFSET_FROM_EXTRUDER) #define BED_ZERO_REF_Y (- 9.4f + Y_PROBE_OFFSET_FROM_EXTRUDER)
to match the mk42 and the mk3 frame which has modded parts because i didn’t want to cut the extrusions.
But i have 2 problems:
- I can’t use the calibrate Z function because the axsis don’t move up. (after i go to start position i can :-/ / then mesh bed leveling works normally)
- The right side sometimes get stuck an the motor doesn’t move
Did anyone had any problems using this firmware and DRV8825 drivers? Im getting under extrusion right after a retraction is done for the first mm after the retraction, and im inclined to think its the firmware DRV8825. It.runs fine for the rest of the things, but this is messing up the prints. Turning retraction completely off solves it.
what slicer are you using ?
you should be able to solve this with these options…
maybe you retract to fast or to long or to often
Same settings as 1st image. I tried extra length on restart, but its messing up the print. THe ammount needed to be able to fix it is way too much. only 0.7 worked, wich is almost the same as a retraction. The only one that didnt cause i
any problem that i saw was no retraction, but that eventually will cause some problems.
I’ve not had any problems with this firmware and DRV8825. I was using these drivers for a little while before switching to the 2130s and it seemed to work fine.
Has anyone had any luck porting v3.3.1 over to work with RAMPS? It looks like it comes with some nice fixes :).