-
Notifications
You must be signed in to change notification settings - Fork 1.6k
-
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] "Busy processing, please wait..." #2208
Comments
Sorry. I never saw this on one of my printer and I am not working on it. Use the latest TFT FW and Marlin 2.0.9 and maybe someone is willing to help here. Good luck |
Not on your printer, but you already try to help someone else, in this post for example, so maybe you can have any suggestion for me. |
Hello, This message still appears, but when I manipulate several commands at the same time, for example launching an automatic leveling then a home. The message appears, but disappears as soon as the 1st instruction ends, normal operation as a result. |
How did you solve it in this issue ? Change firmware ? |
That's what I just told you, yes. I know my English is bad, but still 😭 |
Any news? |
I change the cable between SKR board and the TFT screen with shielded cable. I run at 250000 baudrate with 1meter cable... |
And...? |
I made the change this morning, it is printing now |
It also failed after 2hours of print... |
Hello, |
I have the same issues with BTT 1.4 SKR Turbo, I can't change as example "Flow" or "Speed" immediatly it could take up to 2-5min until it changes during printing. I'm also not able to "Cancel" a print on switch off is the solution. My Marlin Parameters: BIGTREE_TFT35_V3.0_E3.27.x.bin --> 18-AUG-2021 Can anybody help ? |
For now, with baudrate at 115200 and a 40cm cable (which I received with the screen) I still not have the problem since yesterday. |
Somebody know if it exists another firmware compatible with the TFT35 V2.0 screen ? |
What makes you believe the firmware is the issue? Do you believe you are the only one using this screen or that all others are not using it because what you believe is a bug? Do you think it could be eventually be the case that the TFT is not the reason for this problem? |
This happend on about 15 TFT screen, so yes I believe it's a bug on the firmware |
How is it possible that the same firmware does work properly for others? |
I maybe find the problem, just need to test. |
For now, it's printing good at 115200 baudrate |
@yannick-alch if the issue was fixed, please close this ticket |
@bigtreetech it seems the issue was solved by the user and no other help is required so the ticket could be close |
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. |
Hi everyone,
Description
I know this bug is known, but I start a new ticket.
When printing, sometimes I have a "Busy processing, please wait..." message ont the TFT 35 V2.0 screen, in red on top of the screen. When this message appear, I have to restart the printer (and then restart the print...).
I'm using TFT35 V2.0 screen, release Vx.x.26 and SKR 1.4 motherboard.
Steps to reproduce
Expected behavior
Finish every print with success
Actual behavior
At a moment, you will see the message "Busy processing, please wait..." on top of the screen
Then, the screen does not respond anymore at any command you want to send (G28, G1, M105, M114...)
Hardware Variant
I am using TFT35 V2.0 screen, release Vx.x.26 and SKR 1.4 motherboard with marlin 2.0.5.3
Also try with release V.x.x.27 and same behavior
By searching on the source code of the TFT35, this is like the screen doesn't receive "ok\n" response from the motherboard, and then "infoHost.wait" is always "true" in the function "sendQueueCmd(void)" in interfaceCmd.c file. So the buffer is always full and wait till receive "ok\n" from SKR.
Maybe I am wrong, but this is my track.
I know @oldman4U , @Magiquall already work on it, but didn't works for me.
Hope somebody can help me deal with this...
The text was updated successfully, but these errors were encountered: