Skip to content

Commit f52354e

Browse files
committed
ConfigurationGuide: Add Common device strings section
The following jq command was used to print out the device strings: jq '{ name: .Name, DeviceStrings: .DigitizerIdentifiers[].DeviceStrings } | select(.DeviceStrings != null)' OpenTabletDriver.Configurations/Configurations/**/*.json
1 parent 8fc2126 commit f52354e

1 file changed

Lines changed: 22 additions & 0 deletions

File tree

site/_wiki/Documentation/ConfigurationGuide.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -265,6 +265,28 @@ The configuration format is a dictionary where the key matches the descriptor
265265
ID (up to 255) and the value is a regex that the string descriptor's value must
266266
match with.
267267

268+
While they are similar to initialization strings, the difference here is that
269+
we read the returned output when initializing the string, and as such can match
270+
tablets based on its contents.
271+
272+
#### Common device strings
273+
274+
Below are some usually common device strings for various vendors.
275+
276+
These are not guaranteed to be correct across all models for the vendor, but
277+
may help some people decode their meaning.
278+
279+
| Index | Value |
280+
| ----: | :---- |
281+
| 2 | XP-Pen: Model Name
282+
| 4 | XP-Pen: Firmware Build ID
283+
| 5 | XP-Pen: Firmware Build String
284+
| 23 | VEIKK: Firmware Build Date
285+
| 201 | Gaomon, Huion, and some other UC-Logic based: Firmware Build ID
286+
287+
Be wary that probing strings can also change behavior in the device, which can
288+
usually be rectified by replugging the tablet.
289+
268290
## Validating values
269291

270292
Assuming you now have a configuration that correctly identifies your tablet,

0 commit comments

Comments
 (0)