search

mriscoc / Ender3V2S1

This is optimized firmware for Ender3 V2/S1 3D printers.
Other
2.62k stars 358 forks source link

[BUG] (Filament unloads at start of print; runout is disabled) #876

Closed cds333 closed 1 year ago

cds333 commented 1 year ago

Did you test with a precompiled firmware?

Yes, and the problem still exists.

Bug Description

At the start of a print while the extruder is supposed to be doing its first purge line, the extruder cranks up in reverse and purges the entire filament.

Enable runout is off (box is unchecked), it is set to HIGH (but that shouldn't even matter since it is disabled). All the numeric values in the filament menu are set to 0.0mm.

The exact same gcode file on the same card will cause the bug randomly. It happens with multiple files, and it has happened on multiple printers. The only thing that I think is consistent is Cura as the slicer.

Bug Timeline

Has been happening for multiple firmware versions.

Expected behavior

Expected a purge line on the bed.

Actual behavior

Extruder completely unloads filament.

Steps to Reproduce

No abnormal steps required.

Version of Professional Firmware

E3V2-427-BLTUBL-MPC v2.1.3 20221222

Printer model

Ender 3 Pro

Electronics

4.2.7

Bed Leveling

UBL Bilinear mesh

Your Slicer

Cura 5.0.0

mriscoc commented 1 year ago

Try with the latest version: Ender3V2-427-BLTUBL-MPC-20230312.bin Suggested slicer scripts are in the Wiki.

cds333 commented 1 year ago

Is there a known cause that was patched?

I know there were similar issues related to filament runout, but since mine is off it cant be that.

The fact that the exact same file will cause the malfunction one print and then not the next would lead me to think the slicer is not to blame.

Thanks for all your hard work. I absolutely love everything else about this firmware and install it whenever I can.

mriscoc commented 1 year ago

Is there a known cause that was patched?

Each version is based in the latest Marlin bugfix available at compile date, so maybe for that release there was some change that fix your issue. But there are no reports about problems with the runout sensor other than HIGH/LOW misconfiguration.

github-actions[bot] commented 1 year ago

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

github-actions[bot] commented 1 year ago

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.