home.social

#zmk — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #zmk, aggregated by home.social.

fetched live
  1. @petejohanson @papawilf Sadly dozens of us on Mastodon may be accurate - see also #MechanicalKeyboard firmware hashtags like #QMK, #ZMK, etc. There is lots on Discord (behind closed doors), or Reddit…

  2. I've got a keyboard, the NocFree &: the firmware is shit. I'm pretty sure they don't have a firmware dev and just thought they could get AI to do it.

    My question: I have .uf2 files for a ZMK build of the keyboard and dongle. Can I just put the parts into DFU mode and copy the .uf2 files over? Shouldn't that get me the ZMK firmware for the board?

    #ZMK #Keyboards #Programming #Firmware #Computers #MechanicalKeyboards

  3. @deshipu looks like it could be made to run a keyboard with Zig github.com/semickolon/kirei

    It is a 32-bit RISC-V with recent Zephyr support docs.zephyrproject.org/latest/ so maybe #ZMK would be possible?

  4. #keyboard input is ludicrous. Why can't the hardware just* send unicode characters to the system?

    (I want my #zmk keyboard to send dollar, pound and euro signs to the system from a us keyboard layout and... lol. There shouldn't even be the notion of a us keyboard layout but here we are)

  5. Nouveau clavier bluetooth split avec ZMK.

    Bon, ZMK c’est assez cool et globalement, le clavier marche plutôt pas mal.

    Il a fallu que je remappe certaines touches qui sont un poil moins accessibles sur Redox que sur mon Ergodox historique (notamment les touches centrales).

    Par contre, c’est très étonnant de voir à quel point la connexion Bluetooth est « fragile ». Mon gros PC est à seulement 80cm du clavier, y’a déjà de la latence de ouf…

    #bluetooth #redox #zmk

  6. I made a thing: a tool that allows programmable keyboards to send arbitrary Unicode characters. I created this mainly for myself, but I'm curious to know if there are other persons on this planet that could use it, so here it is:

    crates.io/crates/infinikey

    Because you didn't ask, here's my story. 😉

    Ever since I bought a split ergonomic keyboard (2008, Kinesis Advantage 2), I have used an English keyboard layout at work despite being German and working in Germany. I think that for my field (software development), English layouts are just superior to the German one(s).

    Still, I also need German umlaut characters for emails and chats in German. Back then I only used Windows at work, so using some Microsoft tool I created a custom keyboard layout. It mapped Ctrl-Alt-A to the letter ä, for example. The problem was that (some) software would still receive the Alt key and for example open its menu. So I built a script with AutoHotkey that handled these keypresses and that worked better. I installed the script on the work and home PCs, and when I got a new keyboard (2023, MoErgo Glove80) I started using it both at work and at home.

    Fast forward to last year, when I started at a new company, and my department there does not use Windows but Linux - yay! However, that meant my AutoHotkey scripts no longer worked. 😢

    I could probably have fiddled with xkb and things, but I really wanted _one_ solution that works on Linux and Windows. After several experiments (different approaches with XCompose/WinCompose and 'misusing' the Espanso text expander), a few months ago I finally decided I need to write my own software. And as of this week, it's not only good enough for daily use, but also published and installable by anyone! 🎉

    Thanks for reading this far. Let me know if you're one of the maybe 10 to 100 persons in the world who have some use for this software. 🙂

    #MechanicalKeyboard #Keyboard #FOSS #OpenSource #Rust #Glove80 #KinesisAdvantage #Windows #Linux #ZMK

  7. I obviously suck at soldering! My left thumb cluster just stopped working, which led to a new "opportunity" to learn - identifying what was wrong.

    I never really bothered to look into how the circuits worked when building it the first time since I was busy learning to type on the split keyboard.

    Tried out #deepseek v4 flash to help identify root causes and guiding me on how to debug it as part of testing how good this very cheap model is.

    The guidance was solid, but I've soon ruled out most things without the error. At least I've learnt some (and removed the useless rotary knob that I tried out)...

    #splitkb #electronics #keyboards #zmk

  8. On est en train de rassembler les informations relatives au #Quacken sur une page web. Pour l’instant il n’y a que deux liens :

    Promis, on étoffe tout ça au fur et à mesure !
    onedeadkey.github.io/quacken/

  9. Keychron/Keychron-Keyboards-Hardware-Design

    All the industrial design files for Keychron keyboards and mice. Includes CAD models (case, plate, stabilizer, encoder, keycap) for Q, Q Pro, Q HE, K Pro, K Max, K HE, V Max, P HE series and M1–M7 mice. 100+ models. STEP/DXF/PDF formats.

    This project is source-available. Commercial use is strictly prohibited.
    Language: Python

    Stars: 1310 Issues: 4 Forks: 99
    github.com/Keychron/Keychron-K

    #3d_printing #cad #gaming #gaming_keyboard #gaming_mouse #hardware_designs #keyboard #keyboard_firmware #keychron #mechanical_keyboard #mouse #qmk #qmk_firmware #zephyr #zmk #zmk_firmware

  10. #Ækeynox équipe les premiers Quacken qui viennent d’être livrés. On a beaucoup bossé sur ce firmware pour en faire une #keymap aussi saine que possible pour toutes les personnes adeptes de #Poticlaviers, débutantes ou aguerries, de 20 à 200 mots par minute.

    On fait en sorte qu’Ækeynox supporte le plus grand nombre possible de claviers #ZMK et #QMK avant les #JdLL, fin mai.

    github.com/OneDeadKey/selenium

    La fonctionnalité Ækeynox sur laquelle on bosse en ce moment, c’est l’émulation #Ergol et #QwertyLafayette. Ça s’annonce bien !

    #aekeynox

  11. @hbons I've long dreamed of getting a "proper" logo (not just for our studio app, but for the project as a whole, usage in social media, etc)

    Is that the kind of thing you help projects with?

  12. @rayk yeah, my biggest concern there is mostly going to be sane mapping of devices into the container(s) for / for flashing, twister, etc.

  13. Messing about with my #KeyboardLayout again (that’s half the fun of #QMK or #ZMK etc in a programable #MechanicalKeyboard), this time the mechanism to get capital letters without a dedicated shift key… ⇧

    I’m giving #AutoShift another go (long press for capitals), alongside #CapWords (like caps lock, but it turns off at the end of a word), and #MagicCommaShift (comma before letter means shift) 🪄 ⇧

  14. . @zmk builds on GitHub Actions have always been uploading artifacts as "firmware.zip". It has always been utter annoying to me.

    So I wrote a small GitHub Actions workflow to overcome this: It adds built firmware files to the release as separate files, just like QMK does:

    github.com/Ardakilic/zmk-confi

    Example release:

    github.com/Ardakilic/zmk-confi

    Might be useful for you. It definitely will be for me :)

    I wish this was in core ZMK thogh.

    #zmk #qmk #mechanicalkeyboard #githubactions

  15. A @zephyr driver that's been a long time coming... github.com/zephyrproject-rtos/

    RGB support on stm32 has been a frequent request from that small subset of folks running on wired boards. Rarely had the SPI based driver worked with the pins used by most designs, so when I saw github.com/zephyrproject-rtos/ get merged, I immediately jumped into an led_strip driver using it!

    It's fairly straightforward, using DMA to feed in a sequence of compare values that correspond to the necessary bit value to send.

  16. @ajit_456 our codebase runs on a myriad of hardware platforms, including interesting DMA ADC workflows for HE/EC designs, settings storage over all sorts of different flash controllers, different underlying bootloader integration, etc. It's not always perfect, and there are occasionally times when platform specific work has to happen, but those are definitely *exceptions* and not the norm.

    Of course, the details vary a lot depending on your specific project.

  17. @AAMfP I found github.com/eswai/zmk-naginata very easy (but I already had plain ZMK working; current advice is target #ZMK v0.3, main branch still in flux).

    On the other hand, there is github.com/eswai/qmk_userspace which I think I got to work months ago - but the details are not fresh in my mind. The whole #QMK user space upheaval was still settling.

    I focused on ZMK as I was doing my first Bluetooth keyboard.

  18. When using Blender I’d like to keep my right hand on the pointing device (pen or mouse) and the other on the keyboard.

    But I use a steeply tented split keyboard, and a few keys I need regularly are on the right half; with a flat keyboard I’d reach over to the other half, but because of the almost 90° tenting this is difficult and slow.

    I think I will try solving this issue by making one key flip the two halves (temporarily).

    What do you think, how would you approach this problem?

    #blender #blender3D #b3d #mechanicalKeyboard #mkb #splitKeyboard #ZMK #QMK

  19. Thought I might unwind Friday night by tinkering with my #MechanicalKeyboard firmware - there are RGB LEDs that could be twinkling for me ⌨️✨

    But no, new mysterious build failures & discovering and reporting out-dated documentation referencing the older #Zephyr that will need updating for #ZMK v0.4 😅

    Hopefully this will just make it all the sweeter once it works?

  20. Turns out there are still some major caveats to using the #RP2350 in a #MechanicalKeyboard on #ZMK with Zephyr 4.1. Roll on ZMK supporting Zephyr 4.3?