Framework Laptop 16 inch Number pad Suggestion

kevin_gonzalez · June 6, 2025, 9:47pm

While having ability to use a number pad on the 16 inch laptop wonderful as I prefer to use a full size keyboard, I think it would be really be helpful if the num lock key was updated to give an led indicator similar to the caps lock led light, to show if the number pad is on or off

Joe_Name · June 6, 2025, 9:51pm

Can I upvote this? Given that it has dual purpose, that would be most helpful!

knipp30 · June 6, 2025, 11:03pm

Windows or Linux user?

I agree an LED would be a godsend!! But for Gnome, there is an extension that adds you current numlock status to the taskbar.

gcf · June 7, 2025, 10:22am

See also Num lock indicator

Klay_Hart · June 7, 2025, 1:21pm

I might try. I know there’s been plenty of people who’ve complained about that. Although I’ve had issues with my backlight on my numpad being randomly off when I boot so I’m not quite sure how well that’ll work for me.

Joe_Name · June 9, 2025, 11:26am

Although there are software options to show the num lock status, there are other situations before logging in that a little blue light like the caps lock would be very nice. OTP when logging in is one.

kevin_gonzalez · June 19, 2025, 1:36am

I’m a windows user (Windows 11)

Kocsonya · June 23, 2025, 11:02pm

Absolutely agree, and I’d go even further: a ScrollLock LED would also be useful. We don’t use scroll lock any more (it was a feature with 80x25 text monitors, many decades ago), but I use the scroll lock key to switch between keyboard layouts, and the LED shows which state the keyboard is.
While you can put all sorts of indicators on the screen, I don’t like to waste precious display real-estate for things that could be solved with a simple LED.

Xavier_Jiang · June 25, 2025, 9:10am

I dont think there is enough space to cram in a NAV clsuter (page up, page down, etc). The separate numpad and keyboard also let you have the numpad on the left.

Updating numlock to have a LED would be really nice, I agree. I’m trying to come up with some .. “novel idea” about using backlight to indicate numlock state (e.g., via breathing)

This is not a problem with the RGB macoropad, because you have per-key RGB. You can just .. set the backlight on the numlock key to be different or whatever.

I will say, my modified firmware that use Esc + Backspace (or the = button) for backlight control is much superior. Next time I will try disabling Via support for significantly less code and clutter, and doing a breathing control for the numlock state. I don’t know, maybe I can blink the CapsLock for all you know. It’s QMK!

MJ1 · June 25, 2025, 12:23pm

Do you mean, have the caps lock key on the keyboard slowly blink as long as numlock is on? You could certainly do that.

Do you happen to have an RGB keyboard? Changing the cap lock key color would another idea. Or the top right key closest to your numpad (presuming it’s on the right).

Keyboard to keyboard communication is possible with a little trick using the indicators. I use it on my mouse, learned of it from an old alternative firmware I found created by Ploopy Co. There is also an example of it from a community member here. I could find links when at my PC.

~edit~
The one I’ve used is based on Ploopyco’s LED-Key BitMasks (lkbm).

github.com/qmk/qmk_firmware

keyboards/ploopyco/trackball_nano/keymaps/lkbm/readme.md

0.23.9

# The keymap that takes commands as LED-Key BitMasks (lkbm)
Based on [maddie](../maddie), this keymap lets you send a 2-bit command by having a macro on your keyboard tap `KC_NUM_LOCK` and `KC_CAPS_LOCK` on and off within a very short window (25ms by default) to represent bits 1 and 2 respectively.  The keymap uses this to allow toggling between sending mouse-movement events and scrolling events; cycling DPI presets, and resetting to the bootloader, so you can reflash without having to unscrew your Ploopy Nano.

Here’s another implementation based on lkbm.

github.com/nicknimchuk/qmk_nano_dualhand

readme.md

main

# qmk_nano_dualhand: a keymap designed for two Ploopy Nano trackballs
This keymap configures two Ploopy Nano trackballs, one for each hand. At any given time, one will be for mouse movement, while the other is used for scrolling. This can be swapped dynamically using commands from a QMK keyboard, potentially reducing injury or strain by not restricting mouse movement to a single hand. 

![Pictured: two Ploopy Nano trackballs with a ZSA Moonlander keyboard on the Platform accessory](https://imgur.com/hrQaC6u.jpg)

## Inter-QMK communication
The primary feature this code provides is a num/caps lock communication feature based on the [lkbm](../lkbm) Nano keymap, which was itself based on [maddie](../maddie). It provides code for sending and receiving commands between QMK devices by toggling the caps lock and num lock keys for "bits" of the commands. The main advantages over the previous versions of this feature are:

* The feature is mostly broken out into separate files, so it's easier to apply to other devices and keymaps.
* The command length is an arbitrary (pre-defined) number of bits, so any number of commands can be created at the cost of slower commands.
* There are many timings that can be easily tweaked to try to find the right balance of speed and command reliability. These timings do not have to influence any other settings in QMK.
* The commands are sent asynchronously, so even if a command takes a full second to send, you can use the device while it is sent.

There's also some disadvantages:

* Commands will likely take longer to allow for two-way communication if desired.
* Bits are only processed if the given lock is toggled twice without the other lock toggling. This reduces misinterpreted commands, but also means that some commands that [lkbm](../lkbm) would handle due to interleaved lock commands will be ignored.
* The asynchronous nature means that typing could happen while caps lock or num lock is temporarily enabled (or temporarily disabled). This can be slightly mitigated by the fact that one command will only use caps lock, and another command will only use num lock (but the rest will use both).
* This feature is not written to minimize flash space. This is not a problem with the Nano, which has plenty of free space by default, but may cause problems with some keyboards. The older options do not require any additional code space to send commands.

This file has been truncated. show original

And the FWL16 altsync firmware by a community member, which looked to be based on nano_dualhand.

Using scroll-lock is also possible, as I do that on my mouse. There is also a kana indicator which should be a possibility but I had trouble getting that to work & I didn’t really have a need for it so I didn’t bother.

Xavier_Jiang · June 27, 2025, 11:02am

Nah. I got the pleb white backlit Numpad and Keyboard. British English dont have RGB, I decided to get a ISO for the funs.

Yeah. Or maybe the other way around. And I was just thinking a blink rather than a fade. Maybe a fast fade.

I would pass. Too much kerfuffle. And also, let’s not confuse the OS in the process.

The “annoying” bit is that the Framework keyboard use more than just USB. They also have a (not working) backlight off when lid is closed or sleep, which doesnt turn back on when you wake it from sleep.
Sleep, I think. lid seems ok.

system · December 24, 2025, 11:03am

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Num lock indicator Framework Laptop 16 framework-laptop-16-amd-7040	18	3470	April 29, 2024
Feature Request: Num Lock on boot, Schematics for Keyboards (to build vial support) Framework Laptop 16 framework-laptop-16-amd-7040	21	2141	March 24, 2024
How to disable numpad backlight? Community Support keyboard-touchpad , framework-laptop-16-amd-7040	15	7000	October 28, 2025
Change Framework 16 numpad plus key to workwith NumLock off Community Support	9	908	May 16, 2024
Number Pad Backlight Framework Laptop 16 framework-laptop-16-amd-7040	5	1505	August 31, 2024

Framework Laptop 16 inch Number pad Suggestion

Related topics