Repository navigation
BX Tacho 2.4.1
BX Tacho firmware 2.4.1, for the Beyblade X launcher RPM meter. Web app: https://dazchi.github.io/bx-tacho/
What's fixed
-
The load calibration no longer drifts into the saved settings. While a launcher sits empty, BX Tacho slowly re-learns its empty level, so that slow drift doesn't cause false loads. Up to 2.4.0 it did this in the saved settings themselves. So whenever any setting was saved (
rpm thr,cal loadof the other launcher, acfgcommand), the re-learned level was stored as that launcher's calibration, andstatusshowed it as the calibration, different on every read. The re-learned level is now kept apart, in memory only: the calibration stays as you measured it, andstatusshows both:cal black : load empty 120 mV (tracking 134 mV), loaded 860 mV; rpm threshold 1400 mVIf the load detection on a board seemed off after changing settings, run
cal load black empty(andwhite) once more after updating. -
VBAT calibration check within ±15 mV.
cal vbat verifynow passes within 15 mV instead of 10: the supply used as the reference in production is itself off by up to about 10 mV.
Updating
From 2.0.0 or later: your settings and calibration are kept.
From 1.x: calibrate again as described in the 2.0.0 release (the layout changed in 2.0.0).
Known limitation: after switching on, or moving BX Tacho from a black launcher to a white one, it stays on the black settings until a bey has been loaded (or the pin pushed up) for 3 seconds. Until then the empty white launcher shows LOADED.
Boards with R7 = 100k: FULL never shows once the battery is charged (see the 2.4.0 release); replacing R7 with 4.7k fixes it.
Files
| File | For |
|---|---|
bx-tacho-v2.4.1.bin |
Updates. In the web app: USB tab (computer, or Chrome on Android with a USB-C cable) or Bluetooth tab. Settings, shot history and calibration are kept. |
bx-tacho-v2.4.1-merged.bin |
A blank board: everything from address 0x0. Overwrites settings and shot history; the battery calibrations are kept. |
ota_data_initial.bin |
A blank otadata (8 KB of 0xFF), only for flashing bx-tacho-v2.4.1.bin by hand (below). |
SHA256SUMS.txt |
Checksums of all three. |
Release build, optimised for speed (-O2), ESP-IDF v6.1.
Updating from a firmware before 0.8 (single app slot): update over USB once. That writes the two-slot partition table that Bluetooth updates need. After that, Bluetooth updates work too.
Flashing by hand (esptool):
python -m esptool --chip esp32c3 write-flash 0x10000 bx-tacho-v2.4.1.bin 0x10e000 ota_data_initial.bin
python -m esptool --chip esp32c3 write-flash 0x0 bx-tacho-v2.4.1-merged.bin
The first form writes the app and a blank otadata, so the board boots this app rather than one in the other slot; the web app does that for you. The second is for a blank board.
Licensed under the GPL, version 3 or later (see NOTICE for the additional permission covering extensions).