Hello all,
Im new to the mechanical keyboard world and have absolutely no idea what Im doing but so far love it. Im a mechanical engineer, I know more about physics and actuators and switches than coding and electrical situations. Right now I have an IBM Model F XT and an Arduino Leonardo with soarers converter hex file uploaded to it. So far the only keys that work on it are "D" "P" "." (numpad period) "0" (numpad zero) and Spacebar. The rest of the keys show nothing in the HID_Listen. I feel as if the program has identified the keyboard as the wrong set (should be set 1, maybe its auto chose set2 or set 3). I have no idea where to go from here and could use any and all help! Please be basic with your instructions, including what software to go to and how to upload it the the arduino etc...
Thanks!
Tator
Ps, I get nothing unless i press the reset button on the arduino twice in quick succession making its LED slowly flash for a few seconds.
IBM Model XT Soarers Code Help
-
orihalcon
- Location: Des Moines / Cedar Falls, IA, USA
- Main keyboard: IBM Model F107
- DT Pro Member: 0190
Check my auction here: http://www.ebay.com/itm/282575691272
....Within I've linked some basic instructions that I wrote on how to configure the Soarer's Converter. I am not a programmer by any means and all credit goes to Soarer for this awesome firmware. I have just explained his instructions in a little different way from a non-programmer's perspective.
You can use force code set1, but every XT I've ever tried one with is auto-detected, so to me, I would say that there would more likely be an issue with your specific XT keyboard hardware potentially. There'd have to be an awful amount of dust for it to knock out all but three keys, but something like an acidic drink spill like orange juice or if it was sitting in water for a long time could have eaten a lot of the traces. Anything that major you should see evidence of without fully taking it apart though.
Best of luck and do let us know if you figure out what the issue was!
....Within I've linked some basic instructions that I wrote on how to configure the Soarer's Converter. I am not a programmer by any means and all credit goes to Soarer for this awesome firmware. I have just explained his instructions in a little different way from a non-programmer's perspective.
You can use force code set1, but every XT I've ever tried one with is auto-detected, so to me, I would say that there would more likely be an issue with your specific XT keyboard hardware potentially. There'd have to be an awful amount of dust for it to knock out all but three keys, but something like an acidic drink spill like orange juice or if it was sitting in water for a long time could have eaten a lot of the traces. Anything that major you should see evidence of without fully taking it apart though.
Best of luck and do let us know if you figure out what the issue was!