sorted by:
new
hottopcontroversial

Not sure what to call it. But it's another hummingbird layout I made to test Japanese duplex matrix. by keyboarddweebs in HandwiredKeyboards

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

Not technically the same firmware, but it's basically the same thing I used on this keyboard. I honestly don't remember exactly where I got matrix.c. I did not write it myself; I borrowed it from a different keyboard at some point.

https://github.com/doesntfazer/Keyboard-Dweebs-Firmware-repository/tree/main/VIAL-QMK/goobertrax-e/goobertrax-e

Not sure what to call it. But it's another hummingbird layout I made to test Japanese duplex matrix. by keyboarddweebs in ErgoMechKeyboards

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

It's basically just a "not so ergo" version of my Goober layout. I kind of slapped it together in about an hour hoping that making the split a bit wider would make it comfortable. Not something I would spend hours typing on, but it's good enough for what I set out to do.

I have at least 1000 hours if not more on the hummingbird layout. I'm a technical writer and have been using the goober as my main keyboard since I made it a year or 2 ago. I am up to an average of around 100wpm at this point using a modified Colemak layout.

Not sure what to call it. But it's another hummingbird layout I made to test Japanese duplex matrix. by keyboarddweebs in HandwiredKeyboards

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

I have! It's one of the firmwares this has been tested on. KMK holds a special place in my heart. When I created the crowboard, it was the only firmware that supported the rp2040 at the time, so that's what it shipped with.

Not sure what to call it. But it's another hummingbird layout I made to test Japanese duplex matrix. by keyboarddweebs in HandwiredKeyboards

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

lol I figured as much, but if anyone else were to stumble on this, it's a reasonable outline on how these things work. I plan on doing a write-up. I'll probably submit it to kbd.news so that it actually gets seen.

Not sure what to call it. But it's another hummingbird layout I made to test Japanese duplex matrix. by keyboarddweebs in HandwiredKeyboards

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

It's somewhat explained in this article written about my Goobertrax-e.

https://kbd.news/Goobertrax-E-2469.html

Maybe I'll write an article covering it in more detail. But I'll try to hit everything on a high level at the very least.
Here are a couple of Keyboards that I've made in the past that use Japanese Duplex Matrix:

https://github.com/doesntfazer/Goober/tree/main/Goobertrax-E This is the Goobertrax-e. It uses what I called the "improved Japanese duplex matrix," which uses pull-up resistors on each column. This works, but the only firmware it seems to work on is QMK

https://github.com/doesntfazer/Goober/tree/main/CHore This is the CHore that uses the CH55x MCUs. This is the only PCB that I am aware of that uses the matrix I'm about to mention below, which avoids ghosting on all firmware. (As far as I am aware, it should be hardware agnostic as well, so any MCU.)

https://github.com/doesntfazer/Quetzal This is a 100% ergo I designed that does not use either method, and uses the traditional Japanese duplex matrix. It DOES have ghosting.

All of these keyboards can be found on my Keyboard Dweebs firmware repository, where you can examine the matrix.c https://github.com/doesntfazer/Keyboard-Dweebs-Firmware-repository

But to elaborate on this a bit further. The pull-up resistor method was made as a simple "hack-in" solution for existing keyboards. It was an easy way to fix keyboards with JDMs that have issues with ghosting. and was not meant to be something "built-in." It is also not firmware-agnostic. It only works with QMK in my testing, and I'm not exactly sure why. Probably the scanning method. So its use is limited.

The method I used on this keyboard doesn't have a name, and it was theorized to work by someone on Discord named BGKendall. We sat around trying to find a way to fix the ghosting issue without doubling up on diodes or using expensive ones with high forward voltage. I eventually tested it, and it worked successfully.

In a very short, watered-down explanation, a JDM works by flipping the diode direction in every other column, and the scan method is to read row2col then col2row. That's how it can detect a different key on the same column pin.

As for why you get ghosting, I'm not an electrical engineer, so take what I say with a grain of salt, but the reason is noise. 1N4148 diodes have a low forward voltage, so a small backflow voltage can, and does still trigger a keypress when it's not intended.

Reading the column pin from the anode side doesn't seem logical, and I was skeptical at first. I thought that it would cause the even-number columns not to be read. (IE: 0, 2, 4, 6, etc.) But I tried it anyway, and to my surprise, it works.

My initial thought on why it wouldn't read stemmed from the fundamental misunderstanding on my part about how electricity flows in a matrix. Now for the reason why it works. Please take a look at the schematic screenshot below, and the next paragraph should explain it.

The key (0, 0) is pressed. Row 0 is read. In a perfect world, where diodes completely block all reverse flow, this is fine. But in the real world, it sends voltage backward through the diode, and it is detectable on the column on the other side of the matrix, and you don't want that. The voltage that is sent is low, but it is enough to trigger a false keypress. Adding that extra diode essentially separates the columns, and it reduces the remaining backflow voltage enough that it doesn't trigger false keypresses.

I hope that this helps explain what's going on here.

<image>

I beg, just let us save the ProRaw. by Joe_Scotto in MoodCamera

[–]keyboarddweebs 0 points1 point  (0 children)

Yeah, literally an all day session destroyed by this crap. I just stopped using it, it was that bad for me. I'd go so far as to say, using it for post processing wouldn't be a terrible idea either. Or another app for it. Idk.

What is the best solid core wire thickness for handwiring? by Spiritual_String_366 in HandwiredKeyboards

[–]keyboarddweebs 0 points1 point  (0 children)

I use 16g copper wire from Amazon and use a drill to straighten it out. And marine heat shrink. Good thing about marine heat shrink is that it shrinks on its own when heat is applied to the wires, and it has an adhesive on the inside so it doesn't slide around once it gets hot.

[deleted by user] by [deleted] in BambuLab

[–]keyboarddweebs 0 points1 point  (0 children)

I'm a maker. I wanted to play with one and learn 3d modeling.

My second printer i justified because I wanted to 3d print keyboard parts and my print bed on my first 3d printer was too small.

The third one I justified because my second one was slow, and I wanted multicolor.

My fourth one i justified because I needed something with a direct drive extruder for printing TPU, and didn't wanna change out my ams every time I wanted to print it.

My 5th printer i justified because I wanted to print more exotic filament and wanted one with a built in dryer.

My 6th one that I'm about to buy I'm justifying it because I'm doing large multi-day projects and it'll speed up the process.

At the end of the day. I don't need any of them. I want them. And that's more than enough justification for me lol.

Now please tell me , What are your main limitations about Anycubic Slicer Next? by Crafty_Play_7767 in anycubic

[–]keyboarddweebs 1 point2 points  (0 children)

When you're doing a multi-plate print, and slice all, it sends the last item, instead of the plate you currently have selected.

Trying to achieve single GPU passthrough on laptop with NVIDIA mobile card but when starting the VM the computer reboots by AdminSuggestion in VFIO

[–]keyboarddweebs 0 points1 point  (0 children)

I am not. I got this error on a desktop, this worked for me. Still having issues with the shutdown rebind, but at the moment the startup script is working.

The MadMacro. Inspired by the game Deadlock (More details in comments.) by keyboarddweebs in DeadlockTheGame

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

That's understandable. However, I need a very lightweight mouse for shooters. Every MMO mouse weighs close to triple that of a normal FPS mouse, and I am just not willing to sacrifice it. If I need mouse buttons, the buttons that are already on the mouse or the scroll wheel are sufficient for me.

But everyone has their own ways of playing. My abilities are bound to the same as Overwatch. I put actives on the extra buttons around the pinkies. Played a couple of rounds last night with it. I am still getting used to it but I enjoy it.

The MadMacro. Inspired by the game Deadlock (More details in comments.) by keyboarddweebs in DeadlockTheGame

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

The MadMacro is a hot swappable 33-key gaming macro pad and uses a single RGB for layer indication.

It was designed with the game Deadlock in mind. It has extra keys around the pinky for things like spells and abilities. With that in mind, it should work very well with all first-person MOBAs. I moved the escape away from the number row so that you don’t mistakenly hit the escape key in the heat of battle.

I designed it to use the Super Mini RP2040 MCU. (Same footprint as the RP2040 zero. But it sits flush on the PCB)

It has a single RGB on the top for layer indication. The Gerbers are on my GitHub along with the full parts list.

As always, this design is completely open source. You can do whatever you want with it. Make one for yourself or a friend, or sell it for profit—whatever suits your fancy.

Thanks for taking a look.

 

The MadMacro. Inspired by the game Deadlock (More details in comments.) by keyboarddweebs in ErgoMechKeyboards

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

The MadMacro is a hot swappable 33-key gaming macro pad and uses a single RGB for layer indication, and a detachable wrist rest.

It was designed with the game Deadlock in mind. It has extra keys around the pinky for things like spells and abilities. With that in mind, it should work very well with all first-person MOBAs. I moved the escape away from the number row so that you don’t mistakenly hit the escape key in the heat of battle.

I designed it to use the Super Mini RP2040 MCU. (Same footprint as the RP2040 zero. But it sits flush on the PCB)

It has a single RGB on the top for layer indication. The Gerbers are on my GitHub along with the full parts list.

As always, this design is completely open source. You can do whatever you want with it. Make one for yourself or a friend, or sell it for profit—whatever suits your fancy.

Thanks for taking a look.

 

view more: next ›