Touch works right - Making full class with events support about lilygo-epd47 HOT 10 CLOSED

1. I can't add more functions to the touch, because the supplier only provides me with a simple sample program, and did not give me a data manual. I asked them for it, but they did not provide it.
2. I have tested it and it will not fail to read
3. I can provide you with the sample program that the supplier gave me to facilitate your research, but it is not helpful to me.

5_5_Touch.zip
L58数据手册V1.0.pdf

from lilygo-epd47.

I understand. But to implement touch you need at least press down and lift up events.
Without that is completely useless. Because otherwise there is no real press of a button.
you press and hold, then you repeat same button press multiple times.
I’m sorry but if this L58 has not that then it was simply a poor choice for a touch controller. I will try to translate the PDF and sniff all that comes per I2C but as a consumer I shouldn’t need to reverse engineer your products to get them running.
In the code I see just X and Y returning via I2C. If this is really the touch controller for a mobile screen it should have events, they need to be somewhere . Thanks for your time

from lilygo-epd47.

I feel helpless ! This is not my choice.

from lilygo-epd47.

It's no problem, I just want to help, so maybe we can get the events somehow. But if we can not then at least this should be in the product description explained. Otherwise it can make other developers helpless too ;(

from lilygo-epd47.

Updated my touch examples and the wiki. Added “tap simulation” with a timeout. Still does not work 100% correctly like having press and lift up evens but is more usable:
https://github.com/martinberlin/cale-idf/wiki/Model-parallel-ED047TC1.h#touch-research

@lewisxhe I will sniff the I2C and try to discover if has events. But next time if the provider is not able to deliver proper documentation/examples then its simply not a good choice even if the price quality is great (looking at least). I know it was not your choice but at least who decides this should now!

from lilygo-epd47.

I have explained the problem to LilyGo, and the touch panel should be replaced later. Thank you for your contribution.

from lilygo-epd47.

Waiting for another panel since mine is broken. Lilygo sent me a proposed solution so when it arrives I will test it and document it here. It seems that comes at least a press down /lift up event.
Added it here in my component but I need to wait to test it:
martinberlin/cale-idf@fbf6371

Thanks Lewis for the follow ups!

from lilygo-epd47.

@martinberlin unfortunately this sort of poor component choosing is not unique to LilyGO. I see this in almost every custom design developer kit coming from China. Well tested components and systems are often canned for undocumented, "cheaper" counterparts, most of the time for no good reason.

For example, the M5Paper (M5Stack's version of the EPD47) has a bunch of questionable choices. The EPD is driven by an IT8951, an SPI-connected microcontroller (with lots of great capabilities, by the way!), which ends up saving a few pins only to cause a permanent 100-130mA drain when on. The AXP192 PMU is replaced with a lesser controller that has much less documentation, and can't even report events like charger connected, or charging complete. And one could go on.

To me, both of these boards seem like they were put together by a handful of teams with little to no communication with each other, often the solution just getting "slapped on", with little regards to compatibility with the rest of the system.

And then we end up with devices that look good on paper, but have fatal design flaws, issues that cannot be fixed in software. I for one would rather have a good hardware design that is a bit more expensive and has little software support initially, than to have a device that cannot be fixed due to faulty hardware.

from lilygo-epd47.

I agree on your points. But I must say that this epaper proves to be quite nice, both in resolution, price and quality. I like it so far.
I'm still waiting for my new touch.
One point I dislike: This touch FPC connectors on the PCB are not the best quality. I understand you are not supposed to plug in and out the touch many times, but mine broke after just a few times. And when this tiny things brake it's impossible to repair.

The issue is that once you stick the touch, if it brakes the connector, you have a half usable epaper.
I will update this when the touch arrives and I still have to confirm if it delivers press/release events that are necessary to detect the "TAP" event. Without that is very hard to make an usable button ;)
And I will additionally make a supplement that can be 3D printed, to place the touch flat cable, in a position that is harder to brake.

from lilygo-epd47.

@lewisxhe touch is now updated and supporting events in Cale-idf epaper component and my ESP-IDF component also:
https://github.com/martinberlin/FT6X36-IDF Supports L58 touch.

Proof-of-concept video: https://twitter.com/martinfasani/status/1384244324922105864

from lilygo-epd47.