ISO/IEC (E). PDF disclaimer. This PDF file may contain embedded typefaces. In accordance with Adobe’s licensing policy, this file. Reference number. ISO/IEC (E). Fourth edition. Permission can be requested from either ISO at the address below or ISO’s. During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. For example, the SAK byte will inform the .
|Published (Last):||11 June 2011|
|PDF File Size:||17.26 Mb|
|ePub File Size:||12.21 Mb|
|Price:||Free* [*Free Regsitration Required]|
Post as a guest Name. Point is your communication has to succed on all levels so don’t worry to try to communicate with card by not compatible protocol – if you by some miracle will not get error on CardProtocol level you will definitely get one on your application level and result will be same.
Probably the best course of action will be to implement a “pragmatic” approach: Sign up using Facebook. Will your reader software have 144443-4 support all generic Mifare Plus cards, or just the ones personalized for a specific application or service?
Should I just try some commands from Mifare Plus command set and check if I get correct replies? I think that the whole purpose of Lso is to provide a generic way to exchange is with different cards. I develop some software for a card reader and I need to identify which commands the card supports for example, if it supports commands in ISO structure or not. For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information.
So you know you will need to use different card driver.
Okay, I’ve come with my own answer. Or is there any smarter way to do it? Or other cards with different command sets i. If not, there will be errors on that level.
ISO/IEC – Wikipedia
But still, the ATS has some useful information. During the 14443–4 protocol some parameters are exchanged that you can use to determine the card’s capabilities. Complete communication stack will look like this: Sign up using Email and Password.
For example, Mifare Plus with its native command set. On top of it there are implemented interfaces of different kso and if both sides: I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization.
Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model. Keep in mind that your goal is to connect two applications, one in the card and one in io computer.
There is no smarter way. If you have two applications which wants to communicate try one and then try second.
Sign up or log in Sign up using Google.