Ender 5 S1 firmware support

S3mco · 7 June 2023 18:22

I see there’s ender 3 S1 firmware. Wondering if there will be Ender 5 s1 firmware added to the pre-made firmware list?

CRCinAU · 13 June 2023 02:44

The Ender 5 S1 is not currently supported in Marlin.

If you are able to contribute, the current status is here:

github.com/MarlinFirmware/Marlin

[WIP] Creality Ender-5 S1

MarlinFirmware:bugfix-2.1.x ← thinkyhead:port_creality_ender5_s1_bugfix-2.1.x

opened 07:14AM - 14 Feb 23 UTC

thinkyhead

+5909 -79

Creality Ender-5 S1 adds support for a new Resistive Touch Screen controller and… a new motherboard. Many code changes and a few new options are included to support the new controller. The Ender-5 S1 is a cube-shaped machine with a standard X / Y gantry and Z bed, so it should be configurable with the existing firmware options, plus whatever is needed to interact with the UI on the RTS. This machine can have an optional Wi-Fi add-on, so there is some code to also support that component. This PR is a work in progress, with the aim to make the Ender-5 S1 work with the basic Marlin firmware as closely as possible, and to fix up any eccentric or extraneous customizations to the firmware behavior. At this time this code is not functioning correctly and the machine simply reboots. So, it needs to be fixed up, refined, and tested. The closer we can get to the basic Marlin code without the added customizations, the better. Some changes by Creality may actually fix or work around existing bugs, so may be worth keeping. Calling all brave Ender-5 S1 users to help develop and test this implementation! It would be nice to improve the UI, which is definitely in a rough form. The machine also ships with aggressive acceleration so that should also be re-tuned in the configuration, along with enabling any other motion options that make it perform fast, but reliably. Configurations (also work-in-progress) are posted at https://github.com/MarlinFirmware/Configurations/tree/import-2.1.x/config/examples/Creality/Ender-5%20S1 The TODO on this can be seen by looking at the code changes. The ultimate aim is to get any required behavioral changes to be conditional so they only apply to this machine (and any others that want those changes), and to integrate any required bug-fixes or behavioral improvements that make sense for all.

Once support lands and is completed, I can look at doing dailies for them at that point.