I didn't think there was a conflict at all between N and CWT/BWT. N is how
long the reader waits before sending the next byte. CWT is how long it
waits before giving up on receiving the next byte. BWT is how long it waits
before giving up on receiving the next block.
Also, I'm not getting the
: "Jim Rees" <[EMAIL PROTECTED]>
To: "Smart Muscleheads" <[EMAIL PROTECTED]>
Sent: Friday, June 29, 2001 1:47 PM
Subject: Re: MUSCLE Error using an IBM MFC in GemPlus readers.
> The Gemplus reader shouldn't wimp out just because BWT is "reserved."
The MFC docs claim it to be ISO 7816 compliant. Is there anyone who has
has success reading IBM MFC cards with a GemPlus reader?
Rich
On Fri, 29 Jun 2001, Peter Tomlinson wrote:
> >From ISO 7816-3:1997, ATR looks like:
>
> 3B Direct data convention
> EF TB1, TC1, TD1 present, 15 historical byte
Mahlzeit
On Fri, Jun 29, 2001 at 08:47:57AM -0400, Jim Rees wrote:
> The Gemplus reader shouldn't wimp out just because BWT is "reserved." My
> Todos driver does its best to talk to the card and uses defaults when the
> protocol parameters don't make sense. There are an amazing number of cards
The Gemplus reader shouldn't wimp out just because BWT is "reserved." My
Todos driver does its best to talk to the card and uses defaults when the
protocol parameters don't make sense. There are an amazing number of cards
out there that aren't strictly 7816 compliant.
Besides, isn't BWT given b
>From ISO 7816-3:1997, ATR looks like:
3B Direct data convention
EF TB1, TC1, TD1 present, 15 historical bytes
00 TB1 Vpp not used
FF TC1 Min delay between character transmissions is default value (11 etu
for T=1)
81 TD1 T=1 protocol only, TD2 is present
31 TD2 TB3 and TC3 present
FF TB3 BWI for
>From ISO 7816-3:1997, ATR looks like:
3B Direct data convention
EF TB1, TC1, TD1 present, 15 historical bytes
00 TB1 Vpp not used
FF TC1 Min delay between character transmissions is default value (11 etu
for T=1)
81 TD1 T=1 protocol only, TD2 is present
31 TD2 TB3 and TC3 present
FF TB3 BWI for
