Calibration Basics: Mapping Touch to Display Pixels

A touch controller reports coordinates in its own sensor space. Calibration defines the transform from that sensor space to the display’s pixel space—scaling, offset, rotation, and any axis inversion. The transform is stored either in the controller, in the driver, or in the OS layer, depending on the design. Calibration is only as good as its reference: the mapping is measured against known points on the display, so a calibration routine needs a stable display geometry and a stable touch stack.

Resistive Calibration: 4-Point and 25-Point Routines

Resistive screens measure a voltage divider across two conductive layers. Pressure bends the top layer, and the measured position can drift as the layers age, flex, or shift slightly in the stack. Calibration compensates by sampling known points:

• 4-point calibration — samples the four corners and computes a linear transform; fast and adequate for many applications.
• 25-point calibration — samples a denser grid to correct nonlinearity across the surface; slower but more accurate where precision matters.

Resistive calibration is often performed in the field or at startup because the stack can change over the product’s life, especially with heavy use.

PCAP Calibration: Why Factory Calibration Is Enough

Projected capacitive screens sense a change in capacitance at fixed electrode intersections. Because the sensor geometry is stable and the controller measures the same physical grid every time, the mapping from sensor to display is consistent—so PCAP screens are calibrated at the factory and do not normally drift in service. If a PCAP screen behaves as if misaligned, the usual causes are software: wrong resolution configuration, incorrect axis mapping in the driver, or a coordinate transform applied twice. Those are integration faults, not calibration drift, and they are fixed in configuration rather than by a field calibration routine.

When Calibration Fails: Hardware Behind Touch Drift

When a screen that was aligned starts drifting, look for hardware causes before recalibrating:

• Sensor or cover shift — a cover glass or sensor that moved relative to the display changes the mapping.
• Bonding or lamination changes — stack movement from temperature or mechanical stress alters the relationship.
• Controller or firmware changes — a firmware update that changes scaling or reporting breaks the existing calibration.

Recalibrating a drifting PCAP screen without finding the hardware cause just hides the problem until it drifts again.

Validating Calibration: 9-Point and 16-Point Accuracy Tests

Acceptance testing measures how close touches land to the intended targets:

• 9-point test — touches at a 3×3 grid of known positions, measuring error at each.
• 16-point test — a denser 4×4 grid for tighter validation across the surface.

Define the acceptable error (for example, a stated millimeter tolerance at each point) and the test conditions—touch size, speed, and surface state—before testing. Accuracy claims belong in the report with the grid and conditions stated.

Questions to Ask the Supplier About Calibration

1. Is this technology factory-calibrated, and what is the stated accuracy?
2. What calibration routine is available for resistive, and when should it run?
3. How is the coordinate mapping configured for my display resolution and orientation?
4. What accuracy test and report will accompany the module?

Calibration is a module-and-host integration topic: the controller choice and driver mapping have their own guides, and this article owns the calibration method and validation itself.

Frequently Asked Questions