-
Foundations
-
- Unirse a este curso para acceder a recursos
-
- Unirse a este curso para acceder a recursos
-
-
Sensing technologies
-
- Unirse a este curso para acceder a recursos
-
- Unirse a este curso para acceder a recursos
-
- Unirse a este curso para acceder a recursos
-
-
Integration
-
Applications
-
Custom development
1.1 Welcome: the display shows; the touch system senses
Chapter 1 · Foundations
Welcome: the display shows; the touch system senses
Trace a touch from the user's hand to an application, and separate display performance from touch performance.
Narration script
Slide 1 of 157 · Welcome: the display shows; the touch system senses
Welcome to Touch Panel Technology. I'm Diggy Breiling, founder of FPD.DEV, The Future of Display and Systems Development. I began repairing LCDs in 1992 and optically bonding them in 1994. The first touch panels I used were resistive panels that I made myself by 1995. I have firsthand experience integrating almost every touch panel type and have worked directly with over a dozen touch panel manufacturers, past and present. That practical experience shapes this course, from how each technology works to the tradeoffs that matter in a finished product. We'll begin by tracing a touch from the user's hand to an application.
Slide 2 of 157 · Two systems, one experience (1 of 2)
Let's, let's look at this step by step. An LCD, OLED or microLED produces an image. A touch system locates an interaction and reports it. They can be physically integrated, but a bright picture does not prove accurate touch, and accurate touch does not prove a readable picture. Think of five cooperating elements: the surface the user touches; the sensor; the controller and its firmware; the host interface and operating-system input stack; and the application. A failure at any one can look like a bad touchscreen. The course follows that chain from physics through integration and use.
Slide 3 of 157 · Two systems, one experience (2 of 2)
We begin with everyday explanations, then examine the mechanisms, electrical interfaces, optical and mechanical integration, and application-specific tradeoffs. Basic voltage, current and wavelength concepts help; no touch-controller design experience is assumed. This course is a living document. We revise chapters as technology, practical experience and guidance evolve. Standards also change through revised editions, so check which edition applies to your project. Enrolled learners will typically have access to updated chapters as they are released.
Slide 4 of 157 · What a good touch system must do
Describe intended actions before choosing a sensor: tap, drag, draw, pinch, confirm or operate through gloves. Specify the smallest target, active area, viewing position, permitted false activations, and response time. Include release detection: an input that never lets go can be more troublesome than a missed tap. Accuracy describes how close a reported coordinate is to a known reference touch position. Precision describes how closely repeated measurements agree under the same conditions. Resolution is the reporting increment. A 16-bit coordinate field does not establish submillimetre accuracy. Latency also belongs to the complete chain: sensing, filtering, transport, operating system, application and display update. Throughout the course, example numbers and animations are teaching models, not measured performance of an FPD.DEV product.
Slide 5 of 157 · Learning route
Chapters 1-2 build a selection vocabulary. Chapters 3-11 explain the sensing families and feedback options. Chapters 12-15 connect them to displays, hosts and verification. Chapters 16-20 examine commercial, industrial, aviation, military and ground-transport use. Chapters 21-22 turn requirements into a custom-product brief. For each mechanism, ask: what physical quantity changes, what measures it, how is position inferred, and what else can produce the same change? This last question explains most difficult failures. The exercises ask for engineering reasoning rather than memorized brand claims. Use the glossary for terminology and the references for implementation details.
Slide 6 of 157 · Apply the idea
Sketch the five elements for a ticket machine. Where would you investigate if the image works but no touch is reported? Pause here and consider your answer. Check that the touch controller has power and that the host computer recognizes it. Then check whether touch reports arrive, whether their coordinates map to the right display, and whether the application responds. A working picture alone does not prove that this input chain works.
Slide 7 of 157 · Chapter 1 complete
Complete the chapter exercise and review any open questions. These are living courses. Enrolled learners will typically receive a notification when chapter content is updated, so please sign in and enroll in the course. Next is Chapter 2: The simple comparison: benefits, compromises and selection. I'm Diggy Breiling, founder of FPD.DEV, The Future of Display and Systems Development. Thank you for joining me.
Chapter reading
Use Back and Forward to browse without interrupting the video. Choose another chapter in the course sidebar. Use the chapter PDF and animated slide deck below.
Reading 1 of 3
Two systems, one experience
An LCD, OLED or microLED produces an image. A touch system locates an interaction and reports it. They can be physically integrated, but a bright picture does not prove accurate touch, and accurate touch does not prove a readable picture.
Think of five cooperating elements: the surface the user touches; the sensor; the controller and its firmware; the host interface and operating-system input stack; and the application. A failure at any one can look like a bad touchscreen. The course follows that chain from physics through integration and use.
We begin with everyday explanations, then examine the mechanisms, electrical interfaces, optical and mechanical integration, and application-specific tradeoffs. Basic voltage, current and wavelength concepts help; no touch-controller design experience is assumed.
This course is a living document. We revise chapters as technology, practical experience and guidance evolve. Standards also change through revised editions, so check which edition applies to your project. Enrolled learners will typically have access to updated chapters as they are released.
Reading 2 of 3
What a good touch system must do
Describe intended actions before choosing a sensor: tap, drag, draw, pinch, confirm or operate through gloves. Specify the smallest target, active area, viewing position, permitted false activations, and response time. Include release detection: an input that never lets go can be more troublesome than a missed tap.
Accuracy describes how close a reported coordinate is to a known reference touch position. Precision describes how closely repeated measurements agree under the same conditions. Resolution is the reporting increment. A 16-bit coordinate field does not establish submillimetre accuracy. Latency also belongs to the complete chain: sensing, filtering, transport, operating system, application and display update.
Throughout the course, example numbers and animations are teaching models, not measured performance of an FPD.DEV product.
Reading 3 of 3
Learning route
Chapters 1-2 build a selection vocabulary. Chapters 3-11 explain the sensing families and feedback options. Chapters 12-15 connect them to displays, hosts and verification. Chapters 16-20 examine commercial, industrial, aviation, military and ground-transport use. Chapters 21-22 turn requirements into a custom-product brief.
For each mechanism, ask: what physical quantity changes, what measures it, how is position inferred, and what else can produce the same change? This last question explains most difficult failures.
The exercises ask for engineering reasoning rather than memorized brand claims. Use the glossary for terminology and the references for implementation details.
Apply what you learned
Sketch the five elements for a ticket machine. Where would you investigate if the image works but no touch is reported?
Suggested answer
Check that the touch controller has power and that the host computer recognizes it. Then check whether touch reports arrive, whether their coordinates map to the right display, and whether the application responds. A working picture alone does not prove that this input chain works.
Maurizio Napolitano from Trento, Italy · CC BY 2.0 · Source · Unmodified photograph; scaled for display
References and links
- USB-IF: HID specifications and usage tables
- Microsoft: Required touchscreen HID collections and reports
Glossary
- Accuracy
- Closeness of a reported coordinate to a defined reference position.
- Precision
- Repeatability or spread of results under specified conditions.
- Resolution
- Smallest coordinate increment or representable change; not equivalent to accuracy.
- Latency
- Time between explicitly defined input and output events.
- PCAP
- Projected capacitive touch; patterned electrodes sense electrical coupling changes.
- Self-capacitance
- Measurement of an electrode relative to an electrical reference.
- Mutual capacitance
- Measurement of coupling between transmit and receive electrodes.
- Baseline
- Reference measurement used to identify changes associated with touch.
- SNR
- Signal-to-noise ratio; specify the signal, noise measure and conditions.
- SAW
- Surface acoustic wave sensing through controlled propagation on a surface.
- APR
- Acoustic pulse recognition; a touch-generated mechanical response is used to locate contact.
- DST
- Dispersive signal technology; a bending-wave sensing implementation.
- EMR
- Electromagnetic resonance, used by compatible pen digitizers.
- Haptics
- Tactile feedback produced by the system.
- HID
- Human Interface Device class/protocol family; the descriptor defines report interpretation.
- Report descriptor
- Data describing the structure and meaning of HID reports.
- Contact ID
- Identifier used to distinguish and track a contact.
- I2C
- Two-wire synchronous bus; raw I2C communication does not itself implement HID.
- SPI
- Synchronous serial peripheral interface, with device-specific protocol behavior.
- UART
- Asynchronous serial hardware; electrical levels and framing must be specified.
- Optical bonding
- Joining optical layers with a transparent material to manage the interface.
- Parallax
- Apparent relative position shift caused by viewing separated planes from an angle.
- NVIS
- Night Vision Imaging System; pronounce 'en-vis' in this course.
- Qualification
- Evidence against a defined set of requirements for an identified configuration.
- Validation
- Evidence that the system satisfies its intended use.
- Verification
- Evidence of conformance to specified requirements.
- Ghost touch
- Reported contact that does not correspond to an intended physical touch.
- Palm rejection
- Classification or suppression of unintended hand contact.
- On-cell / in-cell
- Touch structures at a display-cell surface / integrated within the display structure; verify supplier construction.
- Touch plane
- Geometric region in which the sensing system detects an object.
FPD.DEV — The Future of Display and Systems Development.
ShadowSense™ is a trademark of Baanto International Ltd. The ShadowSense technology and related intellectual property belong to Baanto. FPD.DEV’s explanatory graphics are original teaching illustrations.
No hay comentarios por ahora