Forum › MIFARE SDK › Classic Card returning bytes instead of tag lost on read operation. › Reply To: Classic Card returning bytes instead of tag lost on read operation.
Hi Matthew,
The MIFARE Classic is ISO14443-3 (part 3!) compliant. In part 3 there is no mechanism for error handling, e.g. if you make an authentication with the wrong key, the tag goes into an error state and stops communication. Take in mind, for ISO14443-4 (part 4!) you have an error handling.
A “tag lost” is detected if a command fails. How this is handled, is defined in the middleware (the software inside of Android, between NFC library and NFC driver). As part 3-device have no error handling, therefore I assume a tag lost is handled in the same way and no response is generated.
The TapLinx team
The MIFARE Classic is ISO14443-3 (part 3!) compliant. In part 3 there is no mechanism for error handling, e.g. if you make an authentication with the wrong key, the tag goes into an error state and stops communication. Take in mind, for ISO14443-4 (part 4!) you have an error handling.
A “tag lost” is detected if a command fails. How this is handled, is defined in the middleware (the software inside of Android, between NFC library and NFC driver). As part 3-device have no error handling, therefore I assume a tag lost is handled in the same way and no response is generated.
The TapLinx team
+ 0
|
- 0