-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for RT protocol to ibmpc_usb #723
Comments
Hi, Do you have the keyboard? |
Thanks. I think the help I need is adding to ibmpc_usb handling for keyboards with RT protocol and their different key codes so that when it detects an RT keyboard it uses the right codes. Those codes go with this layout: I tried my RT keyboard with a standard ibmpc_usb hex.
Some keys in RT protocol are different than PS/2, so we get different results. Caps Lock turns on Num Lock light but does lock caps. ESC registers as F13. Insert registers as / Delete registers as End Home registers as Page Up End registers as Insert Page Up registers as Page Down Page Down registers as Delete NumLock registers as ESC / registers as NumLock
Print Screen sends Scroll Lock sends Pause registers as Home The keyboard has a speaker. I have it connected to C6 on my Pro Micro 32U4. It seems that Soarer implemented RT support before disappearing, but I'd prefer to use TMK. |
Its keyboard ID is BFB1, not BFB0. Interesting. What is layout of your keyboard? |
I will handle RT keyboard as a kind of Terminal keyboard. It looks equivalent to IBM 101-key/102-key Terminal keyboard, as for scan code. The current converter firmware supports keymap for 122-key Terminal by default. http://www.tmk-kbd.com/tmk_keyboard/editor/unimap/?ibmpc_usb_32u4_terminal ESC, PrintScreen, ScrollLock and Pause on RT keyboard can be remapped with F13, F23, F24 and Home on Keymap Editor recpectively. Current firmware doens't support RT LED indicator, Do you know how the speaker is connected to the pin and how we can control it? Does Soarer's support it? |
Try this patch and check if the indicators show their states.
|
Here are a couple images of mine: Mine is NOS and has differences compared to those shown in the IBM documentation, mainly that the split left space keys and ISO Enter keys are not printed. There are also no identifying labels on the back of mine. Very unusual. There's a DT thread with many images of the interior for this type of keyboard and how the speaker is connected - seems to be simple 2-wire https://deskthority.net/viewtopic.php?f=62&t=4101. I'm assuming that like other IBM keyboard speakers, the host was intended to send directly. I will have to take mine apart soon, as I've noticed that several keys only register if I press them down hard and hold them down. There's no way it could be usable at this point because of this. The keyboard is capacitive (Brother dome and foil) so I'm wondering if there's something going on inside that's causing the capacitance to not register properly. The cord is long and thick, but I used 1k pullups on clock and data. I am also directly connecting my converter to the computer - no hubs. I tried patching the two files in question but it's possible I did something wrong because after flashing and rebooting the console gets flooded and causes QMK Toolbox to freeze. |
Use hid_listen, QMK Toolbox won't work as debug console. https://github.com/tmk/tmk_keyboard/wiki#debug-console Did Capslock and NumLock LED indicator work? |
Scan code Set 3 IBM RT and IBM Terminal 101-key/102-key have same scan codes.
|
Hi Hasu!
Would you be willing to add support for RT protocol? Codes are similar to PS/2 but with some differences described in the documentation below page 482-502.
https://archive.org/details/bitsavers_ibmpcrt75XferenceVolume1Jun87_19098532/page/n481/mode/2up
The text was updated successfully, but these errors were encountered: