Good morning, Everyone,
Flowing up on an example that is on the wiki "DisplayManagerDemo" which works In Simulation. (Touch responded in simulation)
However, I recreated that same project using 4-wire resistive touch screen "ili9488" with esp32 S3 Wroomer.
I not getting any response on the touch 4-wire touch (and not in the simulation as well).
I have "touch" example ONLY that work with ili9488 with the same configuration. that I have now. I tested and it work.
When doing it with the "DisplayManagerDemo". Not touching. What am I doing wrong?
I need help with solving the issues. Please and thanks to everyone. I have my example below.
regards
ryan
DisplayManagerDemo_ili9488
-
- Posts: 74
- http://meble-kuchenne.info.pl
- Joined: Thu Jun 16, 2022 6:16 pm
- Has thanked: 116 times
- Been thanked: 13 times
DisplayManagerDemo_ili9488
- Attachments
-
- DisplayManagerDemo_esP32_s3.fcfx
- (48.52 KiB) Downloaded 269 times
-
- Matrix Staff
- Posts: 1936
- Joined: Mon Dec 07, 2020 10:06 am
- Has thanked: 506 times
- Been thanked: 688 times
Re: DisplayManagerDemo_ili9488
Hi Ryan,
In the properties of the touch component you didn't have the GLCD linked. this would stop the simulation touches from working.
With it linked it's now simulating correctly.
In the properties of the touch component you didn't have the GLCD linked. this would stop the simulation touches from working.
With it linked it's now simulating correctly.
Regards Ben Rowland - MatrixTSL
Flowcode Online Code Viewer (Beta) - Flowcode Product Page - Flowcode Help Wiki - My YouTube Channel
Flowcode Online Code Viewer (Beta) - Flowcode Product Page - Flowcode Help Wiki - My YouTube Channel
-
- Posts: 74
- Joined: Thu Jun 16, 2022 6:16 pm
- Has thanked: 116 times
- Been thanked: 13 times
Re: DisplayManagerDemo_ili9488
hi BenR,
Thanks for pointing it out to me. (It's working now). I was looking for it, but didn't saw it.
There's more problem.
>> I enable Queue fast Pixel (yes) as it allows the display to go faster. But he displays is not moving Faster anymore after I updated the library not too long ago.
>>From the Original example "DisplayManagerDemo" its Flip XY is Yes.
This is how I would like my display to work Flip X yes, Flip Y no.
However, on the other hand, the physical touch on the display remains at a fixed position on the screen. when it has been touched "BUT WORKING"
I tried playing with the Physical Orientation (0-3), I increment and decrement the X, .Ycrood. But it remains the same.
I thought once the touch is enabled, anywhere on the screen will be available to touch. Its only Works where the blue area is)
I am not sure what else to do at the moment. (I need some suggestions on how to get it to work).?
I attached an image of it.
regards
ryan.
Thanks for pointing it out to me. (It's working now). I was looking for it, but didn't saw it.
There's more problem.
>> I enable Queue fast Pixel (yes) as it allows the display to go faster. But he displays is not moving Faster anymore after I updated the library not too long ago.
>>From the Original example "DisplayManagerDemo" its Flip XY is Yes.
This is how I would like my display to work Flip X yes, Flip Y no.
However, on the other hand, the physical touch on the display remains at a fixed position on the screen. when it has been touched "BUT WORKING"
I tried playing with the Physical Orientation (0-3), I increment and decrement the X, .Ycrood. But it remains the same.
I thought once the touch is enabled, anywhere on the screen will be available to touch. Its only Works where the blue area is)
I am not sure what else to do at the moment. (I need some suggestions on how to get it to work).?
I attached an image of it.
regards
ryan.
- Attachments
-
- 20240807_114400.jpg (59.15 KiB) Viewed 5993 times
-
- Matrix Staff
- Posts: 1936
- Joined: Mon Dec 07, 2020 10:06 am
- Has thanked: 506 times
- Been thanked: 688 times
Re: DisplayManagerDemo_ili9488
It looks like the X/Y coordinates from the touchscreen need scaling up to correctly match the pixels on the display, maybe try multiplying the X/Y coordinates you get from the touchscreen component. Maybe * 3 or *4.
Regards Ben Rowland - MatrixTSL
Flowcode Online Code Viewer (Beta) - Flowcode Product Page - Flowcode Help Wiki - My YouTube Channel
Flowcode Online Code Viewer (Beta) - Flowcode Product Page - Flowcode Help Wiki - My YouTube Channel
-
- Posts: 74
- Joined: Thu Jun 16, 2022 6:16 pm
- Has thanked: 116 times
- Been thanked: 13 times
Scaling UP ili9488 Display
Hi
Goodmorning to everyone,
I Need Assistance at the moment and value Your Support.
There was a simple example on the Wiki that demonstrates how you would you use capacitive touched with buttons on screen, to navigate to different, different screens on the touched display. I took it down and recreated that example it with my Esp32 S3 using Resistive touch
and the XPT2046. It works fine in simulation shows the Button ID etc. It also works fine.
(I had some resistive touch screen laying down). The Touch Screens are GOOD.
I see examples of the XPT2046 with touch screens. but there's no button pressed on the examples.
I recently revisited this project a week ago, I was looking at it from last year. I have time now, so now I got the CONCEPT of how to add buttons to the screen and can navigate around on different, different screens base on the options I choose. What I don't know is how to scale up my display for it to touch properly. ""I am only getting touch at "ONE" little area."" Close to the Pin Headers of the Touch Screen
In the simulation mode I used "BUTTON 2" to go to the "Color Options" that is what I want it to do.
But on my board, Button 1 does that and not button 2.
I then went back in simulation and used "Button 4" to go to "Color Options" and it work (SIMULATION)
But on my board Button 1 still goes to the color options.
That clearly means my display as not been scale up.
I can't seem to get mine to work. Is something differently wrong or missing?
Does anybody else as this problem?
How can I get mine to work?
Here's a short video of the demonstration.
https://youtube.com/shorts/sUgw4PqJhhM
I also attached my File as well Regards
Ryan
Goodmorning to everyone,
I Need Assistance at the moment and value Your Support.
There was a simple example on the Wiki that demonstrates how you would you use capacitive touched with buttons on screen, to navigate to different, different screens on the touched display. I took it down and recreated that example it with my Esp32 S3 using Resistive touch
and the XPT2046. It works fine in simulation shows the Button ID etc. It also works fine.
(I had some resistive touch screen laying down). The Touch Screens are GOOD.
I see examples of the XPT2046 with touch screens. but there's no button pressed on the examples.
I recently revisited this project a week ago, I was looking at it from last year. I have time now, so now I got the CONCEPT of how to add buttons to the screen and can navigate around on different, different screens base on the options I choose. What I don't know is how to scale up my display for it to touch properly. ""I am only getting touch at "ONE" little area."" Close to the Pin Headers of the Touch Screen
In the simulation mode I used "BUTTON 2" to go to the "Color Options" that is what I want it to do.
But on my board, Button 1 does that and not button 2.
I then went back in simulation and used "Button 4" to go to "Color Options" and it work (SIMULATION)
But on my board Button 1 still goes to the color options.
That clearly means my display as not been scale up.
I can't seem to get mine to work. Is something differently wrong or missing?
Does anybody else as this problem?
How can I get mine to work?
Here's a short video of the demonstration.
https://youtube.com/shorts/sUgw4PqJhhM
I also attached my File as well Regards
Ryan
-
- Matrix Staff
- Posts: 1956
- Joined: Wed Dec 02, 2020 11:07 pm
- Has thanked: 626 times
- Been thanked: 657 times
Re: DisplayManagerDemo_ili9488
Hello.
I have made an improvement to the XPT2046 resistive touch sensor.
Instead of returning either 0 or 1, it now returns the pressure value.
Therefore, within the decision branch, you can use for example.
All false touches will then be ignored.
The component will be pushed to the update system ASAP
I have made an improvement to the XPT2046 resistive touch sensor.
Instead of returning either 0 or 1, it now returns the pressure value.
Therefore, within the decision branch, you can use
Code: Select all
If Touch >10
All false touches will then be ignored.
The component will be pushed to the update system ASAP
Martin
-
- Posts: 74
- Joined: Thu Jun 16, 2022 6:16 pm
- Has thanked: 116 times
- Been thanked: 13 times
Re: DisplayManagerDemo_ili9488
Hi
Thanks, that is very ingenious of you.
.
After adding that little part to my program yesterday. It shows me that new touch screens (that never used) are defective.
Brilliant idea, YOU GUYS ARE DOING A GREAT JOB.
I will check it and let you know how it goes, when I have the time.
Regards
Thanks, that is very ingenious of you.


After adding that little part to my program yesterday. It shows me that new touch screens (that never used) are defective.
Brilliant idea, YOU GUYS ARE DOING A GREAT JOB.
I will check it and let you know how it goes, when I have the time.
Regards
-
- Posts: 74
- Joined: Thu Jun 16, 2022 6:16 pm
- Has thanked: 116 times
- Been thanked: 13 times
Re: DisplayManagerDemo_ili9488
Hi
Thanks very much for your HELP and your ingenious idea with the XPT2046.
Both Blend and work very well.
I can now, navigate between both options on my board.
Regards
Thanks very much for your HELP and your ingenious idea with the XPT2046.
Both Blend and work very well.


I can now, navigate between both options on my board.
Regards