TigerScale V3 v3.1.3

v3.1.3

Updates no longer give up on the first hiccup, and when one does fail it now says
why.

Fixed

• A download was abandoned after ten seconds without a byte. That is
  aggressive for a TLS transfer on a device that is also weighing, serving a web
  interface and talking to the cloud: a transfer that would have recovered was
  reported as a failed update. The window is now thirty seconds.
• A failed image is retried once, automatically. The stalls seen so far were
  transient. Asking someone to start a two-minute update over by hand, for
  something the scale can retry itself in two seconds, is a poor trade.
• A stall now reports where it happened and how much memory was left. The one
  failure captured before this happened with the heap down around 31 KB, which is
  a real lead — and it was only visible because a serial cable happened to be
  attached at the time.

Known issues

• The underlying cause of the stalls is not yet proven. The evidence points at
  memory pressure during the TLS handshake and transfer rather than at the
  network. Updating shortly after a restart, while the heap is least fragmented,
  is still the most reliable moment.

Updating

Over the air from Settings > Update, or over USB with
bash scripts/flash.sh --fs. Both keep your WiFi credentials, TigerTag session
and calibration.

TigerScale V3 v3.1.2

v3.1.2

An update started from the scale's own screen now reports itself like any other,
and a failed update no longer stops the scale looking for the next one.

Fixed

• An update launched from the touchscreen was invisible to everything else.
  The screen called the updater directly with its own progress callback and never
  touched the shared status, so the web interface, the local API and Studio all
  reported "idle, 0%" for the entire two minutes. It now publishes the same
  phases and the same percentage as an update started from the web interface, so
  a client cannot tell which one started it.
• One failed update disabled update checking until the next reboot. The
  automatic check required the status to read exactly idle, and a failure
  leaves it reading error — which is kept on purpose, so the interface can say
  what went wrong. The check now stands down only while an update is genuinely
  running. Failing and then never looking again is the opposite of what you want.

Updating

Over the air from Settings > Update, or over USB with
bash scripts/flash.sh --fs. Both keep your WiFi credentials, TigerTag session
and calibration.

TigerScale V3 v3.1.1

v3.1.1

Housekeeping around the outside of the scale: the page that installs it was
rebuilt, and the link in the scale's own web interface now points at the
ecosystem rather than the shop.

Fixed

• The footer link in the device's web interface pointed at the TigerTag store.
  It now goes to tigersystem.io, which is where the ecosystem is actually
  described. Same fix in the README and the installer page.

Changed

• The web installer was rebuilt for people who have never flashed a board: what
  to have ready before starting, the wiring question with an interactive diagram
  to answer it, a shopping list, and plainer wording throughout.
• It reads in nine languages — the same set as the scale's own web interface
  — chosen from a menu and detected from the browser on first visit.
• Light and dark, with dark as the default and a switch to change it.

The firmware itself is unchanged from v3.1.0. Updating is still worth it if you
use the scale's web interface, since the filesystem image carries the link fix.

Updating

Over the air from Settings > Update, or over USB with
bash scripts/flash.sh --fs. Both keep your WiFi credentials, TigerTag session
and calibration.

TigerScale V3 v3.1.0

v3.1.0

The scale now tells you when an update is waiting instead of expecting you to go
looking. When it finds one it asks, once; if you say no it stays quiet for a day.

Added

• The scale checks for updates on its own — shortly after it joins WiFi, then
  every six hours — and asks whether you want to go to the update page. Answering
  No holds the question for 24 hours rather than raising it at the next check.
• A confirmation step before an update starts, with the one thing that matters on
  it: this takes about two minutes, and the power must stay on.
• A full-screen progress ring while the update is written, replacing the thin bar.
  It runs 0-100% once across both the web UI and the firmware instead of
  restarting between them, so the number always means "how far through".
• Six new interface strings, translated into all eight languages.

Fixed

• The update screen described the download and the installation as two phases.
  They are one: the firmware is written to flash as it arrives off the network,
  so the screen now says "Installation" for the whole operation and stops
  implying a wait that does not exist.
• Two comments in the source still claimed over-the-air firmware update was
  impossible on this board. That stopped being true in v3.0.0, when the partition
  table gained its second app slot.

Known issues

• The update prompt appears only from the idle weigh screen. If the scale is in
  the middle of reading a tag it waits, which in practice means the prompt can
  arrive a few seconds after the check that found it.

Updating

Over the air from Settings > Update, or over USB with
bash scripts/flash.sh --fs. Both keep your WiFi credentials, TigerTag session
and calibration.

TigerScale V3 v3.0.0

v3.0.0

First public release of the V3 firmware, and the first in which over-the-air
updates actually work. Three separate faults were stopping them, each hidden
behind the previous one, and all three are fixed.

Important

This release changes the flash partition table, so it cannot be installed over
the air. Flash it once over USB — with the
web installer or
bash scripts/flash.sh --fs — and every update after this one can go over the air.
Your WiFi credentials, TigerTag session and calibration survive: NVS stays exactly
where it was, verified by reading it off a device before and after.

Fixed

Over-the-air updates, end to end. Previously impossible for three reasons:

• The update manifest pointed at the V2 repository, whose firmware would brick a
  V3 board. Different hardware; it should never have shared a channel.
• The partition table had one factory app partition and no OTA slot, so the
  ESP-IDF updater had nowhere to write and failed with free=0. There are now two
  4 MB slots in the 16 MB flash that was only half allocated.
• The download ran inside the async web server's thread, which starved the task
  watchdog and rebooted the board mid-update. It now runs on its own task.

8 MB of PSRAM that were never switched on. BOARD_HAS_PSRAM was missing from the
build, so the Arduino core never initialised it. Every heap_caps_malloc(SPIRAM)
quietly fell back to internal DRAM — including LVGL's 38 KB draw buffer — and the
whole device ran in roughly 300 KB while 8 MB sat idle. Minimum free heap across a
session went from 2 892 bytes to over 120 000. If you have seen unexplained
resets or SSL - Memory allocation failed, this is very likely why.

A boot-time diagnostic that scanned a dead bus. The I²C scan ran against a bus
that cannot work on this board, printing 124 error lines every boot to report
"0 devices". Pointed at the working bus it now finds six — and immediately revealed
two devices nobody had documented, at 0x51 and 0x6B.

Comments that contradicted the code, and 218 mojibake sequences that had eaten
every section marker and accent in the source.

Added

• Web installer at https://tigertag-project.github.io/Tiger-Scale-V3/ — flash a
  blank board from Chrome, Edge or Opera with no toolchain. Pick your NFC wiring
  first; installing the wrong transport gives a scale that detects no reader.
• Filesystem updates over the air. The web UI can now be updated alongside the
  firmware, filesystem first, as a single operation with one progress bar.
• Documentation: wiring diagram, pinout, cloud and privacy, troubleshooting, and
  a postmortem explaining why USB-connected NFC readers cannot work on this board.
• CI building all five environments with three consistency guards as real gates.

Known issues

• One binary is published, built for HSU. A unit wired for SPI or I²C that takes
  an over-the-air update loses its reader until reflashed over USB.
• Nothing tells you an update exists unless you open Settings → Update. There is
  no periodic check and no indicator on the main screen.
• readWeight() zeroes the weight after 600 ms of missed HX711 samples, which
  can show 0 g on a scale that is working.
• The local HTTP API is unauthenticated — anyone on your network can read state
  and trigger a tare.
• The SPI and I²C builds compile and are published, but only HSU has been verified on
  real hardware.

Updating

From any earlier firmware: USB only, because of the partition change.

bash scripts/flash.sh --fs

or use the web installer.

From v3.0.0 onwards: Settings → Update, over the air.

Enclosure (latest)

The printable enclosure for TigerScale V3, as a Bambu Studio project with the
plates already laid out. Open it in Bambu Studio or Orca Slicer; any slicer that
reads 3MF will open it too, though the plate arrangement is Bambu-specific.

This release is the permanent home of the latest enclosure. The download link
never changes, so anything pointing here always gets the current file:

https://github.com/TigerTag-Project/Tiger-Scale-V3/releases/download/enclosure/TigerScale-V3-enclosure.3mf

Parts

Part	What it is
base	Bottom shell, carries the load cell and the HX711
plateau	The platform the spool sits on
suporte	Load-cell support
ecran	Display bezel for the 3.5" touchscreen
tampa	Top cover
tampa rfid	Cover over the NFC reader bay
traseira	Back panel

The project also carries a leftover test body; it is not part of the enclosure and
does not need printing.

Revisions

• rev 1 — first published version, the one the reference unit was built from.

Notes

• The enclosure is versioned separately from the firmware: it does not have to
  match your firmware version, and it is not reattached to each firmware release.
• Wiring, the bill of materials and the antenna spacing the enclosure assumes are
  in docs/HARDWARE.md.