Skip to content

BX Tacho 2.4.3

Latest

Choose a tag to compare

@dazchi dazchi released this 07 Nov 14:54

BX Tacho firmware 2.4.3, for the Beyblade X launcher RPM meter. Web app: https://dazchi.github.io/bx-tacho/

What's changed

  • Lower default load levels: a board without a load calibration now takes 100 / 200 mV (empty / loaded) on a black launcher, and 490 / 690 mV on a white one (were 100 / 300 and 490 / 750 mV). It then switches to the white launcher's settings above 670 mV instead of 724 mV, so a board whose load sensor reads a little low still recognises a white launcher, and back to black below 140 mV instead of 180 mV.

    The defaults only apply to a board with no saved settings: a newly flashed board (merged image), or after cfg reset. A board that already has settings saved keeps the levels it has. To give such a board the new levels without a calibration, set them directly (from 2.4.2):

    cal load black loaded 200
    cal load white loaded 690
    

    A load calibration (cal load black|white empty|loaded) on each launcher is still the best fit for each board.

From 2.4.1 or earlier, this also brings cal load black|white empty|loaded <mV> (2.4.2: set a level directly), and from 2.4.0 or earlier the fixes of 2.4.1: the load calibration no longer drifts into the saved settings, and cal vbat verify passes within ±15 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.3.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.3-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.3.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.3.bin 0x10e000 ota_data_initial.bin
python -m esptool --chip esp32c3 write-flash 0x0 bx-tacho-v2.4.3-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).