geekhack
geekhack Community => Keyboards => Topic started by: ConiKost on Mon, 19 September 2016, 09:50:51
-
Hi there!
I've found an old IBM Model M 122. It's the one with the older chassis. As they are no LEDs, i think, that was not a PS/2 version. Unfortunately, there is no part number, as the sticker is simply missing.
I couldn't test this one, as the cable has been internally cut off by someone :mad:
So I would like to attach Soarer's Converter, but I don't know the pin assignment on the internal controller. Does someone know this?
The internal controller PCB says "IBM 1391331".
Pictures: https://imgur.com/a/CzopY
Thanks!
-
Hi there!
I've found an old IBM Model M 122. It's the one with the older chassis. As they are no LEDs, i think, that was not a PS/2 version. Unfortunately, there is no part number, as the sticker is simply missing.
I couldn't test this one, as the cable has been internally cut off by someone :mad:
So I would like to attach Soarer's Converter, but I don't know the pin assignment on the internal controller. Does someone know this?
The internal controller PCB says "IBM 1391331".
Pictures: https://imgur.com/a/CzopY
Thanks!
I can't look at the picture but hopefully the wire are still there.
IIRC:
black: 5V
red: data
yellow: clock
white: ground
silver: ground/shield
-
If that would be so easy ;-)
That, whats left of the cable doesn't have any colors..
The part number says 1391136
-> https://imgur.com/a/72DuH
-
If that would be so easy ;-)
That, whats left of the cable doesn't have any colors..
The part number says 1391136
-> https://imgur.com/a/72DuH
Can't help till later today. Will try to give you a shout after I'm off work unless someone else has the answer before then!
-
No Con. -> [] [] <- +5V
Clock -> [] [] [] <- Data
PCB -> ------------------
^
GND
That should be the layout of the connector.
-
If you remove those pins from that black connector, you should be able to see the wire colors. Also, the diagram above is correct.
-
That is how it would be on the F-122, but I didn't realize that the M connected the same way.
-
Thanks guys! I've now attachted my converter to the Model M.
Well, I am not sure, why it's not working 100%. The converter itself is fine, as another Model M works perfectly fine with it.
Standard 102 Keys seems to work fine, F1-F24 produces some keycodes, but the extra 10 keys on the left seems to do nothing except 2 keys. The don't even produce an keycode according to xev.
hid_listen doesn't detect anything and reports "waiting for device.." (windows and linux).
Any ideas?
-
Thanks guys! I've now attachted my converter to the Model M.
Well, I am not sure, why it's not working 100%. The converter itself is fine, as another Model M works perfectly fine with it.
Standard 102 Keys seems to work fine, F1-F24 produces some keycodes, but the extra 10 keys on the left seems to do nothing except 2 keys. The don't even produce an keycode according to xev.
hid_listen doesn't detect anything and reports "waiting for device.." (windows and linux).
Any ideas?
If you are using Soarer's procedure, did you flash the Teensy with pjrc's code and then run Soarer's hex code? There is something similar when using non-Teensy breakout boards, there are several threads on it.
When I have done that, it has activated most or all of the keys, then they can be re-assigned from there.
-
If you are using Soarer's procedure, did you flash the Teensy with pjrc's code and then run Soarer's hex code? There is something similar when using non-Teensy breakout boards, there are several threads on it.
Yes. "Firmware" and Hex Code are correctly flashed. Currently, the Hex Code is empty, as I don't do any remappings. First, I wanted so see, which key reports what..
As I said, the Converter works. Using an "normal" PS/2 Model M 122 Keys 1397003 works just fine. That one is found via hid_listen and every key reports a keycode.
When I have done that, it has activated most or all of the keys, then they can be re-assigned from there.
Most of my keys are working. Only the 2 of 10 extra keys on the left seems to do work and one key on the numpad also does nothing. All of the rest of the keys do work and produce a keycode.
-
If you didn't get to wire colors, did you take notice that above is the pinout of the connector on the PCB? For connector on the cable, it should be mirrored.
-
I really do not know where to go from there.
Are the problem keys all properly seated and making the proper click sound and feel?
-
If you didn't get to wire colors, did you take notice that above is the pinout of the connector on the PCB? For connector on the cable, it should be mirrored.
I've checked the color wires, the converter is correctly attached with +5V, GND, Data and Clock. I've attached it directly to the PCB-pin-connector, not the old cable.
I really do not know where to go from there.
Are the problem keys all properly seated and making the proper click sound and feel?
Well, I am also out of ideas, if that keyboard is maybe damaged?! The keys, which are not working to sound prober with click and feel like the rest of the keys. Maybe matrix damaged?
I am unsure, why hid_listen doesn't detect anything, but xev unter Linux does.
-
I've checked the color wires, the converter is correctly attached with +5V, GND, Data and Clock. I've attached it directly to the PCB-pin-connector, not the old cable.
Are the problem keys all properly seated and making the proper click sound and feel?
Well, I am also out of ideas, if that keyboard is maybe damaged?! The keys, which are not working to sound prober with click and feel like the rest of the keys. Maybe matrix damaged?
I am unsure, why hid_listen doesn't detect anything, but xev unter Linux does.
If some or most of the keys work, then you know that the external cable-to-controller wiring is correct.
The only thing that really remains are the internal traces or the moving parts, but if the key strokes are being detected by anything, then they must exist and be connected and operating in some dimension ....
-
I've to say sorry. Apparently the converter is confused, if there is already a connected keyboard with another converter.
After I've disconnected my other keyboard, hid_listen works and every key works and prints a scan code.
After remapping, it's now working correctly, as I wish :)
Thanks!
-
Oh, yes. Soarer noted it but somehow it stays buried in the TL;DR
Your computer only recognizes the first Soarer's Converter that was currently attached to it.