[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
I have an issue with the ESP32S3 Touch sensor Delay after finishing the required number of cycles (FSM started by Hardware timer)
We know that The touch sensor will measure time of a fixed number of charge/discharge cycles (specified as the second parameter).
Even when meas_time in touch_pad_set_meas_time(sleep_cycle, meas_times) the next measurement start after approximately 140 us have passed after finishing the required number of cycles. please check a picture where I set the number of cycles to a 100. Why is this behavior's ? I checked the esp-idf guide and esp32s3 TRM and couldn't find an answer.
@5ami Because the touch sensor channels use a polling measurement, if you enable multiple channels, this time will first sleep for a while (sleep_cycle) and then switch to the next channel
Answers checklist.
General issue report
I have an issue with the ESP32S3 Touch sensor Delay after finishing the required number of cycles (FSM started by Hardware timer)
We know that The touch sensor will measure time of a fixed number of charge/discharge cycles (specified as the second parameter).
Even when meas_time in touch_pad_set_meas_time(sleep_cycle, meas_times) the next measurement start after approximately 140 us have passed after finishing the required number of cycles. please check a picture where I set the number of cycles to a 100. Why is this behavior's ? I checked the esp-idf guide and esp32s3 TRM and couldn't find an answer.