-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
Mesh leveling data is drawing over the printing screen #1009
Labels
Confirmed but not a bug
The behavior was confirmed but not considered a Professional firmware bug
stale-closing-soon
Comments
mriscoc
added
the
Confirmed but not a bug
The behavior was confirmed but not considered a Professional firmware bug
label
Aug 3, 2023
mriscoc
changed the title
[BUG] Mesh leveling data is drawing over the printing screen
Mesh leveling data is drawing over the printing screen
Aug 3, 2023
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. |
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Confirmed but not a bug
The behavior was confirmed but not considered a Professional firmware bug
stale-closing-soon
Bug Description
When a new auto mesh leveling is required prior printing, the
G29 (or G29 P1 for UBL)
code needs to be inserted in the G-code start script but it may result in this:This is caused by an incorrect position of the G-codes that heat the bed and the hot-end. By example, this G-code snippet will cause that error:
Temperature has high priority in the firmware, and changing temperatures in the middle of printing process will trigger the printing screen. So due to the priority, it will run the M190 without waiting for mesh leveling to complete, then, the mesh points will be drawing over the printing screen.
The correct way of set the start G-code script is detailed in: https://github.com/mriscoc/Ender3V2S1/wiki/Slicer-G-code-Scripts
The text was updated successfully, but these errors were encountered: