Support for Gaomon M106K

[OneBadPeanut]

Description

Id like this tablet to be supported so I could play osu with better drivers please :)

[InfinityGhost]

Export diagnostics in the GUI and send it here. That can help us get a base to start off with.

[OneBadPeanut]

How would I do that?

[InfinityGhost]

• Start OpenTabletDriver.UX.Wpf.exe (assuming you're on Windows)
• In the menu, click Help -> Export diagnostics
• This will show a save file dialog, which you can just save it and drag it here or upload and link

[OneBadPeanut]

Alright this should be it this time. Better than my last post which was a bigline of text
gaomon m106k.txt

[InfinityGhost]

Writing this here for reference

{
  "VendorID": 9580,
  "ProductID": 110,
  "MaxInputReportLength": 8
}

[InfinityGhost]

Does your release have OpenTabletDriver.Console.exe in it?

[OneBadPeanut]

yes it does

[InfinityGhost]

Save this text as Configurations/Gaomon/M106K.json in the configurations folder

{
  "Name": "Gaomon M106K",
  "DigitizerIdentifier": {
    "VendorID": 9580,
    "ProductID": 110,
    "InputReportLength": 8,
    "OutputReportLength": 0,
    "ReportParser": "OpenTabletDriver.Vendors.Gaomon.GaomonReportParser",
    "FeatureInitReport": null,
    "OutputInitReport": null
  },
  "AlternateDigitizerIdentifier": {
    "VendorID": 0,
    "ProductID": 0,
    "InputReportLength": 0,
    "OutputReportLength": 0,
    "ReportParser": null,
    "FeatureInitReport": null,
    "OutputInitReport": null
  },
  "AuxilaryDeviceIdentifier": {
    "VendorID": 0,
    "ProductID": 0,
    "InputReportLength": 0,
    "OutputReportLength": 0,
    "ReportParser": null,
    "FeatureInitReport": null,
    "OutputInitReport": null
  },
  "Width": 254.0,
  "Height": 158.8,
  "MaxX": 50800.0,
  "MaxY": 31760.0,
  "MaxPressure": 2047,
  "ActiveReportID": null,
  "Attributes": {},
  "DeviceStrings": {},
  "InitializationStrings": []
}

We still need to get device strings from the tablet with the console app, however.

[InfinityGhost]

• Make sure the GUI is closed
• Launch OpenTabletDriver.Daemon.exe by itself
• Using powershell, cd into the directory with OpenTabletDriver.Console.exe
• From there run the following, which if successful will return a string and save it to 201.txt which we will use for identification.

./OpenTabletDriver.Console.exe getstring 201 | Out-File ./201.txt

• Send that file or its contents here.

[OneBadPeanut]

I think I might've done something wrong but I will send anyways
201.txt
this was also in the bin folder where opentabletdriver.console was

[InfinityGhost]

oops, forgot we need a development build for the getstring command. https://github.com/InfinityGhost/OpenTabletDriver/actions/runs/278801343

[InfinityGhost]

You'll have to close the daemon and recopy that configuration, but otherwise redo the previous steps with the development build.

[OneBadPeanut]

201.txt
I got this once I did that, was daemon supposed to be closed?

[InfinityGhost]

This configuration should work almost correctly now, however we still need one more thing, the active report range. This is where you use the tablet debugger to see what the ReportID property changes to when dragging, hovering, and when the pen is off of the tablet.

{
  "Name": "Gaomon M106K",
  "DigitizerIdentifier": {
    "VendorID": 9580,
    "ProductID": 110,
    "InputReportLength": 8,
    "OutputReportLength": 0,
    "ReportParser": "OpenTabletDriver.Vendors.Gaomon.GaomonReportParser",
    "FeatureInitReport": null,
    "OutputInitReport": null
  },
  "AlternateDigitizerIdentifier": {
    "VendorID": 0,
    "ProductID": 0,
    "InputReportLength": 0,
    "OutputReportLength": 0,
    "ReportParser": null,
    "FeatureInitReport": null,
    "OutputInitReport": null
  },
  "AuxilaryDeviceIdentifier": {
    "VendorID": 0,
    "ProductID": 0,
    "InputReportLength": 0,
    "OutputReportLength": 0,
    "ReportParser": null,
    "FeatureInitReport": null,
    "OutputInitReport": null
  },
  "Width": 254.0,
  "Height": 158.8,
  "MaxX": 50800.0,
  "MaxY": 31760.0,
  "MaxPressure": 2047,
  "ActiveReportID": null,
  "Attributes": {},
  "DeviceStrings": {
    "201": "OEM02_T151_\\d{6}$"
  },
  "InitializationStrings": [
    200
  ]
}

[InfinityGhost]

I got this once I did that, was daemon supposed to be closed?

If I understand what you meant, the daemon exited after requesting the string? That's a separate issue on its own I'll tackle another time.

[OneBadPeanut]

It says no tablet detected so should i still use the dev build or switch to the other one

[InfinityGhost]

Does it still not detect if you change the DeviceStrings property to empty?

"DeviceStrings": {},

[OneBadPeanut]

it still is not detected. F

[InfinityGhost]

Re-export diagnostics and resend. I think something might have changed.

[OneBadPeanut]

gaomon m106k 2.txt
this is it now i left in everything this time so hopefully it helps

[InfinityGhost]

Okay, try setting this property to empty, restart the daemon and gui

  "InitializationStrings": []

[OneBadPeanut]

no but i got this as a message

[InfinityGhost]

This is gonna require USB packet sniffing the Gaomon driver to figure out what they're doing to open the device stream. https://discord.gg/P3GYdUS and later on we'll see what we can do.

[OneBadPeanut]

alright then I appreciate the help though

[OneBadPeanut]

This is what I also get in daemon.exe