-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[P097] Updating code and (later) documentation #5165
base: mega
Are you sure you want to change the base?
Conversation
- added extra routine for esp32 s2 and s3 - added option to wake up the esp for supported devices (tested with s3) - added second value "state" for easier handling - failed epically to add a long press event because I am just a simple person, but left the remains for someone else to pick up And as always, please don't stone me. me and c++ are not going to be friends in this life anymore. :) If you agree to the changes i will update the documentatzion accordingly
That's why a |
- added and tested wakeup on ep32 classic
get the actual valuename
- added "toggle state" option (since I am not able to add a long press :) )
- added "long press" event - disabled "Single event with all values" since it is not working with the recent code (suggestions are welcome) but there is also the question if it is necessary
- make all touch pins available on s2/s3
- check if touchpad exists
- reverting T10_to_T14 support
Something still smells fishy with the touch inputs on my S3. When i add and then delete a "touch task" and then hit reboot i get quite often a "Guru Meditation Error" Edit: I'll do more testing to rule out other conditions...
|
Ok..it happens to other tasks too.. |
And what if you copy over the old code of this task to see if your changes made any difference? Does this happen on a SPIFFS build or also on a LittleFS build? (different SDK version) |
- type of threshold now dependent on model (uin32_t for s2 and s3) - max threshold value now also dependent on the type of esp
I tried this on a fresh esp32-s3 with a "normal" build to rule out that my changes have something to do with it.
SPIFFS... didn´t test it with LittleFS. The only usable option right now is |
@@ -124,7 +126,7 @@ boolean Plugin_097(uint8_t function, struct EventStruct *event, String& string) | |||
addFormCheckBox(F("Send Touch Event"), F("sendtouch"), P097_SEND_TOUCH_EVENT); | |||
addFormCheckBox(F("Send Release Event"), F("sendrelease"), P097_SEND_RELEASE_EVENT); | |||
addFormCheckBox(F("Send Duration Event"), F("sendduration"), P097_SEND_DURATION_EVENT); | |||
addFormNumericBox(F("Touch Threshold"), F("threshold"), P097_TOUCH_THRESHOLD, 0, P097_MAX_ADC_VALUE); | |||
addFormNumericBox(F("Touch Threshold"), F("threshold"), P097_TOUCH_THRESHOLD, 0, P097_MAX_THRESHOLD_VALUE); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This defined value is only defined for ESP32S2 and ESP32S3... Not sure why the name is changed?
- Hopefully fixed compile errors for non-touch ESP32 variants by standardizing the use of uint32_t for the threshold parameter on ESP32 Classic. The value remains limited by P097_MAX_THRESHOLD_VALUE to 4095.
failed epically to add a long press event because I am just a simple person, but left the remains for someone else to pick uppins 10 to 14 now available for ESP32 s2 and s3they still cause crashesAnd as always, please don't stone me. Me and c++ are not going to be friends in this life anymore. :)
If you agree to the changes i will update the documentation accordingly.