So, I kind of accidentally purchased a Model M, 1392595. Is there some sort of simple mod I can perform to make this work on my PC? Or if not, any tips on selling it?
First post, btw. fantastic forum.
Bummer that you're missing F8...I have F7 and F9 as spares, but no F8.
Yes'sir.
The terminal Ms are AT-compatible, just a different plug and a couple software-interpretation bugs.
Otherwise known as compatible.
USB adapters drop the extra scancodes.
What's needed is a PS/2 to USB converter that lets you use a custom set of scancode mappings. I don't suppose anyone's aware of one?
Actually, I'm currently hacking hasu's teensy project to add those scan codes back in, for the keyboard in ripster's post.
So yes, we are aware of one, but it's a sort of DIY type converter. It's in the mods section, and I'll be posting back any code changes I make, so people should be able to take advantage of it, so long as they have a teensy or a teensy++.
Would it work without a usb converter just plugging into a PS/2 port?Kinda.
If the end of the connector is a normal RJ45, you can make an RJ45->PS2 cable converter assuming you can scrounge a female RJ45 port and a spare PS2 cable from some-place (e.g. old mice).
On most IBM keyboard connectors for RJ45 the colours are, from left to right, looking at the connector with it pointing up, and the clip away from yourself:
empty
empty
black: 5V (yes 5V on black - it's not my fault)
red: data
yellow: clock
white: ground
silver: (ground/shield)
empty
The colours on other PS2 cables are totally different for each one, so you will need to probe the pins and ends of the wire to figure out which goes where before wiring up the cable. Some sort of meter or even a continuity tester will suffice for this.
Male
Show Image(http://www.computer-engineering.org/ps2protocol/spindin.JPG)
(Plug)
I'm going to give it a whirl tomorrow, but chances are it will probably end up for sale. Haha.
Thanks for this, can see where the cables come of the RJ45 please can you help by telling me where each cable goes onto the PS/2 cable?
Thanks for this, can see where the cables come of the RJ45 please can you help by telling me where each cable goes onto the PS/2 cable?
Try this:
https://geekhack.org/index.php?topic=61878.msg1721863#msg1721863
And yes... you can also do it to the 1392595, etc etc....
Just go to my gallery of pictures in my sig to see more transformations.Show Image(http://i.imgur.com/JpdGegy.jpg)
If i had a faulty controller I'd rather fabricate a alternative controller for that instead of trying my luck on ebay.
I'm trying figure out here is: is looping on print "wFF" in debug console a software issue or a hardware one.
Thanks for the advise
wFF is printed out by soarer's software, (and also by TMK, perhaps?) in a debug console.
It means the converter wrote FF to the keyboard, repeatedly, with no response.
Presumably either the wires were not hooked up correctly, (easiest error is to accidentally swap clock and data, as mentioned) - or there is some more exciting problem with the controller.
Feel free to drop by irc some time, we can likely figure out which with a few quick tests, otherwise - the forum. :)
I should be awake in about an hour... making coffee.
1) The solder joins at the 5 pin connector (only four of which are used) look shot. should touch those up, likely whatever bent it also broke those joins - but the traces are likely fine, so it's an easy thing to fix and rule out.
if hasus stuff runs on d5 and d2, then you are good, there... clock is on the lower left pin, and data on the corner pin beside vcc and gnd.
gnd is in the middle between clock and data, and vcc is alone on its row... (how I remember them)
So - I'd reflow those solder joins - and don't leave a controller resting with B3 and B4 possibly touching a grounded bolt. :)
I can't see what is going on with that brown component next to the connector either - might want to double check it isn't shorting to anything, and has good joins as well.
#
# PS/2 protocol implementations
# USART is recommended if it is available, others are for reference purpose.
# INT implementation will drop simultaneous key strokes.
#
#PS2_USE_USART = yes # uses hardware USART engine for PS/2 signal receive(recomened)
PS2_USE_INT = yes # uses external interrupt for falling edge of PS/2 clock pin
#PS2_USE_BUSYWAIT = yes # uses primitive reference code
acts as a pull up between Vcc and Data
I better have pull up resistors on both data and clock lines, I think that short wires works without pull-ups but not sure.
The wiring looks ok to me I don't know why it doesn't work and I don't have this converter hardware to test right now.
Try connecting clock to D0 and data to D1 and build firmware after changing lines in Makefile like this.
This pin usage is compatible to Soarer's so you can use it in case :DCode: [Select]#
# PS/2 protocol implementations
# USART is recommended if it is available, others are for reference purpose.
# INT implementation will drop simultaneous key strokes.
#
#PS2_USE_USART = yes # uses hardware USART engine for PS/2 signal receive(recomened)
PS2_USE_INT = yes # uses external interrupt for falling edge of PS/2 clock pin
#PS2_USE_BUSYWAIT = yes # uses primitive reference code
Waiting for new device:...
Listening:
wEE
remaining: FFFC
Keyboard ID: 0000
Code Set: 1
Mode: PC/XT
R05
I better have pull up resistors on both data and clock lines, I think that short wires works without pull-ups but not sure.
The wiring looks ok to me I don't know why it doesn't work and I don't have this converter hardware to test right now.
Try connecting clock to D0 and data to D1 and build firmware after changing lines in Makefile like this.
This pin usage is compatible to Soarer's so you can use it in case :DCode: [Select]#
# PS/2 protocol implementations
# USART is recommended if it is available, others are for reference purpose.
# INT implementation will drop simultaneous key strokes.
#
#PS2_USE_USART = yes # uses hardware USART engine for PS/2 signal receive(recomened)
PS2_USE_INT = yes # uses external interrupt for falling edge of PS/2 clock pin
#PS2_USE_BUSYWAIT = yes # uses primitive reference code
This thing took a unexpected turn here:
The controller board might be ok.
So Ive unplugged teensy from the controller, still getting wFF from hid_listen.
Then I decided to check if the teensy board is faulty.
It's not! I tried to load blinky.hex from teensy's official website, works fine, the hid console output is correct too.
Then try soarer's converter (1.12).
I got this output first time plugged in:Quote
Waiting for new device:...
Listening:
wEE
remaining: FFFC
Keyboard ID: 0000
Code Set: 1
Mode: PC/XT
R05
Still not registering key strokes though.
:eek:
acts as a pull up between Vcc and Data
I follow Soarer's advice and have pull-ups between both data and clock to power.
It's going mode 1 instead of mode 2? Maybe that's the problem? It should be going mode 3 to mode 2.
It's going mode 1 instead of mode 2? Maybe that's the problem? It should be going mode 3 to mode 2.
I was wondering if there was a resolution to that controller issue. Did you wind up swapping the controller out?
It's going mode 1 instead of mode 2? Maybe that's the problem? It should be going mode 3 to mode 2.
I was wondering if there was a resolution to that controller issue. Did you wind up swapping the controller out?
I will try to throw in another teensy first, which i used for a point to point wiring keyboard.
Then I'll see if i should replace the controller.
According to the source code wFF is the code for reset and teensy keeps pooping those in console even without connecting to the model m controller sounds super suspicious.
here's the updates.It's going mode 1 instead of mode 2? Maybe that's the problem? It should be going mode 3 to mode 2.
I was wondering if there was a resolution to that controller issue. Did you wind up swapping the controller out?
I will try to throw in another teensy first, which i used for a point to point wiring keyboard.
Then I'll see if i should replace the controller.
According to the source code wFF is the code for reset and teensy keeps pooping those in console even without connecting to the model m controller sounds super suspicious.
For some odd reason, I am still wondering if you ever got that keyboard working!
So is everything all good now? Sounds to me you got it all sorted out.Everything is pretty much working now.