# How to calibrate touch screens

**How To Calibrate Touch Screens **

**Touch screens are finding their way into a variety of embedded products.
Most touch-enabled devices will require a calibration routine. Here's a good one. **

Resistive-type touch screens are normally used in cost-conscious designs. Their construction is simple, their operation is well understood, and the hardware and software required to support them is readily available from multiple manufacturers.

Despite the advantages of resistive-type touch screens, devices equipped with them almost always require that a calibration algorithm be the first task to run when the final product comes out of the box. Calibration is necessary because it is difficult to perfectly align a touch screen's coordinates to the display (LCD or otherwise) behind it. If a button or other "live" feature on the display is to be properly activated, the coordinates of the area touched on the screen must be sufficiently close to the coordinates of the feature on the display. Otherwise, the software may not correctly act upon the soft button presses.

This article proposes a calibration algorithm for resistive-type touch screens that is both efficient and effective. This algorithm was developed after identifying the sources of touch screen errors and deriving the optimum method for transforming the coordinates provided by the touch screen to match the coordinates of the display. The calibration method requires that three targets or test points-no more, no less-be displayed and touched in sequence to determine the screen's individual calibration factors. These calibration factors are then used to translate screen coordinates into true display coordinates.

**Touch screen technology**

The cross section of a resistive-type touch screen is shown in Figure 1. The construction is simple. Two sheets of glass are brought together to form a sandwich, the interior glass surfaces having been coated with a thin layer of conductive material. Small glass beads maintain a nominal separation between the conductive surfaces. When a finger or stylus presses against the surface of the glass, the material bends just enough to contact the lower sheet. In this construction the spacing between beads determines the sensitivity of the screen. The closer the beads are, the higher the pressure that must be exerted before the top glass sheet will bend enough to make contact.

**Figure 1: Cross section of a resistive-type touch screen**

**Figure 2: Equivalent circuit**

An equivalent resistive circuit is shown in Figure 2: a touch screen controller (digitizer or A/D) applies the V sources to the ends of one of the conductive layers, while the other conductive layer-on the opposite sheet of glass-plays the role of the potentiometer wiper. The Vtest value read by the digitizer depends on where the glass is touched and the conductive surfaces come into contact. The controller then translates the voltage reading into a binary quantity representing, for example, the X-coordinate of the point where the screen was touched. The voltage potential is then applied to the second surface's endpoints and the first surface plays the role of the wiper, yielding a value that represents the Y-coordinate.

Controllers may collect 200 or more samples per second. The sampling rate usually depends on background noise and controller quality. A smart controller may also incorporate useful features like the ability to interrupt the CPU when a touch is detected, as well as the ability to sample continuously at a set rate as long as the screen is being touched. The device idles when the screen is not being touched.

**Sources of error**

Several sources of error affect the X and Y coordinates produced by the touch screen controller. The most important sources of error are electrical noise, mechanical misalignments, and scaling factors. User idiosyncrasies may also play a role if, for example, the finger or instrument used to activate the screen does not maintain continuous contact or pressure against it. Any of these errors can produce unusable data, and all need to be compensated for if the touch screen data is to be useful.

Electrical noise triggered by thermal or electromagnetic effects and system design weaknesses are omnipresent in all kinds of electrical systems. In the case of a touch screen, the A/D conversion is particularly susceptible to electrical noise because of the high input impedance of the A/D front-end circuitry. In addition to carefully laying out the printed circuit board containing the touch screen controller, noise problems are normally addressed by adding low-pass filtering to the A/D inputs. Software also comes to the rescue, usually discarding one or two of the least significant bits of the A/D conversion and implementing algorithms to remove from the sampled stream those data points that fall outside permissible ranges. The same software algorithms may remove errors introduced by the user. Such errors normally manifest themselves as sampled points that fall well outside permissible limits as the applied pressure varies.

**Figure 3: A circle on the display and its equivalent touch screen
coordinates**

Mechanical misalignments and scaling factors are the errors addressed by the calibration algorithm proposed in this article. Consider the images in Figure 3. The circle represents an image shown by the LCD under the touch screen; the ellipse represents an exaggerated set of coordinates that the touch screen could produce if the user were to trace the round image shown by the LCD. The reconstructed image appears rotated, translated, and scaled by a different factor in each direction. The challenge for the calibration algorithm is to translate the set of coordinates reported by the touch screen into a set of coordinates that accurately represent the image on the display.

**The mathematics**

To derive a general solution to the problem, it is convenient to describe each point as a mathematical quantity. We see from Figure 4 that it is possible to describe each point on the display as a vector PD and its corresponding equivalent, as reported by the touch screen, as a vector P.

**Figure 4: Vector representations of point**

It is also reasonable to assume that P and PD are related by a quantity that transforms the display coordinates into the apparent touch screen coordinates, like this:

PD = MP (1)

where M is the appropriate transformation matrix and the object of this exercise. If we can assign values to the elements of the transformation matrix M, then we can solve for all PD points given the P points reported by the touch screen.

Let us proceed under the assumption that each display point can be obtained from a corresponding touch screen point, but that the touch screen point has suffered rotation, scaling, and translation.

If we express the points as (X,Y) pairs based on the vector's length and angle, both the display and touch screen points in question can be represented by the following equations:

(2a)

(2b)

If the reported touch screen points have experienced rotation because of touch screen misalignment, and qr = qD - q is the angular misalignment of the reported point, an intermediate point is expressed by:

(3)

Each of the X and Y dimensions is also scaled by its own factor, which we will call KX and KY. Accounting for scaling produces the following equation, which comes closer to describing a display point in terms of screen point coordinates:

(4)

Finally, let us add translation elements XT and YT to yield the equation of a display point in terms of the data reported by the touch screen:

(5)

We can now make a key, pragmatic assumption in order to represent Equation 5 in a form that will enable us to solve for its unknown quantities. While the touch screen may be rotated with respect to the display, the rotation angle qr should be sufficiently small that we can assume sinqr qr and cosqr 1.0. This assumption yields another useful set of approximations:

(6a)

(6b)

and Equation 5 can then be re-expressed by the following combination of terms:

(7)

The advantage of Equation 7 is that we have expressed actual display coordinates in terms of touch screen coordinates. Restating the above equation we get:

(8)

Except for X and Y, all the terms on the right side of the above equation are constant, given our previous assumption that in the practical case the effects of scaling, rotation, and translation could be accounted for with constant quantities.

Expressing the XD and YD coordinates in more convenient terms, we arrive at the equations that translate touch screen points to display points:

(9a)

(9b)

The previous equations seem almost intuitive. Remember, though, that they are only valid when the angular misalignment between the display and the touch screen is small.

**Calibration matrix**

Common calibration algorithms use data from two to as many as five sample points to collect calibration information. The exercise above assumes that display point coordinates can be calculated from touch screen coordinates, and that by making simple assumptions we can obtain calibration data by using three sample points-no more, no less. Three sample points are needed because Equations 9a and 9b each contain three unknowns. With three sample points we can obtain sufficient information to set up and solve the simultaneous equations.

**Figure 5: Sample calibration points**

Sample points should also be selected based on practical considerations. They must yield non-redundant simultaneous equations, they must not be too close to the edge of the touch screen (where non-linearities are more likely to occur) and they must be widely spaced to minimize scaling errors. The set of points shown in Figure 5 labeled P0, P1, and P2 meet the suggested requirements. Those points are roughly 10% off the edge of the screen, as far apart as the display geometry allows, and yield the following non-redundant equations:

(10a)

(10b)

(10c)

(11a)

(11b)

(11c)

We need to solve for A, B, C, D, E, and F. Once these parameters are known, obtaining display coordinates is as simple as plugging the raw touch screen data back into Equation 9.

The solution for the unknowns in the previous set of simultaneous equations is well known and will not be derived here; we will skip the intermediate steps and present the final solution. The unknowns are resolved as follows, using the value K as the common denominator for all solutions:

(12)

(13)

(14)

(15)

(16)

(17)

(18)

**Software implementation**

The hardest part of this problem (solving for the set of simultaneous Equations 10 and 11) is now behind us; the actual implementation in software is a straightforward exercise. The program sample provided at 06vidales.zip includes three files: calibrate.c, calibrate.h, and sample.c. The hard work is done in the first. It contains two functions called **setCalibrationMatrix()** and **getDisplayPoint()**. The former implements Equations 13 through 18; the latter implements Equation 9.

The header file contains miscellaneous declarations, and the other source file implements a console application that exercises the calibration functions, attempting to show how you would use these functions within a device.

The code in sample.c assumes that your device implements a routine to collect calibration data before attempting to use these functions. An outline of the proposed calibration process is shown in Listing 1. After taking those steps, the calibration procedure is complete and your applications can begin receiving accurate position information from the touch screen system. The function **getDisplay-Point()** is intended to be called within the touch screen controller's interrupt routine, after the routine has filtered and debounced the data coming out of the digitizer. In a typical implementation, calling **getDisplayPoint()** would be the last step needed before a point of touch screen data could be placed in the user-input queue.

Listing 1 Steps in the calibration process
1. Call
2. Draw the first target at coordinates (XD0,YD0).
3. Collect the data returned by the touch screen driver and save it as (X0,Y0).
4. Draw the second target at coordinates (XD1,YD1).
5. Collect the data returned by the touch screen driver and save it as (X1,Y1).
6. Draw the third target at coordinates (XD2,YD2).
7. Collect the data returned by the touch screen driver and save it as (X2,Y2).
8. Call |

**Special considerations**

The sample functions have been implemented to ensure that accurate results are produced every time. Thus, intermediate values have not been scaled.

Integer 32-bit math is required because the raw numbers provided by most digitizers are 10-bit quantities, and Equations 15 and 18 may yield 31-bit signed values. The equations, as implemented, will work with touch screen digitizer resolutions up to 1,024 pixels, which may be suitable for display resolutions up to about 512 pixels (height or width).

If you want to use these formulas for larger touch screen resolutions, it will be necessary to either use 64-bit integer values or judiciously scale input values or intermediate results to avoid register overflow when calculating the calibration factors.

The function **getDisplayPoint()** does depend on the calibration matrix containing a set of valid quantities to provide reliable results. The structure of the sample provided uses automatic variables to highlight the relationship between the display coordinates, screen coordinates, and the calibration matrix, but in a practical implementation the calibration matrix may best be a global structure that is properly initialized at boot time.

The code available for download at http://www.embedded.com/design/embedded/source-code/4209764/06vidales-zip is offered as a free reference implementation that can be adapted to a variety of applications. No attempt was made to optimize the code.

**One final touch**

The touch screen calibration algorithm described here is simple, flexible, and capable of correcting for common mechanical errors. These errors-translation, scaling, and rotation-result from mismatches between the display and the touch screen located above it. They can be compensated for with mechanical means, but the proposed software solution reduces demanding electromechanical manufacturing and quality problems.

**Carlos E. Vidales** is a software engineering manager with Tekelec in North Carolina. He has worked on a variety of embedded projects, from electro-mechanical systems to voice/data communication products. He holds BS degrees in mechanical and electrical engineering, and an MBA. His e-mail is CVidales.ee77@gtalumni.org.

Return to June 2002 Table of Contents

Please confirm the information below before signing in.

{* #socialRegistrationForm *} {* firstName *} {* lastName *} {* displayName *} {* emailAddress *} {* addressCountry *} {* companyName *} {* ednembJobfunction *} {* jobFunctionOther *} {* ednembIndustry *} {* industryOther *}