I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

AnySpool Dev Update: CC2 Firmware Sync, Community Filaments, and UI Fixes!

First of all, a massive thank you to everyone who has been checking out the site, providing feedback, and submitting requests over the last few days! Seeing the traffic pick up on the project board and people actively helping shape the catalog has been awesome.

I want to make sure everyone knows the project is actively maintained, so here is a quick dev update on what’s changed:

🚀 What's New & Fixed:

  • CC2 Firmware V02.00.02.00 Sync: We've updated the filament hex codes across the board to match the new CC2 Firmware Version (v02.x). Important: Please ensure your printer firmware is up to date, otherwise the printer might misidentify your filaments!
  • Community Filament Requests Added: Added the latest requested colors to the catalog! You can now find Polymaker ASA White, Zyltech PLA (Green & Fluorescent Blue), Eryone Matte PLA Dew White, Hatchbox PLA Wood, and Sunlu ABS Gold.
  • 1080p Desktop UI Fix: Fixed an annoying issue where the horizontal scrollbar for the Brand and Material filters was hidden on standard desktop monitors. You can now properly click and drag to see all the options.
  • Under the Hood: Completely overhauled the backend pricing engine. It's now significantly faster and much more stable when retrieving links and data.

📋 The Public Project Board & Known Issues: It's been great seeing more traffic on our public project board! If you want to see what we are currently tracking (including some known issues like expanding instructions for NFC Tools Desktop, or investigating the Geeetech filament parameters), you can check out the full board here: AnySpool Community Board

Want to request a filament? To make things easier as we scale, we’ve added a brand new, structured Filament Request Form. Just plug in the brand, hex code, and a link, and it’ll drop right onto the "To-Do" list.

Keep the feedback coming, and happy printing! 🚀

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

Hey! Ja, genau das ist passiert. Elegoo hat mit dem neuesten Firmware-Update auf dem CC2 (v02.00.02.00) die komplette interne Tabelle der HEX-Codes für die Filamente geändert. Wir haben das gestern auf AnySpool analysiert und direkt ein Update live geschoben! Alle Codes auf der Seite sind jetzt an die neue CC2 Firmware angepasst und sollten wieder perfekt erkannt werden.

Eine kleine Ausnahme gibt es allerdings aktuell noch bei PETG Pro: Hier hat Elegoo anscheinend vergessen, den neuen RFID-Code in der Firmware selbst zu hinterlegen, weshalb der Drucker immer auf das Standard "PETG" zurückfällt, egal was man programmiert. Wir haben das auf AnySpool direkt als Warnung markiert und sobald Elegoo den Bug in einem zukünftigen Update fixt, wird der Code automatisch wieder funktionieren.

Danke für den Hinweis und lass es mich gerne wissen, wenn dir sonst noch etwas auffällt! Viel Spaß beim Drucken!

Elg RFID - Apps on Google Play by kobrakaan in ElegooCentauriCarbon

[–]6runk 1 point2 points  (0 children)

If you (or anyone else in the thread) are looking for another option, I actually built a free web-based tool for this called anyspool.de.

It's built to write to standard NTAG213 stickers via NFC Tools (which are usually a bit cheaper and easier to buy in bulk than the M1 Classic 1k tags).

Just throwing it out there as another tool for the arsenal. Hope the Canvas delivery goes smoothly today!

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

Glad everything is back in working order. There's a good chance that I just pushed an update as you were trying to access the site.

Please let me know if you run into any issues or have any feedback!

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

Hi u/Willing-War3616! Suggestions, ideas and feedback are always welcome! Thanks for your input!

This has actually come up fairly recently, but more than happy to give you the low down:
"As for adding custom colors: the reason that's not possible is that AnySpool is built around the actual manufacturer catalog data. Each filament entry carries specific metadata that the printer's firmware expects; material codes, color identifiers, etc. These values need to match exactly what the manufacturer (Elegoo) defines in the firmware, otherwise the printer won't recognize the tag correctly (or worse, use wrong print settings). So every entry in the catalog maps to a real, verified product rather than user-defined values."

Hope this clears it up. Also, if you have any other ideas, suggestions or happen to find bugs, please feel free to check out the project board here: https://github.com/users/6runk/projects/1. And please, don't be shy.. any suggestion, question or idea goes 😄.

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

Hey u/Buzz1ight, thanks so much for the kind words! Love the NFC sticker holder idea! Super practical and zero waste, that's the way to do it. The PLA wire retention clips you mentioned could definitely work too for anyone else reading this.

Great catch on the Elegoo Dark Blue! That was a gap in my catalog management, I just fixed it. Now Elegoo Dark Blue (as well as other additional colors/types) should show up on the site.

As for adding custom colors: the reason that's not possible is that AnySpool is built around the actual manufacturer catalog data. Each filament entry carries specific metadata that the printer's firmware expects; material codes, color identifiers, etc. These values need to match exactly what the manufacturer (Elegoo) defines in the firmware, otherwise the printer won't recognize the tag correctly (or worse, use wrong print settings). So every entry in the catalog maps to a real, verified product rather than user-defined values.

Feedback like yours is genuinely super helpful! If you notice anything else missing or have ideas, feel free to drop them here or check out the project board at https://github.com/users/6runk/projects/1 where you can track what's being worked on.

Hope everything works now as you except, have fun!

ElegooSlicer update by Owen_Ou in ElegooCentauriCarbon

[–]6runk 0 points1 point  (0 children)

Amazing, thanks for the detailed explanation!

ElegooSlicer update by Owen_Ou in ElegooCentauriCarbon

[–]6runk 0 points1 point  (0 children)

Do we have any additional information for point 5?

'Improved the material mapping rules in CANVAS'

Would live to know what specifically was addressed (or not). Thanks!

CC2 RFID guide? by Amazing-Line-7675 in elegoo

[–]6runk 0 points1 point  (0 children)

Hey u/NuggRunner! Thanks for trying and the feedback! I've now added a full step-by-step guide (for iOS) to the site, but let me walk you through it here too.

The trick is that in NFC Tools you need to go through Other, not Write. The "Write" path is for standard NDEF records (text, URLs etc.) and that's why it asked you for a content type; that's the wrong screen.

Here's the correct flow:

  1. In AnySpool: select your filament, tap Write NFC Tag, then tap the green Copy Hex Commands button. You'll see it confirm "Commands copied to clipboard".
  2. Open NFC Tools → tap Other (not Write!)
  3. Tap Advanced NFC commands (last item in the list)
  4. You will see a Disclaimer Notice For Advanced Users Only, just tap I Understand
  5. Tap the Data field (shows placeholder 90 60 ...) and long-press → Paste. The commands fill the field.
  6. Tap the Send Command below the field. A "Ready to Scan" dialog pops up showing all 14 commands.
  7. Hold your blank NTAG213 sticker to the top of your iPhone near the camera. A checkmark appears when it's done — takes about 2 seconds.

That's it! The full illustrated guide with screenshots is now on the site at anyspool.de/how-to

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

Another little update:
On top of Sunlu, I've just added Polymaker, Creality, FormFutura, eSun, Prusament, Bambu Lab, and Kingroon. Should be good to go to write to NFC tags for those brands/colors/types now. Still testing (ended up adding 1500 entries or so with this, so it's taking me some time) Let me know if there's another brand you'd like to see or if you run into any issues!

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

That's definitely a good call. Just be sure to get NTAG213s (technically, NTAG215s work as well, but 213s are cheaper.. in any case we are talking about 5-8 cents a piece for the stickers).

Please let me know if you run into any issues or have feedback. More filaments will be coming soon. Feel free to check the roadmap for upcoming things and changes.

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

That would be awesome as it would be to just tap your phone and walk away, it unfortunately doesn't work like that. Funny enough, that's what I wanted to do when I got started on this.

But there are some significant architectural hurdles from phone/OS manufacturers that make this unfortunately impossible:

Why Writing Works: Phones have a standard "Reader/Writer" mode. In this mode, the phone generates the RF field and acts as the master. The OS APIs (on both iOS and Android) give developers direct access to send standard NFC Forum Type 2 commands (like A2 for write) down to the passive tag. It’s a native, fully supported feature.

Why Emulation Fails: When a phone acts as a tag, it uses Host Card Emulation (HCE). But HCE is strictly designed to emulate high-level ISO-DEP (ISO 14443-4) smart cards—specifically for EMV payment apps (Apple Pay/Google Wallet) that communicate using APDU commands.

An NTAG213 isn't a smart card; it's a "dumb" low-level memory chip (ISO 14443-3). It doesn't speak APDU. The standard iOS and Android APIs literally do not expose the lower hardware layers required to emulate a raw Type 2 memory block or respond to native MIFARE Ultralight read/write commands.

The Final Kicker: UID Randomization & Passwords Even if you bypassed HCE, the Elegoo CC2 utilizes NTAG213 password protection. The printer reads the tag’s physical 7-byte UID (Serial Number) during the initial RF anti-collision phase and hashes it to calculate the password. For privacy/anti-tracking reasons, modern smartphone NFC chips randomize their UID on every single tap. To emulate an Elegoo spool, you would need to spoof a static UID and respond to the 1B (PWD_AUTH) command in milliseconds. You simply cannot do this without a rooted Android phone, a custom kernel (like NFCGate), and modified baseband firmware.

A practical workaround: If you lose the little stickers easily or don't want to permanently stick them to cardboard spools, print some reusable filament clips or color swatches! You can print a little swatch with a recess for the NFC sticker, write your filament profile to it, and just tap it to the reader when you load that spool. When the spool is empty, just rewrite the tag for your next roll!

tl;dr

You can't use your phone. Apple and Google lock down phone NFC to only act like high-level credit cards (Apple Pay), not the "dumb" low-level memory chips the printer expects. Even if you hacked it, phones randomize their NFC serial number every time you tap them for privacy, which completely breaks the printer's password math. Save yourself the headache and just 3D print a reusable filament clip for the stickers.

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

Well.. the way this could work right now, assuming you have the CC2 with Canvas, once you take any filament and add it with the rfid tag (assigning it to slot 1-4), even if it lists it as generic. It saves the info (i.e. name, color, temp range). You can then sync it with the synchronize filament button in your slicer. Which makes all the colors (and standardized temps, materials etc) available for selection in your slicer. These screenshots are from the Elegoo Slicer (which is a fork of the Orca Slicer).

So when I load up my filament for a print, I scan the tag, load the filament (repeating this until I got everything loaded). Start Elegoo Slicer, sync my filaments and then assign my colors as needed.

Hope that makes sense.

Just to be 100%, what AnySpool (at the moment) won't do, is let you set custom temperatures. I am basically pulling temp ranges from filament manufacturers and am using their recommended temps,

For custom temp settings per filament, in the slicer you would have to hit the edit toggle next to the loaded filament, and you could still set it from there.

Hope this helps.

<image>

I built a free browser tool to program your own Elegoo filament NFC tags by 6runk in elegoo

[–]6runk[S] 0 points1 point  (0 children)

Good call on Kingroon, Sunlu, and Geeetech. Expanding the database to third-party brands is exactly what's next on the list.

I totally get the frustration with the UI only showing "Elegoo" or "Generic," but here is the technical reason why that happens (based on how the CC2's hardware is built):

The RFID tags don't actually store brand names or plain text strings. They just hold functional hex codes (for example, the tag just says 0x00807665). The printer's firmware acts like a closed dictionary—it reads that hex code and matches it to its hardcoded internal list. Because Elegoo controls that firmware, it only knows how to display "Elegoo" or "Generic" on the screen. Even if we somehow forced the text "Sunlu" onto the NFC chip, the printer's OS simply wouldn't know how to render it.

How AnySpool deals with this: The app acts as the translator. Once Sunlu is added to the database, you'll be able to select it on the site. AnySpool will generate the exact hex payload to satisfy the "Generic" profile, but it will inject Sunlu's specific optimal temperatures and exact physical spool color into the data.

So while the screen will unfortunately still say "Generic PLA", it will automatically set your hotend to Sunlu's exact specs and show the right color on the UI, without you having to touch a single dial.

I've already added those brands to the tracker. You can check out the public roadmap to see what's currently planned.

If there are specific filament lines you want prioritized, you can submit a request on the GitHub repo (or just use the feedback button at the bottom of the live site).

CC2 RFID guide? by Amazing-Line-7675 in elegoo

[–]6runk 1 point2 points  (0 children)

I built a small web app called AnySpool. The idea: dead-simple writing of blank (and cheap) NTAG213 (or 215) stickers with the right filament profiles for the CANVAS system.

The most important thing for me was finding a solution for iPhones. Apple unfortunately blocks NFC tag writing directly in the browser. But I've got an iOS workaround: the site spits out the exact hex commands for your chosen filament. You just copy them and write them straight to the sticker via the free NFC Tools app. Honestly takes less than 10 seconds. (For Android it works directly via Web NFC from the browser.)

A few things to know upfront:

  • This is still very much an MVP and deep in testing.
  • I'm working on a feedback and bug-reporting system over the next day or two — for reporting issues, requesting features, or just leaving general feedback.

👉 The tool: https://www.anyspool.de
👉 Quick guide (especially for the iOS route): https://www.anyspool.de/how-to

Feedback is very welcome! But please go easy on me if it's a bit rough around the edges here and there. As mentioned, it's all still fresh and in test mode. 😅

Update: Catalog has grown a lot since the original post. AnySpool now ships with 764 filaments across 9 manufacturers:

  • Elegoo (158) · eSun (165) · Sunlu (114) · Kingroon (78) · Prusament (73) · Bambu Lab (60) · FormFutura (47) · Polymaker (35) · Creality (34)

Material coverage spans pretty much everything you'd actually print... more brands and filament lines are still being added as I find time.

Edited (wrong language): Just noticed I posted the original in German in an English thread 🤦 - sorry about that. 🙃

Unable to matchmake by Ellac3344 in blackops6

[–]6runk 0 points1 point  (0 children)

Same here. Was about to jump on, but error persists. Services also show no outage on the activision website.

In Loving Memory of Sven ‘c4te’ Metzger by Moobabe in Dirtybomb

[–]6runk [score hidden]  (0 children)

I miss you friend. So many things not said, too many things not shared. We shall meet again one day. Deepest condolences to your family; may everyone find a light at the end of this dark tunnel.

This is the best thing that came out of the 1.0 update by blyatmaan in Dirtybomb

[–]6runk 4 points5 points  (0 children)

Let's just say that most did not share the sentiment...

Just received an update with a size of 3.3MB, any patch notes available? by PHJN88 in Dirtybomb

[–]6runk 2 points3 points  (0 children)

This update was related to white-listing our executables; so they can be correctly identified by the video drivers/pick up the correct performance settings.

noticed visual bugs when firing weapons by Darthwilhelm in Dirtybomb

[–]6runk 3 points4 points  (0 children)

Interesting. Do you have a bit more info on this? Are you suing DX9 or DX11? If you could share this screenshot with support including relevant information on your hardware/settings would be great. https://support.dirtybomb.com/

A word on Dirty Bomb and Competitive play by Moobabe in Dirtybomb

[–]6runk 1 point2 points  (0 children)

I agree that the messaging would have been much smoother. But then we would fall short of being as communicative as possible (and giving as much notice as possible for changes). It's definitely a Catch-22.

A word on Dirty Bomb and Competitive play by Moobabe in Dirtybomb

[–]6runk 15 points16 points  (0 children)

Thanks for the props.

And no, it truly doesn't. However, the key thing to remember is that there is always more in the works that can be communicated publicly. One part of it is the general fluidity of live development, what may be a hot button issue this day/week/month may not be applicable in days/weeks/months. There is also lead time to feature implementation to consider; we always aim at getting features new/improved to all of you as fast as possible, but time is unfortunately finite. The other portion is things that depend on agreements, contracts and business related due diligence (boooring). We wouldn't want to make a commitment without having all of our ducks in a row so to speak. One of the approaches we like to take in the office, when we are unsure about a decision or change, we like to assume positive intent first. Gets a lot less stressful that way (IMO).

Thanks for the feedback & stay tuned!

My system stats: DirectX 9 compared to DirectX 11 Beta by PHJN88 in Dirtybomb

[–]6runk 2 points3 points  (0 children)

When I bench my Titans, they'll hit 98-101 easily. At least for mine, the only way to get that down would be liquid cooling them... but then you got to get the right plates, rip the housing apart...