Closed sinole1987 closed 3 years ago
Kowing that there is an issue, what Is the difference to the other tickets?
I also have the same issue. Have you compiled your own Marlin fw for your board or do you use the precompiled firmware?
The screen freezes or you get the same popup again?
Kowing that there is an issue, what Is the difference to the other tickets?
the difference is screen freezing that didn't happen before. before it was just an error loop.
Maybe this would make sense to add to the already open ticket?
ok I will, it is a year old ticket, but sure. and I didn't compile my own firmware. I can do some programing, but if I was proficient enough, I would have just made the code ignore the screen filament sensor and read the onboard one. it seems that feature is messing up the whole code. Can we have a firmware that works only with onboard filament sensor.
I started VSC for the first time 1.5 years ago without any background in sw development. It is where the fun starts and compiling your own firmware is mandatory for being able to use BTT hardware.
sinole1987 notifications@github.com schrieb am Do. 28. Jän. 2021 um 17:44:
ok I will, it is a year old ticket, but sure. and I didn't compile my own firmware. I can do some programing, but if I was proficient enough, I would have just made the code ignore the screen filament sensor and read the onboard one. it seems that feature is messing up the whole code. Can we have a firmware that works only with onboard filament sensor.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/1571#issuecomment-769216115, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM6XKZF5Y65PD5PADHLPJ5LS4GH6JANCNFSM4WUNMA2Q .
yes, i think at some point I will do that. i think marlin is still not very compatible with tft yet.
I started VSC for the first time 1.5 years ago without any background in sw development. It is where the fun starts and compiling your own firmware is mandatory for being able to use BTT hardware. sinole1987 notifications@github.com schrieb am Do. 28. Jän. 2021 um 17:44: … ok I will, it is a year old ticket, but sure. and I didn't compile my own firmware. I can do some programing, but if I was proficient enough, I would have just made the code ignore the screen filament sensor and read the onboard one. it seems that feature is messing up the whole code. Can we have a firmware that works only with onboard filament sensor. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1571 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM6XKZF5Y65PD5PADHLPJ5LS4GH6JANCNFSM4WUNMA2Q .
I've come to that point as well. I need to learn how to compile my own fw. Otherwise most of the problems I've seen will be unsolved because our printers are different. A common way can not be found. I will invest on myselft this weekend :)
Keep in mind how many different hardware devices are available and this only includes no optional devices like filament runout and levelling items- This alone would end up in hundreds if not thousands of different combinations and therefore firmware versions. Some users have problems to find the right firmware for their TFT, even there are 3 handful of files to choose from. In case you want more than A4988, 1 extruder and a heated bed, you have to compile by yourself.
@sinole1987
Could you please try this firmware to see if it solves the issue: https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/tree/1eb47368ea26ee08b69ca7668ac8d4b55b0409e4
@kisslorand The reported issue is related to your PR as the release right before your PR (see link above) does not have the issue: ExtrusionMenu-Load/UnLoadToMoreMenu #1466
Thank you
yeh i can make basic, firmware or change a thing or two on the firmware, but not really edit subroutines and stuff. but i will try this version and let you know soon.
There is nothing you have to change because the precompiled version already does the job.
It doesnt freez anymore, but still loop until I use the knob to control the massage in marlin. thank you. this is better than freezing.
You mean when you pause the print?
The issue exists also without pausing a print. It is enough to preheat the nozzle and to try to Load filament. This freezes or crashes the screen.
yes, its all related to M0 M1 commands not working on TFT mode. when you press load I think it sends the paus command to the printer.
sinole1987
You have to enable HOST_PROMPT_SUPPORT in Marlin configuration.adv to get the correct buttons (Purge More and Continue).
oh yes thank you. and I installed the firmware updated 2 days ago, seems be working fine. do still need to connect filament sensor to the screen as well if I want to have filament runout in TFT mode?
sinole1987 and sarvenn
Can you both purge filament using Menu-(Un)Load more than once?
So Preheat the nozzle. Once heated go to Menu (Un)Load. Press "Load" and once you get the PurgeMore or Continue button press PurgeMore. What happens, and which mainboards do you have?
ye purge more has issues for sure in new version, but if you go to marlin and come back everything is fine. does the version you send me work fine ? or same problems? i have SKR 1.4 turbo.
The version I sent has Extrude instead of (Un)Load which works for me.
Finally I was able to reproduce this bug. It's very hard to trace the issue, I have to play 20~30 minutes to have the hiccup once on my printer. So far I saw that the TFT is the culprit, it's not frozen but waits buttons from another menu that is displayed. I am monitoring the serial on both sides, motherboard and TFT, so far I didn't see any issue on any side.
Later edit: I was on a wrong track, it is not about menus. I might have a possible fix, check PR #1607.
I have a several hours print going on on my machine, but I believe there could be a Marlin fix for the crash we see when the Purge More button is pressed. Here is the version which includes probably the fix for those who would like to check:
I kinda noticed that it might be a marlin issue reading all of the different threads and reviewing the code.
Could someone please try kisslorand's possible fix: https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/pull/1607
I will be able to test it in a few hours.
What I know so far is, that it affects STM32 (E3 mini, E3 DIP, Pro v1.x) boards but not LPC based motherboards (SKR v1.x) and that the problem always existed (tested firmware back to November last year). The problem became more obvious the time kisslorand moved the (Un)Load to the main screen, replacing the Extrude menu which does not have this problem.
tested it doesn't work on LPC platform.
Well, the way lpc motherboards connect for marlin mode is different from mini baords. we need two cables, since this is a communication issue. it makes sense. the pin mapping is wrong on the program. again I wish I could trace it myself.
Which LPC based board have you tested and what is the problem exactly?
I thought the same first but why do I see the same issue using the SKR Pro v.1.1 which uses EXP 1 and 2?
LPC 1769, and you are on track. All of these motherboards use EXP1 and 2, I am assuming the fix works on motherboards that use EXP3.
Initially I also believed it has to do with the EXP connection. But the SKR PRO destroyed this.
sinole1987 notifications@github.com schrieb am Do. 11. Feb. 2021 um 01:47:
LPC 1769, and you are on track. All of these motherboards use EXP1 and 2, I am assuming the fix works on motherboards that use EXP3.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/bigtreetech/BIGTREETECH-TouchScreenFirmware/issues/1571#issuecomment-777138878, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM6XKZGKIGY5UIEYP54OOCLS6MSI7ANCNFSM4WUNMA2Q .
I am actually happy with the filament detect sensor right now, you don't really need load button. only problem is that nozzle goes on top of the print and dumps a blub of plastic before continuing the print. if it does the dump on the bed and then goes to print its gonna be perfect. should that be arranged on tft firmware?
All users can use the Extrude menu instead of (Un)Load without any problem as it does not use M701. Users with STM32 based mainboards can not use (Un)Load because it will crash the mainboard. This crash is not TFT firmware related and can be reproduced also without a TFT.
The issue is likely fixed thanks to user arjanmels
https://github.com/MarlinFirmware/Marlin/pull/21210
Please update Marlin to see if it solves the problem.
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.
So I know that there are previous posts about how M0,M1 doesn't work on TFT screen. I have updated my screen firmware recently, but I still have issues with loading filament. this time issue is worst. It used to be that screen fell into a error loop. now it freezes altogether.
and then pop up apears. "printer paused" " waiting for user to respond" 5.press ok
then screen freezes
Hardware Variant
using a SKR 1.4 turbo TFT 43 connected through both marlin and serial port