Donkie
Support for OpenPrintTag
Is your feature request related to a problem? Please describe. no problem
Describe the solution you'd like Prusa just announced OpenPrintTag an open nfc tag format for spools.
As it's an open standard, with some luck it'll get adopted by spool manufacturers, but we can also make our own.
Support for it in spoolman would be great, imo.
Describe alternatives you've considered .
Additional context I know this is REALLY early, I am just opening this to ping awareness, and track progress / interest really.
Thanks!
I'm also interested in this, it would have been fun to have some kind of automation with the identification of Filament, interesting to see how Prusa's hardware will work and if we who are not so super technical will be able to use this function
For DIY'ers I think using https://opentag3d.info/ and commercial off the shelf NTAG215 tags makes a lot more sense than the special Prusa tags. Its also an open standard, already used by other manufacturers and the Filaman project is open source to deal with reading/writing/weight updates. I put the same Filaman hardware in my filament dries and use them to read the tag and activate the filament.
For DIY'ers I think using https://opentag3d.info/ and commercial off the shelf NTAG215 tags makes a lot more sense than the special Prusa tags. Its also an open standard, already used by other manufacturers and the Filaman project is open source to deal with reading/writing/weight updates. I put the same Filaman hardware in my filament dries and use them to read the tag and activate the filament.
I disagree. While OpenPrintTag have not released the full hardware spec yet it is ISO/IEC 15693 which is 13.56 MHz just like the NTAG215. I'm not super familiar with the specifics of hardware RFID tags but it kinda looks like it's for an NTAG215.
Regardless. I'm seeing a lot of corporate backers for OpenTag3D but going to their websites they don't seem to be shipping products with it or even providing ready made profiles that an end user can write. Please correct me if I've missed something.
The filament order I placed today from Prusa already has the tags on it. Positron and Voron are already involved with Prusa tags.
+1 for OpenPrintTag support
I think you missed the part of "DIY'er" .. if the filament comes with a tag you don't want to write to it; you just want to scan it and store the UID in Spoolman (bonus points if there is ndef data with more data to also import)
I'm sure the Prusa tags have a generic NXP or similar chip, but the end product, will be a custom antenna and label - which will not be as readily available as f.ex. the ubiquitous Ø25mm NTAG215 labels, and I'll have a hard time believing Pusa will benefit from the same economies of scale, at least when it comes to selling tags to the public.
Hardware and the content of the tags are two different things. Can't one store the OpenPrintTag data in other tags?
I'll probably add support for OpenPrintTag to nfc2klipper shortly, making it able to add new spools to spoolman automatically. I think it should already be possible to connect spoolman spools to spools with OPT, but you'll have to add the spools manually in spoolman. I've obviously not tested it yet.
I mean, if spoolman is going to support rfid tags, might as well do both. No need to fight over which one is better. From what I gather, you can put openprinttag on any compatible tag, it just won't meet the location specifications for hardware systems that will implement integrated readers.
Diversity isn't a bad thing. And I think prusa mostly wants to fight the bambu lock-in.
@cnf it makes little sense for spoolman to have support for any rfid tags, except by having fields for the data in the tags. There are already good interfaces for other programs to read/write from/to spoolman.
Filaman and nfc2klipper currently extend spoolman spools with a field for the tags ID, that can be used with all readable tags, even without having any content in them (as long as the have unique IDs of course).
Automatically creating new filaments and spools in spoolman from the content requires reading it. That can be done with third party programs.
@beikeland
For DIY'ers I think using https://opentag3d.info/ and commercial off the shelf NTAG215 tags makes a lot more sense than the special Prusa tags.
I've added support in nfc2klipper for them. When it reads an OpenTag3D tag for the first time, it will create the vendor (unless there already is a matching one), filament (again, if there already isn't a matching one) and the spool in Spoolman.
If it was common with such tags, it might be a useful feature, but for DIY use (adding the tag & data yourself), I don't see the point if you are already using Spoolman. The "external source" feature adds the same generic data to Spoolman, and at least for me, that's where the data is needed. My printer & slicer gets the info about the spool & filament from Spoolman. I do use rfid tags to know what spool is loaded, but those only need to have a unique id-number (like NTAG215 tags already do), not a lot of data. Then nfc2klipper and spool2klipper fetches the rest of the data from Spoolman.
When I first looked at it it didn't seem possible to get the Spoolman ID from the NFC UID over the API; since then I've just decided to move the lot_nr data over to the comment field and stick the UID in lot_nr so I can filter api/v1/spool?lot_nr= 0123456789ABCD and some triggers to ensure uniqueness while waiting Spoolman to have a dedicated UID field or allow filtering on the extra.nfc_id.
(Previous workflow was an ESP32 reading off the barcode on the filament box and looking up the article_number to add the spool, print and encode the tag automagically, but relying on the UID alone is much simpler indeed.
I believe that the use of both OpenPrintTag and OpenTag3d should be considered, given both would be possibly used for filament management.
