deskthority

Hey lads, need some help over here.
I recently bought a Soarer's converter from orihalcon, to start using my AT and XT keebs, and I have this one personal favourite, it was working perfectly for a few days, and now whenever I plug it in and start pressing stuff it doesn't actually give any output.
I've included a pic of what I can see in hid_listen.exe, as you can see no actual key codes are being sent.
https://imgur.com/a/T0xMMiG

I tried with other keyboards, works perfectly (although they are AT and not XT, could that be the reason even if the scan codes are correct?)
Any tips on what I can do, or something I've messed up? Thanks!

Well, it's seeing the keyboard, and it detects as XT. What's triggering those rFF characters? Are they happening on your keystrokes or do they just show up automatically?

Muirium wrote: ↑

15 Mar 2021, 12:17

Well, it's seeing the keyboard, and it detects as XT. What's triggering those rFF characters? Are they happening on your keystrokes or do they just show up automatically?

Yep, happening on keystrokes (once on down and once on up)
That's what's weird, apparently "r[Hex code]" means a byte is read from the keyboard, no clue what FF means (I don't get FF on other keyboards with valid keystrokes), then it's supposed to be "+[HID code]" and "d[translated HID code]" on the downstroke, but the last 2 parts are missing as well.

Sounds like something is up with that keyboard. You said it worked before?

Muirium wrote: ↑

15 Mar 2021, 13:21

Sounds like something is up with that keyboard. You said it worked before?

so i have disassembled the keeb, and noticed that when i held the PCB and cable at different angles it works sometimes. So root of all evil is cable strain, I have now routed the cable through the case differently, works for now, will see if itholds up, might just rewire the connector at the end of the cable if it starts acting up again.

And so another case was sealed, thanks to Soarer, private keyboard investigator.