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):||5 February 2014|
|PDF File Size:||14.2 Mb|
|ePub File Size:||7.72 Mb|
|Price:||Free* [*Free Regsitration Required]|
What is the recommended way to distinguish between them? Only way how to think about card and don’t get crazy is imagine it like it is full communication stack see OSI model.
smartcard – How do I distinguish different ISO cards? – Stack Overflow
Or is there any smarter way to do it? If you have two applications which wants to communicate try one and then try second.
Now how to do it: During the connection protocol some parameters are exchanged that you can use to determine the card’s capabilities. Sign up using Facebook.
ISO/IEC – Wikipedia
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. Or other cards with different command sets i. Sign up or log in Sign up using Google.
Sign up using Email and Password. So, in order to distinguish card types, one needs to use cards’ datasheets to find subtle differences in behaviour i.
But still, the ATS has some useful information. I think it’ll be enough to handle the personalized ones, plus new blank cards for personalization. So you know you will need to use different card driver. Alexandr Zarubkin 4 Use SAK only for non cards e. Keep in mind that your goal is to connect two applications, one in the card and one in your computer.
Complete communication stack will look like this: Will your reader software have to support all generic Mifare Plus cards, or just the ones personalized for a specific application or service?
Post as a guest Name. Email Required, but never shown. On top of it there are implemented interfaces of different cards and if both sides: ATS is also bad 144434 as different card vendor can set it differently.
For example, Mifare Plus with its native command set. I think that the whole purpose of ISO is to provide a generic 144443-4 to exchange information with different cards.