Hi,
As Ludovic yet answered you can manage that sequence (ie card requests,
tag/chip enumeration, selection of one of them) yourself as long as some
API give you access to such functions; but for most of readers the PC/SC
driver is opaque to these operations -- in short PC/SC manages APDU
exchanges as per ISO 7816/14443-4 but hide details of protocol stack as
per ISO 7816/14443-3; or other way to explain the reader firmware
implements 14443-3 while the reader driver implements 14443-4 with PC/SC
syntax.
That said, some readers manufacturer provide proprietary API offering
direct access to the protocol - this includes (and is not limited to)
Integrated Engineering (SmartID), ID3 semiconductors (CL1356),
Pro-Active (SpringCard), certainly also OmniKey or DUALi that offers a
valuable SDK.
Last point, your sequence: "Select one of them and read it; Select
another and read it" is valid but do not expect to read several chips
simultaneously (it's certainly not required); indeed some several chips
are in the field the reader shall "select" one and "halt" the other
ones, from the chip point of view the "halt" is (more or less) a soft
reset (it will keep its UID but will lose its context) and thus it is
not possible to suspend and then resume the exchange of APDUs.
Sylvain.
Le 27/01/2011 10:26, Alexei Soloview a écrit :
Hello!
I have reader compliant to ISO 14443-3 and smartcards with support of
anticollision function.
The ISO 14443-3 specifies procedures to manage selection of the card for
further communication?
Can I via PCSC-Lite implement the following functionality:
1. Put on reader two smartcards.
2. Select one of them and read it
3. Select another and read it
?
Sincerelly, Alexei.
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
