Multi-Language & Calibration

USB keyboards send scancodes, not characters. The same scancode produces @ on a US layout and " on a German layout. For BLELogger's logging, regex detection, and replace rules to work, the firmware needs the scancode-to-character map for each keyboard.

Calibration workflow

1. Open the Web UI → Calibration panel.
2. Click Start calibration with the target USB keyboard plugged in.
3. Type the guided sequence (printable ASCII subset).
4. BLELogger builds a profile and saves it to the filesystem.
5. Future sessions with the same keyboard auto-load that profile.

The profile is identified by the keyboard's USB VID/PID and serial number when present. Plug in a new keyboard → new profile required.

Built-in layouts

For keyboards without prior calibration, BLELogger falls back to one of 18+ pre-shipped layouts: us, uk, de, fr, es, it, pt, nl, dk, no, se, fi, ch-de, ch-fr, pl, cz, hu, ru, tr, jp, kr. Set the fallback in Settings → Default Layout.

When to recalibrate

• After firmware updates that touch the calibration engine (release notes will say).
• When a calibrated keyboard starts producing wrong characters (rare; usually means firmware change in the keyboard itself).
• When you replace a worn keyboard with a fresh unit even of the same model — the new unit might have different VID/PID/serial.

Bridging vs. logging

Bridging (USB → BLE) works without calibration — scancodes pass through unchanged and the BLE host applies its own layout. Calibration only affects what BLELogger logs internally.