Changing the report descriptor to match what you suggested seems to have cleared up the problem. The device is now recognized and works properly under 10.4.
Thank you for your advice.
Hi john,
In Tiger, Mac OS X now requires that the device be HID compliant in report protocol mode. It will not operated a device in boot protocol. This probably explains why Windows is able to still use the device. Anyway, I noticed 2 glaring issues with this portion of the report descriptor:
Logical Minimum......... (128)
Logical Maximum......... (127)
Report Size............. (8)
Input................... (Constant, Variable, Absolute, No Wrap, Linear, Preferred State, No Null Position, Bitfield)
Report Count............ (6)
Usage Page (Keyboard/Keypad)
Usage Minimum........... (1)
Usage Maximum........... (101)
Input................... (Data, Array, Absolute)
1) The Logical Min and Max should match the usage Min and usage Max when used to declare an usage range array Item. This is necessary as a value in the array corresponds to a matching usage. See HID Spec.
2) The Usage Min starts at 1 and not 0. This does not match the advised keyboard report descriptor outlined in the appendix of the HID Spec. This may not be necessary if your device does not have a null state, but since you device does work in Boot protocol mode, I'm guessing this is NOT the case.
- Rob
On Feb 23, 2006, at 4:46 PM, John Chapman wrote:
Sure - I've removed everything not directly related to the device, and it's attached as a text file.
John
On Feb 23, 2006, at 3:49 PM, Rob Yepez wrote:
Can you send me the HIDReportDesciptor of the device? This can be acquired using USB Prober in the /Developer/Applications/Utilities
Thanks,
- Rob
On Feb 23, 2006, at 11:04 AM, John Chapman wrote:
<USB Bus Probe.txt>
John
On Feb 23, 2006, at 11:57 AM, Rob Yepez wrote:
Hi John,
How does this utility work? Does the device present a USB keyboard interface, or does it create a "virtual" keyboard driver?
The "can't recognize this keyboard" message is new to 10.4. This is useful for detecting the proper keyboard mappings for 3rd party keyboards (ie JIS, ANSI, ISO). To skip detection, you can just close the window and you will no longer be pestered about calibrating the keyboard.
- Rob
On Feb 23, 2006, at 10:36 AM, John Chapman wrote:
Hi all,
I've developed a keyboard emulator which works perfectly on Windows 2000 and XP, as well as OS X up to verision 3.9.
I recently tried the device on a machine running 10.4 and was unsuccessful. The device appears properly in the USB tree of the 'about this mac' window, but no keystrokes are ever received by the computer.
When the keyboard tester utility popped open, we weren't able to make our emulator register. I received the message 'can't recognize this keyboard' and in fact, the utility appeared to hang.
I used a command line prompt to disable the keyboard utility, but the device is still not recognized.
Any ideas or insight would be appreciated.
John
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
