Response time

setting CFG0

(ms)

Cycle times executed to achieve response times (ms)

CFG1 X8

oversampling

CFG1 X16

oversampling

CFG1 X32

oversampling

CFG1 X64

oversampling

Free run

(1)

(1.9)

(3.4)

(6.8)

50

23

21

18

12

100

48

46

43

37

300

148

146

143

137

Keep in mind that the CFG1 response time assumes that physical touch happens right at the beginning of sleep, from

a timing perspective worst-case scenario. The table below reflects the expected minimum, average, and maximum

values for response times under standard conditions.

Response

time setting

CFG0 (ms)

Min / AVG / Max resulting response time (ms)

CFG1 X8 oversampling

CFG1 X16

oversampling

CFG1 X32

oversampling

CFG1

X64 oversampling

Min

Avg

Max

Min

Avg

Max

Min

Avg

Max

Min

Avg

max

Free run

7

11

21

40

50

27

39

50

29

40

50

32

41

50

39

45

50

100

52

76

100

54

77

100

57

79

100

64

82

100

300

152

226

300

154

227

300

157

229

300

164

232

300

Figure 7-2. Response Time

min response time

avg response time

CFG0 - max response time

A

A

B

A: measurement time

B: touch integrity checks

Note:  During high noise, the response times may exceed the configured target, due to the automatic adjustment of

oversampling period by frequency hopping. In the worst-case frequency selection, the maximum response time may

be extended by 30%.

MTCH1010

Response Time

Datasheet

DS40002314A-page 13