Test.InputResolution (2bc34740-73c5-4a63-a9fd-a7bab6051a55)

Article
05/18/2022

This test verifies the device resolution by ensuring that it can support what it reports. Between two slow swipes, every logical unit of X should be hit, and every value of Y when moving down and up vertically.

Test details


Specifications	Device.Input.Digitizer.PrecisionTouchpad.InputResolution Device.Input.Digitizer.PrecisionTouchpad.HIDCompliant
Platforms	Windows 10, client editions (x86) Windows 10, client editions (x64) Windows 10, client editions (Arm64)
Supported Releases	Windows 10 Windows 10, version 1511 Windows 10, version 1607 Windows 10, version 1703 Windows 10, version 1709 Windows 10, version 1803 Windows 10, version 1809 Windows 10, version 1903 Next update to Windows 10
Expected run time (in minutes)	2
Category	Compatibility
Timeout (in minutes)	120
Requires reboot	false
Requires special configuration	false
Type	automatic

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

Device.Input additional documentation

Running the test

Before you run the test, complete the test setup as described in the test requirements: Mouse or other Pointing Device Testing Prerequisites.

Drag one precision contact across the touchpad at 1-2mm/second from left to right, and again from right to left. (This can be done anywhere in the middle 80% of the touchpad surface.)

All Y-axis movement or jitter is ignored in this test when measuring X values (and vice-versa), so if the PT3 cannot move smoothly at a slow pace, a precision contact can be moved by hand across the touchpad to avoid extra friction.
Repeat vertically, dragging first from top to bottom, then from bottom to top.

Note

If all logical x/y coordinates are hit after one swipe on that axis, the test automatically passes without a swipe in the other direction. This is expected.

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

For troubleshooting information, see Troubleshooting Device.Input Testing.

Error	Description/Workaround
[20] positional delta too large	There was a jump in X coordinates between 2 packets. To investigate, open the Hid log in Excel, add a column for DeltaX, and populate it with the differences between the X's. You can then filter out 0s (packets in which the contact has not yet moved horizontally), and expected 1s.
[35] logical coordinate not found	Either the minimum or maximum value was never hit in the two passes. The number given is the X or Y value which was not hit (depending on whether the iteration is for horizontal or vertical drags, respectively).
[31] Too low percent of logical coordinates found	Less than 80% of the logical coordinates were reported during the duration of the test.

[20] positional delta too large

There was a jump in X coordinates between 2 packets.

To investigate, open the Hid log in Excel, add a column for DeltaX, and populate it with the differences between the X's. You can then filter out 0s (packets in which the contact has not yet moved horizontally), and expected 1s.

[35] logical coordinate not found

Either the minimum or maximum value was never hit in the two passes. The number given is the X or Y value which was not hit (depending on whether the iteration is for horizontal or vertical drags, respectively).

[31] Too low percent of logical coordinates found

Less than 80% of the logical coordinates were reported during the duration of the test.

More information

Command syntax

Command	Description
ptlogo.exe Test.InputResolution.json	Runs the test.

File list

File	Location
ptlogo.exe	<testbinroot>\input\PrecisionTouchpad\
config.json	<testbinroot>\input\PrecisionTouchpad\
Test.InputResolution.json	<testbinroot>\input\PrecisionTouchpad\

Share via