Acs Acr30 User manual

ACR30

Smart Card Reader/Writer

Reference Manual

Last modified : 12 March, 2002 – 2.06

ACR30 Reference Manual

Contents

INTRODUCTION ....................................................................................................................... 3

FEATURES .................................................................................................................................. 3

SUPPORTED CARD TYPES .................................................................................................... 3

A. MEMORY-BASED SMART CARDS (SYNCHRONOUS INTERFACE) (*)...................................... 3

B. MICROCONTROLLER-BASED SMART CARDS (ASYNCHRONOUS INTERFACE) ....................... 3

SMART CARD INTERFACE.................................................................................................... 4

A. SMART CARD POWER SUPPLY VCC (C1)............................................................................ 4

B. PROGRAMMING VOLTAGE VPP (C6)................................................................................... 4

C. CARD TYPE SELECTION ....................................................................................................... 4

D. INTERFACE FOR MICROCONTROLLER-BASED CARDS .......................................................... 4

E. CARD TEARING PROTECTION............................................................................................... 4

POWER SUPPLY........................................................................................................................ 4

STATUS LEDS................................................................................................................................4

SERIAL INTERFACE................................................................................................................4

A. COMMUNICATION PARAMETERS ......................................................................................... 4

1. Hardware Baud Rate...................................................................................................... 5

2. Software Baud Rate Selection ........................................................................................ 5

B. INTERFACE WIRING ............................................................................................................. 5

USB INTERFACE ....................................................................................................................... 6

A. COMMUNICATION PARAMETERS ......................................................................................... 6

COMMUNICATION PROTOCOL .......................................................................................... 7

1. Command........................................................................................................................ 7

a) Normal Command (Length < 255 bytes) ..................................................7

b) Extended Command..................................................................................7

2. Response ......................................................................................................................... 7

a) No transmission error with normal response (Length < 255 bytes) ..........7

b) No transmission error with extended response..........................................8

c) Transmission error ....................................................................................8

3. Reset Message ................................................................................................................ 9

4. Card Status Message ...................................................................................................... 9

B. TRANSMISSION PROTOCOL .................................................................................................. 9

COMMANDS ............................................................................................................................. 11

A. CONTROL COMMANDS ....................................................................................................... 11

1. GET_ACR_STAT .......................................................................................................... 11

2. SET_PROTOCOL......................................................................................................... 11

3. SELECT_CARD_TYPE ................................................................................................ 12

4. RESET...........................................................................................................................12

5. SET_NOTIFICATION .................................................................................................. 13

6. SET_OPTION ............................................................................................................... 13

B. CARD COMMANDS ............................................................................................................. 14

1. '104' - type non-reloadable Token Counter Cards (*)................................................. 14

a) RESET (*)...............................................................................................14

b) POWER_OFF (*)....................................................................................14

c) READ_DATA (*)...................................................................................14

d) WRITE_DATA (*) .................................................................................15

e) PRESENT_TRANSPORT_CODE (*)....................................................15

2. I2C-Bus cards (standard and extended addressing) (*).............................................. 16

a) RESET (*)...............................................................................................16

b) POWER_OFF (*)....................................................................................16

c) READ_DATA (*)...................................................................................16

d) WRITE_DATA (*) .................................................................................16

3. Siemens SLE 4432/4442 intelligent 256 Byte Memory Card (*) ................................. 18

a) RESET (*)...............................................................................................18

b) POWER_OFF (*)....................................................................................18

c) READ_DATA (*)...................................................................................18

d) WRITE_DATA (*) .................................................................................19

e) WRITE_PROTECTION (*)....................................................................19

f) PRESENT_CODE (only SLE 4442) (*) ................................................19

g) CHANGE_CODE (only SLE 4442) (*).................................................20

4. Siemens SLE 4418/4428 intelligent 1K Byte Memory Card (*) .................................. 21

a) RESET (*)...............................................................................................21

b) POWER_OFF (*)....................................................................................21

c) READ_DATA (*)...................................................................................21

ACR30 Reference Manual

d) WRITE_DATA (*) .................................................................................22

e) WRITE_PROTECTION (*)....................................................................22

f) PRESENT_CODE (only SLE 4428) (*) ................................................22

5. MCU-based Card ......................................................................................................... 24

a) RESET ....................................................................................................24

b) POWER_OFF .........................................................................................24

c) EXCHANGE_APDU..............................................................................24

d) EXCHANGE_T1_FRAME.....................................................................25

6. Security Application Module (SAM) (**)..................................................................... 26

a) ACTIVATE_SAM (**) ..........................................................................26

b) DEACTIVATE_SAM (**) .....................................................................26

c) EXCHANGE_SAM_APDU (**)............................................................26

d) EXCHANGE_SAM_T1_FRAME (**)...................................................27

APPENDIX A: SUPPORTED CARD TYPES......................................... 28

APPENDIX B: RESPONSE STATUS CODES ...................................... 29

APPENDIX C: TECHNICAL SPECIFICATIONS............................. 30

Note (*) – SAM Reader does not support for memory cards

Note (**) – SAM Reader only

ACR30 Reference Manual

INTRODUCTION

The ACS Smart Card Reader/Writer ACR30 is an interface for the communication between a computer (for example, a PC) and a smart card.

Different types of smart cards have different commands and different communication protocols. This prevents in most cases the direct

communication between a smart card and a computer. The ACR30 Reader/Writer establishes a uniform interface from the computer to the smart

card for a wide variety of cards. By taking care of the card specific particulars, it releases the computer software programmer of getting involved

with the technical details of the smart card operation, which are in many cases not relevant for the implementation of a smart card system.

The ACR30 Smart Card Reader/Writer is connected to the computer through a serial asynchronous interface (RS-232) or USB interface. The

reader accepts commands from the computer, carries out the specified function at the smart card and returns the requested data or status

information.

NOTE - Although the ACR30 is a true card reader/writer as it can read and write smart cards, the terms card reader or reader will be used

indifferently to refer to the ACR30, for the sake of readability and because these designations are commonly in use for this kind of devices.

FEATURES

• ISO7816-1/2/3 compatible smart card interface

• Supports CPU-based cards with T=0 and/or T=1 protocol

• (*) Supports commonly used memory cards (I2C, SLE4406, SLE4418/28, SLE4432/42)

• Support PPS (Protocol and Parameters Selection) with 9600 – 96000 bps in reading and writing smart cards

• RS-232 interface or USB interface to PC with simple command structure

• (**) Security application modules (SAM) inside the reader supporting CPU-based cards with T=0 and/or T=1 protocol (SAM Reader only)

Note (*) – SAM Reader does not support for memory cards

Note (**) – SAM Reader only

SUPPORTED CARD TYPES

The ACR30 can operate MCU card with T=0 and T=1 protocol. The table presented in Appendix A explains which card type selection value

must be specified for the various card types supported by the reader.

A. Memory-based smart cards (synchronous interface) (*)

• '104' type EEPROM non-reloadable token counter cards, including:

Gemplus GPM103

Siemens SLE 4406

• Cards following the I2C bus protocol (free memory cards) with memory capacity up to 16 Kbit and minimum 4 bytes page write capability,

including:

Atmel AT24C01/02/04/08/16

Gemplus GFM2K, GFM4K

SGS-Thomson ST14C02C,14C04C

• Siemens SLE4432/4442 intelligent 256 bytes EEPROM with write protect function:

SLE 4432, SLE 4442

• Siemens SLE 4418/4428 intelligent 1K bytes EEPROM with write-protect function:

SLE 4418, SLE 4428

Note (*) – SAM Reader does not support for memory-based smart card

B. Microcontroller-based smart cards (asynchronous interface)

The ACR30 supports EEPROM microcontroller-based cards with internal programming voltage (VPP) generation and the following

programming parameters transmitted in the ATR:

PI1 = 0 or 5

I = 25 or 50

The ACR30 performs the Protocol and Parameters Selection (PPS) procedure as specified in ISO7816-3:1997.

When the card ATR indicates the specific operation mode (TA2present; bit b5 of TA2must be 0) and that particular mode is not supported by the

ACR30, the reader will reset the card to set it to negotiable mode. If the card cannot be set to negotiable mode, the reader will reject the card.

ACR30 Reference Manual

When the card ATR indicates the negotiable mode (TA2not present) and communication parameters other than the default parameters, the

ACR30 will execute the PPS and try to use the communication parameters that the card suggested in its ATR. If the card does not accept the PPS,

the reader will use the default parameters (F=372, D=1).

For the meaning of the aforementioned parameters, please refer to ISO7816, part 3.

SMART CARD INTERFACE

The interface between the ACR30 and the inserted smart card follows the specifications of ISO7816-3 with certain restrictions or enhancements

to increase the practical functionality of the ACR30.

A. Smart Card Power Supply VCC (C1)

The current consumption of the inserted card must not be higher than 50mA.

B. Programming Voltage VPP (C6)

According to ISO 7816-3, the smart card contact C6 (VPP) supplies the programming voltage to the smart card. Since all common smart cards in

the market are EEPROM based and do not require the provision of an external programming voltage, the contact C6 (VPP) has been

implemented as a normal control signal in the ACR30. The electrical specifications of this contact are identical to those of the signal RST (at

contact C2).

C. Card Type Selection

The controlling PC has to always select the card type through the proper command sent to the ACR30 prior to activating the inserted card. This

includes both the memory cards and MCU-based cards.

For MCU-based cards the reader allows to select the preferred protocol, T=0 or T=1. However, this selection is only accepted and carried out by

the reader through the PPS when the card inserted in the reader supports both protocol types. Whenever an MCU-based card supports only one

protocol type, T=0 or T=1, the reader automatically uses that protocol type, regardless of the protocol type selected by the application.

D. Interface for Microcontroller-based Cards

For microcontroller-based smart cards only the contacts C1 (VCC), C2 (RST), C3 (CLK), C5 (GND) and C7 (I/O) are used. A frequency of

3.6864 / 4 MHz is applied to the CLK signal (C3).

E. Card Tearing Protection

The ACR30 provides a mechanism to protect the inserted card when it is suddenly withdrawn while it is powered up. The power supply to the

card and the signal lines between the ACR30 and the card are immediately deactivated when the card is being removed. As a general rule,

however, to avoid any electrical damage, a card should only be removed from the reader while it is powered down.

NOTE - The ACR30 does never by itself switch on the power supply to the inserted card. This must explicitly be done by the controlling

computer through the proper command sent to the reader.

POWER SUPPLY

The ACR30 requires a voltage of 5V DC, 100mA, regulated, power supply. The ACR30 gets the power supply from PC (through the cable

supplied along with each type of reader).

Status LEDs

Green LED on the front of the reader indicate the activation status of the smart card interface:

Green LED Indicates power supply to the smart card is switched on, i.e., the smart card is activated.

SERIAL INTERFACE

The ACR30 is connected to a computer through a serial asynchronous interface following the RS-232 standard.

A. Communication Parameters

The following communication parameters are used by the ACR30 and cannot be modified by the host computer:

Transmission protocol : serial asynchronous

Parity : none

Data Bits : 8

Stop Bits : 1

Handshake : through CTS

ACR30 Reference Manual

The ACR30 provides two means to select the transmission speed (baud rate) used by the reader in the normal operation, by hardware and/or by

software.

1. Hardware Baud Rate

The default hardware baud rate setting is 9600 bps.

2. Software Baud Rate Selection

The SET_PROTOCOL command allows setting the transmission speed (baud rate) and a delay time inserted between the bytes transmitted by the

reader to the PC.

Please note that the setting made with this command is volatile and will be lost when the reader is being reset or powered up next time.

B. Interface Wiring

For the communication between the ACR30 and a computer, five lines of the RS-232 interface are used: RxD, TxD, CTS, DTR and GND.

RS-232 Interface Wiring

Pin PC Cyber-

mouse

Function

2 RxD TxD Data transmitted from PC to ACR30.

3 TxD RxD Data transmitted from ACR30 to PC.

4 DTR RESET RESET input signal. Allows performing a hardware reset of the

reader module through the RS-232 interface.

Applying a logic '1' signal (negative voltage according to the

RS-232 convention) to this pin causes a hardware reset of the

ACR30.

5 GND GND Reference voltage level for power supply and serial interface.

8 CTS

BUSY CTS (Clear To Send) signal to the PC. Indicates to the PC

whether the ACR30 is ready to receive the next command.

A logic '0' signal (positive voltage according to the RS-232

convention) is applied to this pin while the ACR30 is executing

a command. Only when a '1' signal (negative voltage according

to the RS-232 convention) is present at this pin can the PC send

a command to the ACR30.

NOTE - Communication problems between the ACR30 and a PC can occur if a 25 pin to 9 pin RS-232 adapter or a cable is used in which not

all 9 signal lines are connected. Adapters supplied with computer mouse frequently have not all lines connected. For the correct operation of the

reader, use only a 9 pin to 25 pin adapter and a serial interface cable in which all 9 signal lines are connected!

NOTE - To prevent any radio interference between the ACR30 and other electrical and electronic equipment, do not use an RS-232 cable

longer than 3 meters!

ACR30 Reference Manual

USB INTERFACE

The ACR30 is connected to a computer through a USB following the USB standard.

A. Communication Parameters

The ACR30 is connected to a computer through USB as specified in the USB Specification 1.1. The ACR30 is working in low speed mode, i.e.

1.5 Mbps.

USB Interface Wiring

Pin Signal Function

1 VBUS +5V power supply for the reader

2 D- Differential signal transmits data between ACR30 and PC.

3 D+ Differential signal transmits data between ACR30 and PC.

4 GND Reference voltage level for power supply

NOTE - In order for the ACR30 functioning properly through USB interface, either ACS proprietary device drive or ACS PC/SC device driver

has to be installed. Please refer to the Device Driver Installation Guide for more detail.

ACR30 Reference Manual

COMMUNICATION PROTOCOL

In the normal operation, the ACR30 acts as a slave device with regard to the communication between a computer and the reader. The

communication is carried out in the form of successive command-response exchanges. The computer transmits a command to the reader and

receives a response from the reader after the command has been executed. A new command can be transmitted to the ACR30 only after the

response to the previous command has been received.

There are two cases where the reader transmits data without having received a command from the computer, namely, the Reset Message of the

reader and the Card Status Message.

1. Command

a) Normal Command (Length < 255 bytes)

A command consists of four protocol bytes and a variable number of data bytes and has the following structure:

byte 1 2 3 4 ... N+3

(0<N<255)

N+4

Header Instruction Data length = N Data Checksum

Header Always 01Hto indicate the start of a command.

Instruction The instruction code of the command to be carried out by the ACR30

Data Length Number of subsequent data bytes.(0 < N < 255)

Data Data contents of the command.

For a READ command, for example, the data bytes would specify the start address and the number of bytes to be read. For

a WRITE command, the data bytes would specify the start address and the data to be written to the card.

The data bytes can represent values to be written to a card and/or command parameters such as an address, a counter, etc.

Checksum The checksum is computed by XORing all command bytes including header, instruction, data length and all data bytes.

The following example shows the structure of a command with instruction code = 91Hand three data bytes with the values 11H, 22Hand 33H,

respectively:

byte 1 2 3 4 5 6 7

01 H91 H03

H11

H22

H33

H93 H

b) Extended Command

A command consists of six protocol bytes and a variable number of data bytes and has the following structure:

byte 1 2 3 4 5 6 ... N+5

(N>0)

N+6

Header Instruction Data Length = N Data Checksum

FFHData Length N

Header Always 01Hto indicate the start of a command.

Instruction The instruction code of the command to be carried out by the ACR30.

Data Length Number of subsequent data bytes, and is encoded in 3 bytes. The first byte is FFH. The second byte and the third byte

represent data length N.

Data Data contents of the command.

For a READ command, for example, the data bytes would specify the start address and the number of bytes to be read. For

a WRITE command, the data bytes would specify the start address and the data to be written to the card.

The data bytes can represent values to be written to a card and/or command parameters such as an address, a counter, etc.

Checksum The checksum is computed by XORing all command bytes including header, instruction, data length and all data bytes.

2. Response

The response from the ACR30 to any command depends on whether the command has been received by the reader without error (e.g., checksum

error).

a) No transmission error with normal response (Length < 255 bytes)

The response by the ACR30 to a correctly received command consists of three protocol bytes, two status bytes and a variable number of data

bytes and has the following structure:

ACR30 Reference Manual

byte 1 2 3 4 5 ... N+4

(0<N<255)

N+5

Header SW1 SW2 Data length = N Data Checksum

Header Always 01H to indicate the start of the response.

SW1 Indicates the command execution status:

90 H = command successfully executed

60 H = error in command data; command cannot be executed

67 H = error detected in command execution

FFH= status message initiated by the reader

SW2 Further qualification of the command execution status.

A table listing the possible values of the status bytes SW1 and SW2 and the corresponding meaning is given in Appendix

Data Length Number of subsequent data bytes (0 < N < 255)

Data Data contents of the command.

For a READ_DATA command, for example, the data bytes would contain the contents of the memory addresses read from

the card. The data bytes can represent values read from the card and/or status information.

Checksum The checksum is computed by XORing all response bytes including header, status bytes, data length and all data bytes.

The following example shows the structure of the response to a command which has successfully been executed and which returns three data

bytes with the values 11H, 22Hand 33H, respectively:

byte 1 2 3 4 5 6 7 8

01 H 90 H 00 H 03 H 11 H 22 H 33 H 92 H

b) No transmission error with extended response

The response by the ACR30 to a correctly received command consists of three protocol bytes, two status bytes and a variable number of data

bytes and has the following structure:

byte 1 2 3 4 5 6 7 ... N+6

(N>0)

N+7

Header SW1 SW2 Data length = N Data Checksum

FFHData Length N

Header Always 01Hto indicate the start of the response.

SW1 Indicates the command execution status:

90 H = command successfully executed

60 H = error in command data; command cannot be executed

67 H = error detected in command execution

FFH= status message initiated by the reader

SW2 Further qualification of the command execution status.

A table listing the possible values of the status bytes SW1 and SW2 and the corresponding meaning is given in Appendix

Data Length Number of subsequent data bytes, and is encoded in 3 bytes. The first byte is FFH. The second byte and the third byte

represent data length N.

Data Data contents of the command.

For a READ_DATA command, for example, the data bytes would contain the contents of the memory addresses read from

the card. The data bytes can represent values read from the card and/or status information.

Checksum The checksum is computed by XORing all response bytes including header, status bytes, data length and all data bytes.

c) Transmission error

If the receiving party of a command (i.e., the ACR30) or a response (i.e., the computer) detects an error in the data length or the checksum of a

command, it disregards the received data and sends a "NOT ACKNOWLEDGE" message to the transmitting party upon completion of the faulty

transmission. The "NOT ACKNOWLEDGE" message consists of two bytes:

byte 1 2

05H05 H

If the ACR30 responds with a 'NOT ACKNOWLEDGE' message to a command from the computer, the computer would normally transmit the

command again.

If the computer detects a transmission error in a response from the ACR30, it can send the 'NOT ACKNOWLEDGE' to the reader upon which

the reader will transmit the most recent response again.

ACR30 Reference Manual

3. Reset Message

A reset of the reader occurs automatically whenever the reader is being powered up. A reset can also be actuated through the RS-232/USB

interface.

In either case the reader transmits one time a Reset Message, which has the same structure as the normal response to a command and the

following contents:

byte 1 2 3 4 5 6

Header SW1 SW2 Data length Data Checksum

01 H FF H 00 H 01 H BAUD=12 H

BAUD Indicates the hardware baud rate setting (default baud rate), which is set to 9600 bps (this is only valid in the RS232 reader).

The reader does not expect an acknowledge signal from the computer. After transmitting the Reset Message the reader is waiting for the first

command from the computer.

4. Card Status Message

When a card is being inserted into the reader or an inserted card is being removed from the reader while the reader is idle, i.e., not executing a

command, the reader transmits a Card Status Message to notify the host computer of the change in the card insertion status.

In a system where these unsolicited messages from the reader to the computer are not desired, they can be disabled with the

SET_NOTIFICATION command. Please note that the setting made with this command is volatile and will be lost with the next reader reset or

power up. By default, the Card Status Message will be transmitted by the reader after a reset.

The Card Status Messages have the following structure and contents:

Card Status Message for Card Insertion

byte 1 2 3 4 5

Header SW1 SW2 Data length Checksum

01 H FF H 01 H 00 H FF

Card Status Message for Card Removal

byte 1 2 3 4 5

Header SW1 SW2 Data length Checksum

01 H FF H 02 H 00 H FC

A card status message is transmitted only once for every card insertion or removal event. The reader does not expect an acknowledge signal from

the computer. After transmitting a status message, the reader waits for the next command from the computer.

NOTE - If the card is being removed from the reader while a card command is being executed, the reader will transmit a normal response to

the computer with the response status bytes indicating the card removal during command execution (see Appendix B: Response Status Codes).

B. Transmission Protocol

The start of a command (to the reader) or a response (from the reader, including the Reset Message and Card Status Messages) is indicated by the

respective party through the transmission of the single byte Start-of-Text (STX) character with the value 02H.

The end of a command or response is indicated through the single byte End-of-Text (ETX) character with the value 03H.

Within the command and response transmission only ASCII characters representing the hexadecimal (hex) digits 0...F are used. Each byte of a

command or response is splitted into its upper and lower halfbyte (nibble). For each halfbyte is transmitted the ASCII character representing the

respective hex digit value. For example, to transmit the data byte 3AH, two bytes are actually sent on the interface, namely, 33H(ASCII code for

'3') followed by 41H(ASCII code for 'A'):

Data byte value 3AH

Transmitted values 33 H = '3' 41H= 'A'

The following example shows the transmission of a command with instruction code A2Hand one data byte with the value 3DH. The command

has the following structure:

byte 1 2 3 4 5

Header Instruction Data length Data Checksum

01HA2H01H3DH9FH

This command is transmitted on the serial interface in 12 bytes as follows:

Other manuals for ACR30

Table of contents

ACS ACR30 User manual

Popular Card Reader manuals by other brands