Possible IBM Wheelwriter to USB DIY converter?

[Acknown3]

Hey guys, I've recently found an IBM PW2 in my basement, but I have no use for an electronic typewriter. As such, I'm thinking about pulling out the keyboard and using it with my desktop. Unfortunately, I have no idea how to use this type of connection with my computer. Has anyone done this before? Additionally, how would I map the keys? I'm planning on making it similar to the FC660C.

Additionally, would anyone happen to know the quality of the keyboard compared to the Model F and M? It doesn't feel anywhere near as sturdy as my F, but I've never typed on the M.

[vivalarevolución]

I have the same question.  I wonder if I can just slip those ribbons into a Model M controller and start hacking away.

[E TwentyNine]

It's model M in all but name.  Construction is the same.

It will work with a standard Model M controller, you have to cut those extra leads out on the right (the ones that loop back on themselves) and for the larger connector there's only 15 leads instead of the normal 16 so it'll sit in the slot on one side or the other, you'll have to test.

It will not map the keys correctly without adding a converter (ala Soarer).

You could also set up a Teensy as a controller and wire everything up yourself.

[dorkvader]

I have the same question.  I wonder if I can just slip those ribbons into a Model M controller and start hacking away.

I actually tried this: wont' work at all. (I cut the unused traces )

You'll need to get the connectors and a teensy. Not all matrix positions are mapped on the M I think, so I'm pretty sure that much of the matrix will be inaccessable.

I have pictures from when I bolt modded my WW, if anyone is interested. I have a few more WW KBs that will be bolted when my unicomp order arrives.

[Acknown3]

You'll need to get the connectors and a teensy. Not all matrix positions are mapped on the M I think, so I'm pretty sure that much of the matrix will be inaccessable.

So what exactly would I have to purchase? A teensy and everything involved with Soarer's converter?

[vivalarevolución]

I have the same question.  I wonder if I can just slip those ribbons into a Model M controller and start hacking away.

I actually tried this: wont' work at all. (I cut the unused traces )

You'll need to get the connectors and a teensy. Not all matrix positions are mapped on the M I think, so I'm pretty sure that much of the matrix will be inaccessable.

I have pictures from when I bolt modded my WW, if anyone is interested. I have a few more WW KBs that will be bolted when my unicomp order arrives.

Yea, it would be useful if you could provide pictures from your project with your wheelwriter. 

What connectors would I need to get?  And I could use the Teensy as the controller with Soarer's firmware?

Also, as a comment, I have found the Wheelwriter to be closer to a Model F in feel rather than a Model M.  But it is a membrane keyboard, correct?

[Acknown3]

I finally purchased a Teensy for this project, but I have zero keyboard DIY experience. Is there an idiot's guide for this? The Soarer's Converter images don't include ribbon cables.

[dorkvader]

On my phone at the moment but look at this
http://deskthority.net/workshop-f7/model-m-matrix-teensy-t8149.html

Drsolder the connectors from the PCB and use them

I know another guy who has done it to his ww and will see if I can get him to post.

[mkawa]

I have the same question.  I wonder if I can just slip those ribbons into a Model M controller and start hacking away.

I actually tried this: wont' work at all. (I cut the unused traces )

You'll need to get the connectors and a teensy. Not all matrix positions are mapped on the M I think, so I'm pretty sure that much of the matrix will be inaccessable.

I have pictures from when I bolt modded my WW, if anyone is interested. I have a few more WW KBs that will be bolted when my unicomp order arrives.

that's odd. that looks exactly like an M membrane..

[sethstorm]

On my phone at the moment but look at this
http://deskthority.net/workshop-f7/model-m-matrix-teensy-t8149.html

Drsolder the connectors from the PCB and use them

I know another guy who has done it to his ww and will see if I can get him to post.

I didn't have to desolder connectors from my controller, but I did manage to get lucky enough to find 13 and 9-pin connectors from an electronics surplus store (Mendelson's of Dayton). 

Image of how mine is setup:


Keyboard -> connectors -> thin 2x20 row socket -> wires -> teensy++ pins.

[vivalarevolución]

On my phone at the moment but look at this
http://deskthority.net/workshop-f7/model-m-matrix-teensy-t8149.html

Drsolder the connectors from the PCB and use them

I know another guy who has done it to his ww and will see if I can get him to post.

I didn't have to desolder connectors from my controller, but I did manage to get lucky enough to find 13 and 9-pin connectors from an electronics surplus store (Mendelson's of Dayton). 

Image of how mine is setup:

Show Image

Keyboard -> connectors -> thin 2x20 row socket -> wires -> teensy++ pins.

What firmware did you use on the Teensy? 

And there are a lot of wires spouting out of that connector.

[Acknown3]

I didn't have to desolder connectors from my controller, but I did manage to get lucky enough to find 13 and 9-pin connectors from an electronics surplus store (Mendelson's of Dayton).

Awesome, I live about ten minutes away from Mendelson's so I'll check it out.

[sethstorm]

What firmware did you use on the Teensy? 

Soarer's.  I'll can link the configuration file if you want.

And there are a lot of wires spouting out of that connector.

That's the whole matrix being wired up.  One group goes to one layer, the other group goes to the other. 

With that all said, anyone ever have one of the keys (shift?) map up as one single key? 

[sethstorm]

For a Teensy++ and a Wheelwriter 5:

Pin Diagram

Code: [Select]

Strobe pins, 13 pin strip (1 = leftmost pin as pictured above)
1 : D0
2 : D1
3 : D2
4 : D3
5 : D4
6 : C0
7 : C1
8 : C2
9 : C3
10: C4
11: C5
12: C6
13: C7

Sense pins, 8 pin strip (1 = left most pin)
1: F0
2: F1
3: F2
4: F3
5: F4
6: F5
7: F6
8: F7


Configuration for Soarer's firmware

Code: [Select]

#
# Wheelwriter 5 Matrix (ISO Enter)
# A sane, yet minimalist layout.
#
# Layout Notes:
# Layout mostly follows AT(Ctrl between Tab/Left Shift, Caps Lock below Right Shift) aside from ISO Enter/F11/F12.
#
# Top two keys in the 5-key vertical block are PgUp/PgDn respectively.
# Bottom two keys in the 5-key vertical block are F11/F12 respectively.
#
# The middle key in the 5-key vertical block on the right can be used as follows:
# [Modifier]-WASD : Cursor keys (Up/Left/Down/Right)
# [Modifier]-[Number key] : Equivalent numpad key
# [Modifier]-[Backspace] : Del (for those wishing to perform Ctrl-Alt-Del, use Ctrl-Alt-Modifier-Backspace)
# [Modifier]-[PgDn] : Left Win/GUI key
# [Modifier]-[`] : Escape key
#

matrix
   scanrate 1
   debounce 5
   blocking 0

   sense          PF0      PF1      PF2      PF3       PF4      PF5      PF6         PF7

   strobe   PD0      UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED      LALT
   strobe   PD1      F10      F7      F1      F3      F4      F5      F11         SPACE
   strobe   PD2      F9      F8      F2      UNASSIGNED   TAB      F6      LCTRL         CAPS_LOCK
   strobe   PD3      UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED      LSHIFT
   
   strobe   PD4      UNASSIGNED   A      BACK_QUOTE   1      Q      UNASSIGNED   Z      8
   strobe   PC0      UNASSIGNED   S      UNASSIGNED   2      W      UNASSIGNED   X      I
   strobe   PC1      UNASSIGNED   D      UNASSIGNED   3      E      UNASSIGNED   C      K
   strobe   PC2      G      F      5      4      R      T      V      B
   
   strobe   PC3      H      J      6      7      U      Y      M      N
   strobe   PC4      UNASSIGNED   K      EQUAL_SIGN   8      I      RIGHT_BRACE   COMMA      I
   strobe   PC5      UNASSIGNED   L      3      9      O      5      PERIOD      6
   strobe   PC6      QUOTE      SEMICOLON   MINUS      0      P      LEFT_BRACE   BACKSLASH   SLASH
   
   strobe   PC7      UNASSIGNED   FN2      BACKSPACE   PAGE_UP      PAGE_DOWN   6      ENTER      F12

end

macroblock

endblock

layerblock
   FN2 2
endblock
remapblock
   layer 2
   W UP
   A LEFT
   S DOWN
   D RIGHT
   BACKSPACE DELETE
   BACK_QUOTE ESC
   PAGE_DOWN LGUI
   1   PAD_1
   2   PAD_2
   3   PAD_3
   4   PAD_4
   5   PAD_5
   6   PAD_6
   7   PAD_7
   8   PAD_8
   9   PAD_9
   0   PAD_0
endblock


[vivalarevolución]

For a Teensy++ and a Wheelwriter 5:

Pin Diagram

Code: [Select]

Strobe pins, 13 pin strip (1 = leftmost pin as pictured above)
1 : D0
2 : D1
3 : D2
4 : D3
5 : D4
6 : C0
7 : C1
8 : C2
9 : C3
10: C4
11: C5
12: C6
13: C7

Sense pins, 8 pin strip (1 = left most pin)
1: F0
2: F1
3: F2
4: F3
5: F4
6: F5
7: F6
8: F7


Configuration for Soarer's firmware

Code: [Select]

#
# Wheelwriter 5 Matrix (ISO Enter)
# A sane, yet minimalist layout.
#
# Layout Notes:
# Layout mostly follows AT(Ctrl between Tab/Left Shift, Caps Lock below Right Shift) aside from ISO Enter/F11/F12.
#
# Top two keys in the 5-key vertical block are PgUp/PgDn respectively.
# Bottom two keys in the 5-key vertical block are F11/F12 respectively.
#
# The middle key in the 5-key vertical block on the right can be used as follows:
# [Modifier]-WASD : Cursor keys (Up/Left/Down/Right)
# [Modifier]-[Number key] : Equivalent numpad key
# [Modifier]-[Backspace] : Del (for those wishing to perform Ctrl-Alt-Del, use Ctrl-Alt-Modifier-Backspace)
# [Modifier]-[PgDn] : Left Win/GUI key
# [Modifier]-[`] : Escape key
#

matrix
   scanrate 1
   debounce 5
   blocking 0

   sense          PF0      PF1      PF2      PF3       PF4      PF5      PF6         PF7

   strobe   PD0      UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED      LALT
   strobe   PD1      F10      F7      F1      F3      F4      F5      F11         SPACE
   strobe   PD2      F9      F8      F2      UNASSIGNED   TAB      F6      LCTRL         CAPS_LOCK
   strobe   PD3      UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED      LSHIFT
   
   strobe   PD4      UNASSIGNED   A      BACK_QUOTE   1      Q      UNASSIGNED   Z      8
   strobe   PC0      UNASSIGNED   S      UNASSIGNED   2      W      UNASSIGNED   X      I
   strobe   PC1      UNASSIGNED   D      UNASSIGNED   3      E      UNASSIGNED   C      K
   strobe   PC2      G      F      5      4      R      T      V      B
   
   strobe   PC3      H      J      6      7      U      Y      M      N
   strobe   PC4      UNASSIGNED   K      EQUAL_SIGN   8      I      RIGHT_BRACE   COMMA      I
   strobe   PC5      UNASSIGNED   L      3      9      O      5      PERIOD      6
   strobe   PC6      QUOTE      SEMICOLON   MINUS      0      P      LEFT_BRACE   BACKSLASH   SLASH
   
   strobe   PC7      UNASSIGNED   FN2      BACKSPACE   PAGE_UP      PAGE_DOWN   6      ENTER      F12

end

macroblock

endblock

layerblock
   FN2 2
endblock
remapblock
   layer 2
   W UP
   A LEFT
   S DOWN
   D RIGHT
   BACKSPACE DELETE
   BACK_QUOTE ESC
   PAGE_DOWN LGUI
   1   PAD_1
   2   PAD_2
   3   PAD_3
   4   PAD_4
   5   PAD_5
   6   PAD_6
   7   PAD_7
   8   PAD_8
   9   PAD_9
   0   PAD_0
endblock


Wow, this is phenomenal.  Thanks.

[MrCyprus]

For a Teensy++ and a Wheelwriter 5:

Pin Diagram

Code: [Select]

Strobe pins, 13 pin strip (1 = leftmost pin as pictured above)
1 : D0
2 : D1
3 : D2
4 : D3
5 : D4
6 : C0
7 : C1
8 : C2
9 : C3
10: C4
11: C5
12: C6
13: C7

Sense pins, 8 pin strip (1 = left most pin)
1: F0
2: F1
3: F2
4: F3
5: F4
6: F5
7: F6
8: F7


Configuration for Soarer's firmware

Code: [Select]

#
# Wheelwriter 5 Matrix (ISO Enter)
# A sane, yet minimalist layout.
#
# Layout Notes:
# Layout mostly follows AT(Ctrl between Tab/Left Shift, Caps Lock below Right Shift) aside from ISO Enter/F11/F12.
#
# Top two keys in the 5-key vertical block are PgUp/PgDn respectively.
# Bottom two keys in the 5-key vertical block are F11/F12 respectively.
#
# The middle key in the 5-key vertical block on the right can be used as follows:
# [Modifier]-WASD : Cursor keys (Up/Left/Down/Right)
# [Modifier]-[Number key] : Equivalent numpad key
# [Modifier]-[Backspace] : Del (for those wishing to perform Ctrl-Alt-Del, use Ctrl-Alt-Modifier-Backspace)
# [Modifier]-[PgDn] : Left Win/GUI key
# [Modifier]-[`] : Escape key
#

matrix
   scanrate 1
   debounce 5
   blocking 0

   sense          PF0      PF1      PF2      PF3       PF4      PF5      PF6         PF7

   strobe   PD0      UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED      LALT
   strobe   PD1      F10      F7      F1      F3      F4      F5      F11         SPACE
   strobe   PD2      F9      F8      F2      UNASSIGNED   TAB      F6      LCTRL         CAPS_LOCK
   strobe   PD3      UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED   UNASSIGNED      LSHIFT
   
   strobe   PD4      UNASSIGNED   A      BACK_QUOTE   1      Q      UNASSIGNED   Z      8
   strobe   PC0      UNASSIGNED   S      UNASSIGNED   2      W      UNASSIGNED   X      I
   strobe   PC1      UNASSIGNED   D      UNASSIGNED   3      E      UNASSIGNED   C      K
   strobe   PC2      G      F      5      4      R      T      V      B
   
   strobe   PC3      H      J      6      7      U      Y      M      N
   strobe   PC4      UNASSIGNED   K      EQUAL_SIGN   8      I      RIGHT_BRACE   COMMA      I
   strobe   PC5      UNASSIGNED   L      3      9      O      5      PERIOD      6
   strobe   PC6      QUOTE      SEMICOLON   MINUS      0      P      LEFT_BRACE   BACKSLASH   SLASH
   
   strobe   PC7      UNASSIGNED   FN2      BACKSPACE   PAGE_UP      PAGE_DOWN   6      ENTER      F12

end

macroblock

endblock

layerblock
   FN2 2
endblock
remapblock
   layer 2
   W UP
   A LEFT
   S DOWN
   D RIGHT
   BACKSPACE DELETE
   BACK_QUOTE ESC
   PAGE_DOWN LGUI
   1   PAD_1
   2   PAD_2
   3   PAD_3
   4   PAD_4
   5   PAD_5
   6   PAD_6
   7   PAD_7
   8   PAD_8
   9   PAD_9
   0   PAD_0
endblock


Hey guys, I know this thread is pretty dead at this point, so I hope it's okay to post here, but I was hoping someone could shed some light on this pinout guide for me.  I recently stumbled across a  WheelWriter 1000 and have begun the process of trying to convert it into a working keyboard.  I have all the pieces (breadboard, cables, trio-mate connectors, etc.) and a Teensy 3.2, and now it's time to start putting it all together. 

I've been using multiple guides as a source of reference, and several of them use this pinout guide.  Being completely new to working with hardware I'm running into some confusion.  I have no idea what the letters in front of the numbers mean in this guide.  First I thought D was denoting the digital pins on the teensy, as opposed to the analog ones, but then C and F made no sense.  Next I assumed it was maybe the letters denoting the columns of the breadboard, but wasn't sure, since after wiring it up in that fashion it didn't seem to match the picture in this thread, and the Teensy actually covers up row F in order to expose Rows C and D.

 Any insight on how to properly read this pinout guide would be appreciated. 

Also, will there be a large difference in the way I need to wire a teensy 3.2 as opposed to the 2 or ++?

Thanks.

[suicidal_orange]

This thread was very dead, but still relevant so no problem with the necro )

The codes are a P (standing for pin) followed by the two characters found on the pin labels on a Teensy 2++

Keyboards are made up of a switch matrix which is referenced as rows and columns, but in order to avoid misdetecting keypresses most boards are not wired up with "QWERTYUIOP" as row 2.  Instead the keys are thrown in seemingly at random, as you can see in the second block of code.

The important thing to know is that when you press the 5 key you are connecting wire 8 on the big connector to wire 3 on the small one so your firmware needs to know you'd like to type a 5.  You can see this because wire 8 is C2 so PC2 is 8th down the side, and small wire 3 is F2, so PF2 is 3rd across the top - in the mess in the middle the 3rd entry on row 8 is "5"

If you're using a Teensy 3.2 then Soarer's firmware won't run on it so you will have to make your own firmware so you can connect the wires to any pins, just remember which you connected to which.  That said, unless you're the "coding expert" type of "hardware newbie" I suggest you would be much better off finding a Teensy 2++ so you can use the config helpfully provided above, writing a whole keyboard firmware is not an easy task!

[MrCyprus]

Thanks, that helps a lot. 

I wouldn't say I'm a "coding expert", but I'm certainly a lot more comfortable with coding than I am with hardware.  I found a post on Deskthority about how to write my own firmware, so I'll likely start there I suppose.  I guess once I have that working, wiring it up should make a lot more sense.

[djkib]

All props to Soarer, but in his absence, I would suggest that tmk_keyboard is a good place to start. check out the "Super Awesome Tools" page pinned at the top of the Making Stuff Together page.

Have fun! I am sure hasu would be more than happy to answer any questions for you, and would be grateful for any information on porting tmk_keyboard to the teensy 3.2...

[vivalarevolución]

I'm quite sure this is doable with TMK using one of phosphorglow's replacement Model M controllers.  I traced the matrix on my Wheelwriter membrane and he said that he could update the firmware to work with it.  He gave me the controller, but I'm not sure if the controller has the updated firmware.  I'll actually to get everything assembled, plug it in, and check.

[MrCyprus]

I'm quite sure this is doable with TMK using one of phosphorglow's replacement Model M controllers.  I traced the matrix on my Wheelwriter membrane and he said that he could update the firmware to work with it.  He gave me the controller, but I'm not sure if the controller has the updated firmware.  I'll actually to get everything assembled, plug it in, and check.

Let me know what you find out.  How did you go about tracing the membrane on your WW?  I did a quick search for any guides on the process but came up short.  I'm assuming you would have to bolt mod the board to do so?  My keyboard has a different layout and 14 pins on the wide strip, not 13, so I'm assuming the matrix may be significantly different...  Here are some photos of my board if you would like to take a look:  http://imgur.com/a/o8yZ7

[vivalarevolución]

I'm quite sure this is doable with TMK using one of phosphorglow's replacement Model M controllers.  I traced the matrix on my Wheelwriter membrane and he said that he could update the firmware to work with it.  He gave me the controller, but I'm not sure if the controller has the updated firmware.  I'll actually to get everything assembled, plug it in, and check.

Let me know what you find out.  How did you go about tracing the membrane on your WW?  I did a quick search for any guides on the process but came up short.  I'm assuming you would have to bolt mod the board to do so?  My keyboard has a different layout and 14 pins on the wide strip, not 13, so I'm assuming the matrix may be significantly different...  Here are some photos of my board if you would like to take a look:  http://imgur.com/a/o8yZ7

You don't need to trace the membrane at all, i just documented the rows and columns so phosphorglow could customize the firmware.  I attached a PDF of my documentation, I can provide a photo of the matrix sheets when I get the chance.

Also, you linked photos do not show the matrix sheets, unless I am missing something.

You do need to bolt mod, like any other Model M.

 Scan 2015-7-29 19.16.54.pdf (312.03 kB - downloaded 268 times.)

[MrCyprus]

I'm quite sure this is doable with TMK using one of phosphorglow's replacement Model M controllers.  I traced the matrix on my Wheelwriter membrane and he said that he could update the firmware to work with it.  He gave me the controller, but I'm not sure if the controller has the updated firmware.  I'll actually to get everything assembled, plug it in, and check.

Let me know what you find out.  How did you go about tracing the membrane on your WW?  I did a quick search for any guides on the process but came up short.  I'm assuming you would have to bolt mod the board to do so?  My keyboard has a different layout and 14 pins on the wide strip, not 13, so I'm assuming the matrix may be significantly different...  Here are some photos of my board if you would like to take a look:  http://imgur.com/a/o8yZ7

You don't need to trace the membrane at all, i just documented the rows and columns so phosphorglow could customize the firmware.  I attached a PDF of my documentation, I can provide a photo of the matrix sheets when I get the chance.

Also, you linked photos do not show the matrix sheets, unless I am missing something.

You do need to bolt mod, like any other Model M.

(Attachment Link)

Hey, sorry to get back to you after such a long time.  I guess there was a bit of confusion. 

How did you go about documenting the rows and columns of your keyboard?  At first I didn't really think I needed to bolt mod my board since all of the rivets are intact and seem to be in good shape.  Then I thought that maybe bolt modding it was the only way to get to the membrane and 'trace' or document it, but after doing some more research on bolt modding I noticed that most people keep the board clamped together and don't open it up to get a look at the membrane.

I did several searches on why it is important to bolt mod and how to document the rows and columns on my keyboard, but they turned up empty.  Could you help me answer these questions? 

Thanks again, and I appreciate your patience.

[vivalarevolución]

Bolt mod is important because as more of those round plastic rivets break that hold together the internal parts, it will affect the quality of the key presses.  You may have missed key presses or ghosting from the loosened internals.

If you are going to bolt mod, I always recommend taking apart the whole thing so you can clean any internal parts.  I've done a couple dozen bolt mods, and I've never kept the parts clamped together.  There are so many guides on the process, that it is not that hard to figure out, you just need to have the proper parts and tools.

To document the rows and columns you will have to take apart the internals and examine the membranes.  You'll notice there are dots that are connected by lines.  Obviously, the dots are where a key presses down and those connected lines make the rows and columns of membrane matrix.  The membranes also have two ribbons that slot into the controller.  All of the lines for your columns and rows are going to terminate at those ribbons and neatly align at the ribbons.

To create a copy of the membrane that I could write on, I just put a piece of paper over the membrane and lightly traced all the lines and dots.

Now take a look at this link here:  http://phosphorglow.net/2015/06/24/matrix-maps-charts/
Notice there are two letters for each dot or key on the keyboard.  That is the identifier we are going to assign for each key in the firmware when we get there.

Rows are going to be the first number for each dot, with the furthest left row as 7 and then count your way down to zero.
Columns are the second number for each dot.  Start with zero on the far left column, go all the the way to nine, and then turn to letters.  My wheelwriter had 0-9, and then A-C.
Trace the lines to see how each dot is connected to the rows/columns on the ribbon, and then write down the row/column next to each dot/key

That's as far as I have gotten because I have not tried to mess with the firmware.  But what I'm going to do is take the SSK firmware from the page I linked above, and adjust that more my matrix.

Now I know that my explanation might be confusing or may not be the best way of doing things.  Ask any questions if you have them.

[MrCyprus]

Hey thanks for the reply. 

After doing some more independent research, I determined I would probably need to open up the board to get a peek at the matrix.  I actually just ordered the nuts and bolts for the mod today, so I should be able to get working on it by the end of the week. 

Should I just continue to post here?  Or open up a separate thread?

[vivalarevolución]

Hey thanks for the reply. 

After doing some more independent research, I determined I would probably need to open it up the board to get a peek at the matrix.  I actually just ordered the nuts and bolts for the mod today, so I should be able to get working on it by the end of the week. 

Should I just continue to post here?  Or open up a separate thread?

Why not keep post here, let's make this thread a central repository for wheelwriter conversions.

[vivalarevolución]

If we are using phosphorglow's replacement Model M controller, I think the conversion process will be relatively easy.  Once you have the matrix documented, all you have to do is adjust the TMK firmware files (linked in this post) and load the firmware onto the controller and see if it works.

However, I usually fail at adjusting the TMK firmware files with my minimal programming knowledge, so I may ask for some help in the TMK firmware thread.

[MrCyprus]

Okay so I opened up the keyboard and mapped the matrix.  Here is what I've got:

 

I already have a teensy3.2, so I think that I am going to attempt to use https://github.com/ageaenes/teensykb to write the firmware.  Someone recommended that I use it over in the TMK thread.

I am going to try and finish the bolt mod this afternoon.  Hopefully it goes well.  I don't have access to a drill press, so I'm going to be using a hand drill.

[vivalarevolución]

Okay so I opened up the keyboard and mapped the matrix.  Here is what I've got:

 

Show Image

I already have a teensy3.2, so I think that I am going to attempt to use https://github.com/ageaenes/teensykb to write the firmware.  Someone recommended that I use it over in the TMK thread.

I am going to try and finish the bolt mod this afternoon.  Hopefully it goes well.  I don't have access to a drill press, so I'm going to be using a hand drill.

Looks good.  Good luck! 

I used a hand drill for all my bolt mods.  It is a little more tedious, but easily doable if you are careful about drilling the holes.

[MrCyprus]

Here's a link to the album I put together of my bolt-mod if anyone is interested.  Getting closer!

http://imgur.com/a/gnxnV

[vivalarevolución]

Here's a link to the album I put together of my bolt-mod if anyone is interested.  Getting closer!

http://imgur.com/a/gnxnV

Looks good.  Your Wheelwriter also is in great condition.

I need to work on my firmware.  But other priorities at the moment.  Sigh.

[MrCyprus]

So I sort of got the firmware working.  The keyboard does type, but not all of the keys are responsive and the keymap is completely off.  Progress, nonetheless.  Here is what my setup looks like: http://imgur.com/a/rGI5l

I'm currently working with Henz, who has been offering me advice on how to modify his/her code, which can be found here: https://github.com/ageaenes/teensykb

[mikew0w]

I haven't touched mine in a bit but it works:

http://i.imgur.com/rhz51EU.jpg
http://i.imgur.com/847NtFh.jpg

I kept the rest of the case to try and make a back for it but I have not found the time

[vivalarevolución]

So I sort of got the firmware working.  The keyboard does type, but not all of the keys are responsive and the keymap is completely off.  Progress, nonetheless.  Here is what my setup looks like: http://imgur.com/a/rGI5l

I'm currently working with Henz, who has been offering me advice on how to modify his/her code, which can be found here: https://github.com/ageaenes/teensykb

Good to hear that you found someone that knows what they are talking about with the firmware code, I´m not very knowledgeble about such topics.

[MrCyprus]

I haven't touched mine in a bit but it works:

http://i.imgur.com/rhz51EU.jpg
http://i.imgur.com/847NtFh.jpg

I kept the rest of the case to try and make a back for it but I have not found the time

Looks good!  I'm considering making a wood case for mine.

Good to hear that you found someone that knows what they are talking about with the firmware code, I´m not very knowledgeble about such topics.

So I successfully mapped the keys with the firmware and got the keyboard working, but I have some sort of issue with column 9, where all of the keys in that column are registering as the same key.  I may have to take the board back apart and look at the matrix to see if there is some kind of break in the column.  Not sure what else could be causing it. 

If you decide to get a Teensy 3 to use as your controller then I can help write your firmware provided you have the matrix mapped out.  I'm familiar enough with Henz's code to walk you through it, and I'm sure Henz would be willing to help with any problems we run into.

Unfortunately, one of the pins on the ribbon cable receiver I have broke off in the breadboard, so now Column 10 of my board is out of commission too.
After I diagnose the problem with Column 9, I plan to order a protoboard from Adafruit and a new ribbon cable receiver so I can solder it all together and start working on a case.

[vivalarevolución]

I finally did the bolt mod last night after months of the parts sitting on the shelf.   I am using phosphorglow's Colossus Model M replacement controller, and works with one of his basic SSK hex files installed.  So that is awesome.  Pretty excited.

Next I need to adjust the firmware files and try to get those optimized for my particular keyboard.  I can do it, but it will be a slight learning experience with TMK for me.

I thought about crafting some sort of case for it, but I'm not sure if this Wheelwriter OS worth the trouble.  The barrel frame has some deep cracking that will only get worse.  I think that I'll use this keyboard for experimentation and go from there.

Oh yea, the other issue I'm having is that my slightly niche distro of Linux does not have the packages I need to build an AVR GCC toolchain, and I'm having some difficulty building the packages from source.  This problem inhibits my ability to compile the firmware and create a hex file.  It might be time for me to break down and just get a Windows license to make my life easier when trying to program all my keyboards. Or, at the very least, use a more well supported version of Linux.