-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Serveral issues with Ender3S1-F1-UBL-MPC-20230809 #1052
Comments
I can confirm that these issues exist. I flashed the Ender3S1-F1-UBL-MPC-20230809 FW as well and I get random actions on first layer where the head moves to back right corner of bed and reverses filament out. With no warning or reason why. I am testing a print on previous version. |
@jderosa3 Thanks for confirming! I was not sure if this is a problem on my side or a real bug. |
No problem. Others have confirmed same issue on other forums as well. |
Duplicate of: #1025 |
I have a run-out sensor and still got this error when active and sensor working fine. |
@mriscoc Sorry, I don't understand your hint. I saw the bug with the filament sensor and set it to "low". as @jderosa3 said, even with sensor and correct setting I got the error. There is sometimes no error message, the printer just behaves strange. I have a stock S1, so your config guide tells me, nothing needs to be changed |
Read the Wiki (manual) and follow the guide about filament sensor. |
You need to found the correct High/Low configuration that match your filament sensor. |
@mriscoc : in my case I don't get a filament error when setting it to LOW. I get errors regarding a heating problem or without an error. This doesn't look like the filament sensor is the reason |
@Horgul123 Heating is not related to the filament runout sensor. |
@jderosa3 your heating issue is not related to the runout sensor, check your thermistor and heatblock silicone jacket. I can't reproduce your heating issue. |
This is what we're saying. But it only happens with your latest firmware. With
the older one everything works, so it can't be a hardware issue.
If there is anything I can do to help you to find the root cause let me know.
I tried it twice with the new new version and had the same issues. When I reinstalled the old version it was ok again
|
I need reproducible steps to be able to debug any possible bug. You are printing from SD or from a host (Octoprint) |
I'm printing via Octoprint.
It happens shortly after starting a print. I'll install the new version
again today and document everything in detail
|
Checked it again as promised. |
Did you disable the +VUSB? |
@mriscoc no, didn't do this. It works fine. At the moment it works with your latest FW, too. No idea, why it made problems a few days ago..... Did the same as yesterday. |
Remove the +VUSB, it causes random behaviors and might damage the control board. |
As mentioned: The printer runs fine. I use a network USB extention, so I don't think the pin is powered. I'll double check this |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Did you test with a precompiled firmware?
No, but I will test it now!
Bug Description
When using the Ender3S1-F1-UBL-MPC-20230809 FW I have several problems:
The issue with the filament sensor is "fixed" with changing the setting to "LOW", but:
Going back to the 202305 FW fixes all problems, so it must be 202308 related.
Can't be reproduced because it happens not always and not always at the same time of of the print
Bug Timeline
new
Expected behavior
Work like previous version 202305
Actual behavior
Strange errors:
Heating suddenly stopped
Nozzel moved to home and print is stopped
Going back to Ender3S1-F1-UBL-MPC-20230522B solves the problems
Steps to Reproduce
starting print
Version of Professional Firmware
Ender3S1-F1-UBL-MPC-20230809
Printer model
Ender3 S1 F1
Electronics
?
Add-ons
none
Bed Leveling
UBL Bilinear mesh
Your Slicer
Cura
Host Software
OctoPrint
Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: