Note: forwarded message attached.
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
--- Begin Message ---Dear Joseph,1. What is CCID compliant reader mean? By the way, i am using ASEDrive IIIe serial reader (Athena's serial reader) where it is a smart reader. (i attached the specification of the reader, please refer.)2. For those command that is under the ISO7816 is actually command that deal with card. (Ex. Select File command, Read Binary command, Write Binary command and etc.) Is that right?3. When i'm not using the ISO7816 protocol commands, i only need to consider the serial timeout (for my case since i'm using serial reader). How about when i'm dealing with the ISO7816 protocol commands, do i need to consider the serial timeout other than considering the CWT and BWT (which is taken care by the reader)? How to calculate the serial timeout? (how long should i wait before i can start receving response from the reader for both command under and not under ISO7816).4. When i'm dealing command under ISO7816 (Read Binary command, 16 byte in length), where i first sent it from the MCU to the reader. Then will the reader actuallyCase 1: wait until it reacived all the 16 byte of command from MCU and then sent it to the card .Case 2: receive 1 byte from the MCU and transmit 1 byte to the card until it finish all 16 byte command.Which case is correct?5. After the card had receive the command that is under the ISO7816, the card will sent back response to the reader. Then will the reader actually,Case 1: Wait until it receive all the response packet from the card (where every byte of the response will be temporary stored in the reader's buffer) and then transmit it to the MCU.Case 2: receive 1 byte from the card and then transmit it to the MCU.Which case is correct?Regards,jackie wong
Joseph Antony <[EMAIL PROTECTED]> wrote:Hi,
On 5/9/06, jackie wong <[EMAIL PROTECTED]>wrote:
>
> Dear all,
>
> For my project, I am connecting my reader to a MCU which act as the host.
> The card uses T1 protocol and we need to consider the CWT and BWT. Therefore
> for this case, the CWT and BWT actually indicate the waiting time for the
> command to transfer from the MCUàCard or Reader àCard?
>
I believe if you are using a CCID compliant reader, then the CWT and
the BWT handling should be taken care of by the reader. What reader
are you using.
>
> Is it true that BWT and CWT for T=1 protocol and work waiting time for T=0
> protocol only in used for command that deal with the card? Other command
> that only deal with the reader like Open Reader command, Close Reader
> command and Set Reader Parameter command that only deal with the reader will
> not use the CWT and BWT?
>
Those that deal directly with the reader will come under usb
communication only and not under ISO7816.
>
> At the beginning, before my reader can deal with the card, I need to sent
> out a startup command to open the operation of the reader where it is done
> under default reader condition where it uses T=0 protocol. So, the command
> is only sent from the MCU à Reader where it does not deal with the card.
> Therefore, do we still need to consider the waiting time (CWT=WI*960 for T=0
> Protocol) when we are receiving the response for the startup command (that
> mean each byte of the response must be receive by MCU within the CWT), since
> the waiting time only in used when we deal with the card?
When not using iso 7816 protocol commands, all you need to worry is
the usb timeouts.
>
> Thanks for helping!
>
> reagrds,
>
> jackie wong
>
>
> ________________________________
> How low will we go? Check out Yahoo! Messenger's low PC-to-Phone call rates.
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.drizzle.com/mailman/listinfo/muscle
>
>
>
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less.
--- End Message ---
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
