Even though there is no sensor configured, the chip will be waken up by WDT periodically. That is the reason why the average current is 9uA in this condition.
The resolution(bits) of proximity sensor is higher than CapSense buttons in most conditions. The higher the resolution is, the more scanning/active time will be(1-bit higher, double the time will be), which will lead to more power consumption. That is the main reason why 1 proximity sensor consumes much more current than 1 button.
Recommend to use as low resolution as it can be in your design. Of course 5:1 SNR(or higher) should be guaranteed.
Increasing the scan period will help on reducing average current also.
In addition, you can refer to AN85951 or MBR Design guide for more details.
"The higher the resolution is, the more scanning/active time will be(1-bit higher, double the time will be), which will lead to more power consumption."
I have verified the scanning time by changing the resolution of proxy sensor but there is no any difference in active time, its remain same 6ms.
Can we reduce current consumption by changing scanning/Active time of proxy sensor?
"1-bit higher, double the time will be" - Can you explain more on that?
Whats the scanning/Active time should be if we use proxy sensor(CS0/PS0) and button in our application?
Please find the attached screen shot of configuration. (EZ-Click)
How did you get the 6ms? You can measure the waveform on the proximity sensor. Its scanning time will be narrow dwon if you use smaller resolution.
The scanning time is related with sense clock divider, resolution and some other paras. In sleep mode, only proximity sensor will scan periodically if no touch and it is set as wake-up sensor. An easy way to get the scanning/active time is monitoring the waveform on the proximity sensor.
1 of 1 people found this helpful
The resolution is fixed to 16-bit for proximity sensors, by design and that is the reason for scan time to be the same.
For low power, refer to Section 7 of http://www.cypress.com/file/46366/download. I hope this helps.