AMS bricks gen2 tags

[Aptimex]

The Readme currently states that "Gen 2", aka CUID tags, "Work" for cloning. However, it seems the AMS (at least the AMS Lite on the latest firmware) tries to write invalid data to Block 0 to prevent the use of those tags, rendering them unusable in the process. Others have mentioned this as well #1

The Readme really needs to be updated with this caveat to prevent users from permanently bricking their Gen2 tags.

[capull0]

You can recover this tags with a PM3.
Or you pay much more per tag where you can change only one time the UID.
fun fact: the AMS will only brick RFID tags after reading the tag and recognize it as bambu spool tag :-)

After a while i came to the result, that cloning the RFID chips will help you with only some filaments, where the print profiles are near the same to Bambu filaments.
I found a reliable and similar way to tell the AMS which filament will be loaded.
https://github.com/capull0/BambuAMSCtrl
This is running on a raspberry pi with an external barcode reader and is working with any spools i have.
I can create my custom filament profile in Bambu Studio which will get a unique ID and with this tool you create a QR code just with this ID and the color.
Before you put a spool in the AMS, scan the QR code and and the tool will automatically select the correct filament to the empty AMS tray starting from left.
I'm working currently on a RFID variant, 2x PN532 connected to an ESP32

[Aptimex]

Care to share the command to unbrick them? I was able to recover a blank/new one that I let the AMS Lite try to read (hf mf wrbl --force --blk 0 -k FFFFFFFFFFFF -d 0102030404080400000000000000BEAF), but the same command failed to recover one that I cloned before letting the AMS read it. Even after replacing the key value with the correct one from the clone.

Yeah the one-time change tags should work fine, but the Readme REALLY needs to specify that.

Neat project.

[wzqvip]

Seems we should use FUID/UFUID, these tags only allow to change once or lock uid (forever).

[thekakester]

I'm fine with updating the Readme. It already said "gen 2" tags worked when I joined, and I didn't know what someone did to get them working. I had the same thing where the gen2 tags would be "bricked", but I was able to unbrick them with some command that I'll try looking up.

[thekakester]

Here's the guide I followed to unbrick: https://stackoverflow.com/a/65522498

[wzqvip]

Is this machine specific? I get cuid work well on p1s. When I use this tag on x1c, it bricks.

I assume x1c and a1/a1mini had extra controllers(arm,esp32) to perform this task. P1 use the motion controller to operate the machine and the screen.

edit： my fault. P1 can also brick tags. Seems there are multiple kinds of cuid tag. One of them works, one will get bricked.

[arnoliudaxia]

Is this machine specific? I get cuid work well on p1s. When I use this tag on x1c, it bricks.

I assume x1c and a1/a1mini had extra controllers(arm,esp32) to perform this task. P1 use the motion controller to operate the machine and the screen.

I meet with exactly the same situation with you.

[Aptimex]

Here's the guide I followed to unbrick: https://stackoverflow.com/a/65522498

I was following that too, turns out I was just using the wrong key. Using the correct key dumped from the tag that was the source of the clone I was able to unbrick it. Thanks.

Interesting that the cuid tags work on some machines and not others. I only have a A1 with AMS Lite so I can't confirm behavior for any other setups.

[MR-Ostrich13]

You can recover this tags with a PM3.
Or you pay much more per tag where you can change only one time the UID.
fun fact: the AMS will only brick RFID tags after reading the tag and recognize it as bambu spool tag :-)

After a while i came to the result, that cloning the RFID chips will help you with only some filaments, where the print profiles are near the same to Bambu filaments.
I found a reliable and similar way to tell the AMS which filament will be loaded.
https://github.com/capull0/BambuAMSCtrl
This is running on a raspberry pi with an external barcode reader and is working with any spools i have.
I can create my custom filament profile in Bambu Studio which will get a unique ID and with this tool you create a QR code just with this ID and the color.
Before you put a spool in the AMS, scan the QR code and and the tool will automatically select the correct filament to the empty AMS tray starting from left.
I'm working currently on a RFID variant, 2x PN532 connected to an ESP32

Can you give me more information. It sound very interesting

[MR-Ostrich13]

hello... now i am also an that point. my gen 2 chip was bricked by the AMS... all tehse commands down't work. even everone uses FFFFFFFFFFFF as Key... but also the read Keys after and before cloning doesn'T work... has anyone an sollution?

And additional to that is it possible to lock a gen2 afterwards. if not it dosn't make sense to go on with that