Hello,

Could you post source for v3.0.4 S1 firmware please?

Thanks

Ender 3 S1 Pro is very capable machine but the rounded corners at higher speeds is an problem which can be solved by enabling Linear Advance in Marlin.

I would like Creality to add this “Linear Advance” feature and create a release for everyone. At the price point which this printer is getting sold, I would expect it to be enabled from the factory, but this was not the case.

Pic of the issue which occurs at high print speeds without linear advance:

On the official page for s1 PLUS downloads all I see are files like "Ender-3S1Plus_HWv24S1_301_SWV2.0.8.28F4_F401_FDM_LASER" Are these files for the base firmware, or are they strictly for laser use only?

Please upload the missing source code files for the STM32F401 board (pins_CREALITY_S1_F401RC.h, for example)

Hi.
Please enable GCODE_MOTION_MODES, it is needed for LaserGRBL and LaserWeb to be compatible with the laser engraving functions. Or release the up to date source code (Ender-3S1Plus_HWv24S1_301_SWV2.0.8.25F4_F401_FDM_LASER) please so we can compile it by self.

Hi Team,

I'm searching for the configuration and configuration_adv for the Ender-3S1 with the attached official CV_LaserModul, could you point me to the right direction where this repository is located or what settings I need to set?

Thank you in advanced,
Cyrelion!

Thank you everyone who helped me successfully find and install the source code firmware for my Ender 3 S1 Pro.

My question is--how do I change the increments in which the Z-Offset Baby Step moves by? For example, it currently changes .05mm a step. Does anyone know how to change it to .01mm? I have changed it before in other firmware, and it always works. Not in the Ender 3 S1 Pro Fixes Firmware.

I've tried:

#define BABYSTEPPING
#if ENABLED(BABYSTEPPING)
//#define INTEGRATED_BABYSTEPPING // EXPERIMENTAL integration of babystepping into the Stepper ISR
//#define BABYSTEP_WITHOUT_HOMING
#define BABYSTEP_ALWAYS_AVAILABLE // Allow babystepping at all times (not just during movement).
//#define BABYSTEP_XY // Also enable X/Y Babystepping. Not supported on DELTA!
#define BABYSTEP_INVERT_Z false // Change if Z babysteps should go the other way
#define BABYSTEP_MILLIMETER_UNITS // Specify BABYSTEP_MULTIPLICATOR_(XY|Z) in mm instead of micro-steps
#define BABYSTEP_MULTIPLICATOR_Z 0.01 // (steps or mm) Steps or millimeter distance for each Z babystep
// #define BABYSTEP_MULTIPLICATOR_XY 1

and I've also tried:

#define BABYSTEPPING
#if ENABLED(BABYSTEPPING)
//#define INTEGRATED_BABYSTEPPING // EXPERIMENTAL integration of babystepping into the Stepper ISR
//#define BABYSTEP_WITHOUT_HOMING
#define BABYSTEP_ALWAYS_AVAILABLE // Allow babystepping at all times (not just during movement).
//#define BABYSTEP_XY // Also enable X/Y Babystepping. Not supported on DELTA!
#define BABYSTEP_INVERT_Z false // Change if Z babysteps should go the other way
//#define BABYSTEP_MILLIMETER_UNITS // Specify BABYSTEP_MULTIPLICATOR_(XY|Z) in mm instead of micro-steps
#define BABYSTEP_MULTIPLICATOR_Z 8 // (steps or mm) Steps or millimeter distance for each Z babystep (Stock is 40)
// #define BABYSTEP_MULTIPLICATOR_XY 1

Any help would be great. Thank you!

I updated the new firmware according to the instructions, now I have a printer stuck in the black hole, it does not show any signs of life, when I insert the TF card in the screen to update it works normally and updates, however when I insert the sd card to update the firmware nothing happens, black screen, the card even reads the card but does not update, I have already tried a bigger name, a smaller name, file only in the pasata, in the pasa and in the root, could someone please help me? @CrealityTech @Creality-mandy

I own multiple Ender 3 S1 Pro, I've noticed that on some machines ABL works fine, others not so great, any chance the bed leveling menu can include UBL ability and view mesh ability? something like jyers firmware?

I just received a bunch of Ender 3 S1 boards with the F4 CPUs and NONE of them will take firmware at all. I've tried the code here as well as 3rd party code, none of them will flash.

Please let us know what the proper method to flash these boards with the F4 CPU should be because none of the ones I have will take any firmware updates over SD.

Working firmware is here: https://www.th3dstudio.com/hc/downloads/unified-2-firmware/creality/creality-boards-creality/creality-ender-3-s1-firmware-v2415_301-board/

To reproduce:

In the main menu, "click" on Bed Leveling.

Expected:
since this is a process that can take a few minutes, I MUST be able to stop it at any time, and if I do, the old mesh should still be in place.

Observed:
there is no way to stop it, except turning off the printer. This is very annoying. ANYTHING that takes time should be stoppable, and there's no reason why bed leveling should be an exception.

I have owned my machine for 6 months. Unfortunately we have the f4 chip so we can not use the automatic leveling that we paid for, nor will it save any settings. Any print that tries to go through other than a calibration print has just ended in a mess of filament all over the place. It has not printed anything but the calibration prints that came with the machine. I cannot get it to work for the life of me. My father and I are both computer technicians and neither of us can figure it out. We have been able to install different firmwares, a lot of different firmwares. None of them produced any prints for us. This is very upsetting because we both know our way around 3d printers. If I cannot get this printer to work, I will have to call Amazon and force them to return it. The customer service has been very rough and no one is willing to tell me what I have to do.

can someone from Creality confirm whether or not M420 S1 or G29 is required with S1 Pro?
I see conflicting information online, some say yes, others say no.

I am in charge of 10 S1 Pro, I've found that adding M420/G29 doesn't really make a difference. some print perfectly fine, others print terribly regardless of what I do.

The issue is mostly first layer adhesion, other times adhesion become an issue at nth layer.

Hello,

Is this firmware used for S1 Pro as well?

Regards,
Ayush

Hi there, and thanks for putting this out to the open source community.

Do you plan on keeping this repository tagged with your binary release versioning from your website? It would be useful to know how this repo corresponds to the binary releases.

Hi!

Is the source code for S1 PRO available as for S1?

Thanks!

Ender 3 S1 Pro, latest firmware
The machine always reboots when I insert the SD card.

--
PS: Additionally: please conform with GPL and give us the source code.

Ender 3 S1 Pro.
Please enable Z_PROBE_SLED, this is useful for leveling.

PS: There are numerous feature request here what is not feature request, but you disabled a feature what is useful. Give out the source code to comply with GPL!

...including source files, as Marlin is released under the GPL-3 license you are obligated to do so

thanks

I have an unexpected mix of hardware. Instead of HW Ver v2.4.S1_301, I have v2.5.S1_100.

How do I build firmware for my equipment?

I am not alone and you can see someone else having the same mismatch (there is a photo with a different HW version)
https://3dprintbeginner.com/creality-ender-3-s1-pro-review/

Dear Creality,

after your announcement in social media regarding "open source" we are missing so many not released source code!

Where is it? Why is it not automatically pushed to github after a new release?

Your PR was good. But we are still waiting.

Please do what you announced: OPEN SOURCE your code please. Full and complete.

Thank you.

Thomas

Hello, in your firmware, the autocalibration of the table does not work. what could this be related to?

version 2.0.8 26F4

When displaying progress "One Hour and Five Minutes" is displayed as 1:5

It should be displayed as 1:05

Thanks

"Permissions of this strong copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights."

from https://github.com/MarlinFirmware/MarlinDocumentation/blob/master/LICENSE

Creality. You appear to still be pushing out new firmware and denying people the source code.. This needs to stop.

You are violating the GNU General Public License v3.0 that you agreed to by not disclosing the source code.

To anyone else: If creality doesnt give source code upon request if its more up to date then here, report Creality by following the instructions here. https://www.gnu.org/licenses/gpl-violation.en.html

Please provide the current source code, this is the only way the firmware can be improved and extended by the community.
Let's improve and optimize the firmware together.
This is how open source works.

Hello, what should I do to solve this problem?

Warning! Ignore unknown configuration option monitor_flags in section [env]
Warning! src_filter configuration option in section [env:DUE] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:esp32] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_build_flags configuration option in section [env:linux_native] is deprecated and will be removed in the next release! Please use build_src_flags instead
Warning! src_filter configuration option in section [env:linux_native] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:SAMD51_grandcentral_m4] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:malyan_M300] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:teensy31] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:teensy35] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:teensy36] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:teensy41] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! Ignore unknown configuration option monitor_flags in section [env]
Warning! src_filter configuration option in section [env:DUE] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:esp32] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_build_flags configuration option in section [env:linux_native] is deprecated and will be removed in the next release! Please use build_src_flags instead
Warning! src_filter configuration option in section [env:linux_native] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:SAMD51_grandcentral_m4] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:malyan_M300] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:teensy31] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:teensy35] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:teensy36] is deprecated and will be removed in the next release! Please use build_src_filter instead
Warning! src_filter configuration option in section [env:teensy41] is deprecated and will be removed in the next release! Please use build_src_filter instead

M48 or Probe repeatability test could be helpful to have. I noticed it isn't enabled and It could be helpfull for both sides. Helps Customer Service by allowing experienced users to provide proof via serial connection if their probe isn't working as intended and can help reduce troubleshooting. And it helps the end user by allowing to test to see if the probe is a issue.

I would like to see Z_MIN_PROBE_REPEATABILITY_TEST enabled.

Side note: If this is merged could the firmware for the s1 pro get updated? I would like that done

After power loss recovery on half of full build plate first player nozzle scratched the bed same way as if ABL was off

Ender 3 S1 pro, latest firmware.

To reproduce run the following gcode:

G28
G29
G29 S0

At the G29 S0 (save mesh to eeprom) the watchdog timer resets the machine.

mriscoc/Ender3V2S1#614

The probe being mounted in the current spot causes false readings by probe or marlin not interpreting it properly. The bracket listed in above github fixes issue. Please fix or offer official bracket for S1 owners

In the patch notes of firmware V2.0.8.28F4 it reads "New model picture preview function."

I haven't been able to get the printer to display the embedded png in any gcode file.
Is there any requirements (file size, image dimensions, image aspect ratio, etc) for this picture preview?

Where can I find the source code for this printer? Is there a firmware version that allows 300°C with upgraded pro hotend?

Enabling assisted tramming could prove helpful by alot for people, However due to the closed source nature of the screens I cannot add it fully.

While the paper method can be fine, this feature uses the probe to fine tune the bed leveling and it provides the correction needed.

I will need you guys to add in the stuff for the screen so people can do it via screen.

i am now on my second f4 mainboard that is stuck with the last firmware flashed to it. i have updated it, with correct firmware along the way, now i cant change anything it wont flash anymore

Hello. Im get Sermoon v1 pro. To many bugs in hardware and software. Im already wrote to support mail of creality and they say to ask you to provide sources. Thnx.

searching for info for enabling the led control menu or neopixel menu on the lcd

I updated the firmware of several languages, I updated the screen with the firmware of several languages ​​but when selecting a language different from the two defaults, all the writings disappear, not even restarting it appears, how to proceed?

Had a filament run out over night, in the morning fed new filament, pressed resume, it purged, but didn't resume printing.

Will this firmware work for me with this hardware version mismatch?

Is it possible to get the firmware for the Ender3 S1 Plus along with the modification of enabling HOST_ACTION_COMMANDS ?

I have an s1 with factory installed sprite and was wanting to set max temp to 300°. That's the easy part. Hard part is trying to find the right way to configure the firmware to use the stock touch screen.

Hello,

Can you please post the source code for the Marlin firmware of the Sermoon V1?

Thank you!

Hello. Just a quick intro, I'm new to the firmware game so please treat me like a total noob. 😅

Context

I upgraded my coldend fan to a 4020 and I'm looking for a way to slow it down. I know Klipper can slow the fan down and you can control it like it's PWM but it seems like you can't do it in Marlin. I already tried changing the EXTRUDER_AUTO_FAN_SPEED in the Configuration_adv.h to 128 (~50%) but it's always running at 100% speed.

Things I've tried

So I've read a couple of issue about PWM in Marlin and tried to apply things but no luck.

1. Change EXTRUDER_AUTO_FAN_SPEED to different values. but it seems like it's always running at 255. I've followed this chain and it brought me to this lines of code which brought me to the assumption of PC0 not being a PWM.
2. Following the chain of code above, it brought me to the PeripheralPins.c of MARLIN_CREALITY_STM32F401RC. So, I added {PC_0, TIM3, STM_PIN_DATA_EXT(STM_MODE_AF_PP, GPIO_PULLUP, GPIO_AF2_TIM3, 1, 0)}, in the PinMap for the PWM. This caused the fan to not turn on at all unless I set EXTRUDER_AUTO_FAN_SPEED to 255.
3. so I commented out the FAN_SOFT_PWM in the pins_CREALITY_S1_F401RC.h and uncommented the FAST_PWM_FAN in the Configuration.h. This didn't do anything.

My Questions

1. Is PC0 a PWM and I'm just setting this wrong?
2. If it is NOT a PWM pin, how can I make it into a PWM?

Rant

I've been pulling my hair on this for a while. I think I'm close but I also feel like I'm doing way too much. I don't know if I'm using the wrong timing or channel for the pin. It's just annoying how Klipper does it well yet Marlin doesn't. I really want to use the stock firmware as much as I could before jumping to a different platform or is that the wrong mindset? I don't know. Maybe people want to upgrade their coldend fan and would want to be able to adjust the speed of it.

Thank you!

Update

I went to the Marlin team and they can't help me cause the pins_CREALITY_S1_F401RC.h isn't in the stock Marlin. They told me that I shouldn't have to touch the PeripheralPins.c. They did let me know that STM32 uses software PWM to all of the fans. so reverted my changes above and tried other things. here are my changes so far:

1. Added #define FAN1_PIN PC0 to pins_CREALITY_S1_F401RC.h.
2. Set E0_AUTO_FAN_PIN to FAN1_PIN.
3. I had to comment out some checks in the SanityCheck.h since it's complaining that the laser has conflicting pin. (Creality did comment the error about E0_AUTO_FAN_PIN conflicting with the laser PWM)
4. Uncommented the #define FAN_SOFT_PWM in the Configuration.h.

Still, no luck. 😞

I would like UBL to be used instead of the current system that is used. UBL would allow for way more detailed meshes and wont impact normal printing time because ubl just probes 3x3 normally but can gererate a mesh like 15x15 with manual input that can be stored and then any bed tilt is detected by a 3x3 probe and it will lay out the mesh accordingly.

The reason I cannot do this is because the screens would require some more input options so people could use UBL with the screen instead of relying on gcode commands.

Ender 3 S1 pro. The supplied bed is warped. Please replace this constant with a variable and allow to change it from menu.
(If you publish the source code and don't violate GPL, then this feature request is not problem, after this we can change ourself. This is the best scenario)

The link to the YouTube which shows how to upgrade the firmware says "This video has been removed"

I am using Ender-3S1_Pro_HWv24S1_301_SWV2.0.8.24F4_F401_FDM_LASER from 3 Aug. 2022. HOST_ACTION_COMMANDS are not enabled. Is it possible to get the current firmware with enabled HOST_ACTION_COMMANDS? My mail is [email protected]. Please enable them in future releases!

Sadly there is no repository for the Ender-3 S1 Pro and i can´t find the current and complete (!) configs for the printer to compile a firmware by myself. As in #4 i can´t just use the S1 version. Also they are older than the newest firmware from 3 Aug.

After checking out the last official firmware update for the Ender 3 S1 (Marlin2.0.8_Ender-3S1_HWv24S1_301_SWV3.1.9_Two_C_F401_FDM_LASER), I wanted to go back to "mriscoc" firmware. It seems the latest screen firmware update (one that includes the "dcboot" file) has made any other screen firmware incompatible. And the screen just stays black.
I tried downgrading to older versions by just flashing older updates, but it didnt seem to help. So I was wondering if there is a way to downgrade to stock firmware for the screen.
Thanks in advance.