mfrc531 NXP Semiconductors, mfrc531 Datasheet - Page 80

no-image

mfrc531

Manufacturer Part Number
mfrc531
Description
Iso/iec 14443 Reader Ic
Manufacturer
NXP Semiconductors
Datasheet

Available stocks

Company
Part Number
Manufacturer
Quantity
Price
Part Number:
MFRC531
Quantity:
5
Part Number:
MFRC531
Manufacturer:
NXP/恩智浦
Quantity:
20 000
Part Number:
mfrc531-01T
Manufacturer:
MFRC
Quantity:
20 000
Company:
Part Number:
mfrc531-01T
Quantity:
420
Part Number:
mfrc53101T
Manufacturer:
TI
Quantity:
11 793
Part Number:
mfrc53101T
Manufacturer:
NXP/恩智浦
Quantity:
20 000
Company:
Part Number:
mfrc53101T
Quantity:
37
Company:
Part Number:
mfrc53101T
Quantity:
37
Part Number:
mfrc53101T/0FE
Manufacturer:
NXP
Quantity:
3 000
Part Number:
mfrc53101T/0FE
Manufacturer:
ST
Quantity:
3
Part Number:
mfrc53101T/0FE
Manufacturer:
NXP/恩智浦
Quantity:
20 000
Part Number:
mfrc53101T/0FE,112
Manufacturer:
NXP/恩智浦
Quantity:
20 000
Part Number:
mfrc53101T/0FE.112
0
Part Number:
mfrc53101T/OFE
Manufacturer:
NXP
Quantity:
5 000
NXP Semiconductors
MFRC531_34
Product data sheet
PUBLIC
11.2.2.3 Collision detection
If an EOF pattern is detected or the signal strength falls below the RxThreshold register
MinLevel[3:0] bits setting, both the receiver and the decoder stop. Then the Idle command
is entered and an appropriate response for the microprocessor is generated (interrupt
request activated, status flags set).
When the ChannelRedundancy register bit RxCRCEn is set, a CRC block is expected.
The CRC block can be one byte or two bytes depending on the ChannelRedundancy
register CRC8 bit setting.
Remark: If the CRC block received is correct, it is not sent to the FIFO buffer. This is
realized by shifting the incoming data bytes through an internal buffer of either one or two
bytes (depending on the defined CRC). The CRC block remains in this internal buffer.
Consequently, all data bytes in the FIFO buffer are delayed by one or two bytes. If the
CRC fails, all received bytes are sent to the FIFO buffer including the faulty CRC.
If ParityEn is set in the ChannelRedundancy register, a parity bit is expected after each
byte. If ParityOdd = logic 1, the expected parity is odd, otherwise even parity is expected.
If more than one card is within the RF field during the card selection phase, they both
respond simultaneously. The MFRC531 supports the algorithm defined in
ISO/IEC 14443 A to resolve card serial number data collisions by performing the
anti-collision procedure. The basis for this procedure is the ability to detect bit-collisions.
Bit-collision detection is supported by the Manchester coding bit encoding scheme used in
the MFRC531. If in the first and second half-bit of a subcarrier, modulation is detected,
instead of forwarding a 1-bit or 0-bit, a bit-collision is indicated. The MFRC531 uses the
RxThreshold register CollLevel[3:0] bits setting to distinguish between a 1-bit or 0-bit and
a bit-collision. If the amplitude of the half-bit with smaller amplitude is larger than that
defined by the CollLevel[3:0] bits, the MFRC531 flags a bit-collision using the error flag
CollErr. If a bit-collision is detected in a parity bit, the ParityErr flag is set.
On a detected collision, the receiver continues receiving the incoming data stream. In the
case of a bit-collision, the decoder sends logic 1 at the collision position.
Remark: As an exception, if bit ZeroAfterColl is set, all bits received after the first
bit-collision are forced to zero, regardless whether a bit-collision or an unequivocal state
has been detected. This feature makes it easier for the control software to perform the
anti-collision procedure as defined in ISO/IEC 14443 A.
When the first bit collision in a frame is detected, the bit-collision position is stored in the
CollPos register.
Table 135
shows the collision positions.
Rev. 3.4 — 26 January 2010
056634
ISO/IEC 14443 reader IC
MFRC531
© NXP B.V. 2010. All rights reserved.
80 of 116

Related parts for mfrc531