Touch problems can come from touch technology, glove material, contamination, overlay, grounding, cable, controller, driver, calibration or the application. Glove operation must be tested with the exact screen, glove and interface.
This guide is for Kiosk operators, UI teams and service technicians during touch selection and troubleshooting. A kiosk is an unattended transaction point, so the user flow, installed modules, site conditions, exception handling and service access have to be designed as one system.
Direct Answer
A sound decision begins with touch technology and physical condition. It then reviews electrical path, driver and calibration, and application, tests the buyer's real workflow on a representative sample and freezes the accepted configuration before bulk release. Compare evidence, limitations and responsibility boundaries instead of counting features.
When to Use This Guide
Use this guide when a kiosk touchscreen not working with gloves project requires an unattended workflow, kiosk form factor, module set, site condition and service plan to be approved together. It is not a substitute for payment certification, accessibility assessment, outdoor rating evidence, site engineering or approval by the local responsible authority.
Use the resulting kiosk touchscreen not working with gloves decisions to prepare an RFQ, sample test, pilot gate or supplier clarification. If the project has already fixed a different configuration, apply the touch technology and physical condition checks as a gap review and record every deviation before deciding whether a retest is needed.
Key Decision Points
Decision 1: Touch technology
What to confirm: Identify PCAP, resistive or another exact panel and controller.
Risk if unclear: Generic touchscreen language does not define glove behavior.
Decision 2: Physical condition
What to confirm: Inspect surface contamination, damage, moisture, overlay and bezel pressure.
Risk if unclear: Mechanical contact can create false or missing touches.
Decision 3: Electrical path
What to confirm: Check controller cable, grounding, power and interference.
Risk if unclear: Intermittent electrical faults may appear as calibration problems.
Decision 4: Driver and calibration
What to confirm: Record driver, firmware, operating system and calibration state.
Risk if unclear: Recalibration cannot fix an unsupported input method.
Decision 5: Application
What to confirm: Test touch targets, gestures and screen edges in the real kiosk interface.
Risk if unclear: A working desktop touch test can still fail the application workflow.
Requirements, Evidence and Tradeoffs
Touch technology
Identify PCAP, resistive or another exact panel and controller. Generic touchscreen language does not define glove behavior.
Physical condition
Inspect surface contamination, damage, moisture, overlay and bezel pressure. Mechanical contact can create false or missing touches.
Electrical path
Check controller cable, grounding, power and interference. Intermittent electrical faults may appear as calibration problems.
Driver and calibration
Record driver, firmware, operating system and calibration state. Recalibration cannot fix an unsupported input method.
Application
Test touch targets, gestures and screen edges in the real kiosk interface. A working desktop touch test can still fail the application workflow.
Evaluation and Approval Process
1. Record the symptom and conditions.
Create a one page requirement record and include touch technology as an explicit field. Identify PCAP, resistive or another exact panel and controller.
2. Clean and inspect safely.
Attach the exact model, revision and source used to verify physical condition. Inspect surface contamination, damage, moisture, overlay and bezel pressure.
3. Test the operating system touch layer.
Run a focused test for electrical path and retain the input, expected result and observed result. Check controller cable, grounding, power and interference.
4. Check controller and driver.
Resolve the boundary around driver and calibration with the responsible supplier or internal team. Record driver, firmware, operating system and calibration state.
5. Test the exact glove and application.
List every deviation affecting application and decide whether correction or retest is required. Test touch targets, gestures and screen edges in the real kiosk interface.
6. Replace or escalate only after the fault layer is identified.
Freeze the accepted wording for touch technology in the quotation, approval and bulk inspection record. Identify PCAP, resistive or another exact panel and controller.
The final approval record should connect touch technology, physical condition, electrical path, driver and calibration and application to the tested configuration and date. It should also name the responsible party, exceptions and change triggers so quotation review and bulk inspection use the same baseline.
Applying This Guide to an AONPOS Enquiry
AONPOS identifies Self Service and Payment Kiosk as one of its two core product lines. Project suitability must still be reviewed for the exact enclosure, computing configuration, installed modules, payment terminal responsibility, site conditions and service access.
Treat every peripheral and module as model specific. Confirm whether it is included, optional or supplied by another party, then record its mounting, interface, software owner and acceptance test before approving a sample.
Common Procurement and Integration Errors
1. Promising all glove support. Generic touchscreen language does not define glove behavior. Correct it by requiring the team to identify PCAP, resistive or another exact panel and controller.
2. Using aggressive cleaners. Mechanical contact can create false or missing touches. Correct it by requiring the team to inspect surface contamination, damage, moisture, overlay and bezel pressure.
3. Recalibrating without recording the original state. Intermittent electrical faults may appear as calibration problems. Correct it by requiring the team to check controller cable, grounding, power and interference.
4. Ignoring grounding. Recalibration cannot fix an unsupported input method. Correct it by requiring the team to record driver, firmware, operating system and calibration state.
5. Testing with a different panel or glove. A working desktop touch test can still fail the application workflow. Correct it by requiring the team to test touch targets, gestures and screen edges in the real kiosk interface.
Buyer Checklist Before Approval
1. Touch technology: Identify PCAP, resistive or another exact panel and controller.
2. Physical condition: Inspect surface contamination, damage, moisture, overlay and bezel pressure.
3. Electrical path: Check controller cable, grounding, power and interference.
4. Driver and calibration: Record driver, firmware, operating system and calibration state.
5. Application: Test touch targets, gestures and screen edges in the real kiosk interface.
Frequently Asked Questions
Which requirement should be confirmed first?
Identify PCAP, resistive or another exact panel and controller. This should be agreed before model selection because generic touchscreen language does not define glove behavior.
What evidence is needed for physical condition?
Inspect surface contamination, damage, moisture, overlay and bezel pressure. Record the exact model, installed option, software or driver condition and observed result. Mechanical contact can create false or missing touches.
What should the representative sample test cover?
The sample should verify electrical path, driver and calibration and application as well as the buyer's complete workflow. Save the inputs, expected result, observed result, configuration and test date so the quotation and bulk units can be checked against the same baseline.
When is a focused retest necessary?
Review and retest the affected functions when a change to touch technology, physical condition, electrical path or driver and calibration can alter the approved result. The change record should identify what changed, which previous evidence remains valid and which test must be repeated.
Request a Model Specific Review
Share the kiosk workflow, enclosure format, required modules, payment responsibility, software environment, site conditions and sample criteria with AONPOS. Request a model specific review before project approval.
Related AONPOS Resources
1. Payment Kiosk Collection: https://aon-postech.com/collections/payment-kiosk
2. Payment Kiosk FAQ: https://aon-postech.com/pages/payment-kiosk-faq
3. Payment Kiosk Knowledge: https://aon-postech.com/blogs/knowledge-for-payment-kiosk
4. Request a Demo or Configuration Review: https://aon-postech.com/pages/get-demo