A while back I was frustrated when wanting to buy a keyboard that there were no triangle-shaped keyboards or circle-shaped keyboards. This lack of peculiar keyboard shapes gave me the idea to make a keyboard that could be reconfigurable into any shape my heart desired. I’m still working on the firmware and making more keys but I wanted to share my progress so far. Heres the source if anyone’s interested in how I made it: https://github.com/notaroomba/keybytes
If anything it needs more light to force the camera to turn down the exposure because the LEDs on the keys are bright. Almost all indoor home videos, youtube or zoom, could be improved by more light.
I like the idea but I could only find an image of two keys. It would be great to see a demo of a full layout. With only two keys it's a very early POC and hardly a keyboard.
Does communication work well and feel snappy with a full set of keys? How is the structural integrity of a full one? Can it be easily moved around? That type of questions could easily make this unusable at scale.
I am waiting on some key switches to make more keys (5 in total), but for now I just wanted to show the progress on the mechanical/electrical side. I don’t have enough PCBs for a full set of keys yet, but when the key switches arrive and I assemble the 3 other boards I’ll let you know how it goes :D
I would assume you could have a custom support the keys rest on, that itself is split eg in the middle, so you can easily split the whole keyboard and have it stored in a compact way (trading length for depth).
OT but I'd like to see circuits of this type, on this scale, available for every loco or car (or building or structure) in a model railroad. An interface to DCC. Every car addressable and effects controllable. Much more cheaply than the current SOTA.
Neat project, given how cheap the ch32v003 is there are lots of opportunities to do fun distributed things with them (assume you have seen bitluni’s projects [1]) - even if they aren’t really practical!
I didn’t see the ch32 firmware in the repository - the ch32v003 only has 1 i2c peripheral - assume you are bit-banging the others?
Fantastic work, I'm always excited to new modular input device projects like this.
Are the connectors actually direction-agnostic? Looking at the layout it seems like depending on which side you connect you have a 50% chance of having the pin order reversed, and there don't appear to be any additional switching components correcting for it.
Do you have plans to address this so that any side can connect to any side? Or can they already and I've missed something?
It’s really rigid with 2 keys so far but I have yet to test with longer configurations. At a higher order quantity, each key comes out to be around 6 USD but I’m trying to minimize that as much as possible with future revisons!
Very good point. I wonder whether the communication would work with rows of connected keys, only joined to other rows at one end? You could then just create simple connection blocks for different row offsets.
I'd suggest also adding blank modules without a switch on them for empty space on the keyboard (for example around arrow keys), that would still provide the interconnect to adjacent keys. Cool project.
I think maybe the most difficult part will be cost. As far as I know, it will cost more than 5 dollars per item. But if the quality is good enough, I think maybe some gaming user will buy it. Customize layouts is really important for gaming user.
Sometimes my keyboards get dropped and lose a keycap or two, but never anything serious. If this is dropped on the floor, my trusty keyboard will turn into a bag of puzzle bits, right in the middle of heated gameplay or a meeting...
perhaps you could add optional magnetic rails for extra support
or even 3d-printed "grids" of arbitrary shapes, with magnets embedded at the junctions, to interface with the keys' magnets while being separate from them
This is a really neat idea for a macro keyboard. If it supported staggered rows and row heights, not to mention structural rigidity it would be good for everyday use too.
good idea!
the other day was doing a roundup on keyboards to see whats new and got a striking realization, how nobody has ever slapped a nvme slot into on the back/core part of the enclosure to use as external drive since lot of us comute everyday with extra peripherals
There isn’t a mouse module yet, but I am going to make more modules that include screens, finger print sensors, and I’ll add in a mouse one too :D. Currently there isn’t support for a staggered manner but I am going to work on it for the next revision.
I looked over the PCB and schematic and it looks well polished. Not a first draft obviously.
I sort of don’t get the 4x I2C busses. I’m probably missing something obvious but it isn’t immediately apparent how the units all have addressing worked out.
The 4x I2C busses were mainly there to reduce parasitic capacitance and also allows me to know where each key is physically relative to each other in software. I’m still working on the firmware for it, but currently the plan is for each of the keys to remember its “parent”, the neighbor that is closest to the main board, and forward events repeatedly to the main board.
- How much does it cost? Sell price, not BoM price. I expect something like $10'000 for a full 104-key layout.
- How heavy would it be?
- Can you lift a 104-key layout from the table without it breaking in 2 (or more) pieces? Can you even lift or move a 40% layout with one hand?
- How do you arrange it in a non-ortholinear layout? If you can't, then anyone can just buy an ordinary ortholinear for $100 and switch layouts in software.
- How does the spacebar key look like? Enter key? Shift? I can't type if those big keys aren't big.
- How do you make spaces between key groups?
- There are a lot of pogo pin connections. It's statistically impossible for all of them to work. Is there any redundancy for those connections? Alternate signal paths with automatic rerouting? Any debugging tools/indicators to find where the bad connections are?
- If you have a MCU in every key, and at that price, I would expect them to have a mini-display in the keycap plus lots of other fancy features.
- How about automatic function assignment for each key based on it's location? Can it do that? If not, then any drop on the floor becomes a half-hour puzzle-solving problem.
I think not-a-keyboard is probably the better use case. A modular plug and play, configurable keypad would be pretty useful for sim enthusiasts or various workstation uses. You could solve the "picking up" problem by putting the modules on a baseplate.
These are great points, however, who said anything about buying a 100% keyboard in this style, or buying anything at all? I didn’t see a sales page, so it’s likely not intended as an off-the-shelf product.
But yes, just eyeballing that it's going to be hard to get it below $5/key and probably more like $10 for the first run.
If anything it needs more light to force the camera to turn down the exposure because the LEDs on the keys are bright. Almost all indoor home videos, youtube or zoom, could be improved by more light.
Does communication work well and feel snappy with a full set of keys? How is the structural integrity of a full one? Can it be easily moved around? That type of questions could easily make this unusable at scale.
What's the production cost of this per key?
I would assume you could have a custom support the keys rest on, that itself is split eg in the middle, so you can easily split the whole keyboard and have it stored in a compact way (trading length for depth).
I didn’t see the ch32 firmware in the repository - the ch32v003 only has 1 i2c peripheral - assume you are bit-banging the others?
[1] https://www.youtube.com/@bitluni
The keys are attached to a board so it can be in any orientation
Maybe using CAN is better.
>https://www.nxp.com/products/LPC11C00
Are the connectors actually direction-agnostic? Looking at the layout it seems like depending on which side you connect you have a 50% chance of having the pin order reversed, and there don't appear to be any additional switching components correcting for it.
Do you have plans to address this so that any side can connect to any side? Or can they already and I've missed something?
How does the rigidity of the keyboard hold up with many keys and what's the cost of the materials at higher order quantity?
It’s really rigid with 2 keys so far but I have yet to test with longer configurations. At a higher order quantity, each key comes out to be around 6 USD but I’m trying to minimize that as much as possible with future revisons!
or even 3d-printed "grids" of arbitrary shapes, with magnets embedded at the junctions, to interface with the keys' magnets while being separate from them
It needs spacers / extensions so it can be laid out as desired.
I sort of don’t get the 4x I2C busses. I’m probably missing something obvious but it isn’t immediately apparent how the units all have addressing worked out.
The 4x I2C busses were mainly there to reduce parasitic capacitance and also allows me to know where each key is physically relative to each other in software. I’m still working on the firmware for it, but currently the plan is for each of the keys to remember its “parent”, the neighbor that is closest to the main board, and forward events repeatedly to the main board.
The real breakthrough would be reprogrammable key legends in something like e-ink.
- How much does it cost? Sell price, not BoM price. I expect something like $10'000 for a full 104-key layout.
- How heavy would it be?
- Can you lift a 104-key layout from the table without it breaking in 2 (or more) pieces? Can you even lift or move a 40% layout with one hand?
- How do you arrange it in a non-ortholinear layout? If you can't, then anyone can just buy an ordinary ortholinear for $100 and switch layouts in software.
- How does the spacebar key look like? Enter key? Shift? I can't type if those big keys aren't big.
- How do you make spaces between key groups?
- There are a lot of pogo pin connections. It's statistically impossible for all of them to work. Is there any redundancy for those connections? Alternate signal paths with automatic rerouting? Any debugging tools/indicators to find where the bad connections are?
- If you have a MCU in every key, and at that price, I would expect them to have a mini-display in the keycap plus lots of other fancy features.
- How about automatic function assignment for each key based on it's location? Can it do that? If not, then any drop on the floor becomes a half-hour puzzle-solving problem.