[BUG] Screen freezes in Marlin mode while starting to draw status screen. #1433
Comments
|
|
|
Try disabling it in the config.ini file by selecting |
as temporary workarround I'll try, but that's not a real bug fix. |
|
There are two dots in the upper corners. Left shows that there are messages available at the touchscreen (which messages) and the right shows that there is activity going on. What else is connected and can you identify a specific TFT firmware version where this is broken. I have no SKR mini but a SKR E3 DIP and have been using Marlin mode today with the TFT firmware from today. |
|
I agree that this is not a permanent solution. |
|
Hi radek8 So serial always on has to be activated and you have to boot up in Marlin mode to verify this issue, right? If one of the two "parameters" is not true, the problem will not occur? |
|
Yes |
The one which I today built/flashed is 6d87753 I do have in my config "serial_always_on" enabled, as that was recommendation for using those TFTs with printers connected to OctoPrint. |
|
Hi kad. So there are 14 days between the two versions and PR merged on Dec. 15th, 17th, 19th and 23rd. Would be good to know which PR exactly broke it, so the developer can review his code. serial always on is needed to keep the serial port active while using Marlin mode. |
|
But those two are from September and kad writes that 1bd1411 works, which is 2 weeks old. Btw, I believe you are in the same timezone. Maybe we should try to get some sleep;-) |
|
I tried 1bd1411 |
|
Looks like a kind of race condition to me. Guess we need the pros for this.
Radek <notifications@github.com> schrieb am Fr. 25. Dez. 2020 um 10:22:
… I tried 1bd1411
<1bd1411>
after 10 restarts it froze 5 times and worked 5 times
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1433 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM6XKZDOLYNDQEQ6NS4XISTSWRKVRANCNFSM4VINNNXQ>
.
|
|
did anyone test with any other printer/board that uses both EXP1 & EXP2 ports with same marlin version and TFT firmware version? |
|
Tested with only EXP3 cable on SKR E3 DIP and TFT35 E3 and no problem. Will test with SKR v1.4 next. |
|
Can someone confirm the following which I can see on 2 different printers now. I compile the firmware using VSC and PIO as usual and only change the env in platform.ini to match the TFT. Then I copy the firmware together with an unchanged config.ini and the TFT folder, both from Copy to SD Card root directory to update folder and update the firmware. Even the default baud rate is defined in config.ini, I get a No printer attached and checking the baud rate I can see, that there is NO baud rate selected in the corresponding TFT menu. Selecting the baud rate there works. 106 keyword found during update. Seems something broken here. |
|
Oldman, I can confirm the same behavior. |
I think this is diverging from original issue and deserve a separate bug report about baud rates. |
|
This may be related. If the settings are being read incorrectly it may also be the reason for the freeze. it needs a little inspection to rule it out. |
|
Hi
I just updated my tft34-E3_V3 with the new firmware and had the same issue
with no printer attached msg. WHen I checked in settings there was no baud
rate selected. Manually selecting the correct rate then showed the printer
attached
…On Sat, 26 Dec 2020 at 09:39, oldman4U ***@***.***> wrote:
Tested with only EXP3 cable on SKR E3 DIP and TFT35 E3 and no problem.
Will test with SKR v1.4 next.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1433 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE5DW5Y4ARFBK7QZLWGKL6LSWWVNRANCNFSM4VINNNXQ>
.
|
|
I tested PR # 1438
|
|
The baud rate issue should be fixed now with e104886 |
|
Can not reproduce it. Also not using SKR v1.4 and Pro with TFT24/35/43. Seems my v1.4 is broken now🥴 |
Make a reset.txt file on your SD Card. I tested this, I had the "no initial baudrate" problem until I used the reset.txt file. I had random issues when config.ini was changed (add/remove parameters) and reset.txt always cured it for me. |
|
After a new addition |
|
In this case only I have the problem hopefully. During my tests the screen of the TFT24 became darker and darker and now there is nothing shown n screen anymore - when using the SKR v1.4. Using the same screen on a SKR Pro of E3 DIP works fine;-(( I bought the v1.4 only for testing and now after 3 weeks, it is broken... |
|
kad. Does disabeling "serial_always_on" solve the problem for you? Any which cables are you using, original or self made? |
|
@oldman4U with SKR 1.4 did you enabled REPRAP_DISCOUNT_SMART_CONTROLLER? |
|
Yes. Everything was working fine. I could make the Marlin test without a problem and suddenly the TFT became darker and darker. Will check the power output today. |
can't confirm right now, as for temporary workarround I reinstalled stock display. 12864 is the only mode that I need in 99% of time due to OctoPrint, thus it is more important to have printer running stable than fighting with tft firmware.
Original 10pin IDC cable and original 5 pin dupont/jst 2.54 cable for rs232. |
|
In this case it is very unlikely that the problem will be solved. You opened this ticket, so it would be good if you could take care of it, or radek8 wants dot do it for you. I can not reproduce the issue using TFT24/35 or 43 and SKR v1.4 as well as SKR Pro. Sounds more like a cable/hardware issue to me, but it wouldn't be the first time that I can not reproduce an issue using my test systems. |
|
I had a similar-ish issue I reported here. After a few more updates to the pre-compiled, using 'serial always on' from then on, I noticed the same issue reported here. I Had to boot while in Marlin mode and the screen froze during boot, at the same point, with the same display artifacts. I had to reflash the TFT to get it out of the loop and boot into touch again. (Later I found out i could change modes if I was fast and did it during boot screens, before the freeze) Then I tried to set 'serial always' to off and it solved the issue and, with the newer firmware, the old issue on my link did not come back. So I had no issues, and 'serial always' was set to off as it had been before the 1st issue appeared. I may try to set always on back again to help diagnose, but I do not need it (was using as 'fix') nor do I use any other devices on the TFT's serials. (no octo, no pronterface). Another thing I noticed that may be related to the 'settings not applying' you are looking into: On the same firmware The 'knob color' I set on config.ini was not applying using the previous firmware (before the one available now - it was there for 14days or so.) I had to set it on the TFT. Setting 'knob idle 0' solved that, don't know why. It wasn't going zero brightness, it had no color set, despite the config.ini setting one. |
|
I'm having a similar problem with my TFT24. If serial_always_on is enabled then when entering Marlin mode the screen freezes and in my case I just get a blank screen, yet using the encoder seems to be working, as I can hear it clicking. I'm using it with a SKR 1.3 with Marlin 2.0.7.2, with every recommended option turned on and an ESP01 running ESP3D. |
Yes, only the TFT display freezes. |
|
@oldman4U tried to flash recent build from master (5b66d67) situation became even worse. With serial_always_on=0 it works, but expectedly not able to communicate with printer from e.g. esp-01 wifi module in LCD12864 mode. with serial_always_on=1 TFT boots in touch mode. but if switched to lcd12864 and trying to reboot - hangs. Only title "LCD12864 Simulator" is visible. not even Marlin boot logos appears. Tried to reboot about 10 times, always consistent hang. Board where it connected to is SKR mini E3 V2.0, today's Marlin bugfix-2.0.x branch build. |
I can confirm this behavior. |
|
Good news. I can reproduce the issue here. Maybe @guruathwal can help us. I would like to add, that I just get a black screen and no rendering besides the "LCD 12864 Emulator" at the top of the screen. kad. "serial always on" defines if the serial ports are active or not while using Marlin. So turning this function off, will also disable the ESP. |
I know, but that was exactly my use case: using LCD12864 most of the time, but keep serial open, so I can use ESP module if needed. That's why workaround with "serial_always_on=0" is not good for me (as commented above). |
|
All I can do, is to add it to the list of verified issues at the moment. Hope someone will help soon. |
|
it may be the long M503 response during boot, can anyone check if the issue is solved with #1468? |
|
Unfortunately the issue is still there, compiled with #1468 applied, reset the tft with reset.txt, applied new config.ini, reboot a couple of times with diferent settings, as well as hardcoded firmware settings, always the same result. |
|
The problem exists even if no printer is connected. |
|
Can confirm the issue and same experience. The only way for me to get the screen to operate again is by reloading a new config.ini as @radek8 mentioned above. Setting serial_always_on to 0 does fix the issue, but that's obviously not a solution. |
|
Does anyone know a build that worked? If yes, please share. |
|
Dunno. A working build might shed some light on it. |
|
Can you check if the issue exist with this commit 8632baa ? |
|
Commit 8632baa |
|
Found the cause. The serial connection was not getting initialized while booting in marlin mode after PR #1438. |
|
Thank you |
|
guruathwal I will just specify that the problems of "Click to Resume" and "damaged M105 command" occurred in Marlin mode, but also after starting in touch mode |
|
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 have two TFT35 E3 V3.0 and both after recent firmware upgrade started to behave problematically.
Reverting to 1bd1411 state helps.
Overall: display is used in touch mode - it is ok. But if it is in Marlin mode and printer boots with both EXP3 and 5pin TFT cables connected - once boot sequence is over and marlin starts drawing status screen (about 1/4th) the TFT freezes. it is impossible to change something or click something, impossible to change modes.
Steps to reproduce
Expected behavior
No freezes, correct drawing in Marlin mode.
Actual behavior
If booted with Marlin mode:
Custom boot screen shows, Marlin boot screen shows. Status screen starts to appear and display freezes.
Screen shows 1/4 of status screen, rest is from Marlin boot screen. No response on clicks.
If booted with Touch mode: it works 90% of times. Some times, after boot trying to initiate move commands from menu (e.g. Home), leads to screen freeze.
I tried to revert firmware to commit 1bd1411 It works without issues.
In addition: while printer is booting and tft in marlin mode, it is possible to switch to touch mode (before status screen appear).
However, most often that leads also to tft freeze once it establishes serial link to the board. Reseting and booting completely in touchscreen mode works.
Hardware Variant
TFT3.5 E3 V3.0
TFT Firmware Version & Main Board Firmware details
Marlin 2.0.7.2, bugfix-2.0.x same effect.
Additional Information
Configuration.hor use Pastebin and paste a link in this issue.The text was updated successfully, but these errors were encountered: