/Ender-5-Plus-Stock-Marlin-BTT-Mini-E3-EZ-V3

Firmware for stock ender 5 plus with BTT Mini E3 V3. Works with stock screen but will have to change pin-out diagram coming soon :)

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

MarlinFirmware's logo

This is a customised version of Marlin for the Ender 5 Plus to work with the BTT SKR 3 mainboard and using the stock LCD.

The stock LCD needs to be flashed with a custom LCD firmware available from https://github.com/Desuuuu/DGUS-reloaded/wiki/Flashing-the-firmware or it will not work with anything other than the stock main board, and the very buggy and outdated version of Marlin that Creality created 5,000 years ago.

The LCD will also need the cable modifying to fit the SKR 3 mainboard, this is a very simple modification and can be done in several ways. I'll add a diagram with pictures showing how it's done once I can figure out how to insert images into this page. (four pins, tx2-pa10 rx2-pa9 gnd-g 5v-+5v, clearly labelled on the silkscreens!)

I have made the compiled Firmware.bin file available in the root of this repo, so you can just copy it onto a micro SD card, plug it into the SKR 3 and power on. Once it stops flashing, power it off, remove the SD card and it will be ready to use.

However, every change I made to the most recent Marlin Bugtree branch is included here too so you can easily make the neccessary changes that you will VERY probably need to make to calibrate this firmware to work correctly with your setup. This is because I haven't got round to learning that side of things, I just wanted to prove the Stock LCD screen could be very easily made to work with Marlin on the SKR 3 and other SKR boards (and klipper too, but there's already a fork for that available from Desuuuu, though I've not tested it as of yet on the SKR 3)

Hope this helps a lot of people save money when they choose to upgrade/replace their main boards, so they're not pushed into purchasing a non-needed, and non-fitting, LCD (like the tft35) :)

Feel free to comment or reach out if you need assitance with anything, or want to leave me any feedback. I thrive on feedback of any kind, so be as blunt and direct or harsh as you feel like. It'll help make a better build for everyone :)

If you feel like buying me a coffee as a thanks, could you please make a donation to Viva instead https://viva.org.uk/donations/viva-donation-form/

Marlin 3D Printer Firmware

GPL-V3.0 License Contributors Last Release Date CI Status GitHub Sponsors
Follow MarlinFirmware on Twitter

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

Marlin 2.1 Bugfix Branch

Not for production use. Use with caution!

Marlin 2.1 takes this popular RepRap 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. Read about Marlin's decision to use a "Hardware Abstraction Layer" below.

This branch is for patches to the latest 2.1.x release version. Periodically this branch will form the basis for the next minor 2.1.x release.

Download earlier versions of Marlin on the Releases page.

Example Configurations

Before building Marlin you'll need to configure it for your specific hardware. Your vendor should have already provided source code with configurations for the installed firmware, but if you ever decide to upgrade you'll need updated configuration files. Marlin users have contributed dozens of tested example configurations to get you started. Visit the MarlinFirmware/Configurations repository to find the right configuration for your hardware.

Building Marlin 2.1

To build Marlin 2.1 you'll need Arduino IDE 1.8.8 or newer or PlatformIO. We've posted detailed instructions on Building Marlin with Arduino and Building Marlin with PlatformIO for ReArm (which applies well to other 32-bit boards).

Hardware Abstraction Layer (HAL)

Marlin 2.0 introduced a layer of abstraction to allow all the existing high-level code to be built for 32-bit platforms while still retaining full 8-bit AVR compatibility. Retaining AVR compatibility and a single code-base is important to us, because we want to make sure that features and patches get as much testing and attention as possible, and that all platforms always benefit from the latest improvements.

Supported Platforms

Platform MCU Example Boards
Arduino AVR ATmega RAMPS, Melzi, RAMBo
Teensy++ 2.0 AT90USB1286 Printrboard
Arduino Due SAM3X8E RAMPS-FD, RADDS, RAMPS4DUE
ESP32 ESP32 FYSETC E4, E4d@BOX, MRR
LPC1768 ARM® Cortex-M3 MKS SBASE, Re-ARM, Selena Compact
LPC1769 ARM® Cortex-M3 Smoothieboard, Azteeg X5 mini, TH3D EZBoard
STM32F103 ARM® Cortex-M3 Malyan M200, GTM32 Pro, MKS Robin, BTT SKR Mini
STM32F401 ARM® Cortex-M4 ARMED, Rumba32, SKR Pro, Lerdge, FYSETC S6, Artillery Ruby
STM32F7x6 ARM® Cortex-M7 The Borg, RemRam V1
STM32G0B1RET6 ARM® Cortex-M0+ BigTreeTech SKR mini E3 V3.0
STM32H743xIT6 ARM® Cortex-M7 BigTreeTech SKR V3.0, SKR EZ V3.0, SKR SE BX V2.0/V3.0
SAMD51P20A ARM® Cortex-M4 Adafruit Grand Central M4
Teensy 3.5 ARM® Cortex-M4
Teensy 3.6 ARM® Cortex-M4
Teensy 4.0 ARM® Cortex-M7
Teensy 4.1 ARM® Cortex-M7
Linux Native x86/ARM/etc. Raspberry Pi

Submitting Patches

Proposed patches should be submitted as a Pull Request against the (bugfix-2.1.x) branch.

  • This branch is for fixing bugs and integrating any new features for the duration of the Marlin 2.0.x life-cycle.
  • Follow the Coding Standards to gain points with the maintainers.
  • Please submit Feature Requests and Bug Reports to the Issue Queue. Support resources are also listed there.
  • Whenever you add new features, be sure to add tests to buildroot/tests and then run your tests locally, if possible.
    • It's optional: Running all the tests on Windows might take a long time, and they will run anyway on GitHub.
    • If you're running the tests on Linux (or on WSL with the code on a Linux volume) the speed is much faster.
    • You can use make tests-all-local or make tests-single-local TEST_TARGET=....
    • If you prefer Docker you can use make tests-all-local-docker or make tests-all-local-docker TEST_TARGET=....

Marlin Support

The Issue Queue is reserved for Bug Reports and Feature Requests. To get help with configuration and troubleshooting, please use the following resources:

Contributors

Marlin is constantly improving thanks to a huge number of contributors from all over the world bringing their specialties and talents. Huge thanks are due to all the contributors who regularly patch up bugs, help direct traffic, and basically keep Marlin from falling apart. Marlin's continued existence would not be possible without them.

Administration

Regular users can open and close their own issues, but only the administrators can do project-related things like add labels, merge changes, set milestones, and kick trolls. The current Marlin admin team consists of:

Project Maintainer

🇺🇸  Scott Lahteine       @thinkyhead         Donate 💸  

🇺🇸  Roxanne Neufeld       @Roxy-3D

🇺🇸  Keith Bennett       @thisiskeithb         Donate 💸  

🇺🇸  Jason Smith       @sjasonsmith

🇧🇷  Victor Oliveira       @rhapsodyv

🇬🇧  Chris Pepper       @p3p

🇳🇿  Peter Ellens       @ellensp         Donate 💸  

🇺🇸  Bob Kuhn       @Bob-the-Kuhn

🇳🇱  Erik van der Zalm       @ErikZalm         Donate 💸  

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.