New Controller for KishSaver and Other Model F

rindorbrot · 16 Feb 2014, 10:47

Ahh ok, I already wondered why there was no mapping for the right alt key in all of the keymaps.
I guess then this will only be a temporary solution for me until the complete replacement controller is finished.

But it's definitely better than nothing and still nice work hasu!

Muirium · 16 Feb 2014, 15:11

hasu wrote:This converter with special serial no. 002 is on the way to AU. Enjoy, 002

Okay, just taken the case off my Kishsaver, and what do I see? Different cable colours!

: Something's Kishy.JPG (429.58 KiB) Viewed 12915 times

Mine is a late dated one (1986) with some differences to the other three Kishsavers I've seen (I proxied for Tinnie, and I took photos when I had them, which I need to wiki…) so I expected there could be interesting times ahead.

I've tested the pins on the cable, and 2 goes to white; 3 goes to red; 4 goes to black, and 5 goes to yellow. Reckon I'm safe following your pinout above? I wonder if they monkeyed around with the controller as well as the cable!

Soarer · 16 Feb 2014, 15:41

Yeah, along the top row of pins, from left to right in that pic it's: nc, +5V, nc, GND, Data, Clock, nc.

Muirium · 16 Feb 2014, 15:44

Cool, that's my interpretation too. Let's try this out…

rindorbrot · 16 Feb 2014, 15:50

Mine ('82) has the same cable colours as snoopy's.
Also what Soarer says is my observation, too.

Muirium · 16 Feb 2014, 16:42

Yup, looks like it works! Just a few unresponsive keys (in hardware) that I need to fix, but the protocol is fine as I type this on it now! Big thanks, guys.

Now how I do define my own keymap? That right Shift and feels-like-an-HHKB delete but it's a trap! is killing me! The documentation doesn't say where to include my file…

rindorbrot · 16 Feb 2014, 17:18

Just put it in tmk_keyboard-master\converter\ibm4704_usb, right next to the others

I have already completed mine, now all I have to do is waiting for the Teensy to get here...

Muirium · 16 Feb 2014, 17:51

I have a spare one in my drawer… never want to run out of Teensies!

Annoyingly, two keys on my Kishsaver are definitely in need of care. S barely registers (so I have my mouse hovering over a virtual keyboard for when it fails, as it comes and goes in spurts (ugh, I need to use words with less S's in them!)) and quote is entirely buggered. Extra problematic as an HHKB arrow on a 60%! That one has a bent spring.

Maintenance is easier on a Model F, right? As you don't have to bolt mod just to get inside. The trouble lies in the foam instead?

Incidentally, I have an "ISO" model. Left Shift is shorter than Hasu's, and I have a <> key (which the converter maps to ±§). For a while, I had four of them…

rindorbrot · 16 Feb 2014, 18:03

Hasu has his modded to have an ANSI Layout, they all initially come like in your picture.
Here's how mine looked before bringing it to the paint shop, where it is currently getting a nice fresh paint!

But of course I took out the inside prior to that, so I can still play around with it case-less at the moment.
I wanted to go with a split right Shift at first, but unfortunately only 1x and 1.75x is possible (not 1.75x and 1x like I wanted), so I left that standard.

Muirium · 16 Feb 2014, 18:20

Ah right, I see. Usually I'm an ANSI guy too, but short left shift has never been my objection: just that double deck return. Not a problem on the little Kishy!

Are those German caps your own addition too?

My paint is in good shape, but I really have to do something about these two dodgy keys. Seems I'm a faster typist than Hasu, too, as dropped double letters are coming up a fair bit all over the keyboard.

Still great to have it up and running this soon, though! Unbelievably compact for a buckling spring. My fingers are wondering what the hell is going on with this heavy metal HHKB!

rindorbrot · 16 Feb 2014, 18:22

Yes, the keycaps are borrowed from my ISO DE Model M, which is now naked

That's why I still have that WTB thread open for a second set of caps

REVENGE · 17 Feb 2014, 02:34

hasu wrote:This converter with special serial no. 002 is on the way to AU. Enjoy, 002

For those who are interested, my converter has some limitations:
1. Keyboard(6019284) has only *3-byte* key buffer.
2. Keyboard has same scancode on both Alt key. You can't use different scancodes on those.
3. My converter is naively *polling* at not so fast speed.
Due to 1. and 3. you probably will see missing keys and transposing keys at very fast typing.(my wpm is less than 60 and I don't have a problem) To solve or mitigate this problem we can use *interrupt* method instead of polling.

Replacing controller board doesn't has these limitations. It is still very intriguig option to squeeze every last drop of its power out of this keyboard.

I tried it out last week, there is some lag with the use of function shift layers, so it's not as responsive as a Poker, for example.

Ingenious reverse engineering BTW.

wcass · 03 Mar 2014, 03:56

Yes, those are Teensy++ mounted upside down.

Muirium · 03 Mar 2014, 09:59

Good job I've another Teensy++ coming from Jdcarpe. Now, however do we get these guys?

wcass · 05 Apr 2014, 05:42

Haata has got the user interface working. He said that he would be working on “key mapping stuff” this weekend. Auto-calibration is still a ways off, so even with this progress you would still need a scope to “tune” the controller.

All three guys are looking forward toward the ARM architecture used on the Teensy 3. These chips have more speed, power, and functionality; cost less, and are easier to source than the chips used on the Teensy++. Moving to the new chip will cut the number of discrete components – perhaps very significantly. The Teensy++ version of the controller has about 250 through holes in less than 10 square inches so it can be a challenging build even for an experienced assembler.

rindorbrot · 05 Apr 2014, 09:19

Good to hear that you make progress. Keep up the great work!

Muirium · 05 Apr 2014, 10:49

Indeed. And now I'm pleased I slipped a Teensy 3.1 into my order alongside a Teensy ++. I'm good with either version, and can scope if necessary.

nourathar · 13 Apr 2014, 18:35

great work !
Also for me the 'scoping' would be fun ! Not a lot of experience doing such things, but I have access to one and to somebody who could help...

wcass · 22 Apr 2014, 16:08

It looks like the DPH controller ready for public beta. Auto-calibration is working so no scope is needed. The first thing you will probably want to do is to order PCB and parts.

The files needed to make the PCB are here
https://gitorious.org/ibm-capsense-pcb

The above has a BOM, but here is another that is all sourced out
https://www.mouser.com/ProjectManager/P ... 2e26f4ea5b

Teensy++ 2.0 (no pins)
http://www.pjrc.com/store/teensypp.html

After you have built your controller, or at lease after you get your Teensy, you will need to build the firmware and program the Teensy. The code and instructions are here
https://gitorious.org/kiibohd-controller/capsense-beta

You should be able to get everything for about $50. If you want/need one of these but all this looks like too much for you, remember that there are folks in this community that contract out their skills.

Monster-Toys · 25 Apr 2014, 15:15

Very cool

So... who can build one for me?

wcass · 25 Apr 2014, 23:24

The listing below has ten guys in the US that do PCB assembly, but only one in Europe.
http://geekhack.org/index.php?topic=458 ... #msg962858

There is probably a thread here at Deskthority where members can offer services, but I can't find it. If you know where it is, please share the link!

Muirium · 25 Apr 2014, 23:37

Don't think there is such a thread here. I'm interested in making one of these for my Kishsaver, and could likely do more of them, but I'm all out of keyboard cash right now as two big caps GBs pounced together! I do already have a couple of Teensy 2++ waiting though.

Monster-Toys · 26 Apr 2014, 10:17

If you really do so, please put me onto your list (of course i would pay in advance). Time is not a big problem, i am not on the run.

Muirium · 26 Apr 2014, 11:19

Cool. If I can source some PCBs, I'll let you know. If anyone else in Europe is interested, I could get on with this fairly soon. Just depends on parts.

wcass · 02 Jun 2014, 05:05

I built mine and and am here to report.

The toughest part was getting the ribbon cable off of the old controller. After spending about a half hour on that and getting nowhere, i gave up and just cut it as close to the controller as i could. It worked out just fine. More on that in a minute.

Take what I advise here with a grain of salt. I am not an expert with a soldering iron - in fact, i suck.

My assembly order was from shortest component to tallest. I started with the diodes, then standard resistors, the chips, switch, resistor array, then capacitors. The diodes, chips, resistor array, and that one odd capacitor have to go in one specific direction; don't put these in backwards or it will not work. This is where i stopped to take the picture in my last post.

Parak used diode leg trimmings to mount his Teensy; I chose to use standard header pins. I only had 32 instead of the 43 that there are holes for, but this turned out OK - the controller only uses 31 pins. I soldered the pins onto the Teensy first and then checked the fit on the PCB. It looked really tight, so i mounted the controller in the keyboard to get a better idea. The Teensy comes very close to the barrel plate, but does not touch. But the opening for the USB cable was too small for my cable to fit inside. It turns out that this is a known issue - some mini USB connectors have larger heads than others. The smallest ones will fit with no problem; average size and larger need to have the the casing trimmed off. I kept the controller mounted and with USB cable connected while I soldered the Teensy onto the controller PCB so that i was sure that they would fit properly.

The final step was to connect the ribbon cable. I cut the old controller off, so i now had to strip some insulation from the cable. I used a razor knife to cut a line about 5mm back, flip the cable to the other side and cut on top of the first cut; use tweezers to grab a spot of insulation between the wires and pull. I tinned the wires to prevent the strands from splitting as i fed all 30 through the holes on the controller PCB (the second toughest part of building this).

And pictures.

: DPH side.JPG (423.62 KiB) Viewed 12156 times

: DPH bottom.JPG (532.21 KiB) Viewed 12156 times

: DPH top.JPG (789.33 KiB) Viewed 12156 times

Muirium · 02 Jun 2014, 15:48

That ribbon connector! I feel your pain.

Xwhatsit sent me a prototype of his Model F controller, to test with my Kishsaver. He modified the design after my feedback, making the ribbon cable pin holes bigger after the fight they gave me!

Anyway, once installed, it works very nicely. His design is all surface mount, so it's quite a lot smaller than the original IBM controller, and gives a lot of space inside the little Kishsaver.

Spoiler:

It's exciting how we have several ways to get these guys back to life now! Great work on all fronts, gentlemen.

wcass · 02 Jun 2014, 20:15

I didn't have problems with the size of the holes, but rather just getting all the wires lined up to the holes. The wires are all the same length, so all 30 need to enter the holes at about the same time. When attempting to do this, usually one or two wires would be leaning slightly one way or another.

Building the firmware for the DPH controller in Windows is complicated. You Linux/Unix guys will have no problems.

In Windows, ... start by downloading software.
You will need Cygwin, CMake, PJRC VSP driver, and Atmel AVR Toolchain
If you don't already have a Windows text editor that speaks Unix properly (Notepad and Wordpad do not; Notepad++ does), you will need to download one or use an editor under Cygwin.

Install Notepad++ (if required).
Install PJRC Virtual Serial Port driver.
Install CMake (suggest you install to the default folder).
Install Cygwin. Avoid installing to any folder with a space such as C:\Program Files
Make sure that the following components are installed:
•make
•git (needed for some compilation info)
•cmake
•gcc-core
•gcc-g++
•libusb1.0
•libusb1.0-devel
Run Cygwin Terminal once to create a user profile. Exit Cygwin.
Run Atmel 8bit AVR Toolchain - this will extract files to a folder. Enter that folder, select all files and folders and Cut.
Navigate to the folder that you installed Cygwin to. Paste the files and folders. You will be merging some folders - that is OK.
Navigate to the home sub folder inside your Cygwin folder; here you will find your user profile. Enter that folder.
Open .bashrc with your Unix compatible text editor.
Add the following line to the end ...
alias wincmake="PATH='/cygdrive/c/Program Files/CMake 2.8'/bin:\"${PATH}\" cmake"
The above line presumes that you are running a 32bit version of Windows and you installed CMake to the default directory. If you have a 64bit version of Windows, your line should look something like ...
alias wincmake="PATH='/cygdrive/c/Program Files (x86)/CMake 2.8'/bin:\"${PATH}\" cmake"
If you did not install CMake to the default directory, you will need to change this line appropriately.
At this point, your Windows box should have everything it needs to build and make the firmware.

Run Cygwin Terminal and type the following commands:
git clone https://git.gitorious.org/kiibohd-contr ... e-beta.git
cd capsense-beta
mkdir build
cd build
wincmake -G "Unix Makefiles" ..
make
If you followed these instructions and i didn't leave anything out, you will now have a 44kb file named kiibohd.hex
You will need to plug in your Teensy and press the button to get it ready to program. You can load that hex file on your Teensy with the PJRC tool Teensy.exe or load it directly from Cygwin with the command:
./load
Windows will start alerting you that new devices have been found, then you can start typing on your new keyboard.

Or, you could skip all that stuff above and just get someone to compile the hex file for you on Linux. That leaves you with the job of pressing the button and running Teensy.exe.

Debugging and changes to the keyboard layout are done using a command line interface over the virtural serial port. You can do this with Portable Putty.

Muirium · 02 Jun 2014, 21:02

wcass wrote:I didn't have problems with the size of the holes, but rather just getting all the wires lined up to the holes. The wires are all the same length, so all 30 need to enter the holes at about the same time. When attempting to do this, usually one or two wires would be leaning slightly one way or another.

Same here. Larger holes would have just made it a bit easier, so they are now standard on the production type. I'm slow when it comes to detailed work, so someone faster could have done my install in under 2 hours, but not me! 2 minutes after that, all 30 pins were soldered in place. It was just a matter of geometry, like you say.

xwhatsit · 06 Jun 2014, 03:47

Oh nice work! How does it go? I'm quite fascinated in how this controller operates in practice. That was a bit of cunning sneaking the USB plug underneath the attachment bracket

Such a different design. Really cool to see the different approaches taken to the same problem.

Ellipse · 09 Oct 2014, 03:38

Has anyone managed to get Hasu's 4704 Kishsaver tmk_keyboard converter working with the 107-key 4704 keyboard (keyboard ID A5)? Compiling the code on github without modification worked 95% for the main 62-key section of the 107-key keyboard, but two of my 107-key keyboards have the same keys not emitting values or key codes - the 8* key, the =+ key, and the left CTRL key produce nothing. On my third one, the 7&, -_, and right control key do not emit codes or matrix values. Adding scan codes to the keymap_common.h file did not fix these 3 keys (although they successfully added some codes for the other keys).

The matrix debug option viewed using hid_listen shows no activity for these keys but by pressing 7& and 9(, I can see that the 8* key probably should be column 1 row 1, the += key should be column 6 row 3, and the lower left control key should probably be column 1 row 6). The columns go from 0 through 7 and the rows go from 00 to 0F.

I carefully read through the source code and 4704-specific and TMK general readme files for this github project but cannot figure it out. I read that there is a way to get the 4704 keyboard to list all its break codes by sending the FC "set key flag" command to the keyboard but do not know how to do so (I could not figure out how to use the console option either).

There are other great 4704 converters out there but I would like to get this one working beyond 95%. In my testing over a few days it produced no ghosting or transposed characters while typing at 80+ wpm.

The hid_listen message when plugging in the keyboard:
IBM 4704 Converter
Keyboard ID: A5
Enable break: x36 zc65:rFD c6B:rFD End

(Does FD in the row codes above indicate an error?)

my adjusted keymap_common.h file is below. I added some codes for 103 keys since I got an error when trying to add more than that. Pressing some keys outside of the main 62-key section result in Error: 78 or Error: 79 both with the unmodified compiled hex file and my adjusted one below.

Spoiler: