<![CDATA[James's Programming Page — WinHidDevice OutputReportByteLength is wrongly read]]> https://swforum.seekye.com/topic/10152/ Thu, 13 Oct 2022 17:04:05 +0000 PunBB <![CDATA[Re: WinHidDevice OutputReportByteLength is wrongly read]]> https://swforum.seekye.com/post/13140/#p13140 Do you mean GetMaxOutputReportLength()? HIDSharp gets its value from Windows's OutputReportByteLength. It does try to reconstruct the descriptor (Windows doesn't give access to it, unlike Linux and Mac), but the lengths themselves come directly from Windows.

What's your report descriptor look like? I'll bet there's something Windows handles differently or incorrectly.

]]> Thu, 13 Oct 2022 17:04:05 +0000 https://swforum.seekye.com/post/13140/#p13140 <![CDATA[WinHidDevice OutputReportByteLength is wrongly read]]> https://swforum.seekye.com/post/13138/#p13138 Hi,

We have a custom HID device that has OutputReportByteLength set to 4 bytes in firmware, but when we open it in Windows, the value is equal to the InputReportByteLength, i.e. 31.

Is it Windows error ?
Linux reports correct value - HidSharp was not used there to test.

]]> Tue, 31 May 2022 08:45:44 +0000 https://swforum.seekye.com/post/13138/#p13138