-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenTag #8
Comments
@spuder I don't think I've got that much to contribute to standardization discussions, but I'll think about if it makes sense to implement OpenTag support in nfc2klipper. If/when manufacturers start to support it, it would probably be good to automatically create manufacturers, filaments and spools in Spoolman from the info in the tags. Until they do, I don't really see the use case for OpenTag with nfc2klipper & spoolman. The info is already in spoolman as the users create it there first and the current format works well with that workflow. Are there other use cases I'm not thinking of? |
nfc2klipper would have to create the vendor if missing, then the filament if missing finally the spool if missing. The spool id from Spoolman will probably have to be handled by adding a new custom field in Spoolman. That field can contain the tags' serial number. The tag writing functions would have to update the spool in Spoolman with the new serial number after writing. |
Originally posted by @spuder in #3 (comment)
A few of us are working on a 3rd party RFID reader called openspool. It works with bambu printers. I'm glad to see someone is doing something similar with klipper
https://github.com/spuder/OpenSpool
There is a discord where several filament manufactures such as Polar Filament are working to standardize on an open format for RFID tags called OpenTag (Formerly called OpenRFID). Many other manufactures have expressed interest in adding tags.
I'd love to see nfc2klipper support the purposed standard.
https://github.com/Bambu-Research-Group/RFID-Tag-Guide/blob/main/OpenSourceRfid.md
Would you be interested in joining the standard discussions on discord?
The text was updated successfully, but these errors were encountered: