Beta build - use with caution!
This is the newest version of the Marlin Firmware, customized and optimized for the 4Max Pro based on davidramiro's Ai3M-2.0.x repo and alfrank's changes for the Anycubic 4Max Pro. The DWIN TFT screen is based on derhopp's repo with his remarkable efforts to get this working with the latest versions of Marlin.
Make sure to take a look at the Wiki in davidramiro's Ai3M-2.0.x repo and also the FAQ.
Anycubic's touchscreen implementation is very hacked together and is based on the old Marlin beta version 1.1.0-RC8. In addition, the wrong thermistor for the hotend is entered in the stock firmware, which has been fixed in this version. Also if your hotbed is concave or not straight you can use the mesh bed leveling.
Warning: If your 4Max Pro works satisfactorily for you there is no reason to do a firmware update.
- There is always a way back to the original firmware. Before the update, please note the currently installed version: Menu Tools / About / Firmware Version on the display of the printer.
- If you don't want to change the firmware yourself, you can simply use Cura to load the latest
.hex
file from the release. - If you want to go back to the Original Anycubic 1.1.7 (Marlin 1.1.0-RC8) firmware download it from here
- After flashing the firmware, no matter which way, you have to reset and save the EEPROM values using a terminal program (e.g. Pronterface).
- connect the printer to the computer via USB cable
- open the terminal program, select the appropriate USB serial interface (on Mac:
SLAB_USBtoUART
) - change
baud rate
orBaudrate
to250000 bps
- connect and wait for the EEPROM values to be output
- then enter the following:
M502
andM500
- Now you can disconnect again, for safety's turn the printer off and on again.
- The new firmware is shown in the printer display (see above) as
v2.0.0
.
- LED control: It would be better to enable
case lights
menu option with PWM control - Light flickers when printing
- PID from the hotend no longer fits => Can be fixed by PID tuning
- Mixing Extruder with G10/G11 may have quirks
- Sensor-less probing is still pretty experimental
Marlin-Ai3M-2.0.x administrator:
- David Ramiro [@davidramiro]
Marlin-A4MaxPro-2.0.x contributors:
- [@mpk]
- Jonas Plamann [@Poket-Jony]
Marlin-2.0.x dev team:
- Scott Lahteine [@thinkyhead]
- Roxanne Neufeld [@Roxy-3D]
- Chris Pepper [@p3p]
- Bob Kuhn [@Bob-the-Kuhn]
- JoĂŁo Brazio [@jbrazio]
- Erik van der Zalm [@ErikZalm]
Notable contributors include:
- Alexey Shvetsov [@alexxy]
- Andreas Hardtung [@AnHardt]
- Ben Lye [@benlye]
- Bernhard Kubicek [@bkubicek]
- Bob Cousins [@bobc]
- Petr Zahradnik [@clexpert]
- Jochen Groppe [@CONSULitAS]
- David Braam [@daid]
- Eduardo José Tagle [@ejtagle]
- Ernesto Martinez [@emartinez167]
- Edward Patel [@epatel]
- F. Malpartida [@fmalpartida]
- Kai [@Kaibob2]
- Luc Van Daele [@LVD-AC]
- Alberto Cotronei [@MagoKimbra]
- Marcio Teixeira [@marcio-ao]
- Chris Palmer [@nophead]
- Steeve Spaggi [@studiodyne]
- Thomas Moore [@tcm0116]
- Teemu Mäntykallio [@teemuatlut]
- Nico Tonnhofer [@Wurstnase]
- [@android444]
- [@bgort]
- [@GMagician]
- [@Grogyan]
- [@maverikou]
- [@oysteinkrog]
- [@paclema]
- [@paulusjacobus]
- [@psavva]
- [@Tannoo]
- [@teemuatlut]
- ...and many others
Marlin is published under the GPLv3 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.
/*
* Flashing a custom firmware happens at your own risk.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
* AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED
* WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
* PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
* THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
* ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
* OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
* IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
* SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/