/Marlin-2.0.x-SKR-Mini-E3-v1.2

The configuration i use for My Printer.

Primary LanguageC++GNU General Public License v3.0GPL-3.0

Marlin 3D Printer Firmware

Build Status GitHub GitHub contributors GitHub Release Date

Marlin is a firmware for RepRap machines, also known as 3D printers. firmware to the next level by adding support for much faster 32-bit and ARM-based boards while improving support for 8-bit AVR boards through the use of a "hardware abstraction layer."

Additional documentation can be found at the Marlin Home Page. Please let us know if Marlin misbehaves in any way. Volunteers are standing by!

BigTreeTech Updated their Firmware, get it here:

https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3

Building Marlin 2.0

To build Marlin you'll need Arduino IDE 1.8.8 or newer or PlatformIO with Visual Studio Code.

Current Target

Creality Ender-3 with SKR Mini E3 v1.2 and Creality BLTouch 3.1

Features Enabled

  • BLTouch (Bi-Linear Bed Leveling)
  • Custom Status Screen (Ender-3 Default)
  • Disable Boot Screens
  • Disable Info Screen
  • Enabled Slim Menus
  • Enabled S Curve Acceleration
  • Disable ARC Support (Cura does not have arc support anyway)
  • Enabled Linear Advance
  • Enabled Square Wave Stepping
  • Enabled Hybrid Threshold for TMC2209 Stepper Drivers
  • Bed Size is 230x230mm
  • Enable Menu to Level Bed Corners (and Center)
  • Pre-Heat for "PLA" and "PETG"
  • Fix for EEPROM saving issue

BLTouch Wiring

I will be updating this picture later to be more clear, the BLTouch Probe cables should go in the Dedicated Probe PIN PC14, not on the Z-Endstop as others suggest.

Please note that ANTCLabs cable colors could be differnet.

Binary File is in the BIN Folder

Please make sure to go over the configuration of the system before installing this Firmware.

4 Flavors, with self explanatory names, BLTouch use a 5x5 grid to probe, and Manual Bed Leveling uses a 3x3 grid.

I am no longer providing 512k variant.

Credits

The current Marlin dev team consists of:

License

Marlin is published under the GPL license because we believe in open development. The GPL comes with both rights and obligations. Whether you use Marlin firmware as the driver for your open or closed-source product, you must keep Marlin open, and you must provide your compatible Marlin source code to end users upon request. The most straightforward way to comply with the Marlin license is to make a fork of Marlin on Github, perform your modifications, and direct users to your modified fork.

While we can't prevent the use of this code in products (3D printers, CNC, etc.) that are closed source or crippled by a patent, we would prefer that you choose another firmware or, better yet, make your own.