Docklight News

TL;DR; Docklight Scripting V2.1 USB HID support didn't work on Windows 10. Here is an updated version with additional improvements: https://docklight.de/download/Docklight_Scripting.zip The Problem Apparently, Windows 10 has a different behavior concerning HID access than earlier versions. Docklight Scripting uses HIDAPI from Alan Ott / Signal 11, and the problem was recently detected and resolved in the HIPAPI implementation  (see  https://github.com/signal11/hidapi/issues/231 ).  The Solution We updated Docklight Scripting's HIDAPI code, so it can now successfully open a HID connection in Windows 10: We also added two Docklight-specific improvements concerning USB HID access: Added support for variable Output Report IDs You can work now with varying, non-zero Output Report IDs using the :I communication channel option, e.g. USBHID:4D8:F708:I Now the first character of your Send Sequences is used as the Output Report ID (instead of the def...

UPDATED 2016-06: See our latest extensions and USB HID related fixes for Windows 10 . Did you design a custom USB HID device and wonder why you cannot test its application protocol with the same ease as serial COM (RS232, ..) or network TCP connections?  Well we did, too, along with quite a few of our users. So it was high time to get this feature off the wishlist and into the software. See the Docklight FAQ - USB HID , or download the new software directly from here:  https://docklight.de/download/Docklight_Scripting.zip While we are still on our way to a concise and fully documented implementation, we found the current V2.0.200 version already very useful for our own projects with fullmo.de - a Microchip PIC based communication gateway running a custom ASCII protocol via USB HID. How to use Docklight Scripting V2.0.200 can connect to your custom HID device via the VID (vendor ID) and PID (product ID) code, if you use the following commun...