|
|
@@ -28,6 +28,12 @@ All notable changes to Bambuddy will be documented in this file.
|
|
|
- **On the Printers page:** while the Cam Wall is showing, the selector sizes the tiles: S fits up to five per row on a wide screen, M four (as before, and still the default), L two, and XL one tile across the full width. Tiles keep their 16:9 shape.
|
|
|
- **Remembered on its own:** the Cam Wall keeps its own size, so changing it leaves the card size alone, and the other way round.
|
|
|
- **On `/camwall`:** the standalone page uses the size last picked on the Printers page, and a kiosk URL can set it with `size=s`, `m`, `l` or `xl`.
|
|
|
+- **Spoolman mode uses Spoolman 0.27's native tags (#3168, requested and contributed by @Niko11111 in #3252)** — Spoolman 0.27 links NFC tags to spools itself: a spool can hold several tags, and Spoolman makes sure no two spools share one. Bambuddy kept its single tag per spool in its own `extra.tag` field, so neither side saw the other's links, a Bambu spool could hold only one of its identifiers, and every SpoolBuddy scan loaded the whole inventory.
|
|
|
+ - **Faster scans:** on Spoolman 0.27 or later, a scan asks Spoolman for the tag directly instead of loading every spool (17 ms instead of 88 ms on a 278-spool install). The old lookup is kept as a fallback for spools linked before.
|
|
|
+ - **Tags collect themselves:** a spool found by a scan or an AMS read gets what was read added to its tags. A Bambu spool collects its tray UUID and the chip UID of each side over time. The AMS also finds a spool linked by its chip alone.
|
|
|
+ - **Linking adds instead of replacing:** linking, unlinking, **Clear RFID Tag** and writing a tag with SpoolBuddy keep Spoolman's tags in step. A tag another active spool holds is refused as before. A tag still held by an archived spool, which is used up or replaced, moves to the active one.
|
|
|
+ - **Copying existing tags:** when Spoolman supports native tags, **Settings → Filament** shows a **Spoolman native tags** section. **Check tags** shows what would be copied and any conflicts, and **Copy tags** copies the tags. Archived spools and AMS slot IDs are left out, and a tag another active spool holds is reported, never moved.
|
|
|
+ - **Nothing lost on older versions:** `extra.tag` is still written everywhere, so readers that only know it and a downgrade to an older Spoolman lose nothing. Older Spoolman versions behave as before.
|
|
|
|
|
|
### Changed
|
|
|
|
|
|
@@ -56,6 +62,9 @@ All notable changes to Bambuddy will be documented in this file.
|
|
|
- **Idle printers:** the printer keeps reporting the last print's mapping after it ends, so it is used only during a print.
|
|
|
- **Shutting Bambuddy down logged an error with a traceback when nothing was wrong (#3243, reported by @Thomansky)** — Stopping Bambuddy cancels the printer updates still waiting to be handled, and each cancelled one was logged as `ERROR ... Exception in scheduled callback` with a traceback, as the last line before the restart. In a log or a support bundle it looked like a crash. A cancelled update now ends quietly; one that actually fails is still logged as an error.
|
|
|
- **A print started from the printer's screen took about six seconds longer to archive (#3009, reported by @bdwilson)** — A job started on the printer's own screen reports its file's full name, extension included (`Part.3mf`), where a job Bambuddy sends reports the bare name. Bambuddy added the extensions to it anyway and asked the printer for `Part.3mf.gcode.3mf` and `Part.3mf.3mf` first, six connections that could not succeed, before trying the real file. The check that reattaches a running print after a Bambuddy restart compared against the same doubled name, so it could not find such a print. When the printer reports the same full name as both the job and its file, that name is now taken as the file itself: it is the only name tried, and the restart check also matches that exact file. Prints Bambuddy dispatches are looked up as before.
|
|
|
+- **AMS Filament Backup showed "?" on the P1S, P1P, A1 and A1 Mini (#3259, reported by @HopNotch)** — These printers never send the `cfg` field Bambuddy read the setting from; they carry it in `home_flag` bit 10, where Bambu Studio reads it for every printer. Bambuddy now falls back to that bit, so the badge shows the printer's real setting and the prefer-lowest-remaining gate follows it. Before 1.2.5.6 the badge seemed to work on these printers only because it read Bambuddy's own print command echoed back, which always said off (#3040).
|
|
|
+- **Statistics counted a multi-material print written from spools as one material (#3262, reported by @ojimpo)** — A print's materials are stored comma-joined, as `PLA, PLA-S` from the sliced file but as `PLA Basic,PLA` once they are taken from the spools that fed it. The Statistics page split on comma plus space only, so those prints showed as one `PLA Basic,PLA` row in the material weight, print count, time and success-rate charts, and the Archives material filter offered the joined string as a material of its own and missed those prints when filtering by `PLA`. Both now split on the comma alone, as the statistics API already did, so existing archives are counted under each of their materials.
|
|
|
+- **A printing queue job showed the slot AMS Filament Backup had switched away from as empty** — When a spool ran out mid-print and the printer carried on from the backup spool, the job's card in the queue still named the original slot, now marked **Empty**, as if the print had a problem. The card now shows the backup spool the printer is using. It follows the printer's own record of the trays the print has drawn from, including a backup that ran out in turn. A switch between two slots the job uses is a normal colour change and is not taken for a backup. Queued jobs still warn about an empty slot as before.
|
|
|
|
|
|
### Security
|
|
|
|
maziggy