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

Update fast nozzle cooling #4014

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

Update fast nozzle cooling #4014

wants to merge 235 commits into from

Conversation

espr14
Copy link
Contributor

@espr14 espr14 commented May 26, 2024

Fast nozzle cooling used 'F' parameter in M109 but this collides with Marlin FW so 'C' should be used (as reserved in https://reprap.org/wiki/G-code)

Tomcus and others added 30 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 "--"
Transfers were not cleaned up ever, if in print preview when finished,
this was caused by wrongly detecting if the transfer is in progress. It
did not check, if the backup file was there, do transfer, where backup
file was not present (finished) were taken as in progress.
CZDanol-prusa and others added 26 commits April 16, 2024 14:52
This reverts commit f605a28bea662f02ec8d5121f4f57cee8ada774b.
Copy pasted from standard printing screen

BFW-5371
Fast nozzle cooling used 'F' parameter in M109 but this collides with Marlin FW so 'C' should be used (as reserved in https://reprap.org/wiki/G-code)
@danopernis
Copy link
Member

This will break existing gcodes. What problem are you trying to solve?

@espr14
Copy link
Contributor Author

espr14 commented Jun 3, 2024

I've created and implemented that parameter but I've used already used parameter. So I've changed it to C. I'm not sure why it's back. Also people don't use it because it was not promoted.

@bkerler
Copy link
Contributor

bkerler commented Aug 19, 2024

@danopernis he used the wrong flag in this commit. It should be fixed in order to reflect the official documentation here , which states that 'C' should be used.

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.