Remaining Weight Is All You Need: Stateful RFID Tags for the U1

:white_check_mark: I have searched this category and verified this feature request does NOT already exist.

on

1. Feature Summary

Store nominal weight on RFID tags and write back remaining filament weight after each print

2. Why this feature is needed

The U1 reads material, color and temperatures from Snapmaker RFID spools, but it has no idea how much filament is left on a spool. Once a spool has been partially used, there is no way to know if it will last for the next print, short of weighing it by hand and subtracting the empty spool weight.

Some scenarios where it matters:

  • Starting a long multi-color print and having one toolhead run out halfway through, wasting time and filament.
  • Swapping spools between storage and the printer: once a spool is unloaded, any knowledge of its usage is lost.
  • Owners of more than one U1 moving spools between machines.

3. Expected outcome

  1. Nominal weight on the tag: each spool tag stores the spool’s net filament weight (e.g. 500 g / 1000 g), written at production.
  2. Remaining weight written back: after each print, the U1 subtracts the filament actually used by that toolhead (based on extruded length, so cancelled or failed prints are also counted correctly) and writes the updated remaining weight to the tag. The value lives on the spool itself, so it stays correct after unloading, storage, or moving to another U1.
  3. Pre-print check: before starting a job, the printer compares the slicer’s estimated usage per toolhead with the remaining weight on each loaded spool and warns if one won’t be enough. Asks for a second spool to use or does the switch automagically if 2 spools of the same color are detected.
  4. Display: remaining weight shown on the touchscreen and in Fluidd next to each filament channel.

Affected Products

Snapmaker U1 Firmware

@Master_Plo
Hi, do you intend to submit it as an Innovation Fund project?

@Zoe_M This is a feature request, not a project offering!

1 Like

You should take a look at Spoolman, which is available in the Paxx12 firmware ecosystem. Spoolman maintains a database of (tagged) spools and how much filament is left on each.

That will be my fault for flagging it late last night as I read it as such

@Zoe_M I mean I could do a project offering, but that would mean reading the tag of the spool, which means finding the keys A and B and looking at how to write the weight on the spool on the free sectors. I’m not sure that snapmaker would appreciate that. If I obtain permission I’m in.

@CrazyIvan I saw the extended firmware feature, but that would mean running a spoolman server. My idea would be a huge help for not really technical people that use snapmaker spools. If a tag standard will ever be reached, this feature is easily ported to all polymaker spools because they are the ones writing the tag (I know that for a fact).

1 Like

You could say that for a lot of features – where do you draw the line? I wouldn’t rate it as an essential, and if anyone were that bothered there’s plenty of help available to run customisations.

I am very much in the camp of Snapmaker providing only the basic functionality, and leaving the community free to add optional bells and whistles.

I don’t know the ins and outs, but I think this server still runs on the U1? Spoolman is not the only solution either, IIRC.

Yeah this is more a nice to have. I was proposing because it does not require huge changes in the code, thus easy and cost effective to implement. I would try to do it myself but the code for reading the tag is not open source, or at least I did not found it on github.
Do you think I should try to apply for the Innovation Fund?
Thx

It’s hard to see a case for it when a solution already exists.

This would be a really useful feature, especially for people managing multiple printers and filament spools. Automatically tracking remaining weight would prevent failed prints and save a lot of wasted material. I particularly like the idea of keeping usage data on the RFID tag itself, so it stays accurate even when spools are unloaded, stored, or moved between machines. It could also be helpful when packing and moving a 3D printing setup, as you wouldn’t lose track of how much filament is left in each spool. Hopefully Snapmaker considers adding this to a future U1 firmware update!

1 Like

Spoolman does this and will provide a warning if there is not enough filament to complete job. The data is stored in a database (which runs on a separate server). The RFID on the spool points to the database record. So nothing is really stored on the RFID.

1 Like

I query how feasible it is to write to a spool tag in-situ. It requires more energy transfer than simply reading. The Spoolman approach of recording the tag’s serial number in a database and associating that with a record of filament type/colour/usage seems more practical.

Can you even write/rewrite the amount of weight to a tag? (genuine question)

Edit: Also would SM only implement this for their filaments if possible since the only other brand on the U1 is polymaker (so not supporting say Sunlu, BL etc etc)

I don’t see why not, they’re not special tags so far as I know so they have a read-only ID and general-purpose writeable storage, which comes over as a burst when the tag receives the RF trigger. The RF has to provide all the energy the tag needs to send the response.

The difference between the tags different manufacturers use is their hardware protocols, and then they might have different specifications on the data layout. Paxx has fixed that by supporting most (if not all) the read protocols and data formatting.

Thats my issue, the manufacturers can’t agree on a standard for the tags, let alone whats written too them

I bought and write my own tags to the openspool format to use with my U1

3 Likes

I investigated a bit how the tags work. They are Mifare Classic 1K
The tags are compose of sectors which are dived into blocks, with the help from Claude I and multiple spools I found this:

Sector 0: block 0 is the UID and manufacturer data. Block 1 is the brand (ASCII, 16 bytes) and block 2 is the maker.

  • Sector 1:
    • Block 4 holds, in order: version, main type, sub type and tray (2 bytes each, low byte first), then colour count, alpha and multi-colour mode (1 byte each).
    • Block 5 holds up to five 3-byte colours, written high byte first.
    • Block 6 holds the SKU (4 bytes, low byte first).
  • Sector 2:
    • Block 8 holds diameter (×100), weight in grams and length in metres.
    • Block 9 holds drying temp, drying time, max nozzle, min nozzle, bed type, bed temp, first-layer temp and other-layer temp, all 2 bytes each.
    • Block 10 holds the date as text (“YYYYMMDD”) and the signing key version.
  • Sectors 3–4: a copy of the sector 0–1 data, shifted by 13 bytes, with the version and main type set to 0. The printer doesn’t read it, but the signature covers it.
  • Sectors 5–9: empty.
  • Sectors 10–15: a 256-byte RSA-2048 signature (PKCS#1 v1.5 with SHA-256). It’s stored in the first three blocks of each sector, ending in block 60.

Each sector on the last block has a standard format keyA||ACL||keyB. The ACLs govern what operations are permitted (read, write, transfer…). Snapmaker uses 2 safeguards: firstly the sectors are only readable, but keyB can write the ACL so we could make the sectors writable. The second, and major one, is that Snapmaker uses a RSA PKCS#1 for integrity checks, thus writing on the tag would invalidate the integrity and the printer would refuse the tag. This means that if they want to maintain this digital cert on the tag (I would really like to know the technical reason why a tag for a spool needs this elaborate stuff) the spools will never be officially writable.

The only solution I see would be to comment out the check on the firmware and add the feature to check the weight on the start of each print. At this point I would probably investigate how to port this idea into Paxx’s extended firmware, and do a pull request there (or the preferred method for submitting code idk).

Thx to all for the interest

Note: To read tags I used a proxmark3

1 Like

And how many people are going to use only Snapmaker filament anyway?

2 Likes

10 posts were split to a new topic: U1 Filament RFID Tags & Custom Spool Holder Discussion

@Master_Plo Couldn’t this be solved by Snapmaker adopting OpenPrintTag or OpenTag3D? The former definitely supports writing remaining filament weight to tags, and I think the latter does too. Both are FOSS, so they would be free for Snapmaker to implement.

I ran into the same issue while developing a spool tracker.

I like the idea of storing the remaining weight directly on the spool—especially when moving it between printers. But while writing to the original tags is restricted, perhaps the tag could simply be used to identify the spool, with the remaining weight stored separately and linked to its UID?

That way, when you put the spool back on the printer, even on a different toolhead, it could automatically retrieve the saved balance. You wouldn’t have to find the spool in a list and enter its remaining weight again every time you swap colours.

Of course, several printers would need access to a shared database, so this wouldn’t fully replace your approach. Keeping the balance on the tag itself has the clear advantage of travelling with the spool without depending on a server. But as an interim solution without rewriting tags, UID-based identification seems useful to me.

The main question is whether the stock firmware exposes a stable UID for each individual spool when it’s moved between toolheads. Has anyone already tested this with original Snapmaker spools?

1 Like