GH-122.2017 Mods, features, and additions

[samwisekoi]

GH-122 2017 Edition

Back in 2014-2015, I designed and in 2016 produced 25 GH-122 PCBs for the dedicated folks who really, really wanted a Stupidly Large Giant MX Keyboard.  My personal goal was a programmable MX-based F-122 layout, but since the PCB was 19.50" x 6.50" anyhow, I filled the rest of the space with switch positions.  And then, because the people who wanted to build such a big board all had different layouts in mind, I designed the PCB so it could be sliced and diced into different sizes and shapes to support many different layouts.

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:


My personal GH-122 in the Unicomp case with NDG SA Keycaps


GH-122 Expanded ANSI Layout


GH-122 Max Keys Layout


GH-122 Tall Winkeyless Layout


GH-122 Wide Winkeyless Layout


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.

1. ✓[FIX] Correct 6.25 stabilizer mounting holes.
2. ✓[FIX] Relocate D160 (similar to D150.)
3. [FIX] Remove pointless lower-left phantom arrow key position?
4. ✓[MOUNTING] Add mounting holes for 5x24 build.
5. ✓[MOUNTING] Add lower mounting holes to PC-122 upper bank.
6. ✓[MOUNTING] Daughterboard mounts for the controller.
7. ✓[MOUNTING] Add center-line support holes between Row B and C (matching GH60.)
8. ✓[UNICOMP] Jumper blocks for upper bank and LEDs, located and labeled for use in the Unicomp case.
9. [UNICOMP] Move USB connector .250 southwest to fit better in the Unicomp case.
10. ✓[REQUESTED FEATURE] Alps compatibility for expanded ANSI only.
11. ✓[REQUESTED FEATURE] Modular/removable keypad.
12. [REQUESTED FEATURE] Modular/removable nav block.
13. [REQUESTED FEATURE] Optional 4x5 nav block.
14. ✓REQUESTED FEATURE] Split spacebar.
15. [REQUESTED FEATURE] 6.0+1.0 spacebar+1 lower row. (6.0+1.0, 6.25, 7.0 spacebar layouts.)
16. ✓[IMPROVEMENT] Partial backlighting circuits, especially transistor mounting locations.
17. ✓[IMPROVEMENT] Make ISO and ANSI Enter and \| switches use same row & column.
18. [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.)
19. ✓[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.

[samwisekoi]

Change Log:

• 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.

[xondat]

2017! Mine too.

Physical PCB changes, this'll be fun.

[jal]

Very much in.

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.

[iamtootallforthis]

Loving my original PCB looking forward to the changes brought by 2017!

[Niomosy]

Damn this is tempting if just to have a nice ANSI monstrosity.

[user 18]

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.

[samwisekoi]

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.

[Data]

 

[Krogenar]

I always loved this project sam, great to hear I'll have another shot at it.

* 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. 

Set to Notify/Watch.

Suggestion/Wish: add some images to this thread of the first version!

[Phenix]

[REQEUESTED 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)

[samwisekoi]

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.    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.

[Phenix]

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)

[samwisekoi]

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

[Phenix]

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

[samwisekoi]

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.

[nathanrosspowell]

Nice! Depending on timing/funds I would really like to pick one up. I have a lot of SA novelty caps that would look great on this.

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 

#8 and #10 on your list are the same, Ron. Maybe "Alps compatibility" was a highly requested feature! 

[Phenix]

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?

[samwisekoi]

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

[nathanrosspowell]

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.

[iamtootallforthis]

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.

[Phenix]

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

[nathanrosspowell]

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 

[samwisekoi]

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

[Niomosy]

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 

Phhht, I'd totally be in for a split GH-122 board if the price wasn't insane

[nathanrosspowell]

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 

Phhht, I'd totally be in for a split GH-122 board if the price wasn't insane

A split version?! Hahaha that would be so crazy.

[samwisekoi]

Split into how many pieces?

 - Ron | samwisekoi

[Data]

Split into how many pieces?

 - Ron | samwisekoi

Like 5?   )

---

Ron, what's driving the format change to 0.375" gutters?  Has someone requested this?

[samwisekoi]

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.

[Trente]

I'm in

[Phenix]

Another column right to arrowcluster - why not, more keys cant be wrong..
will tnat coloumn be on the 'removable numpad section'?

split - sounds good - its in

[Niomosy]

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.

[Data]

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  )

[Phenix]

Command and Conquer edition..

[Spaceman1200]

call me crazy, but i'd go for a split version if i have the desk space lol

[Niomosy]

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.

[samwisekoi]

Okay.  Here are some thoughts...


I believe I can make this work:

GH-122 No-Nav Layout


It seems insane, but maybe this can be made to work.  The blue splits are already available:

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

[Niomosy]

I was thinking that you could simply remove something like the numpad for closer mouse access.  Not so much detached and still functional via any means.

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

[jal]

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.

[Niomosy]

True.  The only thing we really need to change on samwise' diagram is moving the 6 to the other side of the split    We'd been joking around about it in the original 122 thread at one point and it popped into my head to mention for fun this time.

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.

[nathanrosspowell]

I think the split along the alphas (to make it 'ergonomic') is a bit crazy  ) and I agree, maybe a bit much for a R2.

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 

[samwisekoi]

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.

[samwisekoi]

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.

[Phenix]

The splits you showed look really good..
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.

[samwisekoi]

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:


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.

[user 18]

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!

[nathanrosspowell]

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 

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?

[duynguyenle]

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!

[pomk]

I remember some alps custom pcb having uncommon positions upside down. Could that be used here?

[samwisekoi]

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...[/s]

[EDIT] Fixed the numpad.