bigtreetech / BIGTREETECH-TouchScreenFirmware

support TFT35 V1.0/V1.1/V1.2/V2.0/V3.0, TFT28, TFT24 V1.1, TFT43, TFT50, TFT70
GNU General Public License v3.0
1.3k stars 1.65k forks source link

Update or not, that's the question it seems. #624

Closed oldman4U closed 4 years ago

oldman4U commented 4 years ago

I have an Ender3 Pro which works fine with a SKR E3 DIP, 2208 drivers and the standard TFT display. There is also a TFT35 E3 waiting to be installed.

Based on the many Bug reports related to the latest firmware, i ask myself if it is a good idea to change the display now, to wait until a more stable version becomes available, or maybe to use an older version, which has less features but which is more stable.

I believe we all agree when i say that new features are always welcome but they are useless in case they are full of bugs and even worse - brake other things which have been working fine before.

Your advice is highly appreciated.

Thank you

oldman4U commented 4 years ago

After spending some days with the TFT35 testing different versions of the firmware i can say that a touchscreen in general is much better than an LCD. The two BTT touchscreens i have work great, but it would be great to have a comparison chart describing the difference in functions, because size is just one factor. And there are some well documented hardware related differences, but also some not so well documented functions like the ability to dimm the display.

The firmware is still missing many functions and has many bugs, but in general firmware version x.x.26.1 seems to work well with the SKR Pro and the E3 DIP i use.

Conclusion for me without knowing many other solutions.

If you are willing to upgrade your printer from an LCD to a touchscreen - go for it. Based on the low price you have to pay for it, you have to spend a lot of time to make it work.

My personal favourite is the TFT35. Not because of the size but because of the speed and the other functions it offers for a little more. USB disk support and WIFI connection just to name two.

ssombra commented 4 years ago

In my opinion it also depends on your workflow. I usually print using Octoprint and, as far as I know, with some (most?) touchscreens you don't get current print information in the screen unless you send the print from the touchscreen itself. There are some workarounds like connecting the computer with octoprint (a Raspberry Pi in my case) directly to the touchscreen and not to the board, but then you have other issues like blobs (not fast enough). I decided to keep the touchscreen to control some things in the printer and because I like its functionality and look, but I also have a LCD connected.

oldman4U commented 4 years ago

Hello ssombra.

Thank you for your post. Octoprint is great for sure, but most users including me struggle to get a working solution using hardware from BTT and Marlin FW. Functionality wise it also offers 99% of the things you really need for a working solution. The problems are missing or bad communication, (outdated) documentation and way too much bugs in the FW. As a beginner it takes much too long to get the things done, especially when you really expect drag and drop replacement of existing parts - like advertised. I am willing to spend hours to find things out and to learn new things, but that's me and i can imagine that others are not like this and therefore give up before they reach their goal. Look at the many open tickets here, where the person who initiated the ticket simply does not answer any more. I believe that many of them gave up, where some do not know how to close it and some do not take care - for sure.

Happy printing;-)

ssombra commented 4 years ago

I agree with you, these solutions are not for everyone and they are definitely not drag and drop replacements. I also enjoy spending time making things work, for me it's a learning experience, and I have found a lot of support in forums, Facebook groups and here also. Take care

oldman4U commented 4 years ago

I close this ticket, because there are already too many tickets which makes it hard to find the really important and actively used tickets.

github-actions[bot] commented 6 months ago

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.