Marlin 1.1.0 represents an evolutionary leap over Marlin 1.0.2. It is the result of over two years of effort by several volunteers around the world who have paid meticulous and sometimes obsessive attention to every detail. For this release we focused on code quality, performance, stability, and overall user experience. Several new features have also been added, many of which require no extra hardware.
The code has been significantly optimized in several areas, leading to fewer stutters, better delta performance, more reliable USB/Serial communication, and more consistent and deterministic results.
Among the most significant improvements are:
More consistent configuration with sanity-checking.
Many more boards supported, with sane defaults for most common features.
Improved thermal protection, enabled by default with tight margins for error.
Improved Auto Bed Leveling with Bilinear Mesh and probeless operation.
Unified Bed Leveling™ – Combining all forms of bed leveling in one package, plus tools like G26 Mesh Validation to improve leveling accuracy even further.
Option to "fade" leveling compensation out over several layers to save computes on long prints.
Support for up to 5 extruders with different geometries.
Support for mixing and switching extruders.
Linear Advance compensates for viscosity and pressure to reduce ooze and improve surfaces.
Dozens of languages including Japanese, Galician, and Simplified Chinese.
Significantly improved UI performance, especially Graphical Display.
Display rate adjusts dynamically to prevent print stuttering.
M600 Filament Change, Nozzle Clean, Nozzle Park, Auto Park on Pause, etc.
Improved support for Bed Leveling probes and Manual Probing.
Support for Trinamic steppers, i2c control, steppers as endstops.
Endstops can use pin interrupts for improved performance.
M43 Pins Debugging to report about, test, and monitor pins and endstops.
Yeah... The M105 problem is a result of not following proper discipline. Untested changes should not be put into a Release Candidate.
But in the heat of the moment.... It really did make sense. And we had invested a huge amount of time that was used in that decision.
Please start with: [github.com]
and then read: [github.com]
and I can't find the thread where the Floating point isn't allowed inside an Interrupt Service Routine. Go hunt that one down and you will say "Uncle!"
But... Everything will be running much smoother in 2 or 3 days.
Seriously... the M105 problem is very visible and will be 100% fixed in a few days... The bigger problem is we need to figure out how to organize the development and bugfix branches right now so the stable release is 100% stable.
Edited 1 time(s). Last edit at 05/04/2017 09:45PM by Roxy.