-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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] Unresponsive LCD #15169
Comments
This looks like display throttling by purpose. Recently repaired. |
I'm assuming with a delta, even straight lines are broken up into segments. I changed Should the buffers be increased further? |
I'm having the same issue. MKS Gen L. RepRap Discount Smart Controller. Stock buffer sizes, 150 segments |
Same issue on skr 1.3 with tmc spi 64 microstep 200segment at ultra low speed too |
I should also mention that even when compile is successful, I get the following:
|
same issue on both of my printers, one Delta with SKR v1.3 + TMC2208 the other one is CoreXY MKS sbase v1.3 with fast decay mod. I used to have external TMC2208 on MKS sbase and firmware was from 2018, and it worked fine. |
I have to increase the "BLOCK_BUFFER_SIZE" to 128 to get it to work, I only changed this value. |
What are risks of increasing BLOCK_BUFFER_SIZE? Default is 16, comments here say 128 effectively resolves this issue. That's a pretty drastic increase, does it conceivably affect other operations? |
The biggest issue I’ve seen with increasing it is that the Octoprint gcode viewer may “run ahead” of what’s currently printing, and if you cancel a print from the host it will print what’s left in the buffer before stopping. |
I increased my Block Buffer to 128 and the LCD screen wouldn't respond at all. even after reboot. I dialed it back to 64, still no joy. Setting it to 32 seems to work though. I was able to access my menus during the first layer. Oh, and Delta_Segments is set to 150. |
I am not sure if different marlin versions play a role in this problem, have you tried some older commits? I left delta_segments at 200 and still works fine. My problem is really related to this #15293 |
Any new insights into this issue? |
@DkOuvE have you tested with latest 2.0.x ? |
Lack of Activity |
I keep pulling the latest Marlin every couple of days with no changes in the issue. It's also happening on my Cartesian when going at fast print speeds. |
so maybe the printer is so busy that it cant update the LCD? |
Someone with the necessary savvy (and two thumbs) will have to do proper troubleshooting to track down the cause of this issue. |
I have the issue here too, Anycubic Predator, with SKR 1.3, FYSETC MINI12864 v2.1 RGB LCD. |
I think changing the buffer size is just a workaround but not a fix, this board still needs: |
@istyszy this is an issue only affecting more recent builds of Marlin, plus more than one board type, so I don't think it's a board issue, or it would have always been present. |
I have the time to fix it but just not the knowledge. |
Reference to earlier PR #14960 "Repair Display Throttling" |
Change buffer size does not helped me |
Same for me. Tried 32 and 64. Setting 128 has a compile time warning about interest to uint conversion.
Sent from my Samsung Galaxy smartphone.
…-------- Original message --------
From: ZhenyaKa <notifications@github.com>
Date: 07/11/2019 08:40 (GMT+00:00)
To: MarlinFirmware/Marlin <Marlin@noreply.github.com>
Cc: hearnia2k <hearnia_2k@hotmail.com>, Comment <comment@noreply.github.com>
Subject: Re: [MarlinFirmware/Marlin] [BUG] Unresponsive LCD (#15169)
Change buffer size does not helped me
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#15169?email_source=notifications&email_token=AEDB26ACYIDVJKITZIUYAITQSPIAPA5CNFSM4IT4UKGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDLUPKQ#issuecomment-550979498>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEDB26DBFJPTASIRAQYO273QSPIAPANCNFSM4IT4UKGA>.
|
See if the recent merge of 15837 helps. |
I just tried this out on my Anycubic Kossel Linear Plus, with the original Trigorilla mega2560 board. The display was very responsive. I was able to effectively babystep to adjust my print height as the print started, and had no issue navigating menus or adjusting feedrates. I hadn't updated this firmware since perhaps August or September, and it definitely had responsiveness issues then. In both cases I was printing over USB from Octoprint. It's good to see the usability improved! |
Just tried it. The difference is night and day. I can also report no issues using the screen on my Kossel now. Screen is as smooth as butter. |
seems to fix the issue, so more a config issue and not an issue with the firmware as such |
No, it was definitely a firmware issue, it is just fixed! I was pointing out that it works great even with the default values for buffers. |
These are irrelevant for this issue anyway. Increasing BLOCK_BUFFER_SIZE still can improve that. |
Just for another confirmation: Upgraded my firmware today, and now LCD works fine now. |
I have the same issue with a homebrew Delta with the bugfix version from a week ago. I have used the generic Delta example configs to tune my machine. LCD cannot be used during print, also not during UBL or other leveling services. I am in the process of calibrating the new machine, a print has failed but I cannot 'stop' the print because of this haha. SKR v1.3 - Delta - TMC2208 |
Try again with the latest commits from bugfix-2.0.x. This was only fixed a few days ago. |
Wow, served with retroactivity. Thanks! |
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. |
Description
I am using a BIQU SKR, as well as the latest Marlin 2.0 and config for the Anycubic Linear Plus. The Fysetc RGB LCD screen I have connected works properly unless printing the first layer of a print (through both SD and USB). After a print / second layer, the screen becomes responsive again. While the screen is frozen, pressing the button does make audible feedback.
Steps to Reproduce
Expected behavior:
LCD values to change, opening the setting menu when the rotary encoder is pressed.
Actual behavior: [What actually happens]
LCD freezes until the first later is finished.
Additional Information
Cura start GCODE incase that's the issue
The text was updated successfully, but these errors were encountered: