Releases: TigerTag-Project/TigerSpool-RFID
Releases · TigerTag-Project/TigerSpool-RFID
Release list
v1.48.1
v1.48.0
Fixed
- The device connects to the nearest Wi-Fi access point, not the first one
it hears. On a home network with several access points under one name, it
could stay attached to a distant one for good - through reboots - and show a
weak signal while a TigerScale beside it showed full bars. On the bench it
went from -79 dBm to -46 dBm, and from one ping in five lost to none.
Changed
- The three icons at the top of the home screen line up. Account, Wi-Fi
and settings are now the same height, on the same line, evenly spaced. The
Wi-Fi wave was a third smaller than the other two, and the gaps between them
were uneven. - Tapping the account or the Wi-Fi icon opens Settings, like the gear.
Only the gear used to answer. - The Wi-Fi icon shows full signal from -60 dBm, then two arcs from -70
and one from -80, the thresholds phones use. Full used to need -40 or
better, so an excellent connection showed two arcs of three. The setup
page's network list uses the same thresholds.
v1.47.1
Fixed
- A printer that moves to a new address is followed. When your TigerTag
account gives a printer a new IP, the device now uses it. Before, the address
the device already held always won, so a printer that had moved stayed
unreachable on TigerSpool for good while Tiger Studio talked to it fine - an
AD5X did exactly that. - Printers no longer swap addresses and access codes when the account
changes. Adding or removing a printer in Tiger Studio shifted the device's
list by one, and every printer after that point took its neighbour's address
and code - a Bambu Lab would then refuse the connection with an access-code
error, and a switched-on printer could turn into a different one. Each
printer is now recognised by its serial number, wherever it sits in the list,
and keeps its own settings and its own switch. - Two entries in the account for the same printer become one. An old entry
left at a previous address beside the current one used to show up as two
printers, the stale one first. The newer entry wins. - A printer whose settings change reconnects straight away, instead of
staying on the old connection until something else closed it.
Changed
- A printer newly added to your account arrives on the device switched off, as
on first start, so it does not take room you did not choose to give it.
v1.47.0
Added
- The device tells you how full it is before a printer stops connecting.
Settings > Printers, and the Choose printers step at first start, show a
Load bar with a percentage. Some printers take far more of the device's
memory than others - a Bambu Lab or an Anycubic about ten times an Elegoo,
a FlashForge or a Creality - so the limit is not a number of printers but how
much they load it. A printer that would not fit is refused when you switch it
on: the switch does not move, the bar turns red and says Not enough room.
Switching a printer off always works. How it is counted, and every
measurement behind it, is in docs/CONNECTION-BUDGET.md.
Changed
- The documentation says what the firmware does today. Elegoo and Anycubic
were still listed as not implemented; both read slots on real printers. A
Bambu Lab in cloud mode is now documented as read only, which it is. The
firmware README no longer says nothing builds, and the web installer's page
shows the manifest that is actually published.
v1.46.0
Changed
- More printers can be connected at once if you use Bambu Lab in cloud
mode. Every Bambu Lab printer on your account now shares a single secure
connection instead of opening one each. That connection is the most
memory-hungry thing the device does, so a second cloud printer now costs
about a fifteenth of what it did, and there is room left for others. Each
printer still shows its own spools and its own status; only the connection
behind them is shared. Printers in LAN mode are unaffected. - The device answers faster on the network: Wi-Fi power saving is off, which is
the right choice for something that runs from a wall socket.
Fixed
- The device can no longer freeze indefinitely. If its main program ever
stops responding, it now restarts itself within thirty seconds and records
why, instead of staying frozen until it is unplugged.
v1.45.2
Fixed
- The printer you are looking at connects more readily. The device was
reserving far more memory than a Bambu Lab printer on screen actually uses -
its large receive buffer lives in a separate memory the device has plenty of,
and was being counted against the scarce one. Connection limits now use costs
measured on real hardware, printer by printer.
v1.45.1
Changed
- The update page is one page now. Opening it shows your version and a
turning ring while it checks - the check has always started on arrival, but
nothing on screen said so. If something newer exists, the offer appears under
your version instead of replacing it: the download icon, the version you are
on and the one on offer, and Install at the bottom of the screen. - The card is labelled "Version" rather than "Installed version".
v1.45.0
Changed
- Bambu Lab printers are no longer polled. The device asked each one for
its entire state every eight seconds - about 81 KB a minute for two printers,
for spools that had not moved. The printer already announces a spool change
by itself, in a message five times smaller, so the device now listens instead
of asking. Your screen updates exactly as before; the Wi-Fi does a fraction
of the work. - The update page puts Install at the bottom of the screen, and scrollbars
appear only when a page actually has more to show.
Fixed
- Printer connections stopped dropping and reconnecting. A four-second
read limit added to keep the interface responsive was also cutting off large
replies, so the device hung up on printers that were answering perfectly -
once every poll. Four minutes of observation now show none at all, where
there were four reconnections in two and a half minutes before.
v1.44.0
Fixed
- The device reconnects to Wi-Fi on its own. It asked for the network once
at startup and never again - so if the association failed at boot, or the
access point dropped the device later, it stayed there with a lit screen,
every printer red and no way back short of unplugging it. It now asks again
after fifteen seconds and keeps asking. This is the most important fix in the
release.
Changed
- The NFC Tester is a proper bench instrument. It reads in English whatever
language the device is set to - it is used beside a reader log and a
datasheet, and two people comparing the same spool have to see the same
words. One field per row, in a fixed order, with a colour bar across the top
and the raw chip pages behind a HEX Code button. - A spool's readings stay on screen when you take the spool away. They used
to clear the moment the chip left the reader, which is exactly when you want
to read them. - The colour bar shows two or three colours for bicolour and tricolour
spools, decided by the spool's aspect rather than by the colour bytes -
black is a real colour, and an unused slot is stored the same way. - Colours are shown in hex, the main one with its alpha byte, and the page dump
is set in a monospace face so it lines up in columns. - Titles, menu rows and printer names are heavier and larger, and buttons
are set in a size meant to be read at arm's length. - The NFC Tester has an icon of its own instead of borrowing the Display row's
sun, and the sun now matches the other icons' size.
v1.43.1
Fixed
- The device can check for updates and refresh its account again while
several printers are connected. With six connections open there was still
memory free, but not in one continuous piece large enough for a secure
connection - so the update screen showed "manifest HTTP -1" and the printer
list stopped refreshing. The background connections now step aside for the
second or two a secure request needs, and come straight back. The printer you
are looking at keeps its connection throughout.