Skip to content

BX Tacho 2.1.0

Choose a tag to compare

@dazchi dazchi released this 25 Oct 17:45

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

What's new

  • Cleaner launch curves: while a top is loaded, the load sensor's LED is flashed to watch for the release, and some of its light reaches the RPM sensor. The flash now starts exactly at an RPM edge, when the disc shows white, and is off again within 90 % of the white part, so its light can't add or shift an edge any more. That removes the spikes it caused on black launchers, and the release is now seen up to about 30,000 rpm (about 20,000 before). status counts any flash that had to be cut short.
  • RPM threshold scan: rpm scan … apply now sets the threshold 60 % of the way from the black to the white level (it was the midpoint), and keeps the load LED off while it samples, so the LED's light can't raise the white level it finds.
  • Calibration commands always name the launcher: cal load black|white …, rpm thr black|white <mV> and rpm scan black|white … apply. Right after switching on, BX Tacho is on the black settings until a white launcher shows itself, so leaving the name out could save a white launcher's value as the black one's. rpm thr alone still shows both thresholds.
  • load led on|off|auto (diag or meter mode): off now keeps the LED dark (before, it only released on, and the diag readings kept flashing it); auto goes back to normal. While it's held, load and the diag screen show the live raw LOAD_SENSE voltage instead of freezing.

Updating

From 2.0.0: your settings and calibration are kept. Running the RPM scan again on each launcher is worth it, for the new 60 % threshold:

diag on
rpm scan black 5 apply    (on a black launcher, turn it slowly)
rpm scan white 5 apply    (on a white launcher)
diag off

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 the first top is loaded (or the pin pushed up). Until then the empty white launcher shows LOADED.

Files

File For
bx-tacho-v2.1.0.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.1.0-merged.bin A blank board: everything from address 0x0. Overwrites settings and shot history; the battery calibration is kept.
ota_data_initial.bin A blank otadata (8 KB of 0xFF), only for flashing bx-tacho-v2.1.0.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.1.0.bin 0x10e000 ota_data_initial.bin
python -m esptool --chip esp32c3 write-flash 0x0 bx-tacho-v2.1.0-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).