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

Layer update during printing #1319

Merged

Conversation

kisslorand
Copy link
Contributor

Requirements

BTT TFT or MKS TFT

Description

Layer update during printing was broken due to PR #1272

Benefits

Layer display during printing fixed. It shows the actual layer height, it updates during printing.

Related Issues

Fixes this issue: #1314

@oldman4U
Copy link
Contributor

oldman4U commented Dec 1, 2020

Hi.

Why would you change the event to MKS_32_V1_4?

@oldman4U
Copy link
Contributor

oldman4U commented Dec 1, 2020

And I believe you have a typo, you write "Targetl" but I believe it should be "Target" and suddenly the compiling which failed before also works.

@kisslorand
Copy link
Contributor Author

kisslorand commented Dec 1, 2020

Hi.

Why would you change the event to MKS_32_V1_4?

I keep forgetting to set it back to original before making a commit. MKS_32_V1_4 is what I use for my builds.

And I believe you have a typo, you write "Targetl" but I believe it should be "Target" and suddenly the compiling which failed before also works.

Yup, there was a typo.

New commit is on the way, hope it fixes layer update during print issues for BOARD_SD, TFT_USB and TFT_SD gcode file source.

@oldman4U
Copy link
Contributor

oldman4U commented Dec 1, 2020 via email

@mehmetsutas
Copy link
Contributor

👍🏻

I was just making the same change and saw this. :)

@kisslorand
Copy link
Contributor Author

Does it work with these changes with SD onboard? I can test it only with SD and USB connected to the TFT.

Copy link
Contributor

@mehmetsutas mehmetsutas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe on line 278 we should put the coordinatequery call in ternary if also. If it is not printing from BOARD_SD, we do not need to call coordinatequery frequently.

@kisslorand
Copy link
Contributor Author

kisslorand commented Dec 1, 2020

Why do you need it when printing from BOARD_SD?

Answering my own question... to find out the "Z:". :)

Actually I watched terminal while printing from TFT_USB and I didn't see a single M114 sent to Marlin. In the PrintingMenu.c I also see no point using it at all while printing from a media attached to the TFT.
How about this in line 278:
if (infoFile.source == BOARD_SD) coordinateQuery();

@mehmetsutas
Copy link
Contributor

@kisslorand that was exactly what I would do.

@oldman4U
Copy link
Contributor

oldman4U commented Dec 1, 2020

How can I test the code with all PRs failing to check successfully?

@kisslorand
Copy link
Contributor Author

I guess you can check the changes made and do that to your files locally than build it. How did you do it before?

@mehmetsutas
Copy link
Contributor

I am not able to check it right now. But all changes are reasonable. If it can compile, it should work.

@oldman4U
Copy link
Contributor

oldman4U commented Dec 2, 2020

I guess you can check the changes made and do that to your files locally than build it. How did you do it before?

This works with just a few changes. I use GitHub Desktop to merge PRs to my local repository.

@oldman4U
Copy link
Contributor

oldman4U commented Dec 2, 2020

off topic

@mehmetsutas Have you got a mail from me yesterday?

@bigtreetech bigtreetech merged commit 8d428c5 into bigtreetech:master Dec 2, 2020
@kisslorand kisslorand deleted the Layer-update-during-printing branch December 21, 2020 18:24
jeffeb3 pushed a commit to V1EngineeringInc/BIGTREETECH-TouchScreenFirmware that referenced this pull request Nov 10, 2021
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.

4 participants