Blueprint

Stenoboard

A stenography keyboard.

Created by Elijah Spitzer Elijah Spitzer

Tier 3

9 views

0 followers

CAN CAN ⚡🚀 approved Stenoboard ago

Tier approved: 3

Grant approved: $101.00

nice keeb

Elijah Spitzer Elijah Spitzer submitted Stenoboard for review ago

CAN CAN ⚡🚀 requested changes for Stenoboard ago

Please make a top plate for your case.

Elijah Spitzer Elijah Spitzer submitted Stenoboard for review ago

Shaurya Bisht Shaurya Bisht requested changes for Stenoboard ago

still ordering a pico? dm one of the reviewers if you have a reason to do so

Elijah Spitzer Elijah Spitzer submitted Stenoboard for review ago

Elijah Spitzer Elijah Spitzer added to the journal ago

Reviewer info

For any future reviewers information as I seem to answer the same questions a lot:

  1. PCBWAY is much cheaper for larger boards them JLCPCB. In this case by about $50.
  2. The RP Pico is cheaper then the XIAO ( it's only $4 ) and it works just as well while allowing space for future upgrades like LED'S.
  3. There is purposely no top-plate as it was based off of the ANNE PRO 2, which does not use one. I like the look much better.

Screenshot 2025-11-18 at 10.33.20 AM.png

CAN CAN ⚡🚀 requested changes for Stenoboard ago

You don't need a pico for this, only a XIAO Esp32 if you are using a keyboard matrix. Please make a hackpad first so you know how it works.

Elijah Spitzer Elijah Spitzer submitted Stenoboard for review ago

Jay Jay ⚡🚀 requested changes for Stenoboard ago

1Mon 1Mon requested changes for Stenoboard ago

can you please order the pcb from JLC instead of PCBWAY?

Elijah Spitzer Elijah Spitzer submitted Stenoboard for review ago

Elijah Spitzer Elijah Spitzer submitted Stenoboard for review ago

Elijah Spitzer Elijah Spitzer added to the journal ago

Created 3D Render

I created a 3d render of all the parts together, with the PCB, keycaps, switches, and case.

I had issues figuring out how to get the PCB file from Kicad to Fusion360, but I found all I had to do was upload it into a folder in Fusion360 and then I could right click and press import into current project.
Screenshot 2025-11-18 at 10.33.20 AM

1Mon 1Mon requested changes for Stenoboard ago

really cool project! i love steno! why do you need 60 switches? your pcb only has spots for 28. additionally, your readme also needs a pic of the entire board assembled. id also like to see a bit more info in your journal entries on your decisions while making this keyboard.

Elijah Spitzer Elijah Spitzer submitted Stenoboard for review ago

technical_. technical_. requested changes for Stenoboard ago

Couple of BOM related issues, is there a reason why you are ordering from PCBWAY and not JLCPCB? In addition, why not source components from LCSC rather than Digikey and bundle the JLCPCB + LCSC order?
Pardon me, if I'm wrong for your specific case, but I believe most parts should be cheaper on LCSC.
In addition, the tier for this keyboard is only a tier three, and not a tier two. Please increase hardware complexity, or cover the excess cost using your own money.
Even if you initially made this as a Hack-Pad, please try to journal to the best of your ability, and recall as much information as you can.
You should be able to have a decently good memory on your design process, problems when designing etc.

Elijah Spitzer Elijah Spitzer submitted Stenoboard for review ago

Elijah Spitzer Elijah Spitzer added to the journal ago

Made the PCB, Code, and Case

Sorry for the one journal, I was originally making this as a Hackpad so I didn't have journaling abilities.

I originally created the schematic with all the traces going directly from each key individually to a GPIO, which I quickly realized was not going to work for all 28 keys I needed. Domain helped me figure out how to use tags in Kicad to "matrix" them into columns and rows to allow you to put a lot more on a board, but I still ended up having to move from a XIAO to a Pico to get the extra GPIO slots that I needed. Kai Pereira then helped me fix all my problems, which were few, the only big issue was that when I moved my neopixels down I accidentally drew another trace right through one of them which would have messed up the entire PCB.
Screenshot 2025-11-11 at 10.53.30 AM

When I first began my schematic I was using the XIAO RP2040 chip because it was small and I had lots of experience with it, but as I was dealing with so many buttons I had to switch to the Raspberry Pi Pico for the extra GPIO slots. I should have routed all the switches on the right of the PCB in the schematic to the right GPIO slots, but as this was the first keyboard I had created I made the mistake of wiring it all onto the left side, which made routing much harder. I should have just redone the schematic, but it passes all DMC checks ( except for the silkscreen overlap thats always there ) Kai Pereira was a huge help with this:
Screenshot 2025-11-11 at 11.05.10 AM

I had a bunch of experience with Fusion 360 already so the case was pretty easy. I based it off of the keyboard design I have where the base PCB is visible with just keys on top of it and a case on the bottom and for it to come up partly on the sides. To create it I created a schematic with the full diameter of the keyboard so roughly ≈200mm by ≈75mm. I did run into an issue because I created the sides in the same schematic as the bottom of it, and I forgot how to extrude each one separately so I ended up just creating two schematics and joining them for the sides and bottom of the case. To add text I created a brand new schematic over where I wanted it to be and just used Fusion360's built in text tool, and then in the editor I used the cut tool to place it about 2-3mm into the floor of the case. For production I am planning on just 3d printing it myself:
Screenshot 2025-11-11 at 11.05.57 AM

Elijah Spitzer Elijah Spitzer started Stenoboard ago

11/11/2025 - Made the PCB, Code, and Case

Sorry for the one journal, I was originally making this as a Hackpad so I didn't have journaling abilities.

I originally created the schematic with all the traces going directly from each key individually to a GPIO, which I quickly realized was not going to work for all 28 keys I needed. Domain helped me figure out how to use tags in Kicad to "matrix" them into columns and rows to allow you to put a lot more on a board, but I still ended up having to move from a XIAO to a Pico to get the extra GPIO slots that I needed. Kai Pereira then helped me fix all my problems, which were few, the only big issue was that when I moved my neopixels down I accidentally drew another trace right through one of them which would have messed up the entire PCB.
Screenshot 2025-11-11 at 10.53.30 AM

When I first began my schematic I was using the XIAO RP2040 chip because it was small and I had lots of experience with it, but as I was dealing with so many buttons I had to switch to the Raspberry Pi Pico for the extra GPIO slots. I should have routed all the switches on the right of the PCB in the schematic to the right GPIO slots, but as this was the first keyboard I had created I made the mistake of wiring it all onto the left side, which made routing much harder. I should have just redone the schematic, but it passes all DMC checks ( except for the silkscreen overlap thats always there ) Kai Pereira was a huge help with this:
Screenshot 2025-11-11 at 11.05.10 AM

I had a bunch of experience with Fusion 360 already so the case was pretty easy. I based it off of the keyboard design I have where the base PCB is visible with just keys on top of it and a case on the bottom and for it to come up partly on the sides. To create it I created a schematic with the full diameter of the keyboard so roughly ≈200mm by ≈75mm. I did run into an issue because I created the sides in the same schematic as the bottom of it, and I forgot how to extrude each one separately so I ended up just creating two schematics and joining them for the sides and bottom of the case. To add text I created a brand new schematic over where I wanted it to be and just used Fusion360's built in text tool, and then in the editor I used the cut tool to place it about 2-3mm into the floor of the case. For production I am planning on just 3d printing it myself:
Screenshot 2025-11-11 at 11.05.57 AM

11/18/2025 - Created 3D Render

I created a 3d render of all the parts together, with the PCB, keycaps, switches, and case.

I had issues figuring out how to get the PCB file from Kicad to Fusion360, but I found all I had to do was upload it into a folder in Fusion360 and then I could right click and press import into current project.
Screenshot 2025-11-18 at 10.33.20 AM

11/26/2025 - Reviewer info

For any future reviewers information as I seem to answer the same questions a lot:

  1. PCBWAY is much cheaper for larger boards them JLCPCB. In this case by about $50.
  2. The RP Pico is cheaper then the XIAO ( it's only $4 ) and it works just as well while allowing space for future upgrades like LED'S.
  3. There is purposely no top-plate as it was based off of the ANNE PRO 2, which does not use one. I like the look much better.

Screenshot 2025-11-18 at 10.33.20 AM.png