Test.LinearityVertical

This test verifies that the touchpad reports a straight line (that corresponds to contact movement) when a single contact is moved vertically back and forth across the surface of a touchpad (within a tolerance of .5mm).

Test details

Associated requirements

Device.Input.PrecisionTouchpad.Precision.Linearity Device.Input.PrecisionTouchpad.Precision.MotionJitter 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.

This test requires very precise movement in a straight line. We recommend that you perform this test by using a precision rig or other precision device that is capable of straight line movement without any jitter.

  1. Place a precision contact slightly outside the top edge of the touchpad.

  2. Drag the contact in a straight line from top to bottom across the touchpad.

  3. Drag the contact the other direction from bottom up to top.

  4. Repeat this pattern for a total of five iterations.

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Input Testing.

Error Description/Workaround

[15] contact didn’t move in straight line

Reported path strayed varied from a straight line by more than the allowed tolerance.

[14] packet too far from edge: ###

  • Swipe must start at or before the edge.

  • Swipe must go all the way to the opposite edge. Performing swipe too quickly might not allow the device to fully report.

More information

Command syntax

Command Description

ptlogo.exe Test.LinearityVertical.json

Runs the test.

File list

File Location

ptlogo.exe

<testbinroot>\input\PrecisionTouchpad\

config.json

<testbinroot>\input\PrecisionTouchpad\

Test.LinearityVertical.json

<testbinroot>\input\PrecisionTouchpad\

Send comments about this topic to Microsoft