8d9bfdc254
* add some split data to info.json * add tags * add half of config_options.md to info.json * add support for designating master split * sort out split transport and primary * fix bad data in UNUSED_PINS * fixup custom transport * wip * allow for setting split right half keyboard matrix * add SPLIT_USB_DETECT * minor cleanup * fix an erroneous message * rework split.usb_detect * adding missing rgblight vars to info.json * add mouse_key to info.json * add all remaining options from docs/config_options.md * fix audio voices * qmk info: Change text output to use dotted notation * tweak layout output * resolve alias names * break out some functions to make flake8 happy * add a field for bootloader instructions * qmk generate-info-json: add a write-to-file argument Adds an argument that instructs qmk generate-info-json to write the output to a file instead of just to the terminal. * -arg_only, +action Because it was never my intention that one would have to specify a value for the argument that enables writing the file. * Bring qmk generate-info-json inline with other generate commands * pytest fixup * fix esca/getawayvan * fix data driven errors for bpiphany converters * features.force_nkro -> usb.force_nkro * split.primary->split.main * fix esca/getawayvan_f042 * fix the bpiphany converters for real * fix bpiphany/tiger_lily * Apply suggestions from code review Co-authored-by: Nick Brassel <nick@tzarc.org> * fix generate-api errors * fix matrix pin extraction for split boards * fix ploopyco/trackball_nano/rev1_001 Co-authored-by: James Young <18669334+noroadsleft@users.noreply.github.com> Co-authored-by: Nick Brassel <nick@tzarc.org> |
||
|---|---|---|
| .. | ||
| keymaps | ||
| rev1_001 | ||
| config.h | ||
| info.json | ||
| readme.md | ||
| rules.mk | ||
| trackball_nano.c | ||
| trackball_nano.h | ||
readme.md
Ploopy Trackball Nano
It's a DIY, QMK Powered Trackball...Nano!
- Maintainer: PloopyCo
- Key contributors: Drashna Jael're, Germ
- Hardware Supported: ATMega32u4 16MHz(5v)
- Hardware Availability: Store, GitHub
Make example for this trackball (after setting up your build environment):
make ploopyco/trackball_nano/rev1_001:default:flash
make ploopyco/trackball_nano/rev1_001:via:flash
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.
Hardware Reset Button
The Ploopy Nano has a handy bootloader reset mechanism: two via pins on the board, designated by the reference designator MCU.J.X BOOTLOADER. If you stick an uninsulated paperclip or a pair of metal tweezers into both holes and plug in the Nano, it will start in bootloader mode.
Revisions
Occasionally, new revisions of the PCB will be released. Every board comes with a designator that looks something like R1.001.
Match the firmware that you flash onto the board with the designator on the board.
Customzing your Ploopy Nano Trackball
You can change the DPI/CPI or speed of the trackball by calling adns_set_cpi at any time. Additionally, there is a DPI_CONFIG macro that will cycle through an array of options for the DPI. This is set to 375, 750, and 1375, but can be changed. 750 is the default.
To configure/set your own array, there are two defines to use, PLOOPY_DPI_OPTIONS to set the array, and PLOOPY_DPI_DEFAULT.
#define PLOOPY_DPI_OPTIONS { CPI375, CPI750, CPI1375}
#define PLOOPY_DPI_DEFAULT 1
The PLOOPY_DPI_OPTIONS array sets the values that you want to be able to cycle through, and the order they are in. The "default" define lets the firmware know which of these options is the default and should be loaded by default.
The DPI_CONFIG macro will cycle through the values in the array, each time you hit it. It stores this value in persistent memory, so it will load it the next time the device powers up.
Fuse settings
When flashing the bootloader, use the following fuse settings:
| Fuse | Setting |
|---|---|
| Low | 0x5E |
| High | 0x99 |
| Extended | 0xC3 |