i'll try to get a shot of the back tonight.
hammers and springs for the additional keys? If you've got a few extras, I'd happily trade you (or anyone else) some M parts or a few bucks
after counting my parts, i'd be happy to send you a half dozen model F/AT spring/plate assemblies from a board i'm converting :)
even better if you have a model M Right-Arrow & Ctrl to trade :D
I don't suppose that means you have a spare space & backspace does it? :-) (http://geekhack.org/showthread.php?t=13632)
It seems a shame to spend a bunch on a probably-functional F-XT and then tear it up just for four parts (why on earth do they cost so much? They won't work on anything newer than 1982. o_O).
Woohoo!
Oh yea: Is there any noticeable difference between the F and M stems? They're completely interchangeable, right?
If you want to add keys, you need to find someone who has a junk Model F that you can cannibalize for extra stems and (more critically) hammers. Anything short of that isn't going to work.
I wonder how much it would cost to have fabricated, in small quantities, parts that would fit into an M: an F-like front plate, an F-like foam pad, and an F-like capacitive matrix board with a teeny bit of logic
By "stems", you're meaning the piece that the spacer guide thingamabob is stuck into in msiegel's picture?
So I need them for the M-spacebar-swap and for adding two keys to the keypad then, but not for the M-backspace-pipe-and-enter-swap, correct?
And the model M keys/plungers/whatever fit into them properly? Or is there a step in the backspace/enter swap that I'm missing?
Adding four of those to the wishlist in the previous post, then. :3 Hehe.
I have extra Model F hammers and stems in storage if you really needed them. I am, however, currently living about 1500 miles away from them, and I would rather not have to call up a friend to drive out and rummage around for them, ship it to me, etc. Hopefully someone else on the board can help you out in that regard.
if all goes well, we'll find out in 2011 :)
although my goal isn't to fit an f into an m, i will be replacing all the electronics and structural components.
current design for colemak layout - you can see why i need extra stabilizer guides :)Show Image(http://geekhack.org/attachment.php?attachmentid=14240&stc=1&d=1293212145)
i have circuitry to design... and not being an EE, this is a very slow process :)
Looks like he's using the AVR's ADC for that one though. You'd think that you could like... Use a TTL buffer or something with just the right value resistors to make the output flop between 0 and 1 when the key was pressed... I guess that would probably end up being temperature sensitive though, wouldn't it? :s
I don't really know what I'm talking about. >_>
Looks like it would indeed be easier to just decode XT scancodes in software hahaha.
we now know that the sensor/detector circuits can handle a fair amount of stray capacitance (here in the form of added wires :)
this keyboard totally rocks
Model M Mini is the King
In 1980, ADCs were huge and expensive, so I don't think there's any way that's what the model F uC is doing. They've -got- to be generating 1s and 0s with an RC circuit some way, right?
maybe *not*! :O
the capacitive BS patent doesn't mention an RC oscillator, iirc...
i'm beginning to think that square silver mystery component on the controller pcb is not an oscillator at all, but is actually a custom chip comprised of 1) a 5-way analog switch used to select each row, and 2) a high speed comparator with latching output.
Aha, like so:
http://en.wikipedia.org/wiki/RC_circuit#Series_circuit (http://en.wikipedia.org/wiki/RC_circuit#Series_circuit)
Gurglemath. >_>
i think half the junk (ICs) on that pcb is column selection logic. rather than let a column float if it's not selected, it's pulled down to ground to suppress noise.
in the next couple of days i'm planning to start hardware experiments. the simulator is really great, in that i've only killed off half my teensy's analog input pins so far XD
but it's about time for the rubber to meet the road.
i don't have an o-scope, so i like those testing ideas. keep em coming! :D
i'm beginning to think that square silver mystery component on the controller pcb is not an oscillator at all, but is actually a custom chip comprised of 1) a 5-way analog switch used to select each row, and 2) a high speed comparator with latching output.
The PC board only has like... 6 lines going from the uC to the silver thingy. So there must be a decoder in there. I bet the uC has a counter in it and sends a binary digit to the silver thing and it decodes it and maybe does some tri-stating and uh, stuff, maybe? And then it looks like there is a uhm... A silver barrel thingy with one end hooked to the ground plane and the other end hooked to one of the pins on the silver thing. Aha, it's a 6 uF capacitor, must just be a filter cap or something.
Surely in 1980, if the thing was using an oscillator, there'd be an external crystal instead of some special something built into the silver thing.
oops, ninja'd :)
yes, no crystal! it's quite a mystery :D
there's a partial schematic of the pcb somewhere... where did i see that...
Oh, it's ultra speshul. =:O
IBM octal capacitive keyboard matrix receiver with 8-to-1 multiplexer (ibm-8273565.sym) (http://www.gedasymbols.org/user/alexander_kurz/symbols/ibm-8273565.sym)
documentation: best guess
during the scan cycle, imagine each pad getting its own pulse. i'm pretty sure the pads can all be sensed independently.
the multiplexer just selects one row at a time to look at :)
reference capacitors
i'm heading out of here to do some work... later :)
So like.... Possibly the uC is like "Ohai silver thing, I wanna read row 3", and it gets decoded inside and row 3 is routed into a comparator. Then the UC pulses a column and the comparator is like "Ohai, I'm done (put a bit on OUT and assert G)"?
on the ATmega32U4 that's used for teensy, the analog input pins go through a multiplexer to a single adc.
however, docs claim the adc can do 15ksps... which might just be fast enough :D
PS: Also of course, I'd try finding some source of AC for more actual pulses to measure for each key trigger. I'd suppose a signal generated by your soundcard run through an audio amplifier would very much suffice; if you got a high quality card, you can easily generate a 20 or even 48kHz pulse signal with any old free signal generation software; then level it in with your multimeter and the amplifier volume, and there you have your replacement pulse signal, perfect for testing. Just don't forget to disconnect the other speaker while you're at it.
Hey Matt! Sorry for kinda disappearing. Work got kinda busy for a while. :3
How are things going with your capacative hackery?
Yeah, I'm currently doing a double sense, since I'm not so stable yet... the IBM F does not seem to actually do this, though... I think it would add 16 bytes to the RAM image of the controller, on top of the 8 required to retain the actual current key state, plus 10-16 for the event buffer. The 8048 only had 64 bytes of ram - space is _tight_. From our probing it is clear that the keys are all scanned in sequence, so the whole matrix would need to be stored as a tentative version... hmm, I suppose the second pass can check as it goes, so that doesn't require a full copy...
00-07 registers
08-09 stack, one level only
0A-29 Flags for keys, 2 bits per key. 0 = Make only, 1 = Make/Break, 3=Repeat
2A,2B Used when reading the keyboard
2C-3B Bitmap of pressed keys
3C-3E Buffer of scancodes to send to the host
3F Last scancode transmitted to host
fun stuff - thanks for pulling them bins! btw - did you do it with a home uC/breadboard, or do you have a fancy programmer for it? Once I remembered thta almost all these chips need to be _verified_ after burning, it became clear that a lot of them will be easily recovered since security and IP idiocy was not a factor at that point.
(I have a 1390131, I want to pull the stuff in case it is dual-mode, and detects XT machines... )