-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[BUG] TFT35 freezes on mesh edit mode #2853
Comments
Do you have always the same issue (e.g. when you move to Tuner menu and press on UP/DOWN buttons) or it is a random issue (sometime you get M14, other times a freeze here or there) or you have the issue when closing the Tuner menu (after pressing on the OK button after you adjusted the mesh height) and coming back to Mesh Edit menu?
If you get the issue only when moving back from Tuner menu to Mesh Edit menu, from Pronterface, OctopPrint etc. try to use the command:
and verify if you get the issue or not Furthermore, try to set a mesh grid smaller than 9x9 in Marlin (e.g. 5x5) and verify it the issue is not present |
All the time this time
Any time an adjustment is made in mesh edit ot freazes before the change.
…On Wed, Oct 4, 2023, 10:52 AM Antonino Di Guardo ***@***.***> wrote:
Do you have always the same issue (e.g. when you move to Tuner menu and
press on UP/DOWN buttons) or it is a random issue (sometime you get M14,
other times a freeze here or there) or you have the issue when closing the
Tuner menu (after pressing on the OK button after you adjusted the mesh
height) and coming back to Mesh Edit menu?
If you get the issue only when moving back to Mesh Edit menu, from
Pronterface, OctopPrint etc. try to use the command:
M421 I<index I> J<index J> Z<feedrate>
and verify if you get the same issue or not
—
Reply to this email directly, view it on GitHub
<#2853 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWBRE7VJIRPACQZDZZPCSLX5WO4JAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBXGM3TKOBSGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
Sorry your english is not so much clear to me. |
Failure mode 1
1. Enter mesh edit mode.
2. Select point to edit
3. Adjust tft35 adjustment knob -> no response and it freezes
4. Reset.
Failure mode 2
1. Enter mesh edit mode.
2. Select point to edit
3. Adjust tft35 with on screen up or down hutton -> no response and it
freezes
4. Reset.
…On Thu, Oct 5, 2023, 7:42 AM Antonino Di Guardo ***@***.***> wrote:
Sorry your english is not so much clear to me.
So, do you mean that you have a freeze when you press on UP/DOWN buttons
in the Tuner menu to adjust mesh height? Is that enough for the TFT
freeze? do you always get the M14 error message before the freeze?
—
Reply to this email directly, view it on GitHub
<#2853 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWBRE5XWRNB7YDRCACVLLLX53BNJAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGA2TANZSGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
In all cases TFT35 says wait for processing before ot freezes.
It does not throw an error code
…On Thu, Oct 5, 2023, 7:46 AM FrozenIceman ***@***.***> wrote:
Failure mode 1
1. Enter mesh edit mode.
2. Select point to edit
3. Adjust tft35 adjustment knob -> no response and it freezes
4. Reset.
Failure mode 2
1. Enter mesh edit mode.
2. Select point to edit
3. Adjust tft35 with on screen up or down hutton -> no response and it
freezes
4. Reset.
On Thu, Oct 5, 2023, 7:42 AM Antonino Di Guardo ***@***.***>
wrote:
> Sorry your english is not so much clear to me.
> So, do you mean that you have a freeze when you press on UP/DOWN buttons
> in the Tuner menu to adjust mesh height? Is that enough for the TFT
> freeze? do you always get the M14 error message before the freeze?
>
> —
> Reply to this email directly, view it on GitHub
> <#2853 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AHWBRE5XWRNB7YDRCACVLLLX53BNJAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGA2TANZSGE>
> .
> You are receiving this because you authored the thread.Message ID:
> <bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/2853/1749050721@
> github.com>
>
|
ok, so do you see any movement of the nozzle before the freeze? I mean, try to set 1mm on Tuner menu and then press on UP or DOWN button. Is the nozzle moved before the freeze? |
No, the position of the nozzle does not change. Nor does the display
indicate the position has changed.
…On Thu, Oct 5, 2023, 7:49 AM Antonino Di Guardo ***@***.***> wrote:
ok so do you see any movement of the nozzle before the freeze? I mean try
to set 1mm on Tuner menu and then press on UP or DOWN button. Is the nozzle
moved before the freeze?
—
Reply to this email directly, view it on GitHub
<#2853 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWBRE6YJRIDRIE26BAMJCDX53CIJAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGA3DIMBTGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
ok. Are you using the pre-compiled TFT fw from master branch? if possible always try to compile the fw by yourself |
Yes, I was using the precompiled branch on the Master that was released
last week.
I'll work on compiling my own and testing it for late next week.
…On Thu, Oct 5, 2023, 7:51 AM Antonino Di Guardo ***@***.***> wrote:
ok. Are you using the pre-compiled TFT fw from master branch? if possible
always try to compile the fw by yourself
—
Reply to this email directly, view it on GitHub
<#2853 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWBREYVZOVKK7ICEIYE643X53CQXAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGA3DQMJXHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
which is your TFT variant? I will compile it for you |
Thank you!
I use the following tft display, it has the GD processor on it.
BIGTREETECH TFT35 E3 V3.0.1
Note, I won't be able to test it until at least Tuesday
…On Thu, Oct 5, 2023, 7:54 AM Antonino Di Guardo ***@***.***> wrote:
which is your TFT variant? I will compile it for you
—
Reply to this email directly, view it on GitHub
<#2853 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWBRE6T2P33PRQAPCABZFDX53CZZAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGA3TENJUGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
BIGTREE_TFT35_V3.0_E3.27.x.bin
Is the firmware file I used
…On Thu, Oct 5, 2023, 7:57 AM FrozenIceman ***@***.***> wrote:
Thank you!
I use the following tft display, it has the GD processor on it.
BIGTREETECH TFT35 E3 V3.0.1
Note, I won't be able to test it until at least Tuesday
On Thu, Oct 5, 2023, 7:54 AM Antonino Di Guardo ***@***.***>
wrote:
> which is your TFT variant? I will compile it for you
>
> —
> Reply to this email directly, view it on GitHub
> <#2853 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AHWBRE6T2P33PRQAPCABZFDX53CZZAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGA3TENJUGY>
> .
> You are receiving this because you authored the thread.Message ID:
> <bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/2853/1749072546@
> github.com>
>
|
if you have the GD E3 vsersion, shouldn't you use BIGTREE_GD_TFT35_V3.0_E3.27.x.bin? |
Woops, yes you are right, that is the one I used.
Sorry currently looking through github on my phone.
…On Thu, Oct 5, 2023, 8:02 AM Antonino Di Guardo ***@***.***> wrote:
if you have the GD E3 vsersion, shouldn't you use
BIGTREE_GD_TFT35_V3.0_E3.27.x.bin?
—
Reply to this email directly, view it on GitHub
<#2853 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWBRE3MK2Q5K2TL774FCY3X53DZDAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGA4DQNBVGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
try this fw. It includes my PRs. However the |
Thank you and appreciated.
When I get back to the printer I will try your build.
Thank you!
…On Thu, Oct 5, 2023, 8:32 AM Antonino Di Guardo ***@***.***> wrote:
try this fw. It includes my PRs. However the Mesh Edit is the same as the
current official BTT fw. You have to provide the config.ini file (even
the current one you are using) due I added two new baudrate values on
parameter serial_port. Eventually, after the fw installation move on Connection/S
Ports menu and change baudrate for mainboard if it has been changed
BIGTREE_GD_TFT35_V3.0_E3.27.x.zip
<https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/files/12820233/BIGTREE_GD_TFT35_V3.0_E3.27.x.zip>
—
Reply to this email directly, view it on GitHub
<#2853 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHWBRE6RVL4AWJS47BA2Q5DX53HIHAVCNFSM6AAAAAA5RENHV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBZGE2DENRZG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
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. |
TFT35 is completely unuseable in mesh edit mode in UBL mesh leveling 9x9.
This is similar to the initial error in prior report before it was corrected. The TFT display is unresponsive when adjusting mesh position in mesh edit mode.
Re: [bigtreetech/BIGTREETECH-TouchScreenFirmware] [BUG] TFT35 Mesh Edit throws M14 and unable to adjust Mesh (Issue #2786)
Steps to reproduce
Work around
9. Build mesh on tft 35 side
10. Save mesh
11. Switch to marlin mode
12. Load mesh
13. Adjust mesh in marlin
14. Switch back and forth to tft35 periodically mesh edit , without adjustment, to visually see adjustment points
Expected behavior
Tft35 is able to mesh adjust
Actual behavior
Tft35 froze and couldn't change mesh offset point
Hardware Variant
TFT 35 GD E3
Latest, from week of September 28th
SKR mini e3 v3
Marlin 2.1.2
Additional Information
See prior open issue with images of process.
The text was updated successfully, but these errors were encountered: