Precision Touchpad Test Error Messages

In this topic:

General error messages

 

Error number Message Description

1

Explicitly failed by user

Operator failed the iteration/test by using a hotkey.

2

Failed too many iterations: #

Too many iterations failed. Includes the number of failed iterations.

3

Received input at an unexpected time

The test did not expect to receive data, but data was received (example: Z-Height Detection test).

5

Received too many contacts:#

Operator placed too many contacts down. Includes the number of detected contacts.

6

Received too few contacts:#

Operator placed too few contacts down. Includes the number of detected contacts.

7

Test didn't receive enough data

If the error occurs on contact lift, it indicates that the test required contacts to last a particular duration, but that duration was not met. If it occurs on contact down, the error indicates that the test received a zero-contact frame as the first data – this can be caused by a non-capacitive button press, but is more likely a protocol error (device sending an empty frame).

9

Received unexpected contact

On a test that requires a specific number of contacts, this error indicates that a contact came down after a contact went up. All contact-downs should occur before all contact-ups.

10

Geometry data outside expected range:#

This error only occurs during the Geometry Reporting test. Width and/or height were outside the range expected by the test. Includes the detected width and height in himetric units.

11

Contact displacement too large:#

The contact’s overall X/Y displacement was too large. Includes the detected displacement in himetric units.

12

Interaction too short:#

The interaction length (the time from first contact down to last contact up) was too short. Includes the detected interaction length in milliseconds.

13

Interaction too long:#

The interaction length (the time from first contact down to last contact up) was too long. Includes the detected interaction length in milliseconds.

14

Packet too far from edge:#

Indicates that the first packet was too far from the edge of the touchpad. Includes the distance from the edge in himetric units.

15

Contact didn't move in straight line:#

The contact deviated too much from a line of best fit. Includes the maximum detected deviation from the line in himetric units.

16

Line drifted off axis too much:#

This error only occurs during the Linearity tests. The contact’s displacement in either X or Y was too large. Includes the deviation in himetric units.

17

Not enough separation of points:#

This error only occurs during the Converge/Diverge tests. If converging, the beginning points were too close to each other. If diverging, the ending points were too close to each other. Includes the distance between points in himetric units.

18

Too much separation of points:#

This error only occurs during the Converge/Diverge tests. If converging, the beginning points were too far from each other. If diverging, the ending points were too far from each other. Includes the distance between points in himetric units.

20

Positional delta too large:#

The position delta between two packets was too large for the test. Includes the detected delta in himetric units.

23

Device doesn't support minimum number of contacts:#

The device doesn’t support the required minimum number of contacts. Includes the number of supported contacts.

24

Device supports too many contacts:#

The device supports more than the required maximum number of contacts. Includes the number of supported contacts.

25

Packet not in expected position:#

This error only occurs during the Positional Accuracy test. Indicates that the packet’s location was not in the required position. Includes the packet’s location in himetric units.

26

No packets outside border region

On tests that involve drawing a straight line with the precision contact rig, this error indicates that the entire line was in the border region of the touchpad.

27

Saw packet travel backwards

This error only occurs during the Linearity tests. Indicates that a packet was seen travelling backwards in relation to the rest of the packet stream.

28

Too low DPI:#

This error only occurs during the Input Resolution test. Indicates that the logical range of X/Y on the touchpad, combined with its physical dimensions, do not support the required DPI. Includes the calculated DPI.

29

Saw confidence bit set after cleared

This error only occurs during the Confidence Reporting test. Indicates that a contact was seen setting the confidence bit after it had been cleared for that contact.

30

Confidence bit set too long:#

This error only occurs during the Confidence Reporting test. Indicates that the confidence bit was not cleared early enough in the contacts lifetime. Includes the length of time the confidence bit was set in milliseconds.

31

Too low percent of logical coordinates found:#

This error only occurs during the Input Resolution test. The X or Y coordinate in packets received in a given iteration must include a minimum percent of the total range. Includes the percent actually found.

32

You must run this test elevated

PTLogo.exe must be started from an elevated command prompt window for this test.

33

Device does not support selective reporting

Device does not support selective reporting.

34

Duplicate packets:#

This error only occurs during the Linearity tests. Indicates that two consecutive packets had the same X/Y location, even though the contact was moving. Includes the scantime of the detected duplicate packet.

35

Logical coordinate not found:#

This error only occurs during the Input Resolution test. Indicates that a required X or Y coordinate was never reported by any packet during the iteration. Includes the required coordinate in logical units.

36

Confidence always set

This error only occurs during the Confidence Reporting test. Indicates that the confidence bit was never cleared.

HID-specific error messages

 

Error number Message Description

1

Invalid X bitsize

The bit count for Tx/Cx is outside the range [1,32]. Only checked if C is present.

2

Invalid Y bitsize

The bit count for Ty/Cy is outside the range [1,32]. Only checked if C is present.

3

Invalid packet transition

This can present itself with any of the following error messages:

  • Last move location different

    The coordinates of the tip switch clear report for a given contact are not the same as the coordinates of the last tip switch set report.

  • Missing tip-on

    The first report didn't have the tip switch set, or there were two packets in a row without the tip switch set.

  • Missing tip

    A contact present in the previous reported frame with the tip switch set was not found in the current frame.

4

Invalid scan time

This can present itself with any of the following error messages:

  • (Not present)

    The device does not support the scan time usage in its descriptor.

  • (Range)

    The scan time reported is outside the logical range.

  • (Delta > 10ms more than 1% of the time)

    The delta in scan time from frame to frame exceeds 10ms more than 1% of the time.

  • (Delta > 16.7ms)

    The delta in scan time from frame to frame was larger than 16.7ms.

  • (Duplicate)

    The scan time was duplicated in two sequential frames.

  • (Differing values in frame)

    The scan time value was not identical for all reported contacts of a given frame.

  • (Drifted from wall clock)

    The deltas in scan time drifted too far from system time. > 5% clock drift.

5

Invalid XY

This can present itself with any of the following error messages:

  • (Invalid T)

    With C, Width, or Height present, Tx and/or Ty were not present or not within their logical range.

  • (Invalid C)

    With T, Width, or Height present, Cx and/or Cy were not present or not within their logical range.

  • (Invalid T/C combo)

    T was not contained within bounding box formed by C, Width, and Height.

6

Invalid width or height

This can present itself with any of the following error messages:

  • ""

    Width and/or height was present, and either one was not present, or one/both were outside their logical range.

  • (0)

    Width and/or height were present, but the logical value for one/both was zero.

8

Invalid contact ID

This can present itself with any of the following error messages:

  • (Not present)

    The device does not support the ContactID usage in its descriptor.

  • (Dupe in frame)

    A contact ID was duplicated in a single frame (sometimes caused by an incomplete frame being reported).

14

No data in frame

There were no contacts in the frame, and the physical button is not down, but the physical button was not previously up.

16

Invalid # of contacts in frame

The number of contacts in the frame did not match the reported Actual Count.

17

More than max contacts in frame

The number of contacts in the frame exceeded the maximum number of contacts the device supports per MAX COUNT.

18

Sampling rate out of range

The sampling rate was not in the allowed range for the number of contacts reported.

21

Invalid actual count

The device does not support the ActualCount usage in its descriptor.

22

Invalid confidence

The confidence switch was not set (and the test was not the confidence test).

See Also

Show:
© 2014 Microsoft