A field team faces an unresolved physical question: Why can a glove turn one touch sample into eighty-one? They must answer it before changing glove thickness on the real device. Predict the direction first.
See the relationship before changing it
The figure reads from left to right. The blue card is glove thickness. The middle card applies this page's relationship. The green card is effective thickness. Walk the arrows once: set the input, apply the rule, then read the result with its unit.
The retained audit below checks several chapter fixtures. This added model holds every other chapter fixture fixed, so the numeric fixture does not switch without explanation.
Derive the baseline in four named moves
- 1
Name the input. The chapter baseline for glove thickness is 3.
- 2
Name the relationship. bare deff=1.00/4.00=0.250 mm; C=3.54 pF; T=2.45 us with glove deff=0.250+3.00/1.50=2.25 mm; C=0.394 pF; T=0.273 us r=3.54/0.394=9.00; N≈r²=81; scan current=0.0100x81=0.810 mA
- 3
Substitute the chapter fixture. Set glove thickness to 3. The page ledger gives effective thickness as 2.25 mm.
- 4
Read the result. Keep mm beside the value. Use it only inside the technical boundary on this page.
Predict, then change glove thickness
Try Predict the direction of effective thickness. Move one control, calculate, then check your prediction.
Observe A small geometric change can become a large energy cost when firmware tries to recover the signal by averaging alone. Reset the control to 3 and compare effective thickness.
Explain Only glove thickness moves here. The other chapter fixtures remain fixed.
Check yourself
What should you do before trusting a moved-control result?
What does this small model leave out?
1. Treat each layer as electrical distance
A dielectric separates charge without conducting it. Divide each physical thickness by its relative permittivity, then add the layer results. More effective distance means less capacitance.
2. Name every algebra move
Scale each layerdeff=Σdi/εr,i.
Invert distanceC=ε0A/deff.
Turn capacitance into timeT=RC ln 2.
Find the lost-signal ratior=Cbare/Cglove.
Square for averagingN≈r².
3. Reproduce bare finger and glove
with glove deff=0.250+3.00/1.50=2.25 mm; C=0.394 pF; T=0.273 µs
r=3.54/0.394=9.00; N≈r²=81; scan current=0.0100×81=0.810 mA
The sample count comes from an ideal averaging rule. It is a warning about cost, not a guarantee of glove detection.
4. Try the glove thickness
TryIncrease fabric thickness while leaving the glass, area, timer, and scan rate fixed.
ObserveCapacitance and timer duration fall roughly as the inverse of effective thickness, while ideal sample demand grows with the square of the loss ratio.
ExplainA small geometric change can become a large energy cost when firmware tries to recover the signal by averaging alone.
The parallel-plate and ideal-noise models make the chain visible but omit product details.
- Field
- Real electrodes use fringing fields, guards, traces, and body coupling
- Noise
- Interference and drift may not improve as square-root averaging predicts
- Interface
- Detection is not usability; users still need perceivable feedback and recovery
Prototype with real gloves, wet surfaces, temperature, users, and installed electronics.
5. Test the failed mode
Measure false misses and false touches with bare, thin-glove, thick-glove, wet, cold, and noisy cases. Check whether voice or a physical control remains available.
6. Record the interface state
Store stack thickness, materials, electrode, threshold, calibration, scan rate, averaging, current, glove set, environment, user outcome, and retest triggers.
7. Check yourself
Why does thicker fabric reduce capacitance?
Why does a nine-times smaller signal suggest 81 samples?
Does 81 samples guarantee an accessible glove mode?
The glass, glove, timer, scan, and current values reproduce the chapter's catalog-typical teaching case.
- Parallel plates
- First-principles scale estimate, not a complete touch-electrode model
- r² samples
- Ideal independent-noise recovery estimate
- 0.810 mA
- Illustrative scan current with no other controller activity
Correct, not complete: coupling arithmetic does not qualify a multimodal interface.
UX Uma guides