Customer:
I have three questions about my Inkplate 10.
Touchpad issue: The touchpads on my Inkplate 10 seem to be triggering by themselves. In the ‘wake from touchpad’ example code, the Inkplate wakes up as though somebody has put their finger on the touchpad, even though there are no fingers touching it. A subsequent call to display.readTouchpad(PAD2) returns TRUE. Originally this happened occasionally but now it has started to happen about 90% of the time. This is while running via USB-C 5v power. I have tried cleaning the touchpads with a dry cloth. Is it possible via software to change the threshold to make the touchpads less sensitive? Otherwise, does this mean there is a problem with my Inkplate and I need to return it?
Enclosure screws: The corner screws have all fallen out of my Inkplate 10 enclosure. The first thing that happened when I unpacked my new Inkplate 10 is that the 4 corner screws fell out of its enclosure. Even when I try to screw them back in, it is as though there is no thread for them to catch on, and they just rotate round and round without tightening. The two central screws seem fine. This is causing problems because I cannot properly tighten the enclosure. Can you please advise how to fix this? Are the screws not long enough, or do you think there has been a 3D printing error?
WROVER GPIO12: I noticed that one of the code samples for Deep Sleep has the comment:
// Uncomment this line if your Inkplate is older than Aug 2021 as older Inkplates have ESP32 wrover-e chips
// rtc_gpio_isolate(GPIO_NUM_12); // Isolate/disable GPIO12 on ESP32 (only to reduce power consumption in sleep)
I bought my Inkplate this month, but it does say ‘ESP-WROVER’ on the ESP chip. Should I be uncommenting this line?
Originally submitted via email support on 7 January 2022. Migrated to the forum for community visibility.
Soldered Support:
Touchpad issue: The touchpad driver we used does not have the possibility to change sensitivity by software. I will test them and try to find what can be a problem with it to have the wrong detection.
Soldered Support:
Enclosure screws: It seems like a 3D print error. If you wish we can send a new enclosure to you.
Attachment omitted in migration: src copy.zip
Soldered Support:
WROVER GPIO12: If you have Inkplate with ESP32-WROVER then you need to uncomment that line to reduce the current in deep sleep. If you use code with commented that line you will have bigger current consumption with ESP32-WROVER module.
Customer:
Thank you for your reply. In answer to the three points:
- That would be great, thanks, how long do you need to test? You will probably want to use the amended example code for touchpad wake up from this pull request: fixes touchpad wake examples by lanrat · Pull Request #121 · SolderedElectronics/Inkplate-Arduino-library · GitHub
I find that the Inkplate sometimes wakes up early from sleep, and then if you call display.readTouchpad(PAD2) it is equal to True.
I also attach my own source as a zip in case it’s useful. In my example:
- The Inkplate 10 connects to Wifi, displays a picture, then goes to deep sleep.
- It is supposed to stay asleep for 30 minutes, or until a touchpad event.
- It wakes up almost immediately on my device.
- After wake, the menu appears. Is it supposed to wait for touchpad inputs. (Pad 1 / Pad 3 move the menu up and down, Pad 2 acts as ‘OK’ button)
- However, it immediately registers an input from Pad2 as ‘OK’ and then downloads a new picture, and goes to sleep again.
-
Yes please, if you could send a replacement enclosure with working screws this would be much appreciated - my current one is not working well with the screws falling out.
-
Thank you for the advice re: WROVER, I shall do this.
Soldered Support:
We tested touchpads on Inkplate 10 and all working. I think that your Inkplate touch driver has been damaged and it reads touch constantly even when no finger. If you have the soldering iron you can try resoldering that IC, but if not you can’t do anything.