Skip to content

ricket split89 v2

Latest

Choose a tag to compare

@Ricket Ricket released this 08 Nov 01:44
· 294 commits to ricket-split89 since this release

Keyboard: handwired/split89

split89 keyboard with Cherry MX Speed Silver keys.

keymap: ricket

Differences from the stock split89 firmware:

  • Reordered bottom-left keys: ctrl, fn, win, alt. To match the order on my laptops.
  • Enable NKRO, and enable it by default. There seems to be no downside to this, unless you plug the keyboard into something really old.
  • Fn+pause toggles NKRO, in case you want to turn it off for whatever reason.
  • Disable mousekeys, tapping, oneshot features. I don't use them and maybe disabling them will be smaller/faster. (I'm not actually certain I disabled them now that the format switched to json)
  • Set USB polling interval to 1ms - verified using Keyboard Inspector. The default used to be 10ms, nowadays it is 1ms by default I think, but I explicitly configured it just to make sure.
  • Change debounce algorithm to sym_eager_pk. i.e. symmetric eager per-key. This results in a faster input time from key depress, where the default algorithm waits for the debounce time before sending the input.
  • Explicitly set debounce time at 5ms which is the default. I chose to keep the default because it doesn't matter much with eager debounce algorithm, and the official spec sheet for the speed silver switches states "Bounce time: < 5 ms", and I don't want to do a bunch of experimentation to figure out what the lowest reliable limit here is.

Differences since v1 release below:

  • Reordered the bottom-left keys. Previously ctrl-win-alt-fn, now ctrl-fn-win-alt to match my laptop layouts so that I can better build that muscle memory.
  • QMK is moving from .c files to a .json file, I updated to that. They also updated some defaults but I have kept them explicitly specified, as noted above. Also as a result of this, I'm no longer certain that I disabled some features, because QMK lacks documentation about the features config map, but oh well.

To flash: use the QMK toolbox (get the portable exe). Run as administrator and install drivers if you haven't already (it's in the menu). Load the hex file and enable auto flash. Unplug the keyboard, unplug the halves from each other. Then, there's a fiddly bit that I'm not sure exactly but basically you want to plug it in, maybe hold the reset button down while you plug it in or maybe not. Release the reset button if you were holding it, and wait about 10 seconds to see if it flashes or not. Then press the button once, wait 10 seconds. Then if it didn't flash, double-press the reset button and see if it works. Also, if it says "flash successful", you need to actually read the output because it might've actually failed. Eventually through some combination of pressing the reset button, you'll get a flash where it pauses for a moment to write, and then also it verifies the firmware afterwards, and then you can do the other half of the keyboard.