Applies to: Docklight Scripting, Article ID: dl_faq040
You can use Docklight Scripting V2.2 (or higher) as USB HID terminal to access USB HID “Custom Class” devices, and test your protocol implementation by sending or receiving HID report data. You can use both, a HID report-based approach that shows you the individual outgoing / incoming reports. Or an application-layer approach where you only display the actual payload data (e.g. a text-based protocol you implemented), but not the original report frame including report ID (if used) and trailing zero fill bytes. PLEASE NOTE: * You cannot access Mouse/Keyboard or other standard HID input device classes. Windows immediately opens these for exclusive access and does not allow a second client application to control them. * To comply with Windows 10 behavior, USB HID devices are opened with Access Mode = Shared. So you can actually tap into other application connections and use Docklight Scripting to protocol the device responses, but you will not see the Output Reports the other Windows application (besides Docklight Scripting) sends to the device. * USB HID is a fresh addition, so any feedback on this feature, especially on things missing or not working as expected, is highly appreciated!