How to Remap a Macropad With VIA

KM16 Macropad combines sixteen keycaps with one large knob and two smaller knobs on an anodised aluminium body. VIA remapping is confirmed for the product, although the exact controls exposed can depend on its firmware revision.

What does VIA change on a compatible macropad?

VIA communicates with compatible keyboard firmware over USB and edits the dynamic keymap made available by that firmware. The firmware decides which layers, encoder actions and other features the configurator can show. Treat the connected device as the authority instead of following a screenshot from another keyboard.

Before changing anything, capture the current layout or export a definition when the available VIA interface supports it. Photographing the physical labels also helps. A known-good starting point matters when several keys use unfamiliar codes.

How do you remap the first key?

Connect the pad by cable, open the current VIA interface and authorize only the intended device if the browser asks. Select one physical position and assign a harmless output such as Escape or an unused function key. Test it in a plain text field before editing another control.

If the device does not appear, confirm the cable carries data, reconnect it and check VIA's current compatibility guidance. Do not flash firmware taken from a similar-looking pad. Visual resemblance does not establish that firmware, bootloader or pin assignments match.

Do mappings follow the pad to another computer?

VIA-compatible firmware commonly stores its dynamic keymap in nonvolatile device storage, which can let remaps travel with the keyboard. That general behavior does not prove every setting on every revision persists identically. Disconnect the configurator, power-cycle the pad and test the result before relying on portability.

Application shortcuts still belong to the destination computer. A key may continue to emit F13 while the new operating system has no action assigned to it. Document the hardware output separately from the command it triggers.

How should you handle layers and knobs?

Add layers only when the connected firmware exposes them and you can keep a reliable route back to the base layout. Verify hold, tap and toggle behavior individually. Do not publish a layer count copied from a generic guide as a specification for this pad.

Test clockwise rotation, counter-clockwise rotation and knob press as separate inputs. Some firmware exposes all of them, while another build may not. The KM16 Macropad offers many physical controls, but a documented base map is more useful than a dense layout you cannot recover from memory. Keep a dated copy of that base map so later experiments can be compared against a known configuration.