Fastest scan-time is decided by sensor scan time. In this code example, scan period is controlled by WDT. You can try to decrease LOOP_TIME_FASTSCANMODE. For more details, see the code example document.
Regarding that 'bug', I will try to reproduce it and find the root cause.
You can try to decrease LOOP_TIME_FASTSCANMODE.
that I have tried already. It doesn't matter if I setup 10u, 5u ... the lowest scantime keeps at 20ms (measured with a datalogger).
Also change the clocksetting (IMO to 48MHz and Modulator clk to 48MHz) does not help. Scantime keeps at 20ms minimum.
I have setup the CapSense tuning mode to "Full Auto-Tune".
As I know from the fix programmed version CY8CMBR3116, the minimum Setup Time in EZ-Click is 20ms... so maybe that is really the minimum and the same for the PSoC4000S devices??
I will try to reproduce it and find the root cause.
thank you, I hope you can reproduce it
BTW: what does that "u" after every Value means?
@rzzh, could you reproduce the problem in the meantime? thank you
Last many days, I was involved in some other projects support, so I am late to do some experiment around this CE.
Yes. I have reproduced the issue. Not sure the root cause.
The workaround is changing the definition and initialization of softcounter:
uint16 softCounter = SCANMODE_TIMEOUT_VALUE;
Kindly have a try.
1 of 1 people found this helpful
I think that the issue is with WDT_Start().
Calibrating wdt match value to slow scan mode and then calibrating to fast scan mode should resolve this issue.
(i.e) swap lines 469-471 with 474-476
Since WDT_Start() sets the watchdog match value to slow scan match value, this issue arises.
Let me know if this helps.
thank you very much that works :-), I have swaped it as follow:
/* Get the actual match value required to generate a given delay */
watchdogMatchValue = WDT_TIMEOUT_SLOW_SCAN;
wdtMatchValSlowMode = watchdogMatchValue;
watchdogMatchValue = WDT_TIMEOUT_FAST_SCAN;
wdtMatchValFastMode = watchdogMatchValue;