ReLow60 Firmware v1.13 & ReConf v1.4.0: 7-Step Polling Rate Selection and USB Diagnostics
Overview
The ReLow60 L-HE firmware has been updated to v1.13 and the configurator ReConf to v1.4.0. This release includes the following changes:
- Polling rate can now be selected from seven steps between 125 Hz and 8000 Hz
- Fixed a bug where the legacy “1000 Hz” setting was actually running at 62.5 Hz
- Added a USB polling rate diagnostic that measures the host’s actual polling interval
- The diagnostic screen now also displays the keyboard’s own scan rate (added in v1.14)
In addition, future firmware updates can now be completed entirely within ReConf (this update alone still requires flashing via Web DFU, as before).
7-Step Polling Rate Selection
The previous on/off toggle for “enable 8000 Hz” has been replaced with a seven-step selection: 8000 / 4000 / 2000 / 1000 / 500 / 250 / 125 Hz. The setting can be changed from the ReConf configuration screen.
8000 Hz provides the fastest input response but consumes more USB bandwidth and host-side processing. You can now lower it to suit your environment and preferences.
Bug Fix for the “1000 Hz” Setting and Request to Verify Your Configuration
In previous versions, selecting “1000 Hz” caused the keyboard to actually run at 62.5 Hz.
In USB high-speed connections, the value specifying the polling interval is interpreted as an exponent. The previous firmware treated this value as a direct divisor, causing the keyboard to operate at 128 microframes (= 62.5 Hz) instead of the intended 1000 Hz.
v1.13 corrects this calculation so the keyboard operates at the polling rate you select.
If you had 1000 Hz selected previously, please reselect your polling rate in the settings screen after updating to v1.13. The setting will be automatically migrated to the new format during the update, but we recommend confirming that the intended value is set.
USB Polling Rate Diagnostic
The keyboard only sends a signal to the host when input changes. This means no communication occurs while idle, making it impossible to know how frequently the host is actually polling the keyboard.
If you feel input is occasionally delayed despite having 8000 Hz configured, the cause may lie in the cable, port, or hub — but there was previously no way to isolate it.
v1.13 adds a polling rate diagnostic to ReConf. During the diagnostic, the keyboard maintains a listening state and uses the USB frame number counter to measure response intervals. Because measurement is based on USB bus timing rather than the keyboard’s internal processing time, you can see exactly what is happening between the keyboard and host.
If the measured value falls significantly below the configured 8000 Hz, you can swap the cable or port and re-run the test to isolate the cause.
The diagnostic can also help distinguish whether the issue is on the cable side or the PC side. Missing USB frame signals indicate a problem with the cable or connection path, while frames arriving but responses being delayed indicate the PC cannot keep up with processing. The latter will not improve by replacing the cable; in that case, we recommend trying a different port or checking USB power-saving settings.
Note that very infrequent delays do not produce a perceptible difference. The diagnostic only shows a warning when delays reach a level that could have a real impact.
Longer measurement increases confidence in the result. A faulty cable may behave normally for a while before degrading, so after a short measurement the display reads “No issues so far,” switching to a definitive “This cable is good” after 30 seconds or more.
In the screen above, 13 out of 135,946 reports were slightly delayed. At 8000 Hz, a single delay is 125 microseconds, so this frequency and duration is imperceptible. The verdict therefore remains green, explicitly stating that no action is needed while showing the measured values. There is no need to replace a cable that is working fine.
ReLow Series Keyboard Configurator
Keyboard-Side Speed Also Displayed (Added in v1.14)
Polling rate is “how frequently the PC reads the keyboard.” Whether the keyboard can keep up with that rate is a separate question — you need both figures to understand the full picture of input latency.
The diagnostic screen therefore also shows the rate at which the keyboard is evaluating key states (the scan rate). The measured value on ReLow60 is approximately 11,600 Hz.
Two figures are shown as a breakdown. The frequency at which sensor readings are updated is 15,625 Hz, and the frequency at which key state is evaluated based on those readings is approximately 11,600 Hz. Since the granularity at which key input is actually detected is determined by the slower of the two, the scan rate displayed is the evaluation-side value.
Against 8000 Hz polling, the keyboard runs at approximately 11,600 Hz, meaning the USB side is the bottleneck in this combination.
[Added and corrected 2026-08-22] This section originally described the feature as part of v1.13, but it is in fact included in v1.14. It was added after v1.13 was published, and was mistakenly written up as a v1.13 feature. We apologise for the error.
The scan rate is not displayed on v1.13 — the field is left blank. Please update to v1.14 from the ReConf settings screen.
Note that two builds ended up in circulation as v1.13: one with this feature and one without. Both report the same v1.13 version, so there is no way to tell them apart, which is why the version was reissued as v1.14.
This Will Be the Last DFU Update
Until now, firmware updates required putting the keyboard into bootloader mode and, on Windows, swapping the driver using Zadig — a process that was confusing for first-time users.
Starting with v1.13, firmware can be updated directly from within ReConf. It uses the same communication path ReConf already uses (WebHID), so no driver swapping or selection of a flashing device is required.
However, this feature becomes available after updating to v1.13. This update (v1.12 → v1.13) must still be performed via Web DFU as before. From the next firmware update onward, ReConf will display an update notice and the update will complete with a single button press.
The firmware file is fetched automatically — no need to search for and download it manually. The keyboard verifies the file contents before flashing, so corrupted files or files intended for a different model are rejected before writing. If the cable is disconnected during transfer, the keyboard remains in its previous state and can be retried immediately.
The conventional Web DFU update path remains available as a recovery option if needed.
How to Update
This update should be performed using the firmware update feature (Web DFU) in ReConf. The procedure is described in a separate article.
Step-by-step instructions for flashing firmware from your browser via ReConf
Settings are preserved during the update. Existing configurations including keymaps, actuation points, and Rapid Trigger settings are retained as-is (only the polling rate setting is automatically migrated to the new seven-step format).
Other Fixes
- Fixed an issue where, after pressing and releasing six or more keys simultaneously, the keyboard continued to hold “pressed” state internally. This did not surface under normal operating systems but could cause keys to be treated as held down in environments such as BIOS or UEFI setup screens.
Source Code (GPL-3.0)
The ReLow60 firmware is based on libhmk (GPL-3.0), and the corresponding source code is publicly available.
ReLow60 L-HE Firmware (GPL-3.0)