Keybort

This one is a MicroWeb Touch-1 XT/AT. Kinda.

See if you look up that keyboard you find the Deskthority page on it, showing this.
It's clearly pretty similar, but there are some differences.
Also that one uses a PC/XT/AT DIN5 connector, and this one uses some kind of RJ connector.
This one isn't in the greatest of shape, but considering I got it from the Chuck Colby estate sale, it's surprising it isn't completely water-damaged.
It's got some minor rust damage inside, where the metal clips rubbed off on the PCB.
And the control chip is a C35331E.
It's one of those chips you can find a few places that'll sell you one, but nowhere has a datasheet.
"8647" is probably a date code? 47th week of 1986.
That matches the chip on Deskthority.
And all keycaps removed! These are "Futaba MA series" (aka Futaba clicky switch) switches.
It's got 5 pins connected. AT is only 4 pins, but the PC/XT keyboard is 5 pins. So maybe this is a switchable keyboard?
the Deskthority wiki seems to partially agree with that:
There's a jumper under the tab key, which is theorized to be a XT/AT switch.
SO, what the heck is the pinout? I have no idea what the pinout of the IC is, and nothing to connect this to to spy on it, and no results online for googling the name other than the one that's shown up on deskthority.
Well, the PCB has two other chips on it.
They're both 74-series logic.
We can easily find datasheets for those and they should be sharing power/ground.
green is +5V
and either blue or yellow is GND.
(they both seem to be ground, at least as close as my multimeter can tell.

More from foone

More from Tech

A common misunderstanding about Agile and “Big Design Up Front”:

There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.

You’re allowed to think about a desired outcome from the beginning.

It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.

It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.

It’s not BDUF if you help every team member know what success looks like.

Agile is about reducing risk.

It’s not Agile if you increase risk by starting your sprints with complete ignorance.

It’s not Agile if you don’t research.

Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.

It would be a mistake to assume this research should only be done by designers and researchers.

Product management and developers also need to be out with the team, conducting the research.

Shared Understanding is the key objective


Big Design Up Front is a thing to avoid.

Defining all the functionality before coding is BDUF.

Drawing every screen and every pixel is BDUF.

Promising functionality (or delivery dates) to customers before development starts is BDUF.

These things shouldn’t happen in Agile.

You May Also Like