HOGP Digitizer/Pen profile

[StaffanS]

Hi,

There are tons of documentation on how to make a mouse, keyboard or remote control work as a HOGP device, and I have successfully implemented both mouse and remote control support on my setup.

But my goal is to make a pen input device, and there is a HID profile clearly specified in USB HID definitions, and I have seen examples of this with Bluetooth HID (Classic) devices, where no additional drivers are needed on the host system.

I know that iOS typically has blocked HID devices except keyboard support, but Android, Windows and MacOS should allow all supported HID devices.

My question is:

Should I expect the same support for Pen/Digitizer HID device when using BLE, as for PenDigitizer HID over Bluetooth? Or is HOGP only restricted to the most common types - remote control, keyboard and mouse?

I have tried to create a HOGP device exposing a Pen HID device, which can be successfully paired to Windows and Android, and being displayed in the OS Bluetooth devices list as a 'pen'-device.

But when sending reports, there is no reaction on the host system.

Thanks for any help!

[Karl Ylvisaker]

Hello Staffans,

Thank you for your continued patience with this!
Apologies for the great delay you have seen in the handling of your ticket.

Should I expect the same support for Pen/Digitizer HID device when using BLE, as for PenDigitizer HID over Bluetooth? Or is HOGP only restricted to the most common types - remote control, keyboard and mouse?

I have discussed this with a couple of my colleagues, and unfortunately we do not have a clear cut answer for this.

I looked around on the Window's forums and found this documentation for supporting digitizer devices, have you taken a look at this already? It details the requirements in order to be recognized as a HID Pen/digitizer device.
If you make sure to meet these requirements, I should think that it would accept the reports.

To debug this further you could try to use window's event tracing or similar to capture a trace of the windows' side of things, to see if there is anything going wrong upon reception of the reports, or if there is anything unusual happening with the received reports (as opposed to a working keyboard / mouse's reports).

If this does not work, or nothing sticks out in the trace, I would recommend contacting window's support forum directly to ask them about what can be expected from Digitizer handling and recognition.

Best regards,
Karl

[StaffanS]

Hello Karl,

Thank you so much for your effort! Yes, I have indeed checked the requirements for being recognized as HID pen/digitizer device, and the report descriptor should be exactly as a known working device.

It is encouraging that you don't see any blocking issues yet for my intentions, and I will follow your suggestion of checking windows' event tracing to see if I can find any clues to the problem I see.

If I get to any conclusion, I will update the ticket with my findings!

Many thanks

Staffan 

[Karl Ylvisaker]

Hello again, Staffan

StaffanS said:

Thank you so much for your effort!

No problem at all, I am happy to help!
I am only sorry that I could not be of more help with this issue.

StaffanS said:

It is encouraging that you don't see any blocking issues yet for my intentions, and I will follow your suggestion of checking windows' event tracing to see if I can find any clues to the problem I see.

If the device is recognized and the reports are according to the requirements I do not see any reason why this should not work. In that case, I would hope that Windows' support forum could shed some light on it, or clarify what else might be missing.

StaffanS said:

If I get to any conclusion, I will update the ticket with my findings!

Great, I look forward to hearing what you uncover! :) 

Best regards,
Karl