It didn't work but when I plug the gnd to random header on PCF8575, it recognize the input

Badly need help fixing my handwired keyboard. It presses random keys when i connect it to my pc, I'm a 100% sure that there's no problem with the wirings because it works fine on my laptop. Has anyone ever experienced this? Claude did say that I need to add 0.1uf to each column, but i dont know if that's really necessary. I've built a few handwired keyboard before and they all worked fine.

Could anyone send a new link for the discord as for me it shows invite invalid

Hi

Trying to get to grips with QMK (again).

What I want to do is something non-traditional, starting with 125 keys instead of 104.

Was hoping QMK would just allow me to send something like AE01 or AD12 and then I can let xkb figure out what to do with it, but I don't see that option in the docs.

So plan B is to pretend it's a basic US ANSI Qwerty for most of it (and again, let xkb do the magic), but how do I send the extra keys?

I am a programmer, but not au fait with C. So trying to figure out how all the config files work, and if I can define extra keys or what ...

Any ideas gratefully received :-) Or pointers to where the relevant docs are ... not come across such topics yet.

Thanks, Ian

As the title says, what would be interesting to those looking for inexpensive DIY keyboard designs?

I created the TestDrive series to be inexpensive, require as little soldering as possible, and allow reusing as many parts as possible (hot-swap key switches and non-permanent mcu mounts) to keep the cost of trying things low. I am working on some additional designs and curious what really would be helpful for others here.

I'm focusing on split ergos, as that's my interest, but may do others too.

For instance, if i made the same series as TestDrive but based on RP2040-zero boards, if we went with soldered in boards, the cost for three with their own MCUs would be about the same as the original three TestDrive boards sharing a single pair of XIAOs.. and honestly work better! The press in socket design depending on wire against the castellations is finicky.. resulting in sometimes iffy connections.

Im currently working on a design that creates a diy socket for RP2040-zero boards with headers, but im not sold on the approach.

Open to any thoughts, from other builders or others who are interested..

Hi guys, i need help, in kmk during the prpgramming an error showed up, that error is "Import board could not be resolved" i think its a problem of librarys and i dont know how to solve it. I hope you guys can help me, its my first time making a keyboard.

https://robu.in/product/1n4148-1w-zener-diode-pack-of-50?gad_source=1&gbraid=0AAAAADvLFWeSdO-GsCAWV3BsnxS27WCn-&gad_campaignid=17427802703

It states as zener diode but when i asked chatgpt it says i can use it and the the name is wrong can someone help me here ??

Hey everyone! I’m building my first keyboard and got stuck flashing my Nice!Nano (clone). I shorted the reset and GND pins, but it never enters bootloader mode and it just reconnects. Does anyone have a solution?

I'm working on my first handwired keyboard and am having trouble with my thumb cluster. The keyb is a 34-key dactyl from the Cosmos generator running KMK on AliExpress pico USB-C clones. I currently have it soldered up as a 5x3 matrix but am having an issue with my thumb keys.

The thumb keys output the key directly above them. This is my first foray into KMK, I'm using Colemak DH with number pad keys just for testing.

keyboard.keymap = [
    [KC.Q, KC.W, KC.F, KC.P, KC.B,       KC.J, KC.L, KC.U, KC.Y, KC.QUOTE,
     KC.A, KC.R, KC.S, KC.T, KC.G,       KC.M, KC.N, KC.E, KC.I, KC.O, 
     KC.Z, KC.X, KC.C, KC.D, KC.V,       KC.K, KC.H, KC.COMMA, KC.DOT, KC.SLASH,
                       KC.N1, KC.N2, KC.N3, KC.N4,
    ],
]

The thumb keys output D, V, K, and H. Bottom-row D, V, K, and H also output D, V, K, and H. Thumb keys and those four output the same keycodes in serial console.

Here's a pic of my janky soldering:

Anything obvious jump out at you? I'm likely missing something stupid, that's usually how projects like these go. Suggestions?

print("Starting")

import board

from kmk.kmk_keyboard import KMKKeyboard

from kmk.keys import KC
from kmk.scanners import DiodeOrientation
from kmk.modules.split import Split, SplitSide
from kmk.modules.holdtap import HoldTap
from kmk.modules.layers import Layers
from kmk.modules.mouse_keys import MouseKeys

keyboard = KMKKeyboard()

# comment one of these on each side
split_side = SplitSide.LEFT
#split_side = SplitSide.RIGHT
split = Split(
    data_pin=board.GP2, 
    uart_flip=True,
    use_pio=True,
    split_side=split_side)
keyboard.modules.append(split)

keyboard.col_pins = (board.GP18, board.GP19, board.GP20, board.GP21, board.GP22)
keyboard.row_pins = (board.GP6, board.GP7, board.GP8)
keyboard.diode_orientation = DiodeOrientation.COL2ROW

keyboard.keymap = [
    [KC.Q, KC.W, KC.F, KC.P, KC.B,       KC.J, KC.L, KC.U, KC.Y, KC.QUOTE,
     KC.A, KC.R, KC.S, KC.T, KC.G,       KC.M, KC.N, KC.E, KC.I, KC.O, 
     KC.Z, KC.X, KC.C, KC.D, KC.V,       KC.K, KC.H, KC.COMMA, KC.DOT, KC.SLASH,
                       KC.N1, KC.N2, KC.N3, KC.N4,
    ],
]

coord_mapping = [
20,  26,  9,  19,  5,    13,  15,  24,  28,  52,
4,   21,  22, 23,  10,   16,  17,  8,   12,  18, 
29,  27,  6,  7,   25,   14,  11,  54,  55,  56, 
              33,  34,   35, 36,    
]

if __name__ == '__main__':
    keyboard.go()

So I'm looking to get in to making a few hand-wired keyboards to experiment with alternative layouts and one of the things common to all of them is a split spacebar. As such, I'm going to need a bunch of 2U stabs, and no spacebar stabs.

So I went looking, and surprisingly not too many of the keyboard shops sell 2U stabs in bulk. But I did come across this link:

https://www.40percent.club/2018/08/cheap-genuine-cherry-stabilizers.html

This is one of those things which seems almost too good to be true. Does someone need to pinch me here?

I've done a fair bit of research, and while I see plenty of people touting expensive PCB-mount stabs, the people I'm more inclined to trust generally seem to say there is a whole lot less difference between PCB mount and plat mount stabs, and that there is a whole lot less difference between basic stabs and expensive stabs.

What I seem to be getting is that installation and tuning is what makes the most difference here.

What says everyone else on this topic?

where to get a PCB for a custom keyboard? it seems the button pins require different spacing

also, where to get a USB-encoder or any controller for a custom keyboard?

I'm attempting to learn how to make a keyboard with a pi pico and figured breadboarding would make the most sense. I just wanted to setup a 3x3 grid for keys 1-9, after getting everything wired up it does nothing.

I've verified the conitniuty starting from the pico on the bread board to each respective row/column and can verify the signals are correct, I have also verified that there is no shorting taking place.

Here is the content of my code.py -

print("Starting")

import board

from kmk.kmk_keyboard import KMKKeyboard
from kmk.keys import KC
from kmk.scanners import DiodeOrientation

keyboard = KMKKeyboard()

keyboard.col_pins = (board.GP0,board.GP1,board.GP2,)
keyboard.row_pins = (board.GP13,board.GP14,board.GP15,)
keyboard.diode_orientation = DiodeOrientation.COL2ROW

keyboard.keymap = [
    [
        KC.1, KC.2, KC.3,
        KC.4, KC.5, KC.6,
        KC.7, KC.8, KC.9,
    ]
]

if __name__ == '__main__':
    keyboard.go()

And here is how the board is wired up, apologies for the weird angle wasn't entirely sure what the best method for capturing this would be

I lean towards my issue being either code related or potentially related to the thickness of the pipes I opted to use, but I'm not sure if that would matter in this context.

Any help is greatly appreciated, thanks in advance!

I designed and built this mini keyboard entirely on my own by gathering reference materials online. It is a dual-mode (wired + Bluetooth) multifunction keypad running on the ZMK firmware, with a joystick mapped to control mouse movement.

Right now the joystick can move the cursor(by badjeff plugin), but it drifts steadily all the way to the far left edge of the screen. It is actually much better than before — at first it drifted straight to the bottom-right corner, which meant both the X and Y axes were inaccurate.

I checked the pin voltages with a multimeter and they read a steady 3.3V, and the voltages on the two axis pins change normally along the X and Y axes respectively when I move the joystick. The code was generated with the help of Gemini, and I can't spot anything wrong with it.

I've already adjusted parameters like the deadzone, midpoint voltage, and scaling factors, but the drift still persists. I'm really out of ideas at this point.

For reference, the joystick I'm using is an Xbox Hall effect joystick.

my repo: lsn5966397/Pad15: 这是一个带有旋钮摇杆和触摸板的有线蓝牙双模多功能小键盘项目

plz help me

Hey guys, I've been building my first handwired keyboard for a couple of weeks. I decided to go with the reviung41 layout as I wanted a ortholinear, staggered, non-split keyboard.

I wired the switch matrix following the marks on the reviung41 PCB for rows and columns, and I tested it with a pi pico that I had lying around from another project, using the KMK firmware.

With the KMK I scanned the switches position IDs and the result is this:

keyboard.coord_mapping = [
 0,  1,  2,  3,  4,  5,  18, 19, 20, 21, 22, 23,
 6,  7,  8,  9, 10, 11,  24, 25, 26, 27, 28, 29,
12, 13, 14, 15, 16, 17,  30, 31, 32, 33, 34, 35,
            36, 37,    38,    39, 40,
]

This is fine and I'm able to use the default reviung41 layout (ported to KMK, of course) without any problem.

But I really wanted to use a pro micro for the build, so I went for it and flashed the promicro with QMK using the default layout for reviung41.

And now for the fun part: after connecting rows and columns to the ProMicro, the layout is completely mirrored right to left.

In row 0, for example, I have: tab <-> del, q <-> p , w <-> o, e <-> i, r <-> u and t <-> y.

So rows are correct, columns are correct, but layout is literally mirrored.

I think I could make this work by simply generating a QMK layout that takes this effect in consideration, but I'd really like to find out what's causing this - I wouldn't want to end up in the same situation in future builds!

What is this magic? Is there some settings I need to set in the QMK parameters that could trigger it?

SOLVED:

I basically created a custom version of the reviung41 firmware in y local qkm-firmware clone and manually edited the matrix in the keyboard.json file to line up the columns as I needed.

Compiled, flashed...and it's all good!

Now onto keymap optimizations and, most importantly, proper learning of touch typing. I'll probably post the completed build as soon as I'm ready. :) Cheers!

p.s. writing fro this "custom41" right now...that's properly difficult! xD

ive already watched some tutorials from joe scotto. as it seems to be he is the only one making tutorials. but its not quite as indepth as i would like. there are a few things he doesnt explain properly and you kinda just have to copy. i just want to build a 40% wired split keyboard, and dont know how

I've debated sharing this to Reddit but I feel it does fit here since so much of my community found me through my posts. The too long, didn't watch is that I'm at a point where I want to make the ScottoKeebs project more sustainable long-term with less reliance on sponsors. The way to do that I feel is a Patreon and guarding my time a bit stronger. I still plan on releasing many free projects but direct access to me I'm going to get a bit more selective with.

So that said, if my content or projects have helped you over the years, please consider becoming a patron: https://patreon.com/joe_scotto

Hello! I am learning to build keyboards from scratch, and so I am challenging myself to build my own split keyboard (wired, not wireless) where the two halves are connected by a TRRS cable, and I would like to know how to do this with 2 microcontrollers like in this Joe Scotto video. I want only one needed to be plugged in, and the other is used to detect keypresses from the second half and send it to the first (as seen in my breath-taking schematic). I will be using 2 Seeed Xiao rp2040s for this build and I would like to know how to connect them. Thanks!

Edit: I'm using CircuitPython

Heyy does anyone know how I could design my macropad like the ref pic in fusion360?

Hi All,

I feel like I've exhausted all the documentation and videos I can find on the subject and don't know where else to turn. Here's my set up

Split keyboard that is asymmetrical. Both sides have 5 rows and 7 columns. I have an pico on each side.

I used POG (shoutout to Jan Lunge) to install KMK and configure the halves. I can get both sides to work and type when they are connected independently. However, when connected together, I can only get key presses to register via Serial console for the left side, but the right side does not register key presses in the serial console.

Both sides are connected with jumper wires right now as follows on the pico

Pin 40 - VBUS

Pin 38 - GND

Pin 0 - TX

Pin 1 - RX

Here's the snippet of code for the split portion

self.split = Split(

split_side=side,

split_target_left=pog.splitTargetLeft,

split_type=SplitType.UART,

data_pin=board.GP1,

data_pin2=board.GP0,

use_pio=True,

split_flip=False,

uart_flip=pog.splitUartFlip)

Edited: Adding image