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):||7 May 2017|
|PDF File Size:||1.54 Mb|
|ePub File Size:||6.23 Mb|
|Price:||Free* [*Free Regsitration Required]|
Or is there any smarter way to do it? Keep in mind that your goal is to connect two applications, one in the card and one in your computer. Okay, 14443- come with my own answer.
Sign up using Facebook. Or other cards with different command sets i. For example, Mifare Plus with its native command set. I think that the whole purpose of ISO is to provide a generic way to exchange information with different cards.
smartcard – How do I distinguish different ISO cards? – Stack Overflow
Sign up using Email and Password. I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization.
For example, if you have an NFC-enabled Android phone around, you can install an app to quickly see that kind of information. If not, there will be errors on that level. Should I just try some commands from Mifare Plus command set and check if I get correct replies? How do I distinguish different ISO cards? 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.
On top of it there are implemented interfaces of different cards and if both sides: During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities.
So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i.
So you know you will need to use different card driver.
Probably the best course of action will be to implement a “pragmatic” approach: Sign up or log in Sign up using Google. There is no smarter way. ATS is also bad practice as different card vendor can set it differently.
Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model.