These are the possible high level exception codes that can be thrown in a CardTerminalException

Namespace: CardWerk.SmartCard
Assembly: CardWerk.SmartCard (in CardWerk.SmartCard.dll)

Members
  Member name Description
CardCommunicationError An error occurred while communicating with the card. The card must be reset.
CardWithdrawn The card was unexpectedly removed from the card terminal. This exception only happens if there already was a connection to the card. It is not thrown when an attempt is made to power up a card for the very first time.
DriverError The lower layer driver returned an error code. This must only be used, if the drivers error code could not be mapped to some other, more meaningful CardTerminalExceptionCode.
DriverException An exception from a lower layer driver was caught and is propagated as the inner exception of this exception. This must only be used, if the caught exception could not be mapped to some other, more meaningful CardTerminalExceptionCode.
DriverIncompatible The lower layer driver returned some unexpected or unknown result, or some other unexpected driver behaviour occurred.
InvalidAPDU A command APDU or response APDU was invalid according to the requirements of the method that did raise this exception.
TerminalUnavailable This is to indicate that a reader got lost; most likely disconnected after it was already successfully added to the terminal slots that are tracked.
See Also