display / touch / bonding solutions
Industrial touch screens can work reliably with water and thick gloves by co-designing the PCAP sensor stack, cover glass, grounding, and IP65 mechanics with custom controller firmware. We tune Ilitek/EETI algorithms, drive frequency, and mutual/self-cap scan modes to distinguish water films from real touches, then validate with 3–5 mm glove simulations and wet-hand stress tests.
Industrial LCD display solutions
In a PCAP sensor, water, oil, and thick gloves distort the mutual capacitance map, shifting baselines and confusing the controller’s edge/cluster detection. With 5 mm rubber gloves and a thin water film, we see baseline drift up to 20–30% of a finger signal, which triggers ghost touches or complete touch loss if firmware is not tuned.
In our CDTech lab, we recreate these conditions on test jigs and log raw node data to separate glove impedance effects, water-film coupling, and environmental EMI.
From production runs, the main patterns are:
Thin water film: adds a low, wide capacitance “fog” across many nodes, raising baseline slowly.
Large droplets: create localized peaks, often moving as the operator wipes.
Oil/grease: behaves like a slow-moving dielectric; it changes sensitivity but less dynamic.
Thick gloves: attenuate finger signal by 40–70%, depending on material and moisture.
By capturing raw mutual-cap maps before and after contamination, we build “signatures” for each scenario and embed those in our firmware decision logic.
Wet-hand touch tracking is stabilized by combining hydrophobic surface design, smart baseline management, and a dual-mode scan strategy that cross-checks mutual and self capacitance. Instead of globally lowering sensitivity, we selectively ignore signals that match water-film patterns while still accepting high-gradient finger touches.
In practice, we maintain stable tracking on surfaces with continuous mist or droplets while limiting ghost events to under 1 per 10,000 touches in validation tests.
Based on years of CDTech projects, our effective tactics include:
Adaptive baseline: freeze baselines when global shifts resemble water films, and only update after stable dry periods.
Area pattern recognition: water spreads wide with low gradient; fingers create steep, localized gradients.
Time-domain filters: water-induced changes are slow, so we apply dynamic thresholds based on time derivatives.
Self-cap cross-check: if mutual-cap sees a “touch” but self-cap doesn’t confirm, we mark it as suspect.
We also test edge cases: operators putting a whole wet palm on the glass, wiping with cloth, then touching with a wet finger in less than 500 ms.
Changing mutual-cap drive frequency helps separate real touch signals from water-induced and EMI noise. Different frequencies interact differently with parasitic capacitances and conductive films; by shifting or sweeping frequency, we reduce coupling to large water areas while preserving finger-induced gradients.
On Ilitek/EETI controllers, we often move away from default frequencies by 15–30% and enable multi-frequency scanning in critical zones.
In our tuning sessions:
Low-frequency drive: more susceptible to slow, large-area disturbances like water pools.
High-frequency drive: better at ignoring large water plates but can become sensitive to EMI.
Multi-frequency scanning: comparing responses at two frequencies reveals anomalies consistent with water, not fingers.
We log frequency-response curves per project and maintain a CDTech internal database. For outdoor HMIs exposed to heavy rain, we typically adopt a slightly higher base frequency plus aggressive EMI filtering on the FPC and touch tail.
Touch IC firmware is rewritten by adjusting scan sequences, baseline tracking, SNR thresholds, and gesture recognition to treat water films as a distinct “state,” not just noise. We implement state machines that detect “wet surface,” “droplet event,” and “normal operation,” switching algorithms and thresholds accordingly.
On real projects, custom Ilitek/EETI firmware updates have cut water-induced ghost touches by over 90% without significantly degrading responsiveness.
In CDTech debug builds, we commonly tune:
Baseline update rate and conditions (e.g., disallow updates if more than 40% of nodes drift together).
Touch threshold relative to noise floor, often from 3× to 5–6× for wet modes.
Cluster size limits to avoid interpreting large water patches as super-wide fingers.
Edge rejection windows where water tends to accumulate, especially at bezel gaps.
We also expose configurable profiles (dry, wet, glove) to customers who want dynamic switching by MCU via I²C.
Best stack-up and cover lens choices balance sensitivity, mechanical protection, and contamination behavior. For glove and water compatibility, we prefer 1.8–3.0 mm chemically strengthened glass with high-quality hydrophobic/oleophobic coating and a sensor pattern optimized for deeper field penetration.
We avoid unnecessarily thick glass unless impact requirements demand it, and we pair thicker glass with increased drive voltage and optimized sensor pitch.
Below is a common set of stack-ups we use for glove and wet-hand applications:
In CDTech marine HMIs with 3.0 mm glass and 5 mm gloves, we typically increase drive voltage by 20–30% and adjust sensor pattern to maintain SNR without overshooting EMC limits.
IP65 display mechanics support PCAP performance by managing water path, avoiding conductive frames near the field, and preventing water pooling. The mechanical design must protect electronics without creating “capacitive traps” that mimic touches along the bezel.
We pay special attention to gasket materials, venting, and frame grounding so that water doesn’t create unexpected capacitive coupling paths.
From our CDTech IP65 projects, the most effective practices are:
Full-flat front design so water runs off instead of pooling at edges.
Non-conductive or isolated bezels to avoid long grounded edges near active areas.
Carefully selected gasket compression to prevent cap-glass distortion, which shifts node baselines.
Breather membranes to reduce pressure changes that could pump water into micro-gaps.
We simulate water flow and perform real spray tests at different angles, then correlate results with touch logs to find mechanical-only fixes before touching firmware.
Thick 5 mm gloves act as a lossy dielectric that significantly attenuates the finger’s capacitive signature and alters its spatial distribution. The controller sees a weaker, broader signal that may fall near noise thresholds or be mistaken for a spurious large-area disturbance.
Without tailored firmware and higher drive settings, the system either drops touches or amplifies noise, causing jumps and ghost points.
From our glove test matrix:
Thin nitrile (0.1–0.2 mm): ~10–20% signal attenuation.
Medium PU/cotton (1–2 mm): ~30–50% attenuation.
Thick rubber/leather (3–5 mm): ~60–75% attenuation.
We design CDTech glove profiles expecting at least 60% loss. That means increasing drive, improving grounding, and tightening noise control so true touches still clear thresholds with good margin.
We debug systematically by splitting the problem into four layers: sensor/stack-up, grounding/EMI, mechanics/IP sealing, and touch IC firmware. At each layer, we collect quantitative data—raw node maps, noise spectra, and environmental logs—rather than guessing.
A structured checklist often resolves the majority of issues within two or three iteration loops, saving weeks compared to random trial-and-error tweaks.
In our CDTech engineering builds, we follow a sequence:
Measure raw SNR on a dry, glove-free panel to set the baseline.
Introduce water/oil in controlled patterns and record node maps.
Sweep drive frequency and voltage while monitoring noise bands.
Verify ground routing, shielding, and FPC layout under oscilloscope.
Adjust firmware baselines and thresholds and repeat.
Only when each layer’s metrics are within target ranges do we proceed to full IP65 spray and glove-in-use testing.
Wet and glove touch performance should be co-owned by the touch firmware engineer, hardware designer, and mechanical engineer, with one system integrator accountable for end behavior. Treating it as “just a touch IC vendor issue” leads to stalled projects and finger-pointing.
In successful CDTech projects, we nominate a single owner who can change stack-up, layout, and firmware in parallel.
Our internal rule of thumb:
Firmware engineer: owns raw data analysis, algorithms, and profile management.
Hardware engineer: owns stack-up, drive/receive routing, and power/EMI control.
Mechanical engineer: owns IP65 structure, water path, and gasketing.
Project integrator: balances trade-offs and signs off on field test criteria.
We also involve the end user early, having operators test with real gloves and cleaning routines rather than idealized lab conditions.
“The toughest waterproof and glove projects are never solved by ‘turning sensitivity up.’ Every time we see a ghost-touch nightmare, the fix comes from aligning mechanics, grounding, and firmware. In one marine terminal project, we cut ghost touches from dozens per shift to near zero simply by redesigning the front bezel and then updating the Ilitek scan sequence—without changing the LCD at all.”
Robust test regimes combine environmental cycling, IP spray, chemical exposure, and automated gesture loops under different glove and moisture conditions. We script robots to swipe, tap, and multi-touch across the panel while spray nozzles simulate rain, mist, and cleaning.
Before release, CDTech expects at least 100,000 automated gestures across multiple sample units with no systematic ghost patterns or dead zones.
A typical pre-production matrix includes:
Dry bare finger, room temp and -20 to +60°C.
3 mm nitrile and 5 mm rubber gloves, dry and damp.
Mist, droplets, and flowing water at key angles for IP65.
EMI exposure near inverters or motors.
We log error rates, latency, and SNR in each scenario. If any cell exceeds our limits—for example, more than 1% failed gestures—we retune firmware or mechanics before ramping up.
Yes, there are unavoidable trade-offs, and understanding them upfront avoids unrealistic expectations. Pushing for extreme glove sensitivity, full waterproof behavior, and high EMC robustness simultaneously drives controller limits and cost.
We usually define clear performance tiers—light glove, heavy glove, and “extreme wet”—and guide customers to pick the tier that matches real use, not marketing slogans.
Typical trade-offs:
Heavy gloves typically mean higher drive current and potentially higher EMI emissions.
Extreme waterproof modes may temporarily reduce multi-touch capability to prioritize stability.
Strong EMI immunity can require tighter filtering, which slightly slows scan rates.
In CDTech proposals, we always document which scenario is prioritized, for example: “5 mm rubber glove with splash water, minimal ghost touches, two-finger gestures supported, scan latency < 40 ms.”
Can existing industrial displays be upgraded for glove and wet-hand support?
In many cases yes, but not by firmware alone. We often replace the sensor stack, adjust grounding, and then deliver new Ilitek/EETI firmware. Keeping the original LCD and mechanics while only upgrading the touch module is a common and cost-effective CDTech retrofit approach.
What is the minimum glass thickness for robust glove operation?
For 3–5 mm glove support we rarely go below 1.8 mm glass, as thinner glass is more prone to flexing and baseline drift. Between 1.8–3.0 mm, we can usually achieve stable operation with tuned drive settings, while still keeping mechanical strength and optical performance under control.
Does IP65 guarantee good wet-hand touch behavior?
No. IP65 only defines water ingress protection, not touch performance under water. We have seen fully IP65-certified devices with terrible wet-touch behavior. Achieving both requires coordinated design of the PCAP stack, controller firmware, and mechanical water management, something CDTech focuses on from the first prototype.
Can one firmware profile cover both thin gloves and 5 mm rubber gloves?
It is technically possible but often suboptimal. A single “universal” profile tends to overcompensate, causing higher latency or more noise in lighter-glove scenarios. We prefer to provide multiple profiles or dynamic modes so the host MCU can choose the most appropriate behavior for each job site.
How long does a typical CDTech waterproof, glove-compatible project take?
From requirement freeze to mass-production readiness, most projects take 10–16 weeks. The timeline includes stack-up design, first samples, at least one firmware tuning loop for Ilitek/EETI controllers, and a full wet/glove validation matrix. Complex retrofits or extreme environments may add a few weeks for extra mechanical iterations.
Designing waterproof and glove-compatible industrial touch screens is essentially about engineering the entire signal chain—from the operator’s finger, through glove, water, glass, sensor, and mechanics, into the touch IC algorithms. Simple tweaks like “increase sensitivity” never solve the root causes and often make errors worse under EMI or contamination.
The most effective path we’ve refined at CDTech is systematic: choose an appropriate stack-up and coating, design IP65 mechanics that avoid capacitive traps, route and ground the touch circuits correctly, then tune Ilitek/EETI firmware with raw node data under realistic gloves and wet conditions. For buyers, the actionable steps are clear: define real glove and water scenarios numerically, insist on data-driven firmware tuning, and allocate time for at least one full iteration loop before locking the design. This is how industrial touch HMIs stay usable and stable on the real factory floor, not just in the catalogue.
By continuing to use the site you agree to our privacy policy Terms and Conditions.
