MAX66000K-000AA+ Datasheet MAX66000K-000AA+ | P13-P15

MAX66000

ISO/IEC 14443 Type B-Compliant

64-Bit UID

______________________________________________________________________________________ 13

larger than 1, each slave in the field selects its own

4-bit random number, R, in the range of 1 to N. A slave

that happens to choose R = 1 responds to the

REQB/WUPB request. The larger N is the lower the

probability of colliding response frames; however, if N

is 16 and there is only a single slave in the field, it can

take up to 15 SLOT-MARKER commands to get a

response. The method to identify all slaves in the field

relying solely on the random number R and the

REQB/WUPB command is called the “probabilistic

approach.” For mode information about the anticollision

process, see the

Anticollision Examples

section.

SLOT-MARKER Command

Instead of relying on the fact that a participating slave

chooses a new random number for every REQB/WUPB

command, in the “time-slot approach” the master calls

the slaves by their random number R using the SLOT-

MARKER command. Before this can be done, the mas-

ter must have issued the REQB/WUPB command with a

number of slots (N) value greater than 1. The master

can send up to (N - 1) SLOT-MARKER commands.

Figure 19 shows the format of the SLOT-MARKER

request frame. The AFI field is not needed since the

slaves have already been preselected through the pre-

ceding REQB/WUPB request. The response to the

SLOT-MARKER command is called ATQB. See the

ATQB Response

section for details.

The bits marked as “nnnn” specify the slot number as

defined in the Table 3. Any sequence of the permissible

slot numbers is permitted.

ATQB Response

The response for both the REQB/WUPB and the SLOT-

MARKER command is called ATQB, which stands for

“answer to request, Type B.” Figure 20 shows the for-

mat of the ATQB response. The PUPI field (pseudo-

unique identifier) is used by the master to address a

slave for transitioning to the ACTIVE or HALT state. The

data reported as PUPI is the least significant 4 bytes of

the 64-bit UID. The application data field reports user-

defined data that is relevant for distinguishing otherwise

equal slaves in the RF field. The application data field is

factory programmed to reflect the most significant 4

bytes of the 64-bit UID. This allows the master to obtain

the full 64-bit UID in the first response from the slave.

However, this field may be factory-programmed to a

customer-specific value.

The protocol info field provides the master with admin-

istrative information, such as data rate, frame size,

ISO/IEC 14443-4 compliance, frame waiting time, and

whether the slave supports CID and NAD in the

ISO/IEC 14443-4 block transmission protocol. Figure 21

shows where this information is located in the protocol

info field and what the values are.

COMMANDSOF CRC EOF

nnnn0101b (2 BYTES)

Figure 19. SLOT-MARKER Request Frame

INDICATORSOF CRC EOF

50h

APPLICATION DATA

(4 BYTES) (2 BYTES)

PROTOCOL INFO

(3 BYTES)

PUPI

(4 BYTES)

Figure 20. ATQB Response Frame

BIT 8 BIT 7 BIT 6 BIT 5 SLOT NUMBER

0 0 0 1 2

0 0 1 0 3

0 0 1 1 4

… … … … …

1 1 1 0 15

1 1 1 1 16

Table 3. Slot Numbering

MAX66000

ISO/IEC 14443 Type B-Compliant

64-Bit UID

14 ______________________________________________________________________________________

The bit-rate capability of the MAX66000 ranges from

105.9kbps to 847.5kbps in both directions (request and

response); request and response bit rate need not be

the same. The maximum frame size (upper nibble of the

2nd byte) of any request/response specifies 24 bytes.

The largest frame that occurs with the MAX66000 is 19

bytes (Get System Information response). The protocol

type (lower nibble of the 2nd byte) specifies that the

MAX66000 supports the ISO/IEC 14443-4 block trans-

mission protocol. The FWI code 0110b specifies a

frame waiting time of 19.3ms. Note that a slave may

respond long before the maximum frame waiting time is

expired. The ADC code 00b specifies that the

MAX66000 uses proprietary coding for the application

data field. The FO code 01b implies that the MAX66000

supports CID, but does not support the NAD field in the

ISO/IEC 14443-4 block transmission protocol.

HLTB Command

The HLTB command is the only network function com-

mand to silence a slave by parking it in the HALT state.

If, based on the ATQB response, the master does not

want to further communicate with the slave, the master

issues the HLTB command. Figures 22 and 23 show the

format of the HLTB request frame and the correspond-

ing response frame. The data to be used in the PUPI

field must match the PUPI information that the slave has

transmitted in the ATQB response. While in the HALT

state, the slave only responds to the WUPB request.

ATTRIB Command

The ATTRIB command is the only way to select a slave

and make it process commands that are transmitted

according to the ISO/IEC 14443 block transmission pro-

tocol. If, based on the ATQB response, the master

wants to communicate with the slave, the master must

put the slave into the ACTIVE state using the slave

selection command ATTRIB. The normal way for the

master to move a slave out of the ACTIVE state is by

sending a DESELECT command, which uses an

S-block to convey a network function command.

Figure 24 shows the format of the ATTRIB request

frame. The data to be used in the PUPI field must

match the PUPI information that the slave has transmit-

ted in the ATQB response. Param 1 tells the slave how

much time the master needs to switch from transmit to

receive (TR0), how much time the master needs to syn-

chronize to the slave’s subcarrier (TR1), and whether

the master is capable of receiving response frames

without SOF and/or EOF.

The MAX66000 ignores the data of Param 1. To ease

requirements for ISO/IEC 14443 Type B readers, the

MAX66000 has TR0 and TR1 fixed at 128/fs (151µs; fs

is the subcarrier frequency of 847.5kHz) and always

begins and ends its responses with SOF and EOF,

respectively.

1ST BYTE 2ND BYTE

3RD BYTE,

UPPER NIBBLE

3RD BYTE,

BIT 4, BIT 3

3RD BYTE,

BIT 2, BIT 1

BIT RATE CAPABILITY MAXIMUM FRAME SIZE, PROTOCOL TYPE FWI ADC FO

77h 11h 0110b 00b 01b

Figure 21. Protocol Info Field Details

COMMANDSOF CRC EOF

1Dh (2 BYTES)

PUPI

(4 BYTES)

PARAM 1

(1 BYTE)

PARAM 2

(1 BYTE)

PARAM 3

01h

PARAM 4

(1 BYTE)

HLINF

(≥ 0 BYTES)

Figure 24. ATTRIB Request Frame

COMMANDSOF CRC EOF

50h (2 BYTES)

PUPI

(4 BYTES)

Figure 22. HLTB Request Frame

INDICATORSOF CRC EOF

00h (2 BYTES)

Figure 23. HLTB Response Frame

MAX66000

ISO/IEC 14443 Type B-Compliant

64-Bit UID

______________________________________________________________________________________ 15

Param 2 informs the slave about the data rate that shall

be used for communication in the ACTIVE state and the

maximum frame size that the master can receive.

Figure 25 shows the bit assignments for the Param 2

byte. The MAX66000 supports the data rates of

105.9kbps (code 00b), 211.9kbps (code 01b),

423.75kbps (code 10b), and 847.5kbps (code 11b).

The master can choose different data rates for request

and response. Since it does not support chaining, the

MAX66000 ignores the frame size capability and

assumes that the master can receive frames as large

as specified in the ATQB response.

The lower nibble of Param 3 is used to confirm the pro-

tocol type as specified in the lower nibble of the second

byte of the ATQB protocol info. Since ISO/IEC 14443-3

sets the upper nibble of Param 3 to 0000b, the Param 3

value to be used for the MAX66000 in the ATTRIB

request is 01h.

Param 4 assigns the slave the CID number that is used

with the block transmission protocol to address one of

several slaves in the ACTIVE state. Figure 26 shows the

Param 4 bit assignments. Since the MAX66000 sup-

ports the CID field, the master can assign any number

in the range from 0 to 14. According to ISO/IEC 14443-

3, code 15 is reserved.

The ATTRIB request frame contains one optional field,

called higher layer information (HLINF). This field can

be used to include data as in the information field of the

ISO/IEC 14443 Type B block transmission protocol (see

Figure 10). If such data is present and the slave sup-

ports the HLINF field, then the slave processes the

HLINF data and returns the result in its response to the

ATTRIB request. Typically, the ATTRIB request is trans-

mitted without HLINF field. The only HLINF data that the

MAX66000 accepts and processes is the Get UID com-

mand, code 30h.

If the ATTRIB request has a matching PUPI and a valid

CRC, the slave transmits an ATTRIB response frame, as

shown in Figure 27. The upper nibble of the indicator,

also referred to as MBLI, is 0000b, telling that the slave

does not provide any information on its internal input

buffer size; the lower nibble returns the card identifier

value that the master has just assigned to the slave.

The HL response field is optional. There are three

cases to be distinguished:

a) If there was no HLINF field in the ATTRIB request,

then there is no HL response field in the response.

b) If there was a Get UID command code (30h) in the

HLINF field of the ATTRIB request, then the HL

response field is identical to the Get UID response

information field (i.e., 00h followed by the 8-byte UID).

c) If the code in the HLINF field of the ATTRIB request

was different from 30h, then the response frame does

not contain an HL response field.

DESELECT Command

The DESELECT command is used to transition the slave

from the ACTIVE to the HALT state after the master has

completed the communication with the slave. There are

two versions of the deselect request frame, one without

CID and one with CID. Figure 28 shows both versions.

Figure 26 shows the CID format.

BIT 8 BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1

MSb LSb

XXXX

RESPONSE DATA

RATE (UPLINK)

RECEIVER FRAME SIZE CAPABILITY

REQUEST DATA

RATE (DOWNLINK)

Figure 25. Bit Assignments for Param 2 Byte

BIT 8 BIT 7 BIT 6 BIT 5 BIT 4 BIT 3 BIT 2 BIT 1

MSb LSb

(FIXED) CARD IDENTIFIER VALUE (CID)

0 00

Figure 26. Bit Assignments for Param 4 Byte

SOF

FRAME WITHOUT CID

CRC EOF

(2 BYTES)

COMMAND

C2h

SOF

FRAME WITH CID

CRC EOF

(2 BYTES)

CID

(1 BYTE)

COMMAND

CAh

Figure 28. DESELECT Request and Response Frames

INDICATORSOF CRC EOF

MBLI, CID (2 BYTES)

HL RESPONSE

(≥ 0 BYTES)

Figure 27. ATTRIB Response Frame

P1-P3 P4-P6 P7-P9 P10-P12 P13-P15 P16-P18 P19-P21

MAX66000K-000AA+

Mfr. #:

Buy MAX66000K-000AA+

Manufacturer:

Maxim Integrated

Description:

RFID Transponders RFID 14443 ROM ID LF TSTD

Lifecycle:

New from this manufacturer.

Delivery:

DHL FedEx Ups TNT EMS

Payment:

T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet

MAX66000K-000AA+