Arduino VS Marlin

I learned from looking at example code in the Arduino IDE (a really good and free code editor https://www.arduino.cc/en/software). The Arduino IDE allows you to add more boards (like ESP32, ESP8266, Tiny etc.) so you're not limited to using only their Arduino boards.

Based on what I am seeing from the Keystudio website, the software you need is just the Arduino IDE. This can be downloaded from Arduino.cc for most operating systems, including Mac OSX. You may need to install support for other boards or install libraries to make it work with the Arduino and hat included with the kit.

Download and install the Arduino IDE. After installation, open the IDE to the first sketch.

Well, your first course of action would be to download the software - https://www.arduino.cc/en/software

You can download the IDE from here.

You will need to download and install the Arduino IDE to do that. I would suggest the Legacy 1.8.x IDE or the Arduino Web Editor (which will still require that you install some software on your computer to help transfer the program to the Arduino).

The software used for that video is the arduino IDE https://www.arduino.cc/en/software

Wiring: You're on the right track with your wiring assumptions. The red wire should connect to the 5V pin, the black wire to the GND pin, and the green wire to one of the analog input pins (A0-A5) on the Arduino Leonardo. For example, you can connect the green wire to the A0 pin. Programming the Arduino Leonardo: To translate the handbrake input to Assetto Corsa, you'll need to program the Arduino Leonardo to act as a USB HID (Human Interface Device). This will allow your computer to recognize it as a game controller. First, you'll need to install the Arduino IDE (Integrated Development Environment) on your computer. You can download it from the official website: https://www.arduino.cc/en/software

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