qmk-firmware/keyboards/ploopyco/trackball_nano
Ryan ebb512db82
Debounce defines cleanup (#19742)
* Clean up `DEBOUNCE` in config.h, 0-9

* Clean up `DEBOUNCE` in config.h, A

* Clean up `DEBOUNCE` in config.h, B

* Clean up `DEBOUNCE` in config.h, C

* Clean up `DEBOUNCE` in config.h, D

* Clean up `DEBOUNCE` in config.h, E

* Clean up `DEBOUNCE` in config.h, F

* Clean up `DEBOUNCE` in config.h, G

* Clean up `DEBOUNCE` in config.h, H

* Clean up `DEBOUNCE` in config.h, handwired

* Clean up `DEBOUNCE` in config.h, I

* Clean up `DEBOUNCE` in config.h, J

* Clean up `DEBOUNCE` in config.h, K

* Clean up `DEBOUNCE` in config.h, L

* Clean up `DEBOUNCE` in config.h, M

* Clean up `DEBOUNCE` in config.h, N

* Clean up `DEBOUNCE` in config.h, O

* Clean up `DEBOUNCE` in config.h, P

* Clean up `DEBOUNCE` in config.h, Q

* Clean up `DEBOUNCE` in config.h, R

* Clean up `DEBOUNCE` in config.h, S

* Clean up `DEBOUNCE` in config.h, T

* Clean up `DEBOUNCE` in config.h, U

* Clean up `DEBOUNCE` in config.h, V

* Clean up `DEBOUNCE` in config.h, W

* Clean up `DEBOUNCE` in config.h, X

* Clean up `DEBOUNCE` in config.h, Y

* Clean up `DEBOUNCE` in config.h, Z

* Remove default debounce from info.json

* Migrate non-default debounce to info.json
2023-02-03 19:19:58 +00:00
..
keymaps RESET -> QK_BOOT user keymaps (#17940) 2022-08-21 23:55:30 +01:00
rev1_001 Remove UNUSED_PINS (#17931) 2022-08-06 23:23:35 +10:00
config.h Debounce defines cleanup (#19742) 2023-02-03 19:19:58 +00:00
info.json Debounce defines cleanup (#19742) 2023-02-03 19:19:58 +00:00
readme.md fix typos (#15316) 2021-11-28 07:02:32 +11:00
rules.mk Tidy up NKRO_ENABLE rules (#15382) 2021-12-09 16:05:44 +11:00
trackball_nano.c Use a macro to compute the size of arrays at compile time (#18044) 2022-08-30 10:20:04 +02:00
trackball_nano.h Add lkbm keymap (#17218) 2022-07-02 22:03:11 +10:00

Ploopy Trackball Nano

Ploopyco Trackball Nano

It's a DIY, QMK Powered Trackball...Nano!

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.

Customizing 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 { 375, 750, 1375}
#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