Amtelco KB163 Autohotkey help?
-
antigua1103
- Location: United States
- Main keyboard: Xd75 78g zealios
- Main mouse: Mx master s2
- Favorite switch: Yes
Does anyone have a Amtelco KB 163 and use autohotkey? I was told by the buyer that I would be able to use all of the extra keys using autohotkey but the guide I've managed to find does not work for me.
-
MMcM
- Location: San Francisco
- Main keyboard: Das Keyboard
- Main mouse: Logitech
- Favorite switch: MicroSwitch Hall Effect
- DT Pro Member: 0240
I guess nobody is yes to both questions, so I'll try from just the first. (I've never tried autohotkey.)
Is this the USB model or the AT model? If AT, are you plugging it into a PS2 port with a passive adapter or using a USB converter? Because I wouldn't be surprised if some of the latter lost the extended codes. Do they input nothing at all or duplicate a regular code (like y for ON or i for BYE)?
I don't know where Windows gets SC062 as described on the page linked to in your other post here. But, according to my notes, what it sends is more sensible than that suggests. The custom extended codes start with E2, just as some of the standard ones added after the original protocol start with E0. (And Pause starts with E1.)
Soarer's doesn't help because that prefix gets dropped in the first conversion stage.
My thought was that the best bet would be to extend QMK to build a converter, since it already has the low-level PS2 input routines from TMK. I sketched out how that'd work but then discovered I'm out of the right DIN parts here. I'll update here when I get back to it.
Were you thinking to put some interesting keycaps on all the funny keys?
Is this the USB model or the AT model? If AT, are you plugging it into a PS2 port with a passive adapter or using a USB converter? Because I wouldn't be surprised if some of the latter lost the extended codes. Do they input nothing at all or duplicate a regular code (like y for ON or i for BYE)?
I don't know where Windows gets SC062 as described on the page linked to in your other post here. But, according to my notes, what it sends is more sensible than that suggests. The custom extended codes start with E2, just as some of the standard ones added after the original protocol start with E0. (And Pause starts with E1.)
Soarer's doesn't help because that prefix gets dropped in the first conversion stage.
My thought was that the best bet would be to extend QMK to build a converter, since it already has the low-level PS2 input routines from TMK. I sketched out how that'd work but then discovered I'm out of the right DIN parts here. I'll update here when I get back to it.
Were you thinking to put some interesting keycaps on all the funny keys?
-
MMcM
- Location: San Francisco
- Main keyboard: Das Keyboard
- Main mouse: Logitech
- Favorite switch: MicroSwitch Hall Effect
- DT Pro Member: 0240
Okay, I picked up some DIN5 connectors from Jameco and it seems to be working.
For now, it's in an amtelco_kb163 commit in a branch in my working QMK fork.
I didn't put any thought into the key mappings: I just spread F13-F24 around in the various extension blocks. Plus, since this is Winkeyless, it puts GUI on the top-left ON key.
For now, it's in an amtelco_kb163 commit in a branch in my working QMK fork.
I didn't put any thought into the key mappings: I just spread F13-F24 around in the various extension blocks. Plus, since this is Winkeyless, it puts GUI on the top-left ON key.
- kb163.jpg (383.82 KiB) Viewed 2658 times