**IMPORTANT!! This firmware will not work on touch screens other than model DW. In the About, the screen firmware version may have letters following it like "0.3.1 DW". This firmware will work only if your screen has the letters DW or no letters following the version number.
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!
This is based on the work from DaGr70 https://github.com/DaGr70/Marlin_Longer_LK4_pro and Desuuuu https://github.com/Desuuuu/Marlin.
I wanted more features and a more consistent look on the touchscreen. I made these modifications but more features will be added over time.
- Added advanced settings to allow changing Steps/mm, Acceleration and more from the touchscreen.
- Reworked some screens layout and navigation.
- Enabled the M600 command by default.
- Enabled power loss recovery by default.
- Works with non-BLtouch printers
You can see some screenshots here https://github.com/Guizz27/DWIN_LK4Pro/tree/main/Screenshots.
Integrated all changes from https://github.com/Desuuuu/Marlin and https://github.com/MarlinFirmware/Marlin to stay up to date with Marlin and the Reloaded screens updates.
Releases will contain the touchscreen firmware that matches. If you want the source of the screen firmware you can find it here https://github.com/Guizz27/DWIN_LK4Pro.
Marlin 2.0 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.
Baddflash wrote detailed instructions to build and install the printer firmware as well as the screen firmware which you also have to update. Please follow his instructions here: https://github.com/Baddflash/LK4-Pro-Firmware-Tutorial
Platform | MCU | Example Boards |
---|---|---|
Arduino AVR | ATmega | RAMPS, Melzi, RAMBo |
Although this is based on the official Marlin software. The configuration files are specific to Longer/Alfawise "Pro" printers. It may or may not build for other platforms.
The Issue Queue is reserved for Bug Reports and Feature Requests. To get help with configuration and troubleshooting, please use the following resources:
- Marlin Documentation - Official Marlin documentation
- Marlin Discord - Discuss issues with Marlin users and developers
- Facebook Group "Marlin Firmware"
- RepRap.org Marlin Forum
- Facebook Group "Marlin Firmware for 3D Printers"
- Marlin Configuration on YouTube
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.
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:
- Scott Lahteine [@thinkyhead] - USA - Project Maintainer 💸 Donate
- Roxanne Neufeld [@Roxy-3D] - USA
- Keith Bennett [@thisiskeithb] - USA 💸 Donate
- Peter Ellens [@ellensp] - New Zealand
- Victor Oliveira [@rhapsodyv] - Brazil
- Chris Pepper [@p3p] - UK
- Jason Smith [@sjasonsmith] - USA
- Luu Lac [@shitcreek] - USA
- Bob Kuhn [@Bob-the-Kuhn] - USA
- Erik van der Zalm [@ErikZalm] - Netherlands 💸 Donate
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.
Please note that you use this software at your own risks. I am not responsible for any damage it may cause.