Marlin VS Marlin

There is _a lot_ wrong with Marlin. It is a complex codebase, full with ancient artefacts, litterred with preprocessor ifdefs every 2-3 lines of code, dynamic includes in the middle of CPP files, etc[1]. It's about as unreadable as C++ code gets--well, I guess it's not template metaprogramming.

Klipper by contrast is a breeze to read through[2].

I am very grateful for Marlin, for all of reprap, and everyone who has contributed to it. But saying there is nothing wrong with it is straight up misguided.

[1]: https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.1.x/M...

[2]: https://github.com/Klipper3d/klipper/blob/master/src/lcd_hd4...

I think you are mistaken. I can't speak for implementations preceding the Ender 3 V2, so what you're saying may have been true at some point for other machines. However, here you can see Marlin developers confirm that there is an EEPROM on the stock E2V2 board using diagrams from Creality and photographic confirmation. Here is the datasheet for the EEPROM. Here is a thread discussing this Marlin release, and also the then-recent release of official Creality firmware which resolved the same issue. Since the stock firmware is based on Marlin, and at the time Marlin did not support this type of EEPROM, the EEPROM was not usable at launch. Any mainstream firmware (official or third-party) from the last three years will be using the onboard EEPROM unless the user intentionally specified otherwise.

pull latest Marlin from github: https://github.com/MarlinFirmware/Marlin

Also, checked the following discussion but seems like I need to update the firmware to be able to comment that like right? Temperature variance monitor tweaks by zeleps · Pull Request #23571 · MarlinFirmware/Marlin · GitHub

i spent some time and successfully rebased Kobra 2.8.2 OG firmware from an unknown Marlin ~2.0.8 frankenstein to a clean latest (as of now) release (not bugfix) 2.1.x -- v2.1.2.1 + 1 commit

As an example, check the macropocalypse in Marlin - but the actual trigger for me to start was Reprap firmware doing a floating point divide in interrupt context while targeting AVR8 core…

Any change of thermistor or to a PT100/PT1000 will require recompiling the firmware, because every type has different characteristics. Marlin uses an internal table to calculate the temperature for whatever reading it gets from the CPU's analogue-to-digital converter. It has many tables for different thermistors, but only one is ever incorporated at compile time. So you have to specify which type you're using. You can see the commonly-used types in the list in Marlin's Configuration.h file, in the section headed // @section temperature. The tables themselves are in Marlin/src/module/thermistor.

FWIW It IS open source but the GNU General Public License v3.0 rules apply. https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.1.x/LICENSE

Just received a BTT SKR mini E3 v3 to replace the stock Melzi m/b for my AnyCubic Mega Zero 2.0, with a BLTouch add-on. I've got the hardware figured out (with some mods to connector types and some back-alley surgery to get it mounted), but I am really uncertain as to firmware. The AMZ subredit lists the v3 (see last row of table under "Boards") but doesn't have a specific firmware for the v3 on the repository. It says there should be one that would be, effectively, amz2_btt_minie3v3_bl_firmware.bin but that exists nowhere.

From the Marlin github, would I be ok choosing either of these firmware options? (noting that I have a BL Touch) :

I already posted this issue on Github but figuered maybe someone here can help me. I added a BLTouch clone to my MZ2 and flashed the "amz2_melzi_bl_a2-2.0.9.3-kad1-firmware" image from here. After finally dialing in the Probe height and Z-Offset i wanted to do my first print ith it. I ran the Auto-home and afterards the Bed-Levelling. Hoever hile the screen indicated a movement on the X-Axis, the Stepper didn't move at all and another homing resulted in the printer saying homing failed and to please reset it. so i did, homing went fine but afterwards the X-Axis didn't move yet again. neither in levelling nor manually. after another reset i can manually control it just fine, but after levelling its done for. idk know what to do anymore

I ended up just converting my whole setup from kad/Marlin + octoprint to Klipper + Mainsail. It took me a few days to figure out all the intricacies, getting macros and my slicer setup. I've finally got it all working this morning and holy moly it's like I have a new printer. Highly recommend to anyone who's not using Klipper to upgrade. And it didn't cost me anything but time.

Hey, I added a BLTouch to my MZ2 a couple months ago. I used the firmware from this repo, as it's specifically for Anycubic Mega Zero printers.

Big Tree Tech probably has a basic configuration for the Octopus on their github. For additional settings you could take a look at KAD Mega Zero 1.0 and 2.0 releases for printer information.

Hey, I've complied newest Marlin firmware based on this awesome for: https://github.com/kad/Marlin For Mega SE using Mega zero 2.0 as base and setting PIDs to fix e1 heater not being able to heat up.

I got a 3D touch from triangle lab on aliexpress (BL touch knockoff), installed it, flashed the correct kad marlin firmware with how I installed the probe. (I'm using EXT-A2 and Z-min)