bigtreetech / TFT35-SPI

49 stars 9 forks source link

Blank screen when printing #2

Open thomasrtg opened 1 year ago

thomasrtg commented 1 year ago

Hi,

I received and setup my TFT35-SPI touchscreen on a CB1 V2.1. I also bought the IO2 Can as requested by BTT. When I turn on the printer and let it in idle, then screen works like a charm. However, if I start a print, at some point, the screen start to flicker and eventually "disconnect" itself from the printer and became white. The only way to turn it back on is to reboot the printer.

I did only use the ribbon cable included with the screen as I do not have a spare.

Does anyone have any suggestion to fix this issue ?

Conchulio commented 1 year ago

I have the same problem and would be happy about a solution

thomasrtg commented 1 year ago

I have the same problem and would be happy about a solution

Hi, I have not found any solution. Bigtreetech refund me 50% of the price but did not solve my problem

pl4nkt0n commented 1 year ago

Hello guys , seems i‘ve the same problem: The display is working but after some time it turns partially or full blank. I think this happens when klipperscreen switch to sleep mode. Normally you can wake up any display in this stage by just touching it. The touch of the TFT35 SPI is also still working, because if I push the place on the blanked screen where the emergency stop is, the printer will shut off. So only the screen itself is off and this can only be reset with a host reboot.

My System: CB1 V2.2 (without IO2 CAN) Image Version 2.3.2 Klipper V0.11.0.-248 Klipperscreen V0.3.3-10 Mainsail V2.5.1

IMG_6259 IMG_6258 IMG_6260

pl4nkt0n commented 1 year ago

Ok, I have the solution to my problem:

As described in the KlipperScreen documentation , for this display you will have to deactivate 'Screen DPMS' in the klipperscreen settings via display.

The tft35 spi is now working fine and stable.

01.08.2023 Have to correct my answer: The screen's still blanking after some time. with 'DPMS = off' it seems to be stable, but it is not.

Update 13.08.2023: It seems now to be stable. Even after KlipperScreen timeout the tft35 spi can wake up now. I just changed edited lines in the BoardEnv.cfg to this:

bootlogo=true overlay_prefix=sun50i-h616

'sun50i-h616-biqu-sd' for CB1, 'sun50i-h616-biqu-emmc' for CB1 eMMC version

fdtfile=sun50i-h616-biqu-sd

default 'display' for debug, 'serial' for /dev/ttyS0

console=display

uncomment for TFT35_SPI screen

overlays=tft35_spi

uncomment to release 'spidev1.2' to user space

uncomment overlays=spidev1_2 to release 'spidev1.2' to user space (For example: adxl345),

spidev1.0 is used by MCP2515, spidev1.1 is used by tft35_spi

overlays=spidev1_2

SEEMS there MUST BE "overlays=spidev1_2" OR "overlays=spidev1_1"

write the config after the 'overlays' and separate it with a space when multiple functions are enabled

overlays=disable_uart0 pwm ws2812 light tft35_spi mcp2515 spidev0_0 spidev1_0 spidev1_1 spidev1_2 ir

overlays=tft35_spi spidev1_2

SEEMS THERE MUST BE CALLED ALL ACTIVATED OVERLAYS, separated with spaces

------------------------------------------------

rootdev=UUID=680f8206-1a5c-4dd7-b39f-1229d5017302 rootfstype=ext4

freakydude commented 12 months ago

I had a similar problem.

So you have to deactivate the display DPMS by configure your power management manual. See Display_Power_Management_Signaling to get an idea. Deactivating DPMS manually "solved" the issue

or

You help look into KlipperScreen and help them fixing it ;-)