Not all NFC215 tags get recognized by Amiibomb #8
Comments
|
Hi, |
|
Huuum, so if I understand well AmiiBomb say "Waiting for NTAG..." and nothing change? (That's what you said on GBATemp ^^). |
|
ERROR: Your Tag it's probably not a NTAG215! |
|
Can you try to flash the AmiiBombuino inside the v0.2 and tell me if you have anything different? |
|
When I use v0.2, I have this exception: |
|
Ok so, the problem is when I calculate Long UID based on the short UID readed from the tag... |
|
I do not have android phone. Do you want DumpInfo.ino.hex dump ? Thanks |
|
You have to run the Serial Windows inside Arduino IDE, and setting it at 9600 baud to get the informations, after that, you have to scan a NTAG and the informations appear ;)! |
|
Output: |
|
Do you have enough information with my Arduino IDE output ? Thanks. |
|
That looks like most of the ntag215's I've seen. Can you post the same dumpinfo output for one of the working Ntag215's to compare the results of the UID short to long conversion for a working UID vs a non-working UID? |
|
Sorry but I do not have functional NTAG. I have no android for flash a NTAG215. Maybe @PeggerWed can post us a functional NTAG ? |
|
My non working Empty NFC card on AmiiBomb info (there working fine on Tagmo Android) NFC Taginfo (empty card that Amiibomb does not recognize) IC Type: Memory Data: IC detailed information: Version information: Configuration information: Originality check: Technologies supported: Android technology information Detailed protocol information: Memory content: |
|
The old ntags that did work on Amiibomb have he same config, (except there already witten to) If you wish i can ship 2 of those non working on Amiibomb/working on Android Tagmo NFC cards to you. |
|
Ok, i found an old NTAG 512 from my first batch that worked on Amiibomb that was still empty: Amiibomb info:Wachten op NTAG... Gevonden! Short UID is: 04037EAA064F81 "D:\AmiboDumps\Smash 4[SSB4] Donkey Kong.bin" is gepatched. Amiibo is klaar! Veel plezier! NXP Taginfo: (after the card was written) IC Type: Memory Size: IC detailed information: Version information: Configuration information: Originality check: FULL SCAN: Android technology information Detailed protocol information: Memory content: |
|
The problem is when I calculate the Long UID, with certains of them (who can't be write on the NTAG - Read only). I have to see to fix it, but I just don't have time, I just need many UID of NTAG who's not working with AmiiBomb, to test if the calculation will be good! Please be patient. Thanks |
|
Hi, |
|
AcK77, Like told, i'm willing to ship a few not working NTAG cards to you, i live in Belgium and shipping to France isn't a problem Or i can at least read 20+ Long UID's from my batch and post in here. If i'm not wrong i take the following numbers/letters to get the Long UID: Memory content: Seems the Long UID = 04037EF1AA064F8162 Memory content: and short UID is 04037EAA064F81 |
|
LongUID (Empty cards) (for short UID just remove the bold stuff) LongUID (Written Cards) So i noticed, all cards that don't work on Amiibomb have Those cards that did work on Amiibomb have I know those numbers different for alot of cards, but It's a tip maybe :) |
|
Here's how tagmo is overcoming the problem.. scan the entire "raw" or "long" uid, then trim out the checksum bytes from "slot 3" to derive the "actual" or "short" uid. Or the checksum could be calculated (somehow) to go the other direction and generate the long uid from the short uid. Notice how it skips "pages0_1[3]" to generate the correct "short" uid from the first two pages. the long uid then is just the raw first two pages read it looks like.. not sure how to fix this in code, but the problem appears easy to overcome. TagUtil.java Card UID: 04 51 3D BA E8 4C 81 |
|
Well, let's hope AcK77 can do something with all this info :) Im willing to test a new Alpha release to see if the cards get working. |
|
Hi, |
|
Would like to know also. Any news on progress about this problem would be great :) |
|
Has the project died? |
|
I hope not, but no response and no update :/ |
|
Hey, project isn't dead, I'm using it successfully still. The code issue with long to short uid is documented in this thread. Take a stab at forking the code, modify your fork based on the notes here, then compile using visual studio 2017 community edition. Not super hard and you'll learn the fundamentals of software development and simultaneously be giving back to the community! |
|
@peacepinguin: For all others who can't wait until I update AmiiBomb, Right now I don't have time to work on it! So be patient. Your NTAG works, it's just an error inside the UID calculation, I make AmiiBomb open source for get other people fix possible error or add functionality, but all I have it's people who claim there is a mistake "here" or "here"! So if you can't wait the fix, do it yourself :)! Nothing mad here, anyone can understand I'm just busy. |
|
@AcK77 I'm not mad or anything, i was just wondering :) As always, real life stuff is more important then anything else, so take your time. I hope i wasn't one of the people who claimed about mistakes here or there (except for this issue i started) but i think i provided helpfull info for it also. @peacepenguin Maybe i do hope you could share your working version, so i can try out my ntags with it and can get started to have some fun with them. With Kind Regards, |
|
@urherenow Also same goes for phone, but it's easier, i can at least download them on my phone without having to get the sd out That's why i bought the hardware, cheap and no messing around, i bought a few new round flexible tags, those work fine, but i really like to use the rest (60+) of the 100 cards i bought (i used the other +/-40 on my phone and tagmo, a few on the 3ds with the hombrew app) |
|
Hmmm i got a new batch of ntag 215 cards in from china. |
|
Anyone having any luck compiling the Amiibomb Solution in Visual Studio 2017 Community? "Build" -> "Rebuild Solution" results in errors related to serialportstream.. then, updating package 'serialportstream' allows it to compile... Then "Build" -> "Rebuild Solution" compiles successfully with no errors or warnings. Finding the app in the BIN folder of the source code repo, launching Amiibomb.exe immediatly results in: I'll keep going and try to get all these instructions into the Wiki once I get it all working.. |
|
Edit: doesn't look like the rfid library update helps this issue.. try if you're feeling lucky... Anyone want to try the new build with the new MFRC522 library fixes applied that "should" fix this problem? |
|
@peacepenguin |
|
@kokkie20 at least we know the problem isn't solved by simply updating the rfid library. I've got a dev environment setup now, so I'll look into changing how the short - long uid conversion occurs, as was discussed earlier in this thread. |
|
@peacepenguin ok good luck on that, i just got arrived this morning a other rfid scanner (PN532) so will be working on that part seeing how it works and such 👍 Edit: |
|
@kokkie20 i just read some of the old posts that indicate you had already re-compiled using the new library awhile back, and then @Daisayah mentioned that things are good now! So i think i re-did the same thing that you did a month ago. @kokkie20, are your current problematic NTAG's having a different problem than what you helped @Daisayah awhile back with, by updating the mfrc522 library? The issue you're describing sounds a little different, so I want to make sure the UID calculation was found to be a problem, and was already solved by updating the library, so we can close down this issue at last! Then open a new one for any other types of NTAG read problems. now i'm going to order PN532 too, i'm reading that it can do "card emulation", perhaps we can use an arduino+PN532 as the figurine itself! fun stuff to look into with that board! |
|
@peacepenguin Haven't looked into card emulation, first want to get it to write amiibo's correctly combined with amiibomb before i will even look into the emulation haha 🤣 Edit; |
|
Hello, Does someone can test that release please ? If you get better with it, i'll then publish updated source code |
|
Note that the hex file for Uno and Nano are identical(same md5sum). |
|
@olijouve it now detects the bad cards... Well detect... Well probably a bug on my end or something cause now it won't detect any of the cards lol. |
|
Well progress so far on the PN532;
Todo;
DO NOTE: |
|
Will take the time haha :) |
|
I screwed up with RST and SS pin number for Uno and Nano, my board is a Mega so different pins and i forgot to adapt pinout for other board before the builds -_- Can you retry with this new release ? |
|
No luck i get the message "Wating for Ntag" thank you voor your try. |
|
Arghh, don't understand why what did work for me doesn't work for others. |
|
@rlvbrussel what issue are you facing? All ntags not readable nor writable? Some ntags work, others don't? @olijouve what is unique about your build 0.4? I think the UID issue is fixed with new mfrc522 library, so we should open up another thread to track any non-UID related problems. |
|
@peacepenguin no nothing new now i just saw you released a fix last week... |
|
@peacepenguin What do you mean with "I think the UID issue is fixed with new mfrc522 library, so we should open up another thread to track any non-UID related problems." @olijouve |
|
Alpha 2 ist finally working for me on UNO. NFC Stickers are recognised. Pre made NFC Cards are beeing dumped. Only Empty NFC Cards are not recognised. Keep up the good work |
|
Finnaly good news on its way!!! |
|
@kokkie20 can you post a link to your code for your pn532 - amiibomb progress? I have my dev environment setup to mess with this stuff again! Maybe make a github repo for it so we can test it and eventually make a pull request into the main repo? I have many NFC tags and there are some that absolutely are not able to be read by the MFRC522. In all cases though the PN532 is able to read any tag I've thrown at it. So I think there are some newer NTAG cards coming out that the MFRC522 isn't going to deal with. For example, most Android phones contain the PN532 chip, all the issues reported here indicate that Tagmo, the Android alternative to amiibomb, works just fine with these troublesome NTAG215's. Perhaps the code is all fine at this point, and these new ntags simply can't be read with the MFRC522? Another piece to the puzzle, I recently purchased the PowerSaves Portal and PowerTag chip. Using their software, you can scan a real amiibo and clone it to the PowerTag chip. The PowerTag chip is essentially a re-writable NTAG215. Which is really cool in its own right.. But anyway, the MFRC522 does not see it in any fashion at all. No indication in any application used with MFRC522, including amiibombuino. So again, here's another example of a particular "type" of NTAG215, the powertag, that can be read perfectly by real nintdo hardware, android phones, and the pn532 without issue. Everything that i own, that can read an RFID tag, is able to see the PowerTag EXCEPT the MFRC522. We should pursue testing and integrating @kokkie20 's code so people have an alternative option RFID board to use with amiibomb that is 100% reliable! |
|
@peacepenguin Like i said, i will see what i can do, maybe i will make for now a private github (New account, where only you and me know the link to untill we know for sure everything is working as it should be, before we even going release it to the public) you can hit me up with a email if you want just my nick and then gmail after it ;) well i guess you know what i mean with that 😃 |
|
@peacepenguin @kokkie20 any updates? :) |
|
I have sended all my code to peace so he/she can work further on it. |
|
Any Updates? I just put together my amiibomb and get that same error. EDIT: I also have some UIDs for you. Read with the program "GoToTags". The first two also just stoped working with amiibomb. I dont get the error anymore but it does not do anything instead. It's just like the tags are dead. But on my normal nfc reader they work just fine. |
|
I ordered more Tags, now with the longer UID but the amiibomb doesnt read them at all. my normal nfc reader detects them right away, so they work, but the amiibomb doesnt react at all. I have these sticker tags. Can someone help? I have 10 and not one works. |
|
Seriously, just use thenaya on the 3DS. Works perfectly without hassle, and this repository hasn't even been touched in like 8 months. (and that was just a license thing. It's been a YEAR since any actual code was committed). |
I have bought a few new NTAG215 tags, same as the previous ones but not the same store
Amiibomb doesn't recognize the tags, so i tested them on my Android phone that has Tagmo installed (Samsung phone) Tagmo recognizes the NFC NTag215 and writes the amiibo bin perfectly, my N3DS does recognize the tag, so the NTAG215 cards do work perfectly fine.
I checked the info with NFC taginfo from NXP and there identical as the first batch of cards, same info, same stuff, the first batch, Amiibomb could write perfectly fine and it recognized a written card and was able to dump it fine, but this second batch of 10 Amiibomb does not recognize a NFC card while trying to write a bin to it
The text was updated successfully, but these errors were encountered: