Marlin VS moonraker

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

-------------------- Log Start | Thu Oct 19 14:05:22 2023 -------------------- data_path: /home/android/printer_data is_default_data_path: True config_file: /home/android/printer_data/config/moonraker.conf startup_warnings: [] verbose: False debug: False asyncio_debug: False is_backup_config: False is_python_package: False instance_uuid: 766564b4528e4af4b923afa059b299a9 unix_socket_path: /home/android/printer_data/comms/moonraker.sock software_version: v0.8.0-186-g2641fc5 git_branch: master git_remote: origin git_repo_url: https://github.com/Arksine/moonraker.git modified_files: [] unofficial_components: [] log_file: /home/android/printer_data/logs/moonraker.log python_version: 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] msgspec_enabled: False uvloop_enabled: False 2023-10-19 10:05:22,915 [confighelper.py:read_file()] - Configuration File '/home/android/printer_data/config/moonraker.conf' parsed, total size: 1368 B 2023-10-19 10:05:22,916 [server.py:add_log_rollover_item()] - #################### Moonraker Configuration #################### [server] host = 0.0.0.0 port = 7125 klippy_uds_address = /home/android/printer_data/comms/klippy.sock [authorization] trusted_clients = 10.0.0.0/8 127.0.0.0/8 169.254.0.0/16 172.16.0.0/12 192.168.0.0/16 FE80::/10 ::1/128 192.168.2.1 cors_domains = *.lan *.local *://localhost *://localhost:* *://my.mainsail.xyz *://app.fluidd.xyz [octoprint_compat] [history] [update_manager] channel = dev refresh_interval = 168 [update_manager mainsail-config] type = git_repo primary_branch = master path = ~/mainsail-config origin = https://github.com/mainsail-crew/mainsail-config.git managed_services = klipper [update_manager mainsail] type = web channel = stable repo = mainsail-crew/mainsail path = ~/mainsail [update_manager mobileraker] type = git_repo path = /home/android/mobileraker_companion origin = https://github.com/Clon1998/mobileraker_companion.git primary_branch = main managed_services = mobileraker env = /home/android/mobileraker-env/bin/python requirements = scripts/mobileraker-requirements.txt install_script = scripts/install-mobileraker-companion.sh [update_manager fluidd-config] type = git_repo primary_branch = master path = ~/fluidd-config origin = https://github.com/fluidd-core/fluidd-config.git managed_services = klipper [update_manager fluidd] type = web channel = stable repo = fluidd-core/fluidd path = ~/fluidd ################################################################# All Configuration Files: /home/android/printer_data/config/moonraker.conf ################################################################# ------------------- omitting a bunch of HTTP registrations ----------------------- System Info: ***python*** version: (3, 9, 2, 'final', 0) version_string: 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] ***cpu_info*** cpu_count: 4 bits: 64bit processor: aarch64 cpu_desc: serial_number: hardware_desc: Qualcomm Technologies, Inc MSM8992 model: total_memory: 1858336 memory_units: kB ***sd_info*** manufacturer_id: 11 manufacturer: Unknown oem_id: 0100 product_name: 016G7 product_revision: 3.2 serial_number: 000bce12 manufacturer_date: 2/2082 capacity: Unknown total_bytes: 0 ***distribution*** name: Debian GNU/Linux 11 (bullseye) id: debian version: 11 version_parts: {'major': '11', 'minor': '', 'build_number': ''} like: codename: bullseye release_info: {} ***virtualization*** virt_type: none virt_identifier: none ***network*** ***canbus*** ***Allowed Services*** klipper_mcu webcamd MoonCord KlipperScreen moonraker-telegram-bot moonraker-obico sonar crowsnest octoeverywhere ratos-configurator mobileraker ------------------- omitting a bunch of HTTP registrations ----------------------- 2023-10-19 10:05:23,843 [authorization.py:__init__()] - Authorization Configuration Loaded Trusted Clients: 192.168.2.1 10.0.0.0/8 127.0.0.0/8 169.254.0.0/16 172.16.0.0/12 192.168.0.0/16 fe80::/10 ::1/128 CORS Domains: .*\.lan .*\.local .*://localhost .*://localhost:.* .*://my\.mainsail\.xyz .*://app\.fluidd\.xyz ------------------- omitting a bunch of HTTP registrations ----------------------- 2023-10-19 10:05:24,089 [server.py:load_component()] - Component (octoprint_compat) loaded 2023-10-19 10:05:24,115 [server.py:_initialize_component()] - Performing Component Post Init: [dbus_manager] 2023-10-19 10:05:24,154 [server.py:_initialize_component()] - Performing Component Post Init: [file_manager] 2023-10-19 10:05:24,166 [server.py:_initialize_component()] - Performing Component Post Init: [machine] 2023-10-19 10:05:24,167 [machine.py:validation_init()] - Validation version in database out of date 2023-10-19 10:05:24,261 [server.py:_initialize_component()] - Component [machine] failed post init Traceback (most recent call last): File "/home/android/moonraker/moonraker/server.py", line 225, in _initialize_component await ret File "/home/android/moonraker/moonraker/components/machine.py", line 252, in component_init await self.sys_provider.initialize() File "/home/android/moonraker/moonraker/components/machine.py", line 1014, in initialize self.systemd_mgr = await self.dbus_mgr.get_interface( File "/home/android/moonraker/moonraker/components/dbus_manager.py", line 123, in get_interface ret = await self.get_interfaces(bus_name, bus_path, File "/home/android/moonraker/moonraker/components/dbus_manager.py", line 135, in get_interfaces introspection = await self.bus.introspect(bus_name, bus_path) File "/home/android/moonraker-env/lib/python3.9/site-packages/dbus_next/aio/message_bus.py", line 216, in introspect return await asyncio.wait_for(future, timeout=timeout) File "/usr/lib/python3.9/asyncio/tasks.py", line 481, in wait_for return fut.result() File "/home/android/moonraker-env/lib/python3.9/site-packages/dbus_next/message_bus.py", line 195, in reply_notify BaseMessageBus._check_method_return(reply, err, 's') File "/home/android/moonraker-env/lib/python3.9/site-packages/dbus_next/message_bus.py", line 615, in _check_method_return raise DBusError._from_message(msg) dbus_next.errors.DBusError: Launch helper exited with unknown return code 1 2023-10-19 10:05:24,262 [server.py:add_warning()] - Component 'machine' failed to load with error: Launch helper exited with unknown return code 1 2023-10-19 10:05:24,262 [server.py:_initialize_component()] - Performing Component Post Init: [proc_stats] 2023-10-19 10:05:24,262 [server.py:_initialize_component()] - Performing Component Post Init: [announcements] 2023-10-19 10:05:24,264 [server.py:_initialize_component()] - Performing Component Post Init: [webcam] 2023-10-19 10:05:24,265 [server.py:_initialize_component()] - Performing Component Post Init: [klippy_connection] 2023-10-19 10:05:24,266 [server.py:_initialize_component()] - Performing Component Post Init: [authorization] 2023-10-19 10:05:24,266 [server.py:_initialize_component()] - Performing Component Post Init: [update_manager] 2023-10-19 10:05:24,374 [base_deploy.py:log_info()] - PackageDeploy: PackageKit Provider Configured 2023-10-19 10:05:24,417 [update_manager.py:_handle_auto_refresh()] - update_manger: Install validation pending, bypassing initial refresh 2023-10-19 10:05:24,417 [machine.py:_check_service_file()] - Performing Service Validation... 2023-10-19 10:05:24,418 [server.py:add_warning()] - Unable to retrieve Moonraker service info. Service file must be updated manually. 2023-10-19 10:05:24,420 [extensions.py:start_unix_server()] - Creating Unix Domain Socket at '/home/android/printer_data/comms/moonraker.sock' 2023-10-19 10:05:24,423 [server.py:start_server()] - Starting Moonraker on (0.0.0.0, 7125), Hostname: localhost 2023-10-19 10:05:24,425 [app.py:listen()] - SSL Certificate/Key not configured, aborting HTTPS Server startup

14:00:21Application moonraker: Attempting Repo Recovery... 14:00:21Git Repo moonraker: Starting Clone Recovery... 14:00:21Cloning into '/home/biqu/.moonraker_repo_backup'... 14:02:31fatal: unable to access 'https://github.com/arksine/moonraker.git/': Failed to connect to github.com port 443: Connection timed out 14:02:32Git Repo moonraker: Git Clone Failed 14:02:32Error Recovering moonraker14:02:32Git Clone Error

Your virtual_sdcard directory has to be ~/printer_data/gcodes now.

Might be this moonraker one https://github.com/Arksine/moonraker/issues/516

https://github.com/Arksine/moonraker/issues/516 this may be the one you need to do, I did it before but I use regular Klipper with a Voron, not sure if Ratos would need you to do something else

Works with front ends like Octoprint, but there are also frontends that are purpose built for klipper through the moonraker api such as Fluidd and Mainsail

Read this

This issue tracker has some good information

Look in the [power] section of moonraker.conf https://github.com/Arksine/moonraker/blob/master/docs/configuration.md