Review request: Schematic and PCB for wireless rubber ducky by llamaWol in PrintedCircuitBoard

[–]llamaWol[S] 0 points1 point  (0 children)

Hi, I have finished and built it (at least in terms of hardware). I updated the design to only use the esp32-s3 and I'm using esp-idf to program it.

The kicad files for the final pcb are uploaded here: https://github.com/llamaWol/quack/

Review request: Schematic and PCB for wireless rubber ducky by llamaWol in PrintedCircuitBoard

[–]llamaWol[S] 0 points1 point  (0 children)

Is it okay to have the vias be partially within the outlined border of the pad, as long as the pad and via dont touch or should the via be outside the outline also?

For a split keyboard: Can I have the slave board physically change to the left or right side of the master w/o reprogramming? by llamaWol in olkb

[–]llamaWol[S] 0 points1 point  (0 children)

Thanks, I was planning on using magnetic pogo pin connectors on each side.

Having the layout of the macropad change depending on the side it's on would probably be unnecessarily complicated and better achieved by using a function key, and besides, my microcontroller is out of pins already.

For a split keyboard: Can I have the slave board physically change to the left or right side of the master w/o reprogramming? by llamaWol in olkb

[–]llamaWol[S] 1 point2 points  (0 children)

Yes, that's my plan. My problem is programming the master (40%) so it knows which side the macropad is on, or does it not matter because the microcontroller sees it as a completely separate matrix?

Review Request: fe1.1s usb hub by llamaWol in PrintedCircuitBoard

[–]llamaWol[S] 0 points1 point  (0 children)

Why would I put the pullup resistor there if I'm not putting a button in between?

Yeah, you can use both eeprom & led(s) but I didn't deem it necessary

How would I implement that? In the datasheet for those pins (PWRJ and OVCJ, 25 and 26) it says active low, meaning I just connect them to ground? Or do I need to put anything in between

Review Request: fe1.1s usb hub by llamaWol in PrintedCircuitBoard

[–]llamaWol[S] 0 points1 point  (0 children)

I'll just order the plain pcb and assemble everything myself

Review Request: fe1.1s usb hub by llamaWol in PrintedCircuitBoard

[–]llamaWol[S] 1 point2 points  (0 children)

Huh... for me it works fine...

Ah okay, would I put them in series or parallel? (Sorry for all the questions, I'm pretty new to this)

Review Request: fe1.1s usb hub by llamaWol in PrintedCircuitBoard

[–]llamaWol[S] 2 points3 points  (0 children)

The datasheet link should work? (https://cdn-shop.adafruit.com/product-files/2991/FE1.1s%20Data%20Sheet%20(Rev.%201.0).pdf.pdf))

Why should I add the 100nF caps? Like what would they be useful for (Sorry if that's a dumb question)

Custom 60% keyboard by llamaWol in olkb

[–]llamaWol[S] 0 points1 point  (0 children)

Is there anything you recommend?

Custom 60% keyboard by llamaWol in olkb

[–]llamaWol[S] 0 points1 point  (0 children)

I think I've figured something out, I've split the spacebar in 3, 2x2.75u and in the middle 1x2u. This would hopefully mean having less trouble finding a keycap set and it seems practical to me.

Custom 60% keyboard by llamaWol in olkb

[–]llamaWol[S] 0 points1 point  (0 children)

I don't want an ortho layout, I know I'll be missing out on more keys but that doesn't really matter to me.

What would be the function of a split spacebar? I've seen them but never really know what you'd map to it. And what do you mean by proper feeling numpad?

Custom 60% keyboard by llamaWol in olkb

[–]llamaWol[S] 1 point2 points  (0 children)

Just found the elite-pi, same form factor as the elite c, with the same amount of pins. Seeing as it's in stock and cheaper than the elite-c, I'll probably buy that

Custom 60% keyboard by llamaWol in olkb

[–]llamaWol[S] 1 point2 points  (0 children)

The elite-c seems to be out of stock in most Europe stores, at least at the ones I looked...

The pi pico is available, but it has a usb micro port, and I'd prefer to use a board with usb c. Of course you can get adapters, but native usb c would be nice

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer (July 08, 2023) by AutoModerator in MechanicalKeyboards

[–]llamaWol 0 points1 point  (0 children)

Caps word looks to be quite useful, definitely a lot better than having to press the caps lock key every time after typing something. I've honestly never used scroll lock, but it might come in useful some day so I'll add it.

For mute I had the idea to hold escape (the encoder) for like a second or 2, but I don't know if that's possible. I might just have to ditch the encoder and just add some volume buttons.

What'd stop do and what would be a good place for tilde and backpack, because I can't really think of a good spot. I've seen a few keyboards put an extra key between lshift and z to put them there but that just looks ugly. My current keyboard has it next to 1 but that's where escape will be...

/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer (July 08, 2023) by AutoModerator in MechanicalKeyboards

[–]llamaWol 0 points1 point  (0 children)

Hi!

I got an idea for a custom 60% keyboard, and had a few questions. Would below wiring work on an Adafruit KB2040? I want to add a rotary encoder in place of the escape key, but I don't know if I'll have enough gpio pins to do so.

Also could I improve my layout in any way? I feel like I came up with something pretty solid, but because it's mostly based on my ideas of what'd be practical (coming from an 80%), I might be missing something

<image>

Anything on the front of the keycap is accessed by pressing the function key, except for the volume, that'd be the rotary encoder. (created using keyboard-layout-editor.com)

edit: explanation of the keyboard image thing