Post by: samwisekoi on Wed, 04 January 2017, 12:14:40
Back in 2014-2015, I designed (https://geekhack.org/index.php?topic=62003.0) and in 2016 produced (https://geekhack.org/index.php?topic=80326.0) 25 GH-122 PCBs for the dedicated folks who really, really wanted a
One of the key things I did with the design was to make it compatible with the Unicomp PC-122 "IBM" case that is available for $20 in an F-122 layout. This required the board be able to be cut and bent, and so it is.
Here are some of the layouts that can already be built with the GH-122 PCB:
[attachimg=3]
My personal GH-122 in the Unicomp case with NDG SA Keycaps
[attachimg=1]
GH-122 Expanded ANSI Layout
[attachimg=4]
GH-122 Max Keys Layout
[attachimg=5]
GH-122 Tall Winkeyless Layout
[attachimg=6]
GH-122 Wide Winkeyless Layout
[attachimg=7]
GH-122 Left Arrow Cluster Layout
And certainly more possibilities and combinations!
So why another [IC] thread?
There appears to be enough interest in another run of the GH-122 for me to make some updates and do another run of the PCBs. This time around, I'd like to at least have a complete parts list for a case, plate, switches, keycaps, and electronics so a less experimental hobbyist can order what is needed to build a fully-functional keyboard.
The GH-122 has a few key aspects that won't change:
* Mega size with a 7x24 maximum layout.
* Full programability.
* Flexible layout beyond just ANSI/ISO to include functional subsets like 5x24 "Wide Body", F-122 layout -- including the bent F-key rows, etc.
* 100% through-hole constructions, so no advanced equipment or skills are needed to successfully build it.
In addition, I have collected many feature requests that I have filtered and summarized below. Please note that full backlighting is not included. However, each switch can be backlit with additional hand wiring. Aside from that, here are the current upgrades/features/fixes under consideration for the 2017 Edition of the GH-122.
Potential list of updates as of 05-Jan-2017:
Checkmarks added to completed updates. See changelog for details.
- ✓[FIX] Correct 6.25 stabilizer mounting holes.
- ✓[FIX] Relocate D160 (similar to D150.)
[FIX] Remove pointless lower-left phantom arrow key position?- ✓[MOUNTING] Add mounting holes for 5x24 build.
- ✓[MOUNTING] Add lower mounting holes to PC-122 upper bank.
- ✓[MOUNTING] Daughterboard mounts for the controller.
- ✓[MOUNTING] Add center-line support holes between Row B and C (matching GH60.)
- ✓[UNICOMP] Jumper blocks for upper bank and LEDs, located and labeled for use in the Unicomp case.
[UNICOMP] Move USB connector .250 southwest to fit better in the Unicomp case.- ✓[REQUESTED FEATURE] Alps compatibility for expanded ANSI only.
- ✓[REQUESTED FEATURE] Modular/removable keypad.
[REQUESTED FEATURE] Modular/removable nav block.[REQUESTED FEATURE] Optional 4x5 nav block.- ✓REQUESTED FEATURE] Split spacebar.
- [REQUESTED FEATURE] 6.0+1.0 spacebar+1 lower row. (6.0+1.0, 6.25, 7.0 spacebar layouts.)
- ✓[IMPROVEMENT] Partial backlighting circuits, especially transistor mounting locations.
- ✓[IMPROVEMENT] Make ISO and ANSI Enter and \| switches use same row & column.
[FORMAT CHANGE] Change gutter spacing from .34+.33+.33 to .375x3. (Adds 0.125 to width, but more importantly, kills Unicomp or IBM case compatibility.)- ✓[REQUESTED FEATURE] Addressable RGB LED strip circuit, e.g. to attach WS2812B. (Firmware NOT included!)
This thread is to discuss these and other potential features before I go into PCB layout mode. I will let it run until the end of Jan-2017, or whenever it peters out.
FYI, This is my thread, and I reserve the right to ruthlessly trim OT comments and trolling. Humorous trolling has a better chance of surviving.
After this, I will have another thread to assess interest, including interest in the various layouts.
Happy New Year, and happy commenting!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
[attachimg=2]
Post by: samwisekoi on Wed, 04 January 2017, 12:14:59
- 170107 v.1.1.1 Moved D160.
- 170107 v.1.1.2 Corrected 6.25 stabilizer mounting holes (moved to 50mm from center.)
- 170107 v.1.1.3 Added mounting holes for 5x24 build.
- 170107 v.1.1.4 Added mounting hole for 5x22 build.
- 170107 v.1.1.5 Added lower mounting holes for 2x17, 2x15, and 2x12 upper banks.
- 170107 v.1.2.0 Added Alps switch support for ANSI positions plus the expanded function-key banks.
- 170108 v.1.2.1 Rotated Alps switches on numpad 2x positions to correct orientation.
- 170108 v.1.3.0 Added Phenix' split-shift bottom row layout.
- 170108 v.1.3.1 Added mounting hole between G and H to match GH60.
- 170113 v.1.5.0 Revised splits and mounting holes.
- 170114 v.1.5.1 Made ISO Enter and \| use correct ANSI traces.
- 170114 v.1.5.2 Moved COL_22 to pin D6.
- 170114 v.1.5.3 Ordered COL_18-20 properly (NOTE NEW PINS).
- 170114 v.1.5.4 Ordered COL_7-9 properly (NOTE NEW PINS).
- 170114 v.1.5.5 Labeled row and column pins on controller section of PCB.
- 170115 v.1.5.6 Moved LED circuits and resistors.
- 170115 v.1.6.0 Added backlight components.
- 170116 v.2.0.0 Re-ran traces to controller and numpad.
- 170116 v.2.0.1 Added pads, power, and pins for user-added backlight and underlight.
- 170117 v.2.0.2 Added traces and pads for interior pins PA0-PA7.
- 170117 v.2.0.3 Moved cut-lines and holes to final locations.
- 170117 v.2.0.4 Improved LED circuit locations on controller.
- ...
- 170201 v.2.1.2 Moved COL_21 to D0 and therefore BACKLIGHT to B7.
Post by: xondat on Wed, 04 January 2017, 12:28:52
Physical PCB changes, this'll be fun.
Post by: jal on Wed, 04 January 2017, 12:31:46
I've been kicking around an idea for a huge board for a while, but haven't gone anywhere with it. This would either get it out of my system, or, perhaps, get me excited to do something really nutty.
I need to go through the old thread in more detail to comment on the proposed changes; I'll try to do that soon. But this excites me.
Post by: iamtootallforthis on Wed, 04 January 2017, 12:37:09
Post by: Niomosy on Wed, 04 January 2017, 18:00:43
Post by: user 18 on Wed, 04 January 2017, 19:00:38
Post by: samwisekoi on Wed, 04 January 2017, 19:54:29
Ron, any chance we can get a link to what the previous run looked like somewhere in the OP? It might help make sense of some of the list items -- eg. relocating D160.
Sorry, that list was not really properly descriptive to anyone but me. I don't have a good picture with me, so here is the one I do have. I'll do some clean-up on the list and post a better picture when I can.
Specifically re D160, that one diode is below the switch at the very bottom of the PCB (Keypad_Enter), and could interfere with a low-profile or tight wedge case. Therefore, that change is just to move the diode above the switch to reduce interference.
Some of the items are tiny and technical, or would have been noticed by people who built up one of the 2016 (v1.1) PCBs.
Anyhow, here is a pretty render, and I'll post a more informative picture or three when I can. And possibly re-arrange and clarify the list.
Thanks for the request!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Data on Thu, 05 January 2017, 06:21:52
Post by: Krogenar on Thu, 05 January 2017, 09:22:35
Quote
* 100% through-hole constructions, so no advanced equipment or skills are needed to successfully build it.
I'll be honest -- I wanted to go in on the original groupbuy, but I'm not that accomplished at soldering as I would like. I can build hobby robots and such. So that scared me off the original buy. If this will have a case that can go with it as well, then I'm probably in for this. I'm just glad someone else likes their keyboards on the big side. :thumb:
Set to Notify/Watch.
Suggestion/Wish: add some images to this thread of the first version!
Post by: Phenix on Thu, 05 January 2017, 09:40:57
Split spacebar options
eg(row: 1'5, 1, 1'5, 1, 2'25, 1, 2'75, 1'5, 1, 1'5)
eg(1'5, 1, 1'5, 1, 1'25, 1'25, 1'25, 1'25, 1, 1'5, 1, 1'5)
Post by: samwisekoi on Thu, 05 January 2017, 10:48:04
Suggestion/Wish: add some images to this thread of the first version!
I will. The OP version #1 was mostly an announcement that the project is on, and me moving my working list up onto GH.
Now that the thread is up, it is clear that not everyone has the first three threads memorized. :cool: So I shall craft a new OP that is a stand-alone description of the project AND indicates what input I want to get.
[REQUESTED FEATURE]
Split spacebar options
eg(row: 1'5, 1, 1'5, 1, 2'25, 1, 2'75, 1'5, 1, 1'5)
eg(1'5, 1, 1'5, 1, 1'25, 1'25, 1'25, 1'25, 1, 1'5, 1, 1'5)
I'll do a couple of things. #1 I'll add "split spacebar" to the list of requests. #2 I'll fix the 6.25 and 7.0 spacebars and then see what I can do to add a no-stab split spacebar option. OK?
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Phenix on Thu, 05 January 2017, 11:10:07
The Phantom 7BIT is an example for an no-stabilizer design
(split backspace, split shifts and an split ANSI enter (1u+1, 25u)
Post by: samwisekoi on Thu, 05 January 2017, 11:22:01
Sure, awesome!
The Phantom 7BIT is an example for an no-stabilizer design
(split backspace, split shifts and an split ANSI enter (1u+1, 25u)
Thanks for the clue. Most of that is in-place already. I'll grab a Phantom PCB from my stack of uncompleted projects and take a look.
- Ron | samwisekoi
Post by: Phenix on Thu, 05 January 2017, 11:39:43
https://deskthority.net/photos-f62/red-alert-otaku-rgb-moba-7bit-otd-phantom-with-clack-t4017.html
i couldnt source an phantom plate, so I went with an clueboard meanwhile
https://www.dropbox.com/s/amij1ccptq5a8x3/20161215_194329.jpg?dl=0
Post by: samwisekoi on Thu, 05 January 2017, 12:18:45
here is an pic of an 7bit phantom
https://deskthority.net/photos-f62/red-alert-otaku-rgb-moba-7bit-otd-phantom-with-clack-t4017.html
i couldnt source an phantom plate, so I went with an clueboard meanwhile
https://www.dropbox.com/s/amij1ccptq5a8x3/20161215_194329.jpg?dl=0
Wow. OK then. I understand.
However, the question that immediately comes to mind is: What are you going to do with all those extra keys on a keyboard that already supports 150+ keys? Seriously. Personally, I couldn't figure out how to use all of the keys already there. So I built a reduced version just to "simplify" things. (I do understand this for smaller boards like my JD45, which has a split shift.)
Still, I'll get some form of split shift in place!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: nathanrosspowell on Thu, 05 January 2017, 12:21:01
I am a fan of split spacebars on more compact builds for the optimisation in hand movement it gives, but, on a board this size I want to feel like a switchboard operator when typing :D
#8 and #10 on your list are the same, Ron. Maybe "Alps compatibility" was a highly requested feature! :p
Post by: Phenix on Thu, 05 January 2017, 12:25:32
on my clueboard its just handy to have
layer2, enter/layer1, space+layer3
in reach.
it is damn comfortable to have arrows in home row which are on the layer (so not much movement.
i agree - finding bindings for all keys can be hard, but atleast thoss not that often used keys get an extra key which I dont have to remember..
OFFTOPIC:
Whats up with the gh36/pad?
is there any possibility to get one?
Post by: samwisekoi on Thu, 05 January 2017, 12:46:20
With reduced you mean the F122 alike board, or?
on my clueboard its just handy to have
layer2, enter/layer1, space+layer3
in reach.
it is damn comfortable to have arrows in home row which are on the layer (so not much movement.
i agree - finding bindings for all keys can be hard, but atleast thoss not that often used keys get an extra key which I dont have to remember..
OFFTOPIC:
Whats up with the gh36/pad?
is there any possibility to get one?
Good points. Thanks.
The GH36 is behind this one.
- Ron | samwisekoi
Post by: nathanrosspowell on Thu, 05 January 2017, 14:17:16
With reduced you mean the F122 alike board, or?
on my clueboard its just handy to have
layer2, enter/layer1, space+layer3
in reach.
it is damn comfortable to have arrows in home row which are on the layer (so not much movement.
i agree - finding bindings for all keys can be hard, but atleast thoss not that often used keys get an extra key which I dont have to remember..
OFFTOPIC:
Whats up with the gh36/pad?
is there any possibility to get one?
Good points. Thanks.
The GH36 is behind this one.
- Ron | samwisekoi
Devil's advocate: If you want to not move your hands much, why on earth get a 122 key keyboard?
For me the draw to this board is the size and the novelty, not the efficiency. Putting effort into making the extra keys even more redundant feels like neutering the beast.
Post by: iamtootallforthis on Thu, 05 January 2017, 14:19:09
With reduced you mean the F122 alike board, or?
on my clueboard its just handy to have
layer2, enter/layer1, space+layer3
in reach.
it is damn comfortable to have arrows in home row which are on the layer (so not much movement.
i agree - finding bindings for all keys can be hard, but atleast thoss not that often used keys get an extra key which I dont have to remember..
OFFTOPIC:
Whats up with the gh36/pad?
is there any possibility to get one?
Good points. Thanks.
The GH36 is behind this one.
- Ron | samwisekoi
Devil's advocate: If you want to not move your hands much, why on earth get a 122 key keyboard?
For me the draw to this board is the size and the novelty, not the efficiency. Putting effort into making the extra keys even more redundant feels like neutering the beast.
Yeah haha. I purchased this board for the novelty of having a massive board.
Post by: Phenix on Thu, 05 January 2017, 14:24:32
Its just easier for me to have some arrows on the left side, eg while using the right hand for the mouse
This MASSIVE board has lots of keys for eg shortcuts - nevertheless the option for adding some more keys (which also increases ergonomic IMHO (speaking of spit space)) is gokd
Post by: nathanrosspowell on Thu, 05 January 2017, 15:01:55
I dont mind moving my hands..
Its just easier for me to have some arrows on the left side, eg while using the right hand for the mouse
This MASSIVE board has lots of keys for eg shortcuts - nevertheless the option for adding some more keys (which also increases ergonomic IMHO (speaking of spit space)) is gokd
I guess I just can't understand why you are trying to make a F122 more ergonomic :))
Ultimately it's Ron's call, I am not trying to block features being added :thumb:
Post by: samwisekoi on Thu, 05 January 2017, 15:06:36
I dont mind moving my hands..
Its just easier for me to have some arrows on the left side, eg while using the right hand for the mouse
This MASSIVE board has lots of keys for eg shortcuts - nevertheless the option for adding some more keys (which also increases ergonomic IMHO (speaking of spit space)) is gokd
Ah, YOU are the person who I was thinking of in v1.1 (2016) when I enabled a left-hand arrow cluster. That is the switch position I am thinking of removing since no one ever used it.
- Ron | samwisekoi
Post by: Niomosy on Thu, 05 January 2017, 16:19:51
I dont mind moving my hands..
Its just easier for me to have some arrows on the left side, eg while using the right hand for the mouse
This MASSIVE board has lots of keys for eg shortcuts - nevertheless the option for adding some more keys (which also increases ergonomic IMHO (speaking of spit space)) is gokd
I guess I just can't understand why you are trying to make a F122 more ergonomic :))
Ultimately it's Ron's call, I am not trying to block features being added :thumb:
Phhht, I'd totally be in for a split GH-122 board if the price wasn't insane :P
Post by: nathanrosspowell on Thu, 05 January 2017, 16:33:39
A split version?! Hahaha that would be so crazy.I dont mind moving my hands..
Its just easier for me to have some arrows on the left side, eg while using the right hand for the mouse
This MASSIVE board has lots of keys for eg shortcuts - nevertheless the option for adding some more keys (which also increases ergonomic IMHO (speaking of spit space)) is gokd
I guess I just can't understand why you are trying to make a F122 more ergonomic :))
Ultimately it's Ron's call, I am not trying to block features being added :thumb:
Phhht, I'd totally be in for a split GH-122 board if the price wasn't insane
Post by: samwisekoi on Thu, 05 January 2017, 16:36:01
- Ron | samwisekoi
Post by: Data on Fri, 06 January 2017, 11:33:28
Split into how many pieces?
- Ron | samwisekoi
Like 5? :))
---
Ron, what's driving the format change to 0.375" gutters? Has someone requested this?
Post by: samwisekoi on Fri, 06 January 2017, 12:34:23
Ron, what's driving the format change to 0.375" gutters? Has someone requested this?
No. But it would make it easier to add an optional column to the right of the arrow cluster. I put that change on the list along with the Unicomp/IBM case items to trigger any input for or against using that case. As far as I know, I am the only person who has used the Unicomp case, so maybe that feature (and those gutter dimensions) are not really needed.
Also, moving to .375" will make plates, etc. easier to design.
- Ron | samwisekoi
p.s. Show me 10 people who would actually build a split GH-122 and I'll add that request to the list.
Post by: Trente on Fri, 06 January 2017, 12:48:53
Post by: Phenix on Fri, 06 January 2017, 12:54:32
will tnat coloumn be on the 'removable numpad section'?
split - sounds good - its in
Post by: Niomosy on Fri, 06 January 2017, 13:11:49
Split into how many pieces?
- Ron | samwisekoi
So long as I have the option for 6 on the left, however many you want. Two is the common ergo split though a detachable numpad would be interesting. However, that gets us into quite the complicated if rather modular board.
Post by: Data on Fri, 06 January 2017, 13:46:23
Split into how many pieces?
- Ron | samwisekoi
So long as I have the option for 6 on the left, however many you want. Two is the common ergo split though a detachable numpad would be interesting. However, that gets us into quite the complicated if rather modular board.
So VE.A: Command and Control Edition :))
Post by: Phenix on Fri, 06 January 2017, 14:15:45
Post by: Spaceman1200 on Fri, 06 January 2017, 15:42:34
Post by: Niomosy on Fri, 06 January 2017, 15:53:57
Split into how many pieces?
- Ron | samwisekoi
So long as I have the option for 6 on the left, however many you want. Two is the common ergo split though a detachable numpad would be interesting. However, that gets us into quite the complicated if rather modular board.
So VE.A: Command and Control Edition :))
Absolutely. Minus the high-priced case and whatnot that drove the price up out of reach for me.
Post by: samwisekoi on Fri, 06 January 2017, 16:17:33
I believe I can make this work:
[attachimg=1]
GH-122 No-Nav Layout
It seems insane, but maybe this can be made to work. The blue splits are already available:
[attachimg=2]
GH-122 Insane Split Format
Are we talking about Lego-style "click-together" modules or spread across your enormous desk via ribbon cables?
And seriously, would anyone actually build such a thing?
- Ron | samwisekoi
Post by: Niomosy on Fri, 06 January 2017, 19:56:30
I think we were more joking around on the split though. The hilarity of a split/tented 122 board would be incredible, though. We'll save it for once it's simply built by some production company and we can just buy the end result ;)
Post by: jal on Fri, 06 January 2017, 20:23:31
I think we were more joking around on the split though. The hilarity of a split/tented 122 board would be incredible, though. We'll save it for once it's simply built by some production company and we can just buy the end result ;)
Phhht, come on. It can be done! I will absolutely design cases for one.
Could put legs on them, so they stand in front of your desk. Or chair-arm attachments, kind of like grade-school desk surfaces.
Post by: Niomosy on Fri, 06 January 2017, 21:54:37
Still, I did think it might be a bit much for him for round 2 unless he was okay taking more time to set those things up.
Post by: nathanrosspowell on Sat, 07 January 2017, 10:20:44
But, the extra splits by the nav cluster and the numpad seem like it would be a huge plus when trying to fit the pcb into different cases :thumb:
Post by: samwisekoi on Sat, 07 January 2017, 10:30:06
I'll look at the keypad split-outs, however.
Happy Saturday!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: samwisekoi on Sat, 07 January 2017, 12:27:34
Below are the 2016 as-manufactured PCB and a snapshot of the current state of the 2017 PCB.
Posting only for the very interested. Multi-layer and backwards reading skills required!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Phenix on Sat, 07 January 2017, 13:01:37
I would go for Ribbon-attachment of the parts.
the alpha-split looks interesting, similar to VE.A
If you are fine with adding the alpha-split feature I would definitly try it out if I get the pcb..
Nevertheles the numpad and nav cluster ribbon attachments should be focused+used by way more people.
Post by: samwisekoi on Sat, 07 January 2017, 16:39:03
However, because Alps' leads are at the same height, they conflict with each other and with MX switch pads everywhere there are multiple switch positions available.
My goal is to provide ANSI plus extra function keys for Alps users. But here is an example of a switch position where one of the Alps leads shorts out the MX switch:
[attachimg=1]
GH-122 Caps Switch showing Alps conflict with MX pads. Alps lead holes shown in grey.
Because the left-hand Alps lead hole is directly between positive and negative MX pads, I have two options:
A. Force Alps users to use a stepped Caps key, which eliminates the conflict.
B. Drill a blank hole for the left-hand Alps lead (no pad), forcing the builder to jump the switch lead to one of the MX pads WITHOUT shorting the lead to the other MX pad. This is the option shown in the example.
Alps-compatibility is one of the most-requested enhancements, so I am trying to deliver that.
Anyhow, I don't mean to whine about the issue; I just want to show an example of why the first version didn't have Alps-compatibility, and why it is so hard to deliver.
[EDIT] Okay, an ANSI spacebar row in Alps was not horrible. Really the only nasty position is the Caps key, and there are really only the two options listed above. I went with option B, but could easily switch to option A if the Alps-folk preferred it.
Anyhow, below is the current state of the design with Alps-switched fully supported for ANSI plus extra function keys.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: user 18 on Sat, 07 January 2017, 21:34:42
Getting started.
Below are the 2016 as-manufactured PCB and a snapshot of the current state of the 2017 PCB.
Posting only for the very interested. Multi-layer and backwards reading skills required!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Thanks for posting these!
Post by: nathanrosspowell on Sat, 07 January 2017, 22:27:22
I am working on Alps-compatibility. All of the alphas, function keys, nav, and 1x numpad switch positions are done. Some traces needed to be moved, but no big deal.
However, because Alps' leads are at the same height, they conflict with each other and with MX switch pads everywhere there are multiple switch positions available.
My goal is to provide ANSI plus extra function keys for Alps users. But here is an example of a switch position where one of the Alps leads shorts out the MX switch:
(Attachment Link)
GH-122 Caps Switch showing Alps conflict with MX pads. Alps lead holes shown in grey.
Because the left-hand Alps lead hole is directly between positive and negative MX pads, I have two options:
A. Force Alps users to use a stepped Caps key, which eliminates the conflict.
B. Drill a blank hole for the left-hand Alps lead (no pad), forcing the builder to jump the switch lead to one of the MX pads WITHOUT shorting the lead to the other MX pad. This is the option shown in the example.
Alps-compatibility is one of the most-requested enhancements, so I am trying to deliver that.But the example problem shown is minor compared with the problems in the spacebar row.
Anyhow, I don't mean to whine about the issue; I just want to show an example of why the first version didn't have Alps-compatibility, and why it is so hard to deliver.
[EDIT] Okay, an ANSI spacebar row in Alps was not horrible. Really the only nasty position is the Caps key, and there are really only the two options listed above. I went with option B, but could easily switch to option A if the Alps-folk preferred it.
Anyhow, below is the current state of the design with Alps-switched fully supported for ANSI plus extra function keys.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
It doesn't sound like much of a comprimise to me :thumb:
I'd be building an MX setup, but out of curiosity; can the Alps crowd tell me where you'd find a keyset to fill up this beast?
Post by: duynguyenle on Sun, 08 January 2017, 05:46:02
I am working on Alps-compatibility. All of the alphas, function keys, nav, and 1x numpad switch positions are done. Some traces needed to be moved, but no big deal.
However, because Alps' leads are at the same height, they conflict with each other and with MX switch pads everywhere there are multiple switch positions available.
My goal is to provide ANSI plus extra function keys for Alps users. But here is an example of a switch position where one of the Alps leads shorts out the MX switch:
(Attachment Link)
GH-122 Caps Switch showing Alps conflict with MX pads. Alps lead holes shown in grey.
Because the left-hand Alps lead hole is directly between positive and negative MX pads, I have two options:
A. Force Alps users to use a stepped Caps key, which eliminates the conflict.
B. Drill a blank hole for the left-hand Alps lead (no pad), forcing the builder to jump the switch lead to one of the MX pads WITHOUT shorting the lead to the other MX pad. This is the option shown in the example.
Alps-compatibility is one of the most-requested enhancements, so I am trying to deliver that.But the example problem shown is minor compared with the problems in the spacebar row.
Anyhow, I don't mean to whine about the issue; I just want to show an example of why the first version didn't have Alps-compatibility, and why it is so hard to deliver.
[EDIT] Okay, an ANSI spacebar row in Alps was not horrible. Really the only nasty position is the Caps key, and there are really only the two options listed above. I went with option B, but could easily switch to option A if the Alps-folk preferred it.
Anyhow, below is the current state of the design with Alps-switched fully supported for ANSI plus extra function keys.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
I think having dummy holes to jump the adjacent pads to wouldn't be so bad!
Post by: pomk on Sun, 08 January 2017, 06:24:42
Post by: samwisekoi on Sun, 08 January 2017, 09:54:44
I remember some alps custom pcb having uncommon positions upside down. Could that be used here?
In general, no, because it interferes with the LED pads. Worse, the CAPS LED is fully wired for use as an indicator, e.g. with a windowed keycap. In some cases this can work; the numpad vertical 2x positions use this method.
Having said that, I had not looked at the CAPS position with rotation in mind, but I'll try various combinations. Thanks for the idea.
Oh, wait. Can an Alps keycap be used with a switch rotated 90 degrees? I think not. (Please correct me if I am wrong!)
I'll play with this, but I don't want to give up an LED for windowed keycaps to fix this problem.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
p.s. Crap. Does this also mean I have to orient all Alps switches horizontally? Those numpad positions aren't...
[EDIT] Fixed the numpad.
Post by: nathanrosspowell on Sun, 08 January 2017, 10:02:06
For the alphas you can only rotate them 180 degrees.I remember some alps custom pcb having uncommon positions upside down. Could that be used here?
In general, no, because it interferes with the LED pads. Worse, the CAPS LED is fully wired for use as an indicator, e.g. with a windowed keycap. In some cases this can work; the numpad vertical 2x positions use this method.
Having said that, I had not looked at the CAPS position with rotation in mind, but I'll try various combinations. Thanks for the idea.
Oh, wait. Can an Alps keycap be used with a switch rotated 90 degrees? I think not. (Please correct me if I am wrong!)
I'll play with this, but I don't want to give up an LED for windowed keycaps to fix this problem.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
p.s. Crap. Does this also mean I have to orient all Alps switches horizontally? Those numpad positions aren't...
Alps vertical numpad 2u positions do need the stem rotating 90 degrees (like you have it), but in not sure if this is an absolute rule or just the general case. A seasoned Alps user will have to verify.
See the Monarch PCB for an example https://geekhack.org/index.php?topic=75786.0
Post by: pomk on Sun, 08 January 2017, 10:02:22
Post by: samwisekoi on Sun, 08 January 2017, 10:55:24
[REQEUESTED FEATURE]
Split spacebar optionseg(row: 1'5, 1, 1'5, 1, 2'25, 1, 2'75, 1'5, 1, 1'5)eg(1'5, 1, 1'5, 1, 1'25, 1'25, 1'25, 1'25, 1, 1'5, 1, 1'5)
I am going to try your second proposal.
- Ron | samwisekoi
Post by: Phenix on Sun, 08 January 2017, 10:58:45
It matches nicely with most GMK /SA sets..
Post by: samwisekoi on Sun, 08 January 2017, 11:00:51
Only 180 degree orientation changes are allowed for alps.
Alps vertical numpad 2u positions do need the stem rotating 90 degrees (like you have it), but in not sure if this is an absolute rule or just the general case. A seasoned Alps user will have to verify.
Can someone authoritative weigh in on this point? I can rotate the numpad vertical either way, but not both.
Someone who might actually build an Alps version, please specify required numpad 2x orientation and provide pics or a source.
Thanks!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: samwisekoi on Sun, 08 January 2017, 11:26:12
(Nice layout, Phenix! It re-used the ANSI spacebar switch, and only added four new traces. Good job.)
NOTE TO SELF: THIS BOTTOM ROW NEEDS A SECOND ROUND OF CHECKING TO MAKE SURE MY MATH WAS CORRECT.
Anyhow, have a new layout image.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Phenix on Sun, 08 January 2017, 13:01:26
From the image it looks more like 1.5u keys (but probably that's just me who cant read pcbs well enough) in the bottom row.
Out of interest: Is something (with LeftArrowCluster) possible?
1, 1. 1, X, 1, 1.50, 1, 1.25, 1.25, 1.25, 1.25, 1, 1.50, 1, 1.50
(Where X is 1 or 1.25u)
A note to others for split spacebars:
My left thumb is under V in home position
Post by: samwisekoi on Sun, 08 January 2017, 13:22:27
thanks!
From the image it looks more like 1.5u keys (but probably that's just me who cant read pcbs well enough) in the bottom row.
Out of interest: Is something (with LeftArrowCluster) possible?
1, 1. 1, X, 1, 1.50, 1, 1.25, 1.25, 1.25, 1.25, 1, 1.50, 1, 1.50
(Where X is 1 or 1.25u)
A note to others for split spacebars:
My left thumb is under V in home position
I probably did it wrong ;^). Thus all the CHECK THE MATH warnings.
My right thumb is under the N key, and is the only spacebar strike I make -- except when gaming. Then i use my left thumb under the V.
- Ron | samwisekoi
Post by: Phenix on Sun, 08 January 2017, 13:35:52
(I bet there are some cool alternative bottom row options (could one mount an thumbstick in it.. Just wondering..)
Post by: Data on Sun, 08 January 2017, 19:21:18
Post by: samwisekoi on Sun, 08 January 2017, 19:28:04
- Ron | samwisekoi
Post by: samwisekoi on Sun, 08 January 2017, 19:42:26
Out of interest: Is something (with LeftArrowCluster) possible?
1, 1. 1, X, 1, 1.50, 1, 1.25, 1.25, 1.25, 1.25, 1, 1.50, 1, 1.50
Sorry, missed this.
Yes, easy. The 2016 board supported 1-1-1-gap-1-1.50-7.00, etc. And due to IBM weirdness, the gap is 0.340" + 0.375", or about 0.95 key spaces. So with the added split-shift for 2017, your desired layout can be done where X=0.715".
- Ron | samwisekoi
Post by: gadzkun on Sun, 08 January 2017, 20:04:59
Post by: Phenix on Mon, 09 January 2017, 01:07:51
I need to calculate inch some time
Post by: samwisekoi on Mon, 09 January 2017, 10:33:19
So 1u fits?
I need to calculate inch some time
No; sorry. There will always be a gap between the blocks because of the IBM spacing. Details below...
Both IBM and Cherry started out as US companies, so the dimensions are non-metric. Cherry chose 3/4" or 0.750" as a standard switch unit, which is now listed as 19.05mm. Half a switch position is 0.375", which can be filled with a 1.5 unit keycap.
There is no standard for gaps between blocks, although I found both 1/4" and 0.375" examples. And when IBM made the Model F (or earlier) they used the 0.750" width for keycap units. 24 keys is therefore 18" exactly, and with four blocks there are three gaps. Apparently to keep things even, IBM set the total of the three gaps at 1 inch, which I measured as 0.340", 0.330", and 0.330" from left to right,for a total width of 19". And because I was aiming the PCB at the Unicomp version of the IBM case, I used those same gap widths.
The problem is that there are no fractional keycap widths that can fill a 1/3" gap, so no keycap can fill that position.
And thus you find the reason I included moving to 0.375" gaps in my list of potential mods.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Phenix on Mon, 09 January 2017, 10:49:55
its no problem at all, I was just interested in the possibility.
Post by: Data on Mon, 09 January 2017, 10:53:36
For the record, it was no more or less difficult for me to draw 0.340" and 0.330" gutters over 0.375" gutters when I designed the case I'm currently using. /shrug
Post by: samwisekoi on Mon, 09 January 2017, 11:13:44
I don't really see a lot of value moving to the wider gutters and abandoning the Unicomp as one of the cheaper case alternatives. But it's your design. Show us what you have in mind. Maybe there's some sweet trick with the 1.5u mods that we haven't considered yet?
For the record, it was no more or less difficult for me to draw 0.340" and 0.330" gutters over 0.375" gutters when I designed the case I'm currently using. /shrug
I agree. The only reason to change is to add keycaps across the gaps. And doing that at the cost of abandoning the $20 Unicomp case seems to be a bad idea.
However, this is an Interest Check thread, and if eleventy-seven people had endorsed the change, I'd listen. You can see the changes I have made, and so far, this isn't one of them.
- Ron | samwisekoi
Post by: Phenix on Mon, 09 January 2017, 11:40:10
Post by: Data on Mon, 09 January 2017, 13:04:31
I don't really see a lot of value moving to the wider gutters and abandoning the Unicomp as one of the cheaper case alternatives. But it's your design. Show us what you have in mind. Maybe there's some sweet trick with the 1.5u mods that we haven't considered yet?
For the record, it was no more or less difficult for me to draw 0.340" and 0.330" gutters over 0.375" gutters when I designed the case I'm currently using. /shrug
I agree. The only reason to change is to add keycaps across the gaps. And doing that at the cost of abandoning the $20 Unicomp case seems to be a bad idea.
However, this is an Interest Check thread, and if eleventy-seven people had endorsed the change, I'd listen. You can see the changes I have made, and so far, this isn't one of them.
- Ron | samwisekoi
No problem. I thought this was something you came up with. I didn't intend to crap all over the idea, just trying to understand the motivation. Thanks for explaining.
Post by: Niomosy on Mon, 09 January 2017, 13:13:47
So that feeling on my leg was it getting pulled? Hmmph. And even so, I got the 6 wrong? Sigh.
I'll look at the keypad split-outs, however.
Happy Saturday!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Well, I'll be honest. I would love a split 122. I wasn't positive if such a thing was realistic for this run or something more to plan for in the future. I figured I'd mention it and see what happened. The worst case is that it's not feasible for this round. No harm in asking.
As for the 6, I think that ends up a religious battle though I'm a 6-on-the-left proponent so I was ribbing you a bit on that piece. As it stands, the 6 was more for gaming as I make heavy use of it in WoW but might consider just a flat gaming keyboard for that and leave the split to handle work if it came down to that.
Post by: samwisekoi on Mon, 09 January 2017, 13:31:02
As for the 6, I think that ends up a religious battle though I'm a 6-on-the-left proponent so I was ribbing you a bit on that piece. As it stands, the 6 was more for gaming as I make heavy use of it in WoW but might consider just a flat gaming keyboard for that and leave the split to handle work if it came down to that.
Ah, TIL I am a member of the certainly-correct 6-on-the-left sect. All hail diagonal splits!
- Ron | samwisekoi
Post by: Phenix on Mon, 09 January 2017, 14:10:26
Maybe imitating the VE.A for where the splits go?
[+hopefully if you add split halfes some of the other parts like navpad/numpad/makropad(1, 2, 3, 4) become movable/modular as well..
Post by: Data on Mon, 09 January 2017, 14:50:14
Gun to my head, this is how I would split up the GH-122.
(http://i.imgur.com/enmbkum.png)
3 pieces: Left, Right, Numpad. For the record I think it's just a silly idea for an already comically-oversized board.
Post by: samwisekoi on Mon, 09 January 2017, 16:23:13
OK...
Gun to my head, this is how I would split up the GH-122.Show Image(http://i.imgur.com/enmbkum.png)
3 pieces: Left, Right, Numpad. For the record I think it's just a silly idea for an already comically-oversized board.
Oh sure. I can do that!
- Ron | samwisekoi
========== I totally won't do that, but I absolutely could! ==========
Post by: Niomosy on Mon, 09 January 2017, 20:00:22
OK...
Gun to my head, this is how I would split up the GH-122.Show Image(http://i.imgur.com/enmbkum.png)
3 pieces: Left, Right, Numpad. For the record I think it's just a silly idea for an already comically-oversized board.
That's the split I was thinking as well. Basically a big brother to the VE.A in terms of layout.
Post by: Spaceman1200 on Tue, 10 January 2017, 10:55:59
Only 180 degree orientation changes are allowed for alps.Alps vertical numpad 2u positions do need the stem rotating 90 degrees (like you have it), but in not sure if this is an absolute rule or just the general case. A seasoned Alps user will have to verify.
Can someone authoritative weigh in on this point? I can rotate the numpad vertical either way, but not both
Like so? (http://i.imgur.com/WIaaTOT.jpg)
All of my alps boards are like this btw, With the exception of one with the 2x1u's in the numpad which are placed normally
Post by: samwisekoi on Tue, 10 January 2017, 12:57:11
Only 180 degree orientation changes are allowed for alps.Alps vertical numpad 2u positions do need the stem rotating 90 degrees (like you have it), but in not sure if this is an absolute rule or just the general case. A seasoned Alps user will have to verify.
Can someone authoritative weigh in on this point? I can rotate the numpad vertical either way, but not both
Like so?Show Image(http://i.imgur.com/WIaaTOT.jpg)
All of my alps boards are like this btw, With the exception of one with the 2x1u's in the numpad which are placed normally
Yes. Exactly like that. Thank you very much!
Alps users: Numpad 2x vertical switches will be aligned with vertical stem mounts as identified by nathanrosspowell.
- Ron | samwisekoi
Post by: Phenix on Tue, 10 January 2017, 13:11:33
Could you also add split option like this?
(I am mainly asking for left, right, nav, numpad)
The blue lines are just the positions were one could cut the extra keys off
Post by: samwisekoi on Tue, 10 January 2017, 14:41:34
http://imgur.com/a/n89R1
Could you also add split option like this?
(I am mainly asking for left, right, nav, numpad)
The blue lines are just the positions were one could cut the extra keys off
The row traces all go up on the right edge. That is just one of the obstacles to nav-block and numpad modularity. I'm pondering those now, but it will take some time and effort. I will try, but I cannot promise to provide those lower red slices just yet.
- Ron | samwisekoi
Post by: Phenix on Tue, 10 January 2017, 15:24:35
Post by: TerryMathews on Wed, 11 January 2017, 10:31:02
Post by: Niomosy on Wed, 11 January 2017, 15:51:24
Post by: jal on Wed, 11 January 2017, 20:34:55
This might turn out to be one hell of a monster. I am excite.
I'm pretty sure it will. Shaping up nicely. (Clackasorous? Velocomech? Printed Circuit Bruiser?)
Post by: Data on Thu, 12 January 2017, 07:42:25
This might turn out to be one hell of a monster. I am excite.
I'm pretty sure it will. Shaping up nicely. (Clackasorous? Velocomech? Printed Circuit Bruiser?)
(http://i.imgur.com/tcs8S1E.png)
Post by: samwisekoi on Fri, 13 January 2017, 12:58:18
If I cannot get the new layout to work AND do so in a manner that I am certain is electrically functional, I will likely roll-back to v.1.3.1 and move that to GB. We shall see!
Anyhow, here is the current state, including the new splits WITHOUT the needed trace re-routing.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: samwisekoi on Fri, 13 January 2017, 18:27:48
There are still some things I need to do with the controller section, but this is what the board will physically be for 2017.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: xondat on Fri, 13 January 2017, 18:42:59
Couldn't make it happen without a full re-layout. That MAY happen at some point in the future, but for now, the board will include the numpad.
There are still some things I need to do with the controller section, but this is what the board will physically be for 2017.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Physical final version! Is the USB in the same spot? Is a public .step or .dwg (etc) file possible?
Post by: samwisekoi on Fri, 13 January 2017, 20:40:47
Physical final version! Is the USB in the same spot? Is a public .step or .dwg (etc) file possible?
Calm down there, soldier. All in good time, all in good time.
- Ron | samwisekoi
Post by: samwisekoi on Sat, 14 January 2017, 11:59:02
There is some more to do on the traces and lighting circuits, so those things are still coming. AND, for the impatient, while this PCB is generally in its final format, exact placement of mounting holes is likely to change a bit as I think through mounting with and without a plate. Then -- and only then -- will I publish a detailed physical specification and drawings.
Finally, since I've made several changes to controller traces and added Alps* support, I will likely do a pre-production run of 10 PCBs to verify the design. Then we will have an actual group buy. No ETA for either of those just yet.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
*Alps is the correct spelling for Alps Electric (http://www.alps.com/e/company/message.html), even though the logo is in all-caps.
Post by: Phenix on Sat, 14 January 2017, 13:33:45
Post by: samwisekoi on Sat, 14 January 2017, 13:56:26
to bad that the numpad is out for now, nevertheless I really like that you are going all-in on adding more features!
Yeah, there are just too many traces on a board this big. Especially with just that little corner to work with and 0.10"/2.54mm pad spacing to enable normal humans to work on it. Consider that 20 columns plus 7 columns and the CAPS LED mean 3 inches of pads that need to fit above the 1.5" nav cluster. And the traces to those pads create a ribbon .870" across that has to fit into a .750" space between the number row and the function block.
Solvable problems, but much easier to solve when the initial design included features to support an eventual solution. The GH-122.2016 didn't, so I am afraid the GH-122.2017 won't either.
For now, we'll focus on adding features that didn't make it to the board last year!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Phenix on Sat, 14 January 2017, 14:49:46
(ghb,fgv,hjn clusters?)
While the numpad split wont work out for now - the mid-split is then as well not feasible for now?
Post by: TerryMathews on Sat, 14 January 2017, 17:28:46
Might also eliminate enough columns that you could step down from a Teensy 2.0++ to Teensy 2.0.
Post by: Niomosy on Sun, 15 January 2017, 01:18:40
Post by: Phenix on Sun, 15 January 2017, 05:57:52
I use my Numpad occassionally.. But I would prefer to have it detachable..
but in the end its up to Sam which features are/arent added
Post by: samwisekoi on Sun, 15 January 2017, 13:42:56
This version (v.1.6.0) now has pads for a backlighting circuit to the left of the Teensy. The complete set of indicator LEDs, resistors, and a new jumper block are now on the right. Spare resistor pads have been provided in both sections.
This means that:
a) All users can easily relocate/wire the indicator LEDs with a 4-wire cable.
b) Manual wiring of a backlight circuit is supported directly via power, a transistor mount, resistor(s), and pads for running wires to LEDs and resistors anywhere you want backlighting. All positions already had MX-compatible LED pads for manual backlighting. This just makes the task simpler. (Please note that the CAPS switch is already wired for an indicator LED, so those traces will have to be modified if a backlight is desired at that position.
As always, through-hole components with 0.100"/2.54mm spacing for easy soldering are used throughout.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
p.s. I may run a trace from a PWM pin from the Teensy directly to the signal pin on the transistor. I'd like comments on that idea, please.
Post by: kmba on Sun, 15 January 2017, 14:29:34
Post by: rpelkey13 on Mon, 16 January 2017, 03:21:40
Post by: samwisekoi on Mon, 16 January 2017, 10:01:59
One thing I'm wondering is if there's any chance of adding support for an RGB strip. I know RGB is a meme, but with QMK being able to control strips, it feels kinda wasteful to not have a simple underglow available for the banging acrylic bottom case I'll more than likely be commissioning.
How many pins does it take? Can you point me to a thread with some design details?
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Spaceman1200 on Mon, 16 January 2017, 11:56:43
One thing I'm wondering is if there's any chance of adding support for an RGB strip. I know RGB is a meme, but with QMK being able to control strips, it feels kinda wasteful to not have a simple underglow available for the banging acrylic bottom case I'll more than likely be commissioning.
How many pins does it take? Can you point me to a thread with some design details?
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
I'm having problems finding any pics of it, But it should just be 3 to 4 pins.5V,GND and PB pin.
I did find a video on a planck rgb kit I dont know how much help it will be to this project, But hey, it's something
Post by: rpelkey13 on Mon, 16 January 2017, 13:44:53
One thing I'm wondering is if there's any chance of adding support for an RGB strip. I know RGB is a meme, but with QMK being able to control strips, it feels kinda wasteful to not have a simple underglow available for the banging acrylic bottom case I'll more than likely be commissioning.
How many pins does it take? Can you point me to a thread with some design details?
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
The WS2812 led strip takes 3 pins: VCC, GND, and a single data pin. There is information and a datasheet here https://www.sparkfun.com/products/12025. Some info about using the strip can also be found partway down this page https://github.com/jackhumbert/qmk_firmware/wiki under "RGB Under Glow Mod".
Post by: samwisekoi on Mon, 16 January 2017, 15:14:40
- Ron | samwisekoi
One thing I'm wondering is if there's any chance of adding support for an RGB strip. I know RGB is a meme, but with QMK being able to control strips, it feels kinda wasteful to not have a simple underglow available for the banging acrylic bottom case I'll more than likely be commissioning.
How many pins does it take? Can you point me to a thread with some design details?
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
The WS2812 led strip takes 3 pins: VCC, GND, and a single data pin. There is information and a datasheet here https://www.sparkfun.com/products/12025. Some info about using the strip can also be found partway down this page https://github.com/jackhumbert/qmk_firmware/wiki under "RGB Under Glow Mod".
Post by: rpelkey13 on Mon, 16 January 2017, 20:51:12
Post by: samwisekoi on Mon, 16 January 2017, 21:54:09
I said it would take a complete re-route of the controller and all the row/column feed traces to provide a removable numpad. So fine. I did that, and here it is.
Version 2.0 of the GH-122.2017 now with:
- Modular numpad.
- Pads for backlight circuit.
- Pads for addressable RGB LED strips.
Done for the night, me.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Niomosy on Tue, 17 January 2017, 01:21:14
Okay, fine.
I said it would take a complete re-route of the controller and all the row/column feed traces to provide a removable numpad. So fine. I did that, and here it is.
Version 2.0 of the GH-122.2017 now with:This does mean a complete QA and test run will be required, but hey. What are you gonna do?
- Modular numpad.
- Pads for backlight circuit.
- Pads for addressable RGB LED strips.
Done for the night, me.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Well damn, that's a rather pleasant surprise. You're creating quite the monster here.
Post by: Phenix on Tue, 17 January 2017, 02:37:07
As I assume VE. A Style split/nav block splittable is going to be another reroute, I wont push luck any further, as I am already very very happy with the numpad-split
Post by: Pwner on Tue, 17 January 2017, 03:16:19
Well damn, that's a rather pleasant surprise. You're creating quite the monster here.
Seriously.. this thing is great. I don't need one of these, but I certainly want one!
Post by: samwisekoi on Tue, 17 January 2017, 12:08:39
One thing I've already done is add traces and pads to provide access to eight of the internal pins. I did this because the new controller board used 100% of the external pins, and I want the extreme hobbyists to be able to expand the capabilities somehow. So more pins are available, although totally optional and unneeded in any use I've foreseen. Also, I've given up on changing the gutter spacing. That means that the $20 Unicomp case can still be used. And a few possible updates could not be made. Tradeoffs, eh?
So I am going to focus on clean-up, QA, documentation, etc. I'll continue to post updates as I make significant progress. Please do not hassle me here or via PM if I haven't released something you want yet!
Also, in parallel to the PCB, I have been working on a reference case, plate and keycap set. I am not sure how I will release those, but they are coming. (In fact I have most of the prototype items back from the fabricators already.)
Finally, the new controller wiring means a completely new pinout/matrix. I will attempt to get the GH-122.2017 (v.2) into Easy Keymap. Other firmware tools are for others to work on.
That's it for now. I'll switch over to my CAD machine and grab a current layout and attach it to this post.
Cheers!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: samwisekoi on Tue, 17 January 2017, 13:02:29
Pin Circuit
D7 COL_1
E6 COL_2
E0 COL_3
E1 COL_4
C0 COL_5
F0 COL_6
C1 COL_7
F1 COL_8
C2 COL_9
F2 COL_10
C3 COL_11
F3 COL_12
C4 COL_13
F4 COL_14
C5 COL_15
F5 COL_16
C6 COL_17
F6 COL_18
C7 COL_19
F7 COL_20
D0 COL_21 (UPDATED 170201)
E7 COL_22
D5 COL_23
D4 COL_24
B6 ROW_A
B5 ROW_B
B4 ROW_C
B3 ROW_D
B2 ROW_E
B1 ROW_F
B0 ROW_G
D1 NUM_LED (PWM)
D2 CAPS_LED
D3 SCRL_LED
B7 BACKLIGHT (PWM) (UPDATED 170201)
Post by: jal on Tue, 17 January 2017, 13:06:37
said it would take a complete re-route of the controller and all the row/column feed traces to provide a removable numpad. So fine. I did that, and here it is.
Auto-typed by my GH-122 keyboard.
Holy crap, was not expecting that! Wow.
Post by: rpelkey13 on Tue, 17 January 2017, 14:07:28
Post by: samwisekoi on Tue, 17 January 2017, 15:12:14
Man, this keeps getting better and better. I'm basically committed at this point, just have to work on finding a set with enough row correct caps to cover it. Maybe find some nice cherry profile relegendables if they exist.
I am working on a quote from SP for an inexpensive black/white DCS 122-key set including 20 relegendables for the top row and left function block. Sadly, they are currently out of black DCS relegendables, or many normal sets would work. I also have very good pricing from WASD for a 150-key custom set which would enable builders to specify the legends for all of the extra keycaps. WASD uses OEM-profile ABS keycaps, and do not have a 7u spacebar, but it will be an option.
So there will be one or two inexpensive keycap sets.
Finally, there are a number of SA sets that are coming up in 2017 that will have relegendables. Some of them are quite nice, if you like SA keycaps. (I am currently typing on SA keycaps on MX White switches.)
So there are some options for keycap sets.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
[attachimg=1]
Post by: Niomosy on Tue, 17 January 2017, 16:17:03
Post by: Phenix on Tue, 17 January 2017, 16:24:02
can I jumper the complete upper two rows (eg usage in the unicomp case)?
Is it possible to make these areas (F-blocks) detachable (via sockets) or is this technically not possible?
(meaning the case if the F-KEY-Module is not attached)
Post by: samwisekoi on Tue, 17 January 2017, 18:11:02
An general question regarding the Upper-bank-jumpering:
can I jumper the complete upper two rows (eg usage in the unicomp case)?
Is it possible to make these areas (F-blocks) detachable (via sockets) or is this technically not possible?
(meaning the case if the F-KEY-Module is not attached)
I am not sure I understand these questions, but everything you mention should be possible. Perhaps not easy, mind you, but possible.
I will do a Pixel Art collection of the possible configurations.
Auto-typed by my GH-122 keyboard.
- Ron | samwisekoi
Post by: samwisekoi on Tue, 17 January 2017, 18:54:29
The horizontal split in BLUE is designed to be bridged, so the upper and lower sections can be bent and/or separated using jumper wires. The vertical splits shown in YELLOW are not designed to be bridged, so if you cut off columns 1 and 2, the PCB is permanently narrower. (I suppose a true master could jump between the switch pins, but the PCB isn't designed for that!)
The upper-right section is the controller, and due to space requirements, includes the 6 switch positions shown. You absolutely can use the controller when it is cut away from the rest of the PCB, but I do not guarantee that you will still be able to use those 6 switch positions. Maybe you can; just no promises from me.
With the exception of those 6 positions on the controller section, you can make the upper bank be as long or as short as you like. My example shows it in the F-122/Unicomp 2x12 configuration, but it could be anything up to and including 2x17. Or as small as the standard ANSI upper row of Escape, then 4, 4, 4, if you like. (Half-spaces are provided all along the top for that.)
I've shown the controller section tucked under the main body of the keyboard, but as long as all the connections are made, it can be wherever you like.
Again, these are not all of the possibilities. You could make some weird T-shaped thing if you like. But hopefully this answers most of the "what can I build?" questions.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: dead_pixel_design on Wed, 18 January 2017, 15:37:40
Post by: rpelkey13 on Wed, 18 January 2017, 17:32:21
Adding all of that optionality for cutting the board into segments isn't going to compromise the structural integrity of the PCB for those of us that want it to stay together right?
All it's doing is adding silkscreen guidelines and some pinholes to solder to, so there should be no change in the structure.
Post by: samwisekoi on Wed, 18 January 2017, 17:57:45
Adding all of that optionality for cutting the board into segments isn't going to compromise the structural integrity of the PCB for those of us that want it to stay together right?
All it's doing is adding silkscreen guidelines and some pinholes to solder to, so there should be no change in the structure.
What he said.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
[EDIT]
Well, if you actually cut the PCB, the structure will be compromised!
[/EDIT]
Post by: dead_pixel_design on Wed, 18 January 2017, 19:00:04
Post by: donutcat on Wed, 18 January 2017, 22:34:28
Post by: samwisekoi on Thu, 19 January 2017, 09:34:29
Are there any photos you would be willing to share of the reference case prototype?
Coming soon...
I have not received everything yet. When I do (assuming all the parts fit) I will provide photos of a case design that works with or without a plate, and provides an inexpensive way to change layouts (e.g. from F-122 to ANSI+50).
Looks like a fun project, especially with RGB capabilities. what's the distances between the switch outlines and the edge of the mounting holes? Wondering if I could do a hipro case using the PCB itself as a layer of the case, so keeping the outer dimensions the same as the PCB itself. It's kinda funny trying to keep the size down on a board this size, but it'd be clean to the PCB.
The mounting holes are .125" in diameter and .125" in from the edges. You can absolutely make such a case, but please wait for me to publish a physical specification/drawing before you do.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: donutcat on Thu, 19 January 2017, 13:39:34
Quote
The mounting holes are .125" in diameter and .125" in from the edges. You can absolutely make such a case, but please wait for me to publish a physical specification/drawing before you do.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Sure thing. I think I'd have a hell of a time getting all the sizes right just off that mockup of the PCB anyhow.
Post by: samwisekoi on Thu, 19 January 2017, 13:47:15
Anyhow, this looks like the final PCB layout. As it stands, a test run of qty=10 will be $70+/- USD each. I'm not ready for that yet, but soon.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: TerryMathews on Thu, 19 January 2017, 20:34:08
OK, two rounds of QA completed. #1 was a check for shorts at each Teensy pin. #2 was to clean-up some of the issues discovered by the PCB analysis tool. (Keyboard PCBs have lots of "special features" that look like errors; I just fixed the errors that ARE errors!)
Anyhow, this looks like the final PCB layout. As it stands, a test run of qty=10 will be $70+/- USD each. I'm not ready for that yet, but soon.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Bring it on, Ron. My body is ready.
Post by: dead_pixel_design on Fri, 20 January 2017, 12:37:27
Anyhow, this looks like the final PCB layout. As it stands, a test run of qty=10 will be $70+/- USD each. I'm not ready for that yet, but soon.
One question, and it may seem insignificant to some, but do you get to choose the colors of the PCB/screen printed legends/guides on it? I am not going to miss this second run after wishing so badly I could have gotten one of the first ones, but I am going to put the PCB on display in my collection until I have a case built for it, and am more comfortable with assembly so that it gets my best work, not my learning work.. will any consideration be put toward the aesthetic value of the PCB?
Post by: Phenix on Fri, 20 January 2017, 12:52:58
how many traces do I need to jumper if I want to enable
board w/o numpad
->jumpered to an say TRRS socket
->to the external numpad pcb
Post by: xondat on Fri, 20 January 2017, 12:54:04
I'd rock this layout hard
Never expected to see split stuff, but will be interesting making cases for them.
Post by: donutcat on Fri, 20 January 2017, 14:02:42
I (still) have problems getting it - the numpad is choppable.
how many traces do I need to jumper if I want to enable
board w/o numpad
->jumpered to an say TRRS socket
->to the external numpad pcb
If you want a board with detached numpad but still able to use the numpad, it looks like you have 9 traces to jump, 4 columns and 5 rows. If it was 8 I could see a neat double TRRS connection going, but at 9 you're reaching USB C or HDMI territory
Post by: Phenix on Fri, 20 January 2017, 14:36:01
Thanks for the info - now I can look for sth
Post by: samwisekoi on Fri, 20 January 2017, 15:13:01
One question, and it may seem insignificant to some, but do you get to choose the colors of the PCB/screen printed legends/guides on it? I am not going to miss this second run after wishing so badly I could have gotten one of the first ones, but I am going to put the PCB on display in my collection until I have a case built for it, and am more comfortable with assembly so that it gets my best work, not my learning work.. will any consideration be put toward the aesthetic value of the PCB?
My boards have always been white on black, and yes, some consideration will be put toward the aesthetic value of the PCB. Personally, I'd like it to look good enough to be on a wall. We'll see.
I (still) have problems getting it - the numpad is choppable.
how many traces do I need to jumper if I want to enable
board w/o numpad
->jumpered to an say TRRS socket
->to the external numpad pcb
Hmmm. I think we are talking at cross-purposes here. Do you want the numpad to be removed and still be useable on its own? Personally, I'd use a GH-36 for the numpad and just shorten the GH-122, but for the moment, I'll work with what I think is your plan. I am going to discuss it in two parts; #1 making a 7x20 GH-122 and then #2 re-using the GH-122 numpad.
Making a 7x20 (TKL) GH-122.
OK, let's walk through this for the first time. I am thinking as I type, so do NOT use this as instructions in the future. But to give you an idea, here is how I would do it:
1. Carefully slice only the horizontal and vertical splits necessary to remove the GH-122.2017 controller section. (This section includes 6 switch positions, the Teensy++, the indicator LEDs, the jumper pads for CAPS, COLS 1-17, COLS 18-20, COLS 21-24, and the jumper pads for ROWS A-G.
2. Carefully slice the vertical split to remove the numpad.
3. Determine how you will be mounting the controller section. For this configuration, I suggest mounting it so the right edge of the controller section aligns with the (newly cut) edge of the nav block. This keeps the Teensy and the indicator LEDs exposed. There are two mounting holes above COL_14 to enable this mounting. Spacers will be required.
4. Connect the 20 COL jumpers using a 0.10"/2.54mm-pitch ribbon cable or equivalent. Also jump the 2 CAPS+ and CAPS- pads, if desired.
5. Jump ROW A and ROW B from the controller to the 2 labeled pads on the function block.
6. Jump ROWS C-G from the controller to the 5 labeled pads between the alpha and nav blocks.
So that was 20+2+5=27 jumper wires total. 29 if you include the CAPS circuit to the LED on the capslock key.
7. Install the Teensy, LEDs, resistors, diodes, and switches and test everything. Add firmware, then de-bug and fix as needed.
8. Mount and enjoy.
That is all designed to work. let's move on to the experimental numpad re-use.
Re-using a GH-122 Numpad on its own.
This will need to be mounted and encased somehow. That will be difficult, but not impossible. Also, the left-hand switches (1,4,7,NUM) will be perilously close to the cut edge. It should work...
1. Connect the 4 COL 21-24 jumpers using a 0.10"/2.54mm-pitch ribbon cable or equivalent.
2. Connect the 5 rows C-G somehow to either the controller or the main PCB. The diodes are on the columns, so those aren't a problem, but the rows don't (as of now) have pads for this purpose. (Maybe I will add them.) I think I would use the row pads for Alps switches to connect switch C20 to C21, D20 to D21, etc. The row connectors are the switch connectors closest to the diodes. You could also absolutely connect the rows up to the controller. I may add jumper pads for this purpose, but they are not there yet.
Anyhow, that is another 9 connections to enable re-use of the cut-off numpad.
Sorry there are no pictures, but does that wall of text help?
- Ron | samwisekoi
Post by: Phenix on Fri, 20 January 2017, 16:24:34
Looks like just using an GH36 pcb (once available) is easier (interestingly I cant find any programmable numpad pcb for sell (beside winkeyless/gon) - the AMJpad is sold out, and cluepad hasn't a split zero key
Is it odd that I enjoy looking at an complete gh122 the most?
Most of the other layouts are for sure nice, but look a bit.... off..
Post by: Data on Fri, 20 January 2017, 16:53:35
It's really a celebration of excessive inputs.
Post by: donutcat on Fri, 20 January 2017, 17:38:08
Post by: jal on Fri, 20 January 2017, 19:54:12
The GH-122 is best enjoyed with the maximum number of switches one can tolerate.
It's really a celebration of excessive inputs.
Absolutely. Haven't started designing it yet (too focused on how to set up the milling machine I'll cut it on), but I fully intend to make a massive, sprawling case for this. I'm thinking of some tall, imposing design element behind the Fkey rows, maybe an avant garde pattern. The thing has to be sovereign, and so far think a shiny, heavy 20's feel would work well.
Post by: Phenix on Sat, 21 January 2017, 10:23:08
I will try in making an large wood case, atleast 1cm bezel (or what something like 6cm be better fitting for such an giant? ;) )
Post by: Hak Foo on Sat, 21 January 2017, 12:56:09
Post by: samwisekoi on Sat, 21 January 2017, 13:17:07
There are pads on the rows between COL_21 and 22, as well as a second set of ROW pads up on the controller.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: donutcat on Thu, 26 January 2017, 00:01:47
Post by: beard on Thu, 26 January 2017, 04:47:04
I don't usually join forums like this because I have no use for small keyboards, but this seems like a great idea.
Post by: Niomosy on Thu, 26 January 2017, 11:47:57
Any idea when we'll be able to throw money at you for this? I don't want to seem impatient, but I'm getting antsy for a build.
Much as I would like one, my wallet is content to be patient with this one right now. That and it might be a bit before I can really tackle assembly.
Post by: samwisekoi on Thu, 26 January 2017, 12:01:57
I've received the parts for my planned case, and unfortunately the 3D-printed frame has the same straightness issue you'd expect in something shaped exactly like two 20" PBT spacebars. Or a jumbo banana. <sigh> It is currently buried under a couple of pieces of thick sheet metal as I try to coax it into straightness.
In parallel, I have
Next, I am working on a couple of low-cost keycap options, one from SP and another from WASD. Right now, the hardest problem I have there is deciding what possible legends I could use on 150 +/- keycaps. (The SP option will contain around 20 re-legendables.) So that is keycaps.
Then there is a plate. I have an acrylic sample of a universal plate that I will eventually target for stainless steel. I'd like to make a plate that everyone can use so the volume is high and the cost is as low as possible.
Finally the PCB. I am doing some clean-ups and virtual circuit tests now. Once that is done I will prepare a physical specification/drawing for mounting and case design. And slicing and dicing. Once that is done, I will do a test run of 10 Beta PCBs, and if my testing works, will ship the others (possibly along with flat-pack case components) to 5 or more experienced builders in the US to prove the v.2 design. (The US thing is only for postage reasons, including tracking and customs.)
After all of that is done, I will work out a Group Buy model that hopefully includes EU and Asia/Pac hubs.
That's all the news from here.
- Ron | samwisekoi
Post by: dead_pixel_design on Thu, 26 January 2017, 13:10:39
Post by: donutcat on Thu, 26 January 2017, 13:52:59
Post by: TerryMathews on Thu, 26 January 2017, 17:26:06
Once that is done, I will do a test run of 10 Beta PCBs, and if my testing works, will ship the others (possibly along with flat-pack case components) to 5 or more experienced builders in the US to prove the v.2 design. (The US thing is only for postage reasons, including tracking and customs.)
If you're taking applications, I'd like to put my hat in the ring. Reworking and diagnosing keyboards doesn't scare me (anymore) and I've got experience building the following:
* Let's Split v2
* Ergodox
* Phantom
* Several other PCB kits including ZZ96, VE.A, and B.87
I also ported QMK to the Phantom, the Tada68, and cleaned up the code on Satan GH60 and Let's Split. I'd like to port QMK to this.
Post by: samwisekoi on Thu, 26 January 2017, 18:25:49
Once that is done, I will do a test run of 10 Beta PCBs, and if my testing works, will ship the others (possibly along with flat-pack case components) to 5 or more experienced builders in the US to prove the v.2 design. (The US thing is only for postage reasons, including tracking and customs.)
If you're taking applications, I'd like to put my hat in the ring. Reworking and diagnosing keyboards doesn't scare me (anymore) and I've got experience building the following:
* Let's Split v2
* Ergodox
* Phantom
* Several other PCB kits including ZZ96, VE.A, and B.87
I also ported QMK to the Phantom, the Tada68, and cleaned up the code on Satan GH60 and Let's Split. I'd like to port QMK to this.
Yes, that is exactly the sort of experience we will need. Thanks for the hat. Accepted.
- Ron | samwisekoi
Post by: Data on Thu, 26 January 2017, 20:07:25
A brief update...
I've received the parts for my planned case, and unfortunately the 3D-printed frame has the same straightness issue you'd expect in something shaped exactly like two 20" PBT spacebars. Or a jumbo banana. <sigh> It is currently buried under a couple of pieces of thick sheet metal as I try to coax it into straightness.
Blast it with a hair dryer for a few minutes. Maybe try heating it without the weight first, then apply weight if its own mass doesn't bring it down to level. I hear PBT responds well to this method.
Post by: donutcat on Fri, 27 January 2017, 01:05:27
-An RS96 build that I later desoldered to sell
-A b.mini ex that I completely soldered aside from the controller components, including 2 sets of switches soon to be a third to change spring weights
-2 iterations of a 101key Ortho custom layout, one version of which actually used a cut up and stitched together PCB from a CM board I had with spill damage, both versions of which ran TMK
- A Soarer's conversion on a 1991 model M122, which was actually my first mech and also my first delve into large boards.
I've also done a fair bit of desoldered and switch replacement in boards that my brother's currently use, a cherry MX board 3.0 and a qfr, some trace repair in those same boards(they were really hard on those boards the first couple months), and Ive also done a wee bit of soldering and repair on a USB hub that I integrated into my Ortho build.
I'm definitely interested in working towards complete QMK support for this board as I'd love to see some RGB shenanigans with it and complete windows compatible keymappings to enable full in game remappability, but I'm also really interested in the idea of having it run Soarer's as well since the possibility is there with the teensy controller. I'm also really intrigued by the different case possibilities for a board of this caliber, and have a CNC case maker contact that is also looking forward for the eventual chance to work with this board.
Chosen or not, I think the only way I could possibly pass up on this board is if I became homeless tomorrow.
Post by: Spaceman1200 on Fri, 27 January 2017, 04:09:33
GH-122 v1
Bx.mini
Alps64
Monarch
Let's Split V2
2 GH60 builds for friends
KUL Re-build for sister
I have alps and mx switches to test with, just incase you are looking for either or, Just shoot me a message on here if you would like my testing help :D
Post by: Phenix on Fri, 27 January 2017, 08:40:16
For me I think QMK istm is better, as it features tap-dance keys..
Post by: samwisekoi on Fri, 27 January 2017, 10:32:07
The astute reader may have noticed that I completely omitted firmware when I listed my current set of actions. That is because firmware is not my thing. (My favorite programming language is solder.) So I am quite interested in having other people set up various firmware engines for the GH-122.2017. That is why I have already published the pinouts.
Regarding the "which is better?" question, I have experience with both Soarer and Easy AVR in this form factor. I do not have any experience with QMX, but can make some general observations about the firmware you will need.
First, memory limitations with 120-150 switches is a problem. Soarer on a Teensy does not have enough memory to properly configure (IMHO) the appropriate AltGr variations on even an F-122, so I have not been able to program everything I'd like on that. To be fair, I have not tried a Soarer on a Teensy++, which may improve that. However, the ability to quickly change keymapping is absolutely a benefit of the Soarer approach, since you will never know how you will use all of these keys until you have the keyboard under your fingers for a while!
Easy AVR, on the other hand, does not seem to have the same memory limitations, although it does require a re-flash for the simplest keymap change. And it isn't very happy re-flashing from a VM. However, it has a hard limit of 14 keyboard macros, which just isn't enough for a GH-122 with up to 50 function keys! I have not looked to see (or asked) if there is a work-around for this constraint, but I hope there is. I do think that the Easy AVR user interface will make firmware creation and customization easier for most users.
So if there were three people who wanted to configure all three engines for the GH-122, we'd be in the best position for everyone. I would certainly test each of them once available.
Just my €.02 for the day,
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard, including the € symbol that my F-122 can't remember.
Post by: donutcat on Fri, 27 January 2017, 10:34:56
In which way is Soarers better than QMK?
For me I think QMK istm is better, as it features tap-dance keys..
I don't know if it's actually better, but one of my favorite features of it is being able to remap keys without reflashing. It's not a very significant thing, but for someone that doesn't need some of the fancier stuff in QMK, Soarer's might be a better solution for them with a board with this many possible maps.
Post by: Phenix on Fri, 27 January 2017, 12:08:36
Post by: Spaceman1200 on Fri, 27 January 2017, 12:18:11
Post by: donutcat on Sat, 28 January 2017, 14:21:55
Sorry, just getting excited lol, Both Soarers and QMK are great choices, but i probably would lean to QMK since i may want to add RGB underglow to my build
Yeah, personally I would prefer QMK for the RGB control as well, but I'm still really wanting to port Soarer's mostly to be able to say I made it work and so it's available. Also, not related to the firmware discussion, but last night while I was streaming some gatistotle making I was telling people about this project and I broke out my M122 to actually get a good estimate on the size. I'm not the best at estimating the size of stuff, but realizing this is gonna be nearly as big as an M122 is crazy, an actual battlestation of a board. Tempted to see if I could get someone like 1up or SwitchSmith to make a custom sized sleeve for it and see their reactions.
Post by: Pwner on Sat, 28 January 2017, 14:34:54
Tempted to see if I could get someone like 1up or SwitchSmith to make a custom sized sleeve for it and see their reactions.
Probably would be easier to just buy a sleeping bag for it. :))
Post by: Phenix on Sat, 28 January 2017, 15:44:14
this wont be an traveling keyboard (at least for me)..
Post by: Hak Foo on Sat, 28 January 2017, 18:35:19
Post by: Data on Sun, 29 January 2017, 12:22:41
Post by: samwisekoi on Sun, 29 January 2017, 13:39:44
Note that EasyAVR only works with a custom keymap file (patch) unless Metalliqaz steps in to resolve the pinout issues in the current live version (2.03.01, now 9 months old).
I have a custom keymap file for the GH-122.2016. we'll get one for the GH-122.2017 somehow.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
[update]
The attached keymap file was created for a special 2.03.01c version of Easy Keymap. To make sure it will work for everyone, I just installed it with a fresh download of the live 2.03.01 on DT and verified it is fully functional on the GH-122.2016.
[/update]
Post by: samwisekoi on Sun, 29 January 2017, 14:59:21
Then we will have at least one working firmware generator.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: TerryMathews on Sun, 29 January 2017, 18:22:35
Then we will have at least one working firmware generator.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
I've got QMK half-done. Pin assignments are complete, setting up the key placements.
Post by: donutcat on Sun, 29 January 2017, 23:22:36
I used Soarer's in my 2016 GH-122. It actually has a mild issue in that the compiler can't handle config lines >320 or so characters. You can get there on a row with a lot of media keys and UNDEFINEDs; you end up filling dead spots with siingle letters to make it fit.
I'm gonna try to make a complete initial config keeping it as trim as possible. I'm also thinking I can do columns per line instead of rows, which with a board this wide would help quite a bit with keeping characters per line down. I'm looking to have my first test config done the end of this week if I can do some cranking on it during work.
Post by: samwisekoi on Mon, 30 January 2017, 10:31:37
(See https://geekhack.org/index.php?topic=86751.msg2353073#msg2353073 (https://geekhack.org/index.php?topic=86751.msg2353073#msg2353073) for updated matrix.)
Note, a wiring change from GH-122.2016 to GH-122.2017 is that ANSI and ISO use the same matrix positions for Enter and |\ keys. This seems weird when you look at a keyboard, but it makes building and mapping MUCH simpler. Trust me on this one.
Anyhow, I hope this helps. I'll add my suggestions for a 122-key mapping later today or tomorrow.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
p.s. I don't use WIN, MENU, PRT, SCR, or PAUSE, so I might have gotten those swapped around. Please let me know if I did. (Neither my GH-122 nor my JD45 are helpful guides!)
Post by: samwisekoi on Mon, 30 January 2017, 12:46:49
(See https://geekhack.org/index.php?topic=86751.msg2353073#msg2353073 (https://geekhack.org/index.php?topic=86751.msg2353073#msg2353073) for updated matrix.)
In Windows, I would map the Fn1+LOCK and ALT+LOCK key as WIN+L. I don't like a single-press LOCK, but I do like my keyboard to have a LOCK function that works in every OS.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
[attachimg=1]
Post by: donutcat on Mon, 30 January 2017, 14:43:24
Edit: Also, I was wondering if you could give us an exact size file that has the mounting holes and some switch cutouts? They guy I have working on my case wants to start doing some initial design testing but needs something to work with.
Post by: Norman_the_Owl on Tue, 31 January 2017, 18:48:56
Currently using an F122 and i love the layout, except i don't use the numpad...Oh baby.
Post by: donutcat on Tue, 31 January 2017, 23:01:06
Post by: samwisekoi on Wed, 01 February 2017, 09:22:30
Re pin D6: Hmmm. Thanks for the feedback. That is very useful. It works fine for Easy Keymap, but let me see what I can do for the Soarer crowd.
Regarding a physical layout drawing; I have intentionally not issued that yet. I am currently cleaning up the mounting holes and cut lines for the prototype run, and will issue a drawing once that is done. However, the physical dimensions of the complete PCB, including the corner mounting holes, the LEDs, and the Teensy location are identical to the GH-122.2016. That drawing is available in that thread. (I don't want to x-post it here to avoid confusing someone skimming this thread.)
I expect to be ready to publish a prototype drawing in about a week. And probably more information about the prototype run as well.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: samwisekoi on Wed, 01 February 2017, 10:23:37
pin D6: Hmmm. Thanks for the feedback. That is very useful. It works fine for Easy Keymap, but let me see what I can do for the Soarer crowd.
Auto-typed by my GH-122 keyboard.
Ok, V.2.1.2 moves COL_21 to D0 and therefore BACKLIGHT to B7. This combines BACKLIGHT and UNDERLIGHT on a single PWM pin.
Updated PCB drawings, pinout table, and keyswitch matrices to follow.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: xondat on Wed, 01 February 2017, 10:27:00
I expect to be ready to publish a prototype drawing in about a week. And probably more information about the prototype run as well.!!!!!!!!!!
Post by: samwisekoi on Wed, 01 February 2017, 10:40:38
- Ron | samwisekoi
Post by: samwisekoi on Wed, 01 February 2017, 11:01:06
- Ron | samwisekoi
Post by: samwisekoi on Thu, 02 February 2017, 15:57:29
Several notes:
1. Interior mounting holes and cut-lines are not final, and therefore not shown.
2. What is shown is final.
3. Teensy++ 2.0 circuit board and mini B USB connector are centered over column 22.
4. LED holes are centered over column 24, and are centered on the mid-line between rows A and B, and placed on 0.375" centers.
5. All mounting holes are 0.125" in diameter or ~3mm.
6. All LED holes are 0.250" in diameter or ~6mm.
7. Exterior dimensions of the PCB are nominal. Cases should allow for 1/16" (1.5mm) extra room outside of each edge for slightly oversize PCB cuts.
Drawing is in inches.
Hope this helps. A more complete drawing or set of drawings will be available after the pre-production run at the latest.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Data on Thu, 02 February 2017, 15:59:57
Post by: xondat on Thu, 02 February 2017, 16:15:30
Pre-production PCB layout.
Several notes:
1. Interior mounting holes and cut-lines are not final, and therefore not shown.
2. What is shown is final.
3. Teensy++ 2.0 circuit board and mini B USB connector are centered over column 22.
4. LED holes are centered over column 24, and are centered on the mid-line between rows A and B, and placed on 0.375" centers.
5. All mounting holes are 0.125" in diameter or ~3mm.
6. All LED holes are 0.250" in diameter or ~6mm.
7. Exterior dimensions of the PCB are nominal. Cases should allow for 1/16" (1.5mm) extra room outside of each edge for slightly oversize PCB cuts.
Drawing is in inches.
Hope this helps. A more complete drawing or set of drawings will be available after the pre-production run at the latest.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Off to work I go!
Post by: donutcat on Thu, 02 February 2017, 17:18:37
Post by: samwisekoi on Fri, 03 February 2017, 11:50:59
That's all I'm saying...
- Ron | samwisekoi
Post by: elecplus on Fri, 03 February 2017, 12:00:37
Post by: donutcat on Fri, 03 February 2017, 13:30:15
The wise man would wait until Monday before cutting metal or plastic.
That's all I'm saying...
- Ron | samwisekoi
Definitely not cutting anything yet, I'm still in the design drawing stage, but now I have some good numbers to go off of. And also, you didn't say don't cut any wood yet :D
Post by: xondat on Fri, 03 February 2017, 13:41:06
The wise man would wait until Monday before cutting metal or plastic.CNY restricts any physical progress :'(
That's all I'm saying...
- Ron | samwisekoi
Post by: Spaceman1200 on Fri, 03 February 2017, 14:14:04
Post by: dead_pixel_design on Fri, 03 February 2017, 14:19:35
Post by: samwisekoi on Fri, 03 February 2017, 16:13:21
Potato pic from https://www.instagram.com/samwisekoi/
GH-122.2017 custom #keyboard with a full set of 150 custom keycaps from @wasdkeyboards. #geekhack
- Ron | samwisekoi
Post by: dead_pixel_design on Fri, 03 February 2017, 16:16:12
(Attachment Link)
Potato pic from https://www.instagram.com/samwisekoi/
GH-122.2017 custom #keyboard with a full set of 150 custom keycaps from @wasdkeyboards. #geekhack
- Ron | samwisekoi
Good god it's beautiful.
Post by: donutcat on Fri, 03 February 2017, 16:51:58
(Attachment Link)
Potato pic from https://www.instagram.com/samwisekoi/
GH-122.2017 custom #keyboard with a full set of 150 custom keycaps from @wasdkeyboards. #geekhack
- Ron | samwisekoi
That's such an amazing potato. If I may, what was the approximate price on the caps?
Post by: samwisekoi on Fri, 03 February 2017, 17:19:27
- Ron | samwisekoi
Post by: Data on Fri, 03 February 2017, 22:52:12
(Attachment Link)
Potato pic from https://www.instagram.com/samwisekoi/
GH-122.2017 custom #keyboard with a full set of 150 custom keycaps from @wasdkeyboards. #geekhack
- Ron | samwisekoi
Awesome.
But you're missing 6 keys. :confused:
Post by: samwisekoi on Sat, 04 February 2017, 17:26:42
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: xondat on Sat, 04 February 2017, 17:34:32
I'll just leave this here...That's a hell of a minimal case!
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: donutcat on Sat, 04 February 2017, 17:37:51
I'll just leave this here...
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Mmm, the lowest of profiles.
Post by: Phenix on Sat, 04 February 2017, 18:21:59
Is the RCTRL caps 1.25u? It looks alike, because of that small gap - am I wrong?
Post by: samwisekoi on Sat, 04 February 2017, 23:55:52
Is the RCTRL caps 1.25u? It looks alike, because of that small gap - am I wrong?
Ah, I had the switch in the wrong position, so it was offset for the photo. Easy fix. All better now.
- Ron | samwisekoi
Post by: Spaceman1200 on Sun, 05 February 2017, 10:53:45
Post by: donutcat on Mon, 06 February 2017, 01:38:59
Post by: samwisekoi on Mon, 06 February 2017, 11:32:10
Here's a question now that you've got a built one to test with. What is the fit of the switch legs in the PCB holes? I know some PCBs have a really snug grip on the legs and others are easier to work with. I know I could always snip the legs since I only do plate builds, but I prefer the extra rigidity they give, especially for clicky switches.
All the holes are to Cherry specs. The switch leads are flat, and fit easily into the holes. They also are easy to de-solder and remove. And they are very strong when properly soldered in place.
In addition, when I build a keyboard, I use PCB-mount switches for rigidity and proper orientation. To support this, all of the PCBs I design support PCB-mount (so-called "5-pin") switches.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: donutcat on Mon, 06 February 2017, 14:45:15
Post by: samwisekoi on Thu, 09 February 2017, 11:49:03
My plan is to have a ready-kit for the first/proto builders of the GH-122.2017. So I have been experimenting with cases and keycaps, as you've seen with my teaser shots. Unfortunately, one thing I have learned is that 19.5" is too long for acrylic or nylon to span without bending. So I am working on a basic case design that will be rigid enough, and that design work includes modification of mounting holes in the PCB.
Thus, the proto-PCB is evolving around the edges to help ensure it will work in a slim sandwich case. (And in a machined metal case.)
In parallel, my 3D-printed prototypes for fancier cases are exhibiting the typical issues of long pieces of plastic. Warping. I have about got that sorted, but again, the base might need to be metal.
The good news for both efforts is that a water-jet cut metal base in .125" aluminum would cost around $25 USD for qty=5+.
Anyhow, work continues. And again, I caution anyone designing a case to please wait for finalized drawings of at least the prototype PCB.
Finally, and this is important, please do not try to have back-and-forth conversations with me outside of this thread. I check this thread every day, and reply when I can or must. Trying to also keep up with people who want to use PM or e-mail to discuss topics already in this thread is, frankly, just annoying. Please use this thread to ask questions about any aspect of the GH-122.2017.
Thanks and best regards,
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: Data on Thu, 09 February 2017, 12:03:27
Post by: samwisekoi on Thu, 09 February 2017, 14:00:45
Interested to see where the case options go for this version. We were kind of trailblazing in the first round.
Yes indeed. I am hoping to be a tad less Wild West this time around. Specs and a reference design or two.
- Ron | samwisekoi
p.s. Having said that, your work was great, and I am certainly happy with the GH-122.2016 Unicomp/MX White/SA keyboard I use as my home daily driver.
Post by: Data on Fri, 10 February 2017, 06:51:12
Post by: samwisekoi on Fri, 10 February 2017, 09:46:09
Thanks. My only regret is the way I mounted the Teensy causes the USB port to be so low relative to the PCB that the entire case has to be fairly tall to accommodate it. Allowing for a bulky-ish USB connector/cable (I have 4mm clearance at the moment) means the bottom standoffs are 3/4" and the entire case sits a full 1-1/4" off the desk. She's nearly as tall as she is wide. :))
Yep. I am using a .750" cutout just under the Teensy to let the USB connector hang down on my sandwich prototype, and I had to get a very small 90-degree USB cable to fit inside the Unicomp case.
- Ron | samwisekoi
Post by: donutcat on Sat, 11 February 2017, 17:17:09
My friend is putting in work for my case design
Post by: Data on Sat, 11 February 2017, 20:33:40
Post by: donutcat on Sat, 11 February 2017, 23:36:39
Looks like SketchUp. :cool:
Probably, but if he knows what he's doing then it's whatever.
(http://i.imgur.com/MhY7Cagl.png) (http://i.imgur.com/MhY7Cag.png)
Took me forever in Inkscape to get this plate setup, so it's probably better to let him deal with the 3d design.
Post by: Data on Sun, 12 February 2017, 11:08:19
Looks like SketchUp. :cool:
Probably, but if he knows what he's doing then it's whatever.
(http://i.imgur.com/MhY7Cagl.png) (http://i.imgur.com/MhY7Cag.png)
Took me forever in Inkscape to get this plate setup, so it's probably better to let him deal with the 3d design.
If you can do that in Inkscape then you should try 2D CAD (I use AutoCAD). It looks great but it probably would have been a ton easier with the right tools. :thumb:
Post by: samwisekoi on Sun, 12 February 2017, 13:41:01
(And blame IBM for those widths, not me.)
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: TerryMathews on Sun, 12 February 2017, 18:57:39
Post by: samwisekoi on Mon, 13 February 2017, 09:24:02
Am I correct this will work in an IBM F-122 case?
Hmmm. An original IBM F-122 case? Probably. I can measure mine to see if the gutter spacing is correct, but unless I take my F-122 apart (which I won't) I cannot promise there is enough interior space.
However, it absolutely will fit in a Unicomp PC-122 case, which is really an IBM Model M. I am currently using such a case to type this reply. Plenty of room for that build, and you will only need a few inexpensive acrylic spacers and a hot glue gun. (And wire and solder, etc.)
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: donutcat on Tue, 14 February 2017, 14:37:54
Getting there :D
Post by: TerryMathews on Tue, 14 February 2017, 14:52:28
Am I correct this will work in an IBM F-122 case?
Hmmm. An original IBM F-122 case? Probably. I can measure mine to see if the gutter spacing is correct, but unless I take my F-122 apart (which I won't) I cannot promise there is enough interior space.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Gotcha. I've got one of those M-122 cases that are basically identical to the F-122. As long as it mostly fits, I'll massage the insides to make it fit.
Post by: happylacquer on Thu, 16 February 2017, 04:45:15
Post by: samwisekoi on Thu, 16 February 2017, 09:49:53
Man, I wish I knew about this before the PCB orders went in. Would love to be typing on this bad boy right now :thumb:
You do know about this before the PCB orders will go in.
I am am typing this on last year's model.
- Ron | samwisekoi
Auto-typed by my GH-122(2016) keyboard.
Post by: Potatomonkey on Thu, 16 February 2017, 13:32:37
Post by: samwisekoi on Thu, 16 February 2017, 15:30:30
When would the estimated GB date be?
No schedule yet. Soon-ish.
- Ron | samwisekoi
Post by: Data on Thu, 16 February 2017, 19:25:56
Man, I wish I knew about this before the PCB orders went in. Would love to be typing on this bad boy right now :thumb:
You do know about this before the PCB orders will go in.
I am am typing this on last year's model.
- Ron | samwisekoi
Auto-typed by my GH-122(2016) keyboard.
Last year's still extremely wonderful and superb model. :cool:
Post by: ErgoMacros on Sat, 18 February 2017, 02:40:27
As far as Firmware options go, here's another possibility:
https://asylum.madhouse-project.org/blog/2017/02/15/Shortcutting-Kaleidoscope/
"Kaleidoscope" originally started for the Keyboardio project, but intended to be usable on many keyboards.
Gergely Nagy (algernoone) has adapted it to the shortcut.gg pre-production keyboard. See above.
Runs on an Arduino-compatible MCU.
Post by: samwisekoi on Sat, 18 February 2017, 11:33:33
Yesterday the raw .125" aluminum plate came in for the new base plate on the GH-122.2017 sandwich case. I drilled and tapped the four corner holes and it worked! No bowing, no problems! I posted one quick pic to Instagram which 32 of you have already seen!
Anyhow, that gave me enough information to decide where to place mounting holes in the first run of GH-122.2017 PCBs. In addition to the four corners, I will put mounting holes on the top and bottom edges centered in the gaps on each side of the main block. That will be eight edge holes, and there will be a center hole between G and H as on the Pok3r PCB.
[attach=2]
GH-122.2017 Proto PCB mounting holes shown in RED.
That may not be perfect, but it will be enough for the proto run. My goal for the first run is to find bugs and to get feedback on things like where the production mounting holes should be located.
Now that I have the proto mounting holes decided, I can update the CAD files, create some documentation, and launch the first buy. FYI, I really want the first five keyboards to actually get built, so they will only be available in partial kit form. And since some of the most involved people in this thread have been outside of the US, I'll be open to exceptions to the USPS Priority Mail rule. (I'm looking at you, Phenix!)
TL;DR I built the first proto case, know where the proto PCB mounting holes will go, and am ready to do a limited edition first run.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: samwisekoi on Sat, 18 February 2017, 14:11:52
- Ron | samwisekoi
Post by: donutcat on Sun, 19 February 2017, 03:45:00
Post by: Phenix on Mon, 20 February 2017, 16:22:11
Quote
(I'm looking at you, Phenix!)
TL;DR I built the first proto case, know where the proto PCB mounting holes will go, and am ready to do a limited edition first run.
Thanks that I get featured ^-^
Do you happen to have any informations about the limited edition?
(like pricing/included stuff - this is also important for others)
Post by: donutcat on Mon, 20 February 2017, 19:06:31
Have some mounting dimensions.
- Ron | samwisekoi
Just confirming that these are the physical dimensions of the PCB itself? I'm pretty sure that's what it is, but I'm double checking so I don't make silly mistakes in case design.
Post by: Potatomonkey on Mon, 20 February 2017, 19:13:59
Post by: jal on Mon, 20 February 2017, 21:23:07
Post by: nathanrosspowell on Mon, 20 February 2017, 21:43:25
Are my eyes playing tricks on me or does this support a split space?
Read the OP.
✓[REQUESTED FEATURE] Split spacebar.
:thumb:
Post by: Potatomonkey on Mon, 20 February 2017, 21:56:05
Are my eyes playing tricks on me or does this support a split space?
Read the OP.✓[REQUESTED FEATURE] Split spacebar.
:thumb:
I totally missed that lol
Post by: samwisekoi on Tue, 21 February 2017, 09:46:53
The PCB is 19.50" x 6.50" (nominal). See either drawing. Allow for 1/16th" extra around perimeter.
Split spacebar? Check. (In case you need MORE keys...)
Kit components? I need to get some numbers together. Please give me a couple of days for that.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: xondat on Tue, 21 February 2017, 10:30:21
Now that I have the proto mounting holes decided, I can update the CAD files, create some documentation, and launch the first buy. FYI, I really want the first five keyboards to actually get built, so they will only be available in partial kit form. And since some of the most involved people in this thread have been outside of the US, I'll be open to exceptions to the USPS Priority Mail rule. (I'm looking at you, Phenix!)
So there will be two portions to the buy? 5 kits, and unlimited PCBs afterwards?
Post by: samwisekoi on Tue, 21 February 2017, 11:43:02
Now that I have the proto mounting holes decided, I can update the CAD files, create some documentation, and launch the first buy. FYI, I really want the first five keyboards to actually get built, so they will only be available in partial kit form. And since some of the most involved people in this thread have been outside of the US, I'll be open to exceptions to the USPS Priority Mail rule. (I'm looking at you, Phenix!)
So there will be two portions to the buy? 5 kits, and unlimited PCBs afterwards?
That's the plan.
- Ron | samwisekoi
Post by: Hak Foo on Wed, 22 February 2017, 23:30:26
If we can do an "all-positions" plate with the MX/Alps style universal holes, and Costar stabilizer sockets (those will also take ALPS-style stabilizer wires in my experience)-- that would satisfy most users who want to do plate-mount builds. If they don't want every position filled, the top plate will cover extra holes. Getting even 5-10 ordered might get to a quantity break with a place like Big Blue Saw.
I tend to think plate-mount is near mandatory for ALPS, and it's quite valuable for MX if you use the board angled. The plate-mount GH-122 is far more solid feeling than the PCB-mount G80-3000 and 8200 I've used.
Post by: Phenix on Thu, 23 February 2017, 08:25:41
https://deskthority.net/vendors-f52/early-alert-big-blue-saw-sale-coming-next-week-t15817.html
Post by: samwisekoi on Sat, 25 February 2017, 12:19:50
Approximate Cost:
PCB: $60
Aluminum Base: $25
Acrylic spacer: $40
Acrylic top plate: $30 (With your choice of layout and color.)
Total $155 (plus shipping, etc.)
Test kit thread: https://geekhack.org/index.php?topic=87851.0
FYI,
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: BaconEggandCheeseBagel on Sat, 25 February 2017, 12:54:57
Post by: ErgoMacros on Fri, 03 March 2017, 12:52:21
I appreciate that the PCB now supports pads for a connector to a daughter-card supporting alternate status LED arrangements.
Wondering if it's possible to bring out +V and a couple unused Teensy pins in the same connector for other expanded functions. (More status LEDs for layers? a speaker? others?)
Maybe to late for this time, but next?
Post by: samwisekoi on Sat, 04 March 2017, 00:02:08
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: ErgoMacros on Sat, 04 March 2017, 13:46:18
Post by: dead_pixel_design on Mon, 06 March 2017, 11:33:10
OK, I think the test build kit will be approx. $155 USD plus shipping and any taxes.
Should we expect the final product cost to be similar to this? and will the PCB, aesthetically, be different on the final product? And are you offering the option of just purchasing the test PCB?
Post by: samwisekoi on Mon, 06 March 2017, 12:02:35
My intent in offering the kit was to reduce the complexity of early adoption so people would actually build the things. But if five people wanted just the PCBs, and would build them at least enough for testing, I'd be fine with that as well.
The white-on-black look is how all of my PCBs are made. I'd accept polite suggestions, but no promises.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: dead_pixel_design on Mon, 06 March 2017, 12:13:13
Well, given the resounding lack of "Hurrah!" the test kit received, I am open to alternatives for the first edition/test PCBs. To keep my exposure down, I want to buy no more than ten first run PCBs. And, I want to be certain that at least five people will build part of that run.
My intent in offering the kit was to reduce the complexity of early adoption so people would actually build the things. But if five people wanted just the PCBs, and would build them at least enough for testing, I'd be fine with that as well.
The white-on-black look is how all of my PCBs are made. I'd accept polite suggestions, but no promises.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
I'm very interested in the test kit but I am a novice builder and don't know that I could provide the feedback you would be looking for from a test run, I don't know the software, I don't have experience to inform what I would even be looking for, if I got it it would be as a collector's item, and I know that's not what your test run is for. But believe me I feel the Hurrah for the test run. And where I can only afford one or the other, as as much as I would love to have the know-how to help with the testing process and absolutely want to be one of the first to get my hands on it, I think I'm a production model buyer until I have more experience. But trust that I, and I imaging a lot of the followers of this thread, are full of hurrah
Just out of curiosity, what is the Acrylic Spacer? Could it not just be base>PCB>Top plate?
Post by: samwisekoi on Mon, 06 March 2017, 13:11:03
Just out of curiosity, what is the Acrylic Spacer? Could it not just be base>PCB>Top plate?
Take a look at the drawing in the kit thread. The spacer allows for the bottom of the switches, the diodes and resistors, and the main body of the Teensy.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
Post by: TerryMathews on Mon, 06 March 2017, 14:47:01
Well, given the resounding lack of "Hurrah!" the test kit received, I am open to alternatives for the first edition/test PCBs. To keep my exposure down, I want to buy no more than ten first run PCBs. And, I want to be certain that at least five people will build part of that run.
My intent in offering the kit was to reduce the complexity of early adoption so people would actually build the things. But if five people wanted just the PCBs, and would build them at least enough for testing, I'd be fine with that as well.
The white-on-black look is how all of my PCBs are made. I'd accept polite suggestions, but no promises.
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
As stated in the other thread, I'd be down for a kit and a PCB.
Post by: donutcat on Mon, 06 March 2017, 18:13:18
Post by: ErgoMacros on Mon, 06 March 2017, 18:52:14
I'm in if there are any left.
(Thanks for arranging these as kits.)
Post by: samwisekoi on Tue, 07 March 2017, 11:44:33
1a. MOQ=5 of 10 First Edition GH-122.2017 PCB Only.
1b. MOQ=5 of 10 First Edition GH-122.2017 PCB + Sandwich Case Kit.
2. MOQ=20 Production GH-122.2017 PCB Only.
IC thread is here: https://geekhack.org/index.php?topic=88063.0
- Ron | samwisekoi
Post by: Phenix on Tue, 07 March 2017, 14:17:32
Nevertheless I am interested in seeing some final pics!
Post by: user 18 on Tue, 07 March 2017, 22:22:58
Really excited to see pics of the builds though!
Post by: beard on Tue, 20 June 2017, 19:40:49
Post by: iamtootallforthis on Tue, 20 June 2017, 19:46:20
Hi, any news about this project?
Sam is moving house now IIRC so this is on hold right now
Post by: beard on Tue, 20 June 2017, 19:52:10
Post by: dead_pixel_design on Wed, 21 June 2017, 00:25:04
Post by: Giorgio on Sun, 06 August 2017, 13:00:24
RGB underglow is very interesting.
Alps? More holes and the PCB Will collapse under any weight and then self destruct.
I think that many could benefit from a presoldered controller and diodes, and why not, under glow leds.
Thanks
Post by: Giorgio on Sun, 06 August 2017, 13:57:35
I'll just leave this here...
- Ron | samwisekoi
Auto-typed by my GH-122 keyboard.
This case is really nice. I would improve it a little by offering a matte finish, flathead screws recessed into the plate by widening - with an angle - the hole, and smoothing a little the edges of the layered plates (maybe only the top and the bottom one need this. Also... Cutouts for switch removal.
In a sandwich case, is the plate indispensable? I mean, the PCB is "suspended" from the top plate, and it does not touch the bottom one? In other words, are the "mounting holes" enough to support the board, without a plate?
About the firmware, yes it would be nice to reassign keys without having to reflash.
A final word about the keycaps: blank gmk keycaps are about 40% cheaper than doubleshots. So we could have the alphas doubleshots, and the rest of the keys blank.
Finally, a word about the layout, I'm happy that you offer this layout for the function keys, because having them staggered, with empty speces in between, is the only way to find touch type also up there...
[attachimg=4]
[attachimg=1]
Post by: Giorgio on Sun, 06 August 2017, 15:03:55
Only 180 degree orientation changes are allowed for alps.Alps vertical numpad 2u positions do need the stem rotating 90 degrees (like you have it), but in not sure if this is an absolute rule or just the general case. A seasoned Alps user will have to verify.
Can someone authoritative weigh in on this point? I can rotate the numpad vertical either way, but not both
Like so?Show Image(http://i.imgur.com/WIaaTOT.jpg)
All of my alps boards are like this btw, With the exception of one with the 2x1u's in the numpad which are placed normally
what a nice case! who did it for you?
Post by: Spaceman1200 on Mon, 07 August 2017, 08:33:33
Post by: Giorgio on Mon, 07 August 2017, 09:21:35
The case is from the Monarch Keyboard seen here https://geekhack.org/index.php?topic=75786.0
Thanks for you answer!
I'm very impressed by the plate recesses, that allow the switch to clip in, overcoming all the thickness limitations.
I think that such a thick plate could make the difference in an enormous keyboard like the gh-122. BTW, does the gh122 ping? Adding some mass and supports can surely help.
[attachimg=1]
[attachimg=2]
[attachimg=3]
full build log
https://imgur.com/a/AeGHW
Post by: THX1138b on Sun, 08 October 2017, 01:44:21
Post by: semajsiwel on Wed, 26 June 2019, 17:17:00
Been lurking for a while in hopes of an update.
Post by: ErgoMacros on Wed, 26 June 2019, 21:59:16
I keep watching, but it's not looking promising.
I'm 1/2 tempted to try and replicate his work, but there are so many details he clearly knows, that I don't...
And I've never designed a PCB... or a keyboard, or a case...
just seems very unlikely that I'd succeed at it. :(
Post by: semajsiwel on Sun, 07 July 2019, 19:36:43
The manufacturing portion itself I'm confident I could do/have done, but the most complex thing I've designed in this regard was an 8x8 switch matrix for a chess game.
Post by: ErgoMacros on Thu, 11 July 2019, 00:20:16
CueBoard 2x1800. 131 keys, 4 rotery encoders, 2 num pads. Only available on April 1st :(
https://clueboard.co/parts/clueboard-2x1800
No guarantee's it will be available next year, of course.
Post by: hottrout on Thu, 11 July 2019, 05:22:57
Show Image(http://i.imgur.com/wwyrgg2.png)
I'd rock this layout hard
Never expected to see split stuff, but will be interesting making cases for them.
I would 2nd that big time. My all time fav layout and if this was possible I am in in in. Sign me up and take my money.