Creality Ender 3 S1 Pro Firmware | V24S1_301 Board
Do you have an Ender 3 S1 Pro and want firmware that actually works correctly and makes installing upgrades quick? This is the firmware for you!
Maybe you’re adding our EZABL kit to the machine. This is the download for you. You will need to update the LCD and Board firmware for this machine. Directions are below.
Board Limitations Note: Due to the design of the Creality boards with TMC drivers Linear Advance will probably not work correctly. The feature is available but use at your own risk.
LCD Notes: Currently only the 12864 LCDs work 100% correctly with this printer and board with our firmware. We have a kit here to do the conversion. The stock touch LCD is not supported and likely will never be supported due to it being closed source.
Supported CPU List
- STM32F103 RCT6/RET6
- STM32F401 RCT6
- GD32F303 RCT6/RET6
CPU TYPE WARNING: Some Ender 3 S1 boards have shipped with STM32F4 series CPUs. If you have a F4 read the directions in the firmware and below for the proper flashing procedure. You will have to look at the CPU on your printers control board to see if it says STM32F103 or STM32F401 on it to determine what CPU model you have. Flashing the wrong version on the wrong CPU can “brick” your board and we are not responsible if you fail to verify your CPU before installing any firmware update.
We also recommend you download the Unified 2 STL pack as well. This contains EZABL mounts, Gantry leveling Blocks, Solid bed mounts, and Bed Level test files. Click here to go to the Unified 2 STL Pack download page.
1. – Printer Board Firmware Update
NOTE: Every time you flash the firmware it must start with firmware followed by random numbers/letters. It must be a different file name every time you flash. This is a limitation with the bootloader on these boards. It will NOT rename the file like other boards after it flashes.
1.b –Download the firmware
1.c –Extract the files to a folder on your computer
1.d –Open the folder labeled “Firmware” in VSCode
1.e –Open the Configuration.h file that is located under the “Marlin” folder on the left side of the VSCode screen
1.f – In the Configuration.h file, uncomment (remove the 2 / in front of #define) the ENDER3_S1_PRO line and any other options you are going to use in the firmware. If you have the F4 CPU and/or a 512K CPU read the Platformio.ini file for directions on changing your build environment to the correct one.
1.g –Click the ✓ at the bottom of VSCode to compile the firmware. The firmware will compile. This may take 1-5 minutes depending on the speed of your computer and internet connection
1.h – On the left side of VSCode expand “.pio” and “build” until you see the STM32FXXXRXT6_creality folder. Right click on the STM32FXXXRXT6_creality and click “Reveal in File Explorer”.
1.i – In the file explorer open the STM32FXXXRXT6_creality folder
1.j – Look for the latest firmware-XXXXXXXX-XXXXX.bin file and copy that to your SD card. This SD card must be FAT32 formatted. If you compiled more than one time you will see multiple firmware files. Use the latest one based on the date the file has.
F4 CPU Users: If you have a F4 CPU on your board the firmware bin file MUST be placed on the SD card inside a folder called “STM32F4_UPDATE” or it will NOT work.
1.k – Power OFF your printer and Insert the SD card with the latest firmware-XXXXXXXX-XXXXX.bin file into your printer. Turn the printer on. It will take a little longer than normal to boot up.
1.l – When the printer boots you will see the TH3D logo on your LCD. Make sure to reset your EEPROM on your printer after flashing any firmware. You can do this from your printer LCD or by sending a M502 followed by M500 with your favorite Gcode sender application.
THIS FIRMWARE AND ALL OTHER FILES IN THE DOWNLOAD ARE PROVIDED FREE OF CHARGE WITH NO WARRANTY OR GUARANTEE FROM TH3D STUDIO LLC. SUPPORT IS NOT INCLUDED JUST BECAUSE YOU DOWNLOADED THE FIRMWARE.
TH3D STUDIO LLC IS NOT LIABLE FOR ANY DAMAGE TO YOUR PRINTER, PERSON, OR ANY OTHER PROPERTY DUE TO USE OF THIS FIRMWARE. IF YOU DO NOT AGREE TO THESE TERMS THEN DO NOT USE THE FIRMWARE.
We do not maintain a full change log for this firmware. However, you can track all changes and modifications to our firmware code on the GitHub repo for Unified 2 Firmware.