Skip to content
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

gcode: Fix issue on unloaded filament temperature being higher temperature than loaded filament (lower temperature) #3681

Open
wants to merge 224 commits into
base: master
Choose a base branch
from

Conversation

bkerler
Copy link
Contributor

@bkerler bkerler commented Jan 13, 2024

This PR adds a configuration store to remember the past filament and does compare if the temperature is lower than the filament that has been unloaded before, and if, does set the last filament temperature only for loading until purging has finished, thus preventing the nozzle to clog.

Fix is related to issue #3585, #3083 and #1821

Tomcus and others added 27 commits March 28, 2024 12:20
We don't have consent from the user right now and they are not
encrypted. Shouldn't go to "production".

BFW-3468.
Dialog stores the state of underlying screen upon construction
and loads it back upon destruction. Consistently. Like, always.

Without this, ToolBox::DialogToolActionBox would set focused item
which would prevent menu screen from serializing its focused item.
Allow them in redscreen/redscreen.

It's already sent proactively, so it's safe.

BFW-5207.
Show Enclosure menu only if enclosure is active
Change string describing invalid temperature from "N/A" to "--"
Tomcus and others added 19 commits April 16, 2024 14:52
This should prevent noices when calibration X axis on XL and improve
Tool Offset Calibrations, but only when run as part of selftest, not as
gcode (will be done in separate commit/PR)

BFW-5322
We shouldn't run any selftest with phasestepping enabled. To prevent
running G425 with phase stepping we are disabeling phasestepping
temporarily in the gcode it self instead of the selftest state machine.

This improves Tool Offset Calibration results when running said
calibration on already calibrated machine. The results are not perfect
yet. But this change removes the major inaccuracies in the measurements.

BFW-5276
We noticed shifts in measured data. Recomend reading BFW-5276 for more
details, but in the end slowing down the parking speed helped a lot.

BFW-5276
Fill will be in the next commit

BFW-5335
The problem was in write_end_item calling migrate_bank.
The function is called in store init, where migrate_bank would screw things.
In other cases, the free space for the end item is checked
in the parent calling functions.

BFW-3553
This reverts commit f605a28bea662f02ec8d5121f4f57cee8ada774b.
Copy pasted from standard printing screen

BFW-5371
@nazar-pc
Copy link

Not sure where to comment, but these tags on GitHub are extremely annoying for those who subscribe to releases via Atom feed. Please consider an alternative approach there. I'm talking about the likes of https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/build%2F6.0.0-BETA%2B7062.PR3681.B4

@danopernis
Copy link
Member

@nazar-pc thanks for bringing that up. The CI settings that got merged to the master branch after 6.0.0 release seems to contain some changes causing builds to fail and CI system to generate those tags. I will try to fix that tommorow.

Meanwhile I manually deleted those tags.

FYI @bkerler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.