Test.InputResolution

發行項
02/27/2017

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

Associated requirements	Device.Input.PrecisionTouchpad.Precision.InputResolution System.Client.PrecisionTouchpad.PrecisionTouchpad See the system hardware requirements.
Platforms	Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86
Expected run time	~2 minutes
Categories	Certification
Type	Manual

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 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\

Send comments about this topic to Microsoft

共用方式為