Replies: 22 comments 91 replies
|
I would like to ask a few questions regarding the upgrading of the firmware. I currently am running f/w 2.0.8.15F4 in my S1 Pro. |
|
you'll need a microsd card to update the LCD firmware. You might as well do both to establish a good baseline that we can build upon. The Creality instructions are in their release notes:
If you are uncertain which of their firmware files to use, I have them mirrored here: https://github.com/synman/Ender-3-S1-Pro-Firmware/tree/main/0_baseline_firmware -- make sure you grab the firmware for you machine... I have both the S1 Pro and S1 Plus ones in that folder. DO THE SCREEN FIRST. I'm here if you have further questions but this should be a good starting point for you. |
|
This is awesome, thank you! I have extra sd cards coming on Friday so I’ll get on it after I get them (I just want a fresh card so I don’t have to move everything)I will let you know once I get it done. Thank you so much for your help!
|
|
Good time of the day. My S1Pro reports an error when heating 300 degrees. |
|
Do you mind sharing the error? |
|
I'll try to make a video today, I'll upload it later. |
|
No need, this is now fixed. I am dying to know though what you are trying to print at 300C. The stock thermistor table topped out at 295. In my testing, I found that to be the "breaking" point. |
|
Tell me why your firmware is based on 2.0.8.24F4, and not on 2.0.8.26F4? And if, do you know what are the differences between these firmwares? Thank you. |
|
Word has it (I haven't tested this myself) that .26 of the touchscreen works fine. So, unless we find some reason to downgrade, you can stick with it. With the F4 chip you want the STM32F_UPDATE directory off of root with just my firmware .bin file in there. No other files are necessary. It is also a good idea to have no .bin files in the root directory, but I don't think it matters. |
|
Will try that. I copied your firmware into the root and the STM32F_UPDATE directory (thats how the stock firmware seems to be setup, though I noticed when reverting to previous version, the files in root and STM directory were different). With your firmware in root and STM folder, it would not restart (I was originally on v2.0.8.24F4). I could not revert until I tried V2.0.8.26 but it could have been mac adding hidden .fseventsd and .Spotlight folders as soon as you insert the SD card (very annoying that). I will try your firmware with the V2.0.8.26 and V1.0.3 screen and report back. |
|
The stock firmware packages the F1 and F4 firmwares together. F1 in the root and F4 in STMF32_UPDATE. That's the difference... The F4 bootloader looks for it in that subdir. |
Ah. That makes sense. I can confirm loading v2.1.2 over Creality v2.0.8.26 works and works ok with screen ver 1.0.3. I put the _ubl25 build onto the machine with v1.0.3 screen version. No problems so far. |
|
Is there a way to change the screen layout? I installed 2.1.2 just fine (after upgrading to Creality's latest fw and screen fw)... but what I an really looking for is for my screen to show me the current Z height info.. is there any way to easily accomplish this? is there a screen fw for this anywhere? |
|
How can I remove myself from this thread? I keep receiving emails with every post, and it has nothing to do with my original question so it is irrelevant to me. Appreciate any help regarding this. |
|
You can unsubscribe via your notifications feed, I believe. |
|
Good time of the day. The calibration of the table is unstable on your firmware. Because of this, many users return the original firmware. When rebooting, not always, but often, the calibration settings are not saved. |
|
Sounds like a problem with your printer if it’s inconsistent like that. I haven’t seen anyone else complain about leveling? Maybe open an issue with details such as which version of the firmware and any other specific details that would be helpful in troubleshooting. As of now this is just a complaint with no actionable detail. |
|
I think there's a translation error of some kind happening here. @michytka last pointed out the thermistor table was wrong (in his own way), and sure enough, the upstream thermistor table was missing entries over 300C. I suspect this has to do with the UBL 100 point mesh. What people fail to realize is this is what the G29 P1 C command is for... |
|
Hi I would like to upgrade my firmware to get better compatibility with octoprint. I'm currently using Creality v2.0.8.26F4 firmware with display 1.0.3. which one of you firmware would you suggest me to upgrade too? |
|
Loaded latest bugfix-2.1.x and got no serial errors from Pronterface on Mac this time. However, I noticed microstepping has reverted back to 0.05 instead of 0.01. I used bugfix-2.1.x-F4-s1pro_ubl25. (With version 2.1.2 microstepping was at 0.01. Not a problem for me, just observation. I loaded firmware-20230225-215419.bin. |
|
.05 while printing from SD or in general? I could've swore my last change, reverted it for SD only. With my latest sync (yesterday) it should be consistent across all variants / marlin versions. |
|
When levelling and when printing without SD card. (I use a beagle camera from Mintion as pi boards are so expensive right now). |
|
So that's a bug. I'll have to see what messed up. |
|
reopened #6 |
|
the .01mm baby step issue when adjusting babysteps for non sd card based prints was fixed tonight in all builds. I also brought in an upstream merge and implemented a work-around to reduce (if not alleviate) probe failures. |
|
Confirm it works without SD card for me using bugfix-2.1.x-F4-s1pro_ubl25.zip. Also notice that at 40% and 80% it retracts the probe lifts extruder. I am assuming this is the work-around mentioned. One nice to have on the Z microsteps is the ability to switch/choose 0.01 and 0.05 settings. One thought was use 0.01 when fine tuning during a print and 0.05 when levelling. No worries if you're not able to do that though. (Reason is my Z is -2.35 so I have to press down 235 times to get there when levelling after M502+M500+M501). |
|
I really like your suggestion... it makes a ton of sense. Currently, I can't tell if the request is coming from the auto/manual leveling menu or the (while running) adjustment menu. But, I do have a way to determine if a job is active or not -- that's actually part of the bug I fixed so I may be able to hack around the two. |
|
hey @JohnScottUK .... if you're executing I have it all integrated so the touchscreen should immediately show your change via the |
|
Nice! I can use M851 Z-2.20 for safety and then 0.01 baby steps during levelling after flashing a firmware update. |
|
At first: Thanks for the hard work in the firmware and providing it as such! I was super happy with this firmware. Started printing in January. Got octoprint working (I'm not to bad at the IT stuff) and was trying to get this host... stuff working. But ran into an issue regarding Z-Offset. And I have a feeling it's a newbee mistake, but hey... Yesterday I migrated from stock firmware to this firmware (F4 UBL 100) And was now trying to start setting Z-Offset. But when I go to leveling menu. The nozzle stays roughly 13mm from the bed. As the z-offset only goes max -5. I can't get my nozzle set correctly... Has someone got a tip for me to check what I'm doing wrong? Much appreciated! Bed leveling it self is working and got a nice visual in Octoprint |
|
Curious fact: G28 results in (on display:) X:148,5 Y:153.8 Z:10 |
|
Z10 is typically where it gets parked but it should probe down below Z0 all the way to the safe z height. I'm not sure what you're chasing at this point. Go into the leveling aux menu and select one of the points there. That's how you get to Z0. |
|
When running the original firmware, I only had to go to the Auto. LVL. menu and the head would move to Z0. Second I would go to the Aux menu without choosing a location and would do Z-Offset using that original location... You see -> beginners mistake. Thanks for helping me. |
|
Sure thing. I consciously did not carry that behavior forward because I'm a firm believer that the extruder should be parked when not in use. |
|
I think this caught me out. When levelling. After the bed and extruder have autohomed, it will sit higher above the bed With the touch sensor centred( so nozzle is offset). Press 1 on the LCD to get it to drop the nozzle and move it to bed centre. Then continue with z offset adjustment and 2-5 position wheel adjustments. |
|
Made a sizable Binary drop last night. Laser (should be) supported across all versions/variants now but I have no way to test it. Got in a fix for M73 thanks to @JohnScottUK And finished up with a bit more probe tuning. I imagine the bulk of our probe failures are behind us now. |
|
Id be interested. Sure. I am curious as to how the elapsed/remaining time is calculated because they both get reset during my start gcode. I think it will be the gcode command I trigger. My start-stop gcode is here (Cura) and here (Prusa) if anyone is interested. |
@synman too bad you can't block said whiner so the rest of us can benefit from your changes :( |
|
I'd be interested.... |
|
@synman and if not clear, I'd appreciate being added as a contributor too -- I've finally gotten your most recently pushed code up and building in CLion. Was strongly considering a move to Klipper until you started cranking out fixes and additions. Am now reconsidering that and hence want to stay up to speed with this work. |
|
This is only temporary as I truly do believe in the spirit of open source. With that said, access has been granted for those who have requested it. I could really go for some additional real contributors too lol. |
|
Good time of the day. I have a 3S1 Pro printer. Tell me which firmware of the three should I choose - abl, ubl25 or ubl100? Which one is the most stable? Thanks. |
|
I personally use bugfix-2.1.x UBL 100 so it gets the majority of my attention. |
|
All three are equally stable (I tend to try out each on each release to help find bugs). As for which one to use. It's user preference. ABL is the closest to the original firmware for bed tramming. UBL is newer algorithm that should provide a more accurate bed compensation mesh. As for ubl25 or ubl100.. the 25, only uses 25 test points, and 100 uses 100 test points. Obviously the ubl25 takes less time to generate a bed compensation mesh. |
|
Question on M18, M84 - Disable steppers With the original firmware one was able to disable each axis independently. Now X and Y are tied to Z. I'm trying to understand the logic behind this. Is this a common practice with other firmware? I just need some enlightenment. |
|
Those RAT B@$^@#@!!! So close this issue as mute. |
|
Fwiw, it is a very common practice when running in what Marlin calls standalone mode. |
|
Ok. Did know that. Side note: How many decimal places is allowed on any of the axis steps? |
|
it's not so much precision as it is micro stepping... somewhere between those two drives how little of a move the machine can actually make. I believe we currently have the precision set to 4. I can't remember off the top of my head, but it's the value you asked for when we were playing with backlash compensation. |
|
Yep, that's what I've confirmed so far. And yes, it can make a difference, every so slight. |
|
Good afternoon. This is a photo from the internet and I have the same error when installing your firmware on a 3S1 Pro. I put all three abl, ubl25 and ubl100. When starting table auto-leveling. |
|
I can't do that. I have already returned to your first build, on which you connected LA, the ABL version. There is no such problem there. |
|
so this is a two way street. No one is paying my bills here. If you don't get that we are going to have a serious problem. It does not matter what version of the firmware you are running, the touchscreen version should be the same and available on your screen. If you do not have the time to assist me in filling this integration gap I would really rather you just go somewhere else. |
|
No problem, I'll take a photo now. |
|
|
|
thank you. this tells me you are running the November touchscreen firmware. |
|
|
|
@synman I think I have resolved my problems, they were not directly linked to the firmware but I think more to mechanical side of the printer. On the stock FW with ABL probing i didn't had any issue. After some installation of FW I began developing the issue. I did spent a lot of time testing UBL on your FW. After you last FW it began failing even with hack. But at the end I found out i had a loose t-nut on my z axis. Now that i fixed that it works perfectly. Could it be position that by introducing the ubl and other features like backlash it is now less robust if the printer is not set correctly? Is there any check or threshold during probing? P.s. I have not that many experience with 3d printer but I'm a mechanical engineer and i have some knowledge of programming. |
|
wow.... so my firmware sniffs out machines needing tuning and refuses to work on them? hahaha! I would have never anticipated that and am blown away you got things going! Perhaps your issue is different than others are experiencing but it is awesome to hear you've got things going! Are you able to "break" your machine again? :) Or maybe describe exactly what t-nut / etc was loose (how loose / etc)? At this point I'm will to try to recreate your issue as I'm in he midst of battling a Russian invasion lol. |
|
At the beginning it did not notice that but after quite a lot of bed leveling runs it started to make different sounds it was then I begin suspecting that something mechanical is wrong. The t-nut it moved very easily and when it developed sounds you could lift the holder of the nut for a less then a millimeter. The most repitable point of failure for me was probing point 0,0. The same behaviour I observed on all the FW ABL, UBL25 and UBL100. I will test some more. as I have to print tomorrow. |
|
I've that issue on my S1 Pro, i tried ABL and both UBL firmware, when I use and I try to do automatic levelling the nozzle just don't move and after some time I got that error, when I use UBL firmware it starts but near the end looks like that firmware crash because the fan goes at maximum speed and everything are stucked |
|
удалось как-то решить проблему? |
|
@synman, thank you for your work! What type of thermistor is specified in the firmware? I took measurements, and received significant deviations from the specified temperatures. Having set the temperature to 200 degrees, the actual temperature was 180, at 300 - 270. After taking measurements, I found out that a Semitec 104NT-4-R025H42G (104GT-2) thermistor is installed in my printer from factory. |
|
I know for certain we are using the Creality table for the hotend because the corresponding Marlin table tops out below 300C. Let me track down the source for you (you'll see where I left the old table commented out): https://github.com/synman/Marlin/blob/bugfix-2.1.x/Marlin/src/module/thermistor/thermistor_1.h |
|
Creality has us using |
|
further tie to Creality code: https://github.com/CrealityOfficial/Ender-3S1/blob/s1_pro/Marlin/Configuration.h#L546 |
|
I see the thermistor_5 header tops out at 300C. It will demonstrate the same problems we initially saw with thermistor_1 which make it a non starter imho. Further reference: #21 |
|
Thanks for your reply. I saw similar problems on the forum and decided to write to you about it. I will study the data you provided and try to give a more accurate answer. I have owned the printer for about a month and have not checked the temperatures on the original firmware. I will make a rollback to the original firmware and compare the results. |
|
Hello! Thanks for the work on the firmware! I use it on my S1 and S1 Plus and it works great. I think it would be a good idea to change the table and extruder temperature limits for the S1 Plus (from 250 to 300 and from 100 to 110 degrees). |
|
Is there a way to change the screen layout? I installed 2.1.2 just fine (after upgrading to Creality's latest fw and screen fw 1.0.3)... but what I an really looking for is for my screen to show me the current Z height info.. is there any way to easily accomplish this? is there a screen fw for this anywhere? |
|
Hey could anyone provide the original source code before compiling? I would like to make some small changes to the firmware for my liking. |
|
Hi, thank you for your hard work. I have a problem with my S1 Pro that was before. During ABL operation, at some point the printer freezes and the same error appears on the display. I am using bugfix-2.1.x-F4-s1pro. Perhaps some solution to this problem has already been found? the printer is a little over a week old and I don't think anything could have broken. everything works on stock firmware |
|
Try this? |
|
I know it's a bit of an old thread, but I have a S1 Pro with the F1 board. Can I still update to your firmware without any problems? |
|
I appreciate you reaching out and taking the time. I have unfortunately
sold my S1 printer with the intent of upgrading to a bambu labs x1c in the
coming months. Grew annoyed with the printer being the hobby/money pit
instead of printing. I believe at the time I moved on from github and
updated to the most current creality firmware as it appeared to be
overhauled by creality. There was some problem with the mesh setup where it
would over correct and it became impossible to level. That was the nail in
the coffin pushing me to sell it.
…On Sat, Apr 20, 2024, 15:10 Braincake87 ***@***.***> wrote:
I know it's a bit of an old thread, but I have a S1 Pro with the F1 board.
You mention that you should be starting with the 2.0.8.24 firmware, but
that is not available for the F1 board.
The latest version I could get from Creality is the 2.0.8.23.
In the baseline firmware folder here, you have the 2.0.8.16 for the F1, so
that's even a lot older.
Can I still update to your firmware without any problems?
Thanks!
—
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARPXQSXTR73PGB4BVMGFOCDY6LKSVAVCNFSM6AAAAAAUSE2KCGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNZWGMYTQ>
.
You are receiving this because you commented.Message ID:
<synman/Ender-3-S1-Pro-Firmware/repo-discussions/16/comments/9176318@
github.com>
|
|
I had a lot of issues with the ABL as well from the start, since I bought the S1 Pro right when it came out. |
Uh oh!
There was an error while loading. Please reload this page.
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:
build together 💪.
To get started, comment below with an introduction of yourself and tell us about what you do with this community.
All reactions