Guition ESP32-S3-4848S040 Display wakes-up randomly

[vampywiz17]

Perform all steps below and tick them with [x]

• Check the related part of the Documentation
• Update openHASP to the latest version
• Reproduce the issue and describe all steps

Describe the bug

To Reproduce

Install latest beta firmware 7.0 rc11 (Guition ESP32-S3-4848S040)

Expected behavior

The display can not wake up

Screenshots or video

Get this code on console, when the display are wake up:

#[22:50:34.205][98292/109668 10][25324/26056  3] HASP: First touch Disabled
#[22:50:34.219][94196/106476 11][25324/26056  3] MQTT PUB: backlight => {"state":"on","brightness":255}
#[22:50:34.231][90100/106488 15][25324/26056  3] MQTT PUB: idle => off
#[22:50:34.244][90100/104904 14][25324/26056  3] MSGR: File not found: L:/idle_off.cmd
#[22:50:34.272][98292/109556 10][25324/26056  3] MQTT RCV:  = backlight {"state": "on", "brightness": 255}
#[22:50:34.285][94196/107960 12][25324/26056  3] MSGR: backlight={"state": "on", "brightness": 255}
#[22:50:34.300][94196/107960 12][25324/26056  3] MQTT PUB: backlight => {"state":"on","brightness":255}

[vampywiz17]

hmm it does not depend on discovery...

I get this, if the display are wakeing up.

#[22:50:34.205][98292/109668 10][25324/26056  3] HASP: First touch Disabled
#[22:50:34.219][94196/106476 11][25324/26056  3] MQTT PUB: backlight => {"state":"on","brightness":255}
#[22:50:34.231][90100/106488 15][25324/26056  3] MQTT PUB: idle => off
#[22:50:34.244][90100/104904 14][25324/26056  3] MSGR: File not found: L:/idle_off.cmd
#[22:50:34.272][98292/109556 10][25324/26056  3] MQTT RCV:  = backlight {"state": "on", "brightness": 255}
#[22:50:34.285][94196/107960 12][25324/26056  3] MSGR: backlight={"state": "on", "brightness": 255}
#[22:50:34.300][94196/107960 12][25324/26056  3] MQTT PUB: backlight => {"state":"on","brightness":255}

Possible that some problem with touch panel?

[vampywiz17]

Strange thing... it only happen, if i power it my display via 230V... if i use USB type C port, the problem not happen more than one hour...

[smcgann99]

I have that screen running on 240V and do not see this problem, how often does it wake up ?

[vampywiz17]

@smcgann99

I did more test and seems maybe not the 230V the problem...

sometimes happen about 5-10 min, sometimes not happen hours... I dont understand... Seems happen more time, if for example the sun is shine directly to the screen... but it only just a idea...

[smcgann99]

This doesn't really sound like a bug to me.
Do you have the complete log prior to the screen idle off, perhaps something is being sent to the screen ?

[vampywiz17]

@smcgann99

Hello sorry the late answer.

Here:

#[20:08:00.000][102388/111876  8][25364/26012  3] MQTT RCV: p0b3.text = 20:08
#[20:08:59.990][102388/111876  8][25364/26012  3] MQTT RCV: p0b3.text = 20:09
#[20:09:38.479][98292/110356 10][25364/26012  3] MQTT PUB: statusupdate => {"node":"nappali_uj","idle":"long","version":"0.7.0-rc12","uptime":37576,"ssid":"iot_network","rssi":-63,"ip":"192.168.31.162","mac":"80:65:99:C8:8D:40","heapFree":111940,"heapFrag":8,"core":"4.4.6","canUpdate":"false","page":1,"numPages":12,"tftDriver":"Other","tftWidth":480,"tftHeight":480}
#[20:09:38.498][102388/111940  8][25364/26012  3] MQTT PUB: sensors => {"time":"2024-04-21T20:09:38","uptimeSec":37576,"uptime":"0T10:26:16"}
#[20:09:47.082][102388/111940  8][25364/26012  3] HASP: First touch Disabled
#[20:09:47.096][98292/108772  9][25364/26012  3] MQTT PUB: backlight => {"state":"on","brightness":255}
#[20:09:47.108][94196/108768 13][25364/26012  3] MQTT PUB: idle => off
#[20:09:47.121][94196/107184 12][25364/26012  3] MSGR: File not found: L:/idle_off.cmd
#[20:09:47.150][102388/111816  8][25364/26012  3] MQTT RCV:  = backlight {"state": "on", "brightness": 255}
#[20:09:47.163][98292/110228 10][25364/26012  3] MSGR: backlight={"state": "on", "brightness": 255}
#[20:09:47.178][98292/110228 10][25364/26012  3] MQTT PUB: backlight => {"state":"on","brightness":255}
#[20:09:59.989][102388/111876  8][25364/26012  3] MQTT RCV: p0b3.text = 20:10
#[20:10:04.515][98292/110356 10][25364/26012  3] MQTT PUB: discovery => {"node":"nappali_uj","mdl":"1-S3 4848S040","mf":"openHASP","hwid":"806599c88d40","pages":12,"sw":"0.7.0-rc12","node_t":"hasp/nappali_uj/","uri":"http://192.168.31.162","input":{},"power":[],"light":[40],"dim":[]}
#

Other one. I not see any special

#[20:20:59.988][102388/111876  8][25448/26020  3] MQTT RCV: p0b3.text = 20:21
#[20:21:08.632][102388/111940  8][25448/26020  3] HASP: First touch Disabled
#[20:21:08.646][98292/108772  9][25448/26020  3] MQTT PUB: backlight => {"state":"on","brightness":255}
#[20:21:08.658][94196/108768 13][25448/26020  3] MQTT PUB: idle => off
#[20:21:08.672][94196/107184 12][25448/26020  3] MSGR: File not found: L:/idle_off.cmd
#[20:21:08.697][102388/111816  8][25448/26020  3] MQTT RCV:  = backlight {"state": "on", "brightness": 255}
#[20:21:08.710][98292/110228 10][25448/26020  3] MSGR: backlight={"state": "on", "brightness": 255}
#[20:21:08.725][98292/110228 10][25448/26020  3] MQTT PUB: backlight => {"state":"on","brightness":255}
#

[smcgann99]

Well it doesn't look like anything is waking it via command, so it may just be a faulty screen / local interference ?

I haven't seen this issue with my screen.

[fvanroie]

This all sounds to me like electromagnetic interference on the device/microcontroller. Make sure all the needed signals have an appropriate pull-up/pull-down resistor. Fixing an issue that only occurs randomly is nearly impossible without knowing the root cause...

[fvanroie]

Is this problem resolved now?

[username-AL]

I have the same problem.
And also with the display 1-S3 4848S040. Sometimes it wakes up randomly and (it seems to me) it clicking in a random place.

Firmware: 0.7.0-rc12

[vampywiz17]

Is this problem resolved now?

not solved, unfortunately...

[smcgann99]

This sounds more like a hardware issue than a bug. e.g. the screen is registering a touch when there is none.

[fvanroie]

More troubleshooting is needed to determine the root-cause.

• Does it happen when you detach the screen from the PSU? Power it with a stable 5V power-supply and see what happens.
• Does this also happen with other firmware?
• Do you have multiple screens? Do they all have the same symptoms?

[vampywiz17]

More troubleshooting is needed to determine the root-cause.

• Does it happen when you detach the screen from the PSU? Power it with a stable 5V power-supply and see what happens.
• Does this also happen with other firmware?
• Do you have multiple screens? Do they all have the same symptoms?

@fvanroie

- Does it happen when you detach the screen from the PSU? Power it with a stable 5V power-supply and see what happens.

• Try with USB port, it also happen

- Does this also happen with other firmware?

• I try more RC firmware, it happen all of them

- Do you have multiple screens? Do they all have the same symptoms?

• Only one screen, but others are also affect it.

[fvanroie]

Thanks for your feedback. It really sounds like a hardware issue to me.
Maybe you can try other software like Tasmota, ESPhome, ... and see if that also have the problem.

Like stated before, without a way to replicate the random problem, it will be very hard to fix it.

[FreeBear-nc]

It might be that the touch driver chip is reacting to electrical noise and generating an interrupt. Been digging in to the GT911 programming notes, and I see a couple of config registers that can be set to filter out noise (and adjust the touch sensitivity). There are a couple of functions within the Arduino Goodix driver for the GT911 that read the config registers. Whilst there is a function call to set the resolution, there isn't one to adjust sensitivity.
It would only take a few lines of code to craft a suitable function, but the question is where within openHASP to put it (and when to call). Perhaps add something to the Configuration->Display screen in the web interface ?

[fvanroie]

The goodix repo is a fork which already has some openHASP tweaks.
So it is fine to add the settings function to the goodix driver repo.

Then, openHASP can simple call that function when initializing the driver.
At first, a simple test is needed to see if it actually works before thinking about UI changes.

[vampywiz17]

If you do this I glad to test it!

[FreeBear-nc]

Hacked a few lines of code to read the config registers inside the GT911 chip. In the process, learned a little... My trivial little hack causes openHASP to crash & burn with a panic. Not had time to work out why.

In the meantime, I do have a standalone utility that could be used to tweak the relevant register in the GT911 chip.

[smcgann99]

OK so it seems that my screen has developed this problem now ;-(
Recently noticed that devices were switching on randomly, and traced it to the screen registering a button press when there was none.

[FreeBear-nc]

Tried adding a short bit of code to openHASP to modify the relevant register in the GT911 chip during setup. Unfortunately, this addition triggered a panic and infinite reboots. As life is short, and using the JTAG interface to debug is impossible, I've put together a standalone "project" - https://github.com/FreeBear-nc/HA-openHASP/tree/main/GT911
Compile, upload, and then reload the openHASP firmware.

To adjust the noise sensitivity, edit the NR_LEVEL flag in the platformio.ini and recompile/upload - I would suggest 6 or 7 to start with.

[fvanroie]

Does this register fix the ghost touches?

[vampywiz17]

@fvanroie

I can not able to test it...

[vampywiz17]

@FreeBear-nc

3A is enough right?

[FreeBear-nc]

Depends on how big the load is you are switching. If you are switching LED lamps, 3A will be fine.

[vampywiz17]

@FreeBear-nc

I put before the display that we are talking about. Not to clear to me, that need to install it that i protect the noise, or that cause the noise...

[smcgann99]

@username-AL @TNTLarsn @vampywiz17 @FreeBear-nc

It might be useful to collect some more information.

1. Could you detail if you are using the onboard mains power supply or USB / other 5V
2. Have you applied the patch / new firmware build, if so at what setting e.g. 0-15
3. Did the patch solve the problem
4. Did all your screens originally exhibit the ghost touch behaviour or only some. i.e. can some screens work ok without patch.

[vampywiz17]

@username-AL @TNTLarsn @vampywiz17 @FreeBear-nc

It might be useful to collect some more information.

1. Could you detail if you are using the onboard mains power supply or USB / other 5V

2. Have you applied the patch / new firmware build, if so at what setting e.g. 0-15

3. Did the patch solve the problem

4. Did all your screens originally exhibit the ghost touch behaviour or only some. i.e. can some screens work ok without patch.

1. Try both. Problem only main power. With usb, set 10 are solve the problem

2. Applied. Try 5, 8 , 13 and 15

3. no

4. I have only one screen

[smcgann99]

@fvanroie I put message on discourse link back to here, not sure if you can do anything to pin / highlight it so its more visible.

[TNTLarsn]

@username-AL @TNTLarsn @vampywiz17 @FreeBear-nc

It might be useful to collect some more information.

1. Could you detail if you are using the onboard mains power supply or USB / other 5V
2. Have you applied the patch / new firmware build, if so at what setting e.g. 0-15
3. Did the patch solve the problem
4. Did all your screens originally exhibit the ghost touch behaviour or only some. i.e. can some screens work ok without patch.

1. All powered by mains 230V
2. yes setting 10
3. No, but less events than before
4. see screenshot. It seems that only 2 screens are affected

It could be that you have a particularly dirty (noisy) mains supply

I think so too

Real shame as they are nice cheap screens, but I cannot have it randomly switching things on and off ;-(

I've never had unexpected events that switches any buttons etc. on the screen.
It's only the backlight, which turns on and off repeatedly.
When I see that happen, it often helps to touch the display once and switch to another page. Most of the time the screen then stays off.

Overall the "events" were noticeably reduced with the new firmware.

[fvanroie]

How many screens do you have? If only 2 are affected, could you try to swap a good PSU with a bad PSU and see if the problem moves too? That way you can be sure the issue is in the PSU part and not the display part.

This might be a long shot, but what's that mains frequency? Probably it is 50Hz. The backlight is set to 100Hz, so maybe there is some interference... try setting the BACKLIGHT_FREQUENCY to something like 97, 103, 109, 113, 127, 131 or 139.

[FreeBear-nc]

It might be useful to collect some more information.

1. Could you detail if you are using the onboard mains power supply or USB / other 5V
2. Have you applied the patch / new firmware build, if so at what setting e.g. 0-15
3. Did the patch solve the problem
4. Did all your screens originally exhibit the ghost touch behaviour or only some. i.e. can some screens work ok without patch.

1. Got two. One mains powered, the other via USB (used for test & development).
2. Had been running the default 5 noise reduction on the mains powered plate and had a couple of phantom touches.
3. The mains powered one has been running at NR=7 for a couple of days, no phantom events yet.
4. Only the mains powered plate has registered any phantom events, and only a handful over the last couple of months. Too early to say if the patch cures it.

Judging by feedback garnered here, the patch does help to reduce the number of phantom events. Uploaded a new firmware build with a 110Hz backlight frequency.

[smcgann99]

I have two on my desk powered by same mains socket.
One is running standard 0.7.0-rc14 bb8d24d firmware and the other @FreeBear-nc version set to 15.
Stock firmware no events in the last 8 hours, modified firmware around 40 events.

I and others have had ghost events even with the USB power, but it seems less of an issue, indeed if I swap the problem screen back to USB the issues seems to stop with a higher setting 7+

I never noticed this issue when I first got the screen and was using it for development, so perhaps something is failing over time ?

[FreeBear-nc]

I never noticed this issue when I first got the screen and was using it for development, so perhaps something is failing over time ?

Just picked up the main power board for the plate I'm using for test & development... One of the capacitors on the switch mode PSU module is rattling around loose. Going to have to remove the module somehow and solder that capacitor down.

[smcgann99]

I power cycled the bad screen a hour ago and no events yet. Before it was averaging 4-5 an hour.
This is something I noticed before, will see how long it takes for ghost events to come back.

[vampywiz17]

It might be useful to collect some more information.

1. Could you detail if you are using the onboard mains power supply or USB / other 5V
2. Have you applied the patch / new firmware build, if so at what setting e.g. 0-15
3. Did the patch solve the problem
4. Did all your screens originally exhibit the ghost touch behaviour or only some. i.e. can some screens work ok without patch.

1. Got two. One mains powered, the other via USB (used for test & development).
2. Had been running the default 5 noise reduction on the mains powered plate and had a couple of phantom touches.
3. The mains powered one has been running at NR=7 for a couple of days, no phantom events yet.
4. Only the mains powered plate has registered any phantom events, and only a handful over the last couple of months. Too early to say if the patch cures it.

Judging by feedback garnered here, the patch does help to reduce the number of phantom events. Uploaded a new firmware build with a 110Hz backlight frequency.

I try 110Hz firmware, but the problem are also happen.

[smcgann99]

For info after power cycle at 00:00 I have only had 2 false events so far -

07/09/24 05:50:57 LCD:1 btn:p1b51
07/09/24 07:05:45 LCD:1 btn:p0b21

Where yesterday, before power cycle I got all these -

06/09/24 15:39:51 LCD:1 btn:p0b21
06/09/24 15:45:44 LCD:1 btn:p1b51
06/09/24 16:03:13 LCD:1 btn:p1b2
06/09/24 16:17:11 LCD:1 btn:p1b51
06/09/24 16:40:50 LCD:1 btn:p1b51
06/09/24 17:03:30 LCD:1 btn:p1b5
06/09/24 17:03:30 LCD:1 btn:p1b5
06/09/24 17:04:45 LCD:1 btn:p1b5
06/09/24 17:21:45 LCD:1 btn:p0b21
06/09/24 17:26:36 LCD:1 btn:p0b21
06/09/24 17:26:45 LCD:1 btn:p0b21
06/09/24 18:29:19 LCD:1 btn:p0b30
06/09/24 18:30:58 LCD:1 btn:p0b30
06/09/24 18:31:14 LCD:1 btn:p0b21
06/09/24 18:31:39 LCD:1 btn:p0b30
06/09/24 18:32:10 LCD:1 btn:p0b30
06/09/24 18:35:41 LCD:1 btn:p0b30
06/09/24 18:38:21 LCD:1 btn:p0b21
06/09/24 18:43:48 LCD:1 btn:p0b30
06/09/24 18:50:38 LCD:1 btn:p0b30
06/09/24 18:53:51 LCD:1 btn:p0b30
06/09/24 18:59:09 LCD:1 btn:p0b30
06/09/24 19:05:17 LCD:1 btn:p0b30
06/09/24 19:07:55 LCD:1 btn:p0b30
06/09/24 19:15:26 LCD:1 btn:p0b30
06/09/24 19:44:45 LCD:1 btn:p1b51
06/09/24 20:00:20 LCD:1 btn:p1b6
06/09/24 20:15:47 LCD:1 btn:p1b51
06/09/24 20:26:07 LCD:1 btn:p1b6
06/09/24 20:56:49 LCD:1 btn:p1b6
06/09/24 21:14:29 LCD:1 btn:p1b5
06/09/24 21:20:11 LCD:1 btn:p1b5
06/09/24 21:32:31 LCD:1 btn:p1b51
06/09/24 21:53:47 LCD:1 btn:p1b5
06/09/24 22:06:21 LCD:1 btn:p1b51
06/09/24 22:14:38 LCD:1 btn:p1b6
06/09/24 22:24:51 LCD:1 btn:p1b5
06/09/24 22:34:33 LCD:1 btn:p1b51
06/09/24 23:17:33 LCD:1 btn:p1b6
06/09/24 23:29:38 LCD:1 btn:p1b2
06/09/24 23:38:25 LCD:1 btn:p0b42
06/09/24 23:48:56 LCD:1 btn:p1b51
07/09/24 00:02:11 LCD:1 btn:p1b16

Still no events from the new screen on stock firmware.

[smcgann99]

I never noticed this issue when I first got the screen and was using it for development, so perhaps something is failing over time ?

Just picked up the main power board for the plate I'm using for test & development... One of the capacitors on the switch mode PSU module is rattling around loose. Going to have to remove the module somehow and solder that capacitor down.

Did you find a problem with the PSU ?

[FreeBear-nc]

Did you find a problem with the PSU ?

Yes. One of the electrolytic capacitors finally fell off the PSU module - A pain in the b... to solder back in place as there is a relay in the way. Getting the module off the main PCB wasn't easy.
But I have only ever used this particular device on the bench powered via USB.

I did note that it is possible to remove R5 & R6 (both zero ohm links) and insert a suitable small common mode inductor in the space labeled L4. Something like this: https://www.aliexpress.com/item/1005006624953914.html
That may help to filter out any mains borne noise.

[smcgann99]

Update, I swapped over the PSUs between my two screens, and neither screen caused any ghost touches.
Swapped them back to original after around 3 days. STILL no ghost touches!
After 7 days bad screen started with ghost touches again.
Swapped again and now "bad" PSU red LED lights up but screen doesn't power up (works fine on USB)
Noticed that the smaller capacitor looks a little bit suspect (like there is too much black plastic showing at the bottom of the can.
Will do some tests on PSU and swap capacitor.

[smcgann99]

@FreeBear-nc
I replaced the 330uF capacitor with a new one and screen now boots, will monitor over next days for ghost events.
Have you found anything interesting with your screens / PSUs ?

[FreeBear-nc]

Found the 330uF capacitor fell out when poked (bad solder joint). But this particular board sits on the bench powered by USB when (if) I'm testing code.
Next time the power is off, I'll take a look at the Guition that is currently screwed to the wall - I've only had a handful of phantom touches on that board, and nothing since setting noise reduction to 7 (was originally 5).

[smcgann99]

No issues in the last 7 days since changing the 330uF capacitor .....

[FreeBear-nc]

No issues in the last 7 days since changing the 330uF capacitor .....

Starting to sound like a power supply problem.
I noted some of the reviews left on Aliexpress commented about the poor quality of construction. I have a dodgy unit here which would appear to support the opinion that Guition has quality control issues.

If you haven't already tried it, drop noise reduction back down to 5 and see if you get any more phantom touch events.

[smcgann99]

I only had your fix on one unit, which I did set to 5 the other has stock firmware.

Sounds like a batch issue perhaps ?

[vampywiz17]

No issues in the last 7 days since changing the 330uF capacitor .....

You able to make a pic what capacitor are replace it?

[FreeBear-nc]

No issues in the last 7 days since changing the 330uF capacitor .....

You able to make a pic what capacitor are replace it?

It will be the top left one on the PSU board. While you have access to the rear of the module, it is a good idea to check the other capacitor is properly soldered in.

[fvanroie]

Some interesting remarks regarding to the power-supply and upgrades can be found here:
https://michiel.vanderwulp.be/domotica/Modules/SmartDisplay-ESP32-S3-4.0inch/power-supply/#safety-capacitor

[smcgann99]

@fvanroie Interesting read and a useful site in general.
@FreeBear-nc You fitted the inductor yourself ?

[vampywiz17]

@FreeBear-nc
@fvanroie

I took it apart my device and not only C1 and R4 but L4 is also missing.... (a toroidal transformer maybe...)

[vampywiz17]

Somebody able to measure the L4 part? i would like to build it, but it would be good the details.

[FreeBear-nc]

One of my boards has L4, the other doesn't. Don't have an inductance meter so can't measure the value.
I just ordered a few common mode toroidal chokes (3.3mH) on a suck it & see basis. Not able to comment on the effectiveness as this one spends most of the time on the bench powered by USB.
For reference, I bought these: https://www.aliexpress.com/item/1005006620588493.html

None of my boards have C1 or R4 fitted...

[smcgann99]

@vampywiz17 Did you swap the 330uf capacitor, that fixed my issues ?