STMicroelectronics LRI2K Datasheet
Advertisement
Advertisement
LRI2K
2048-bit EEPROM tag IC at 13.56 MHz, with 64-bit UID and
kill code, ISO 15693 and ISO 18000-3 Mode 1 compliant
Datasheet
-
production data
Wafer (SBN18)
Features
• Belongs to the ST25 family, that includes all
STMicroelectronics NFC/RFID tag and reader products
• ISO 15693 standard fully compliant
• ISO 18000-3 Mode 1 standard fully compliant
• 13.56 MHz ±7 kHz carrier frequency
• To tag: 10% or 100% ASK modulation using
1/4 (26 Kbit/s) or 1/256 (1.6 Kbit/s) pulse position coding
• From tag: load modulation using Manchester coding with 423 kHz and 484 kHz subcarriers in low (6.6 Kbit/s) or high (26 Kbit/s) data rate mode. Supports the 53 Kbit/s data rate with
Fast commands
• Internal tuning capacitor (21 pF or 97 pF)
• 1 000 000 Erase/Write cycles (minimum)
• 40 year data retention (minimum)
• 2048 bits EEPROM with Block Lock feature
• 64-bit unique identifier (UID)
• Electrical article surveillance capable (software controlled)
• Kill function
• Read & Write (Block of 32 bits)
• 5 ms programming time
November 2015
This is information on a product in full production.
DocID12112 Rev 9
www.st.com
Contents
Contents
LRI2K
Memory mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Initial dialogue for vicinity cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Communication signal from VCD to LRI2K . . . . . . . . . . . . . . . . . . . . . 14
Data rate and data coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Data coding mode: 1 out of 256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Data coding mode: 1 out of 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
VCD to LRI2K frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Communications signal from LRI2K to VCD . . . . . . . . . . . . . . . . . . . . 19
Load modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Data rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Bit representation and coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Bit coding using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Bit coding using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
LRI2K to VCD frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SOF when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
DocID12112 Rev 9
LRI2K
Contents
SOF when using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
EOF when using one subcarrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
EOF when using two subcarriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Application family identifier (AFI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Data storage format identifier (DSFID) . . . . . . . . . . . . . . . . . . . . . . . . . 29
CRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
LRI2K protocol description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Addressed mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Non-Addressed mode (general request) . . . . . . . . . . . . . . . . . . . . . . . . . 34
Select mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
DocID12112 Rev 9
5
Contents
LRI2K
Request processing by the LRI2K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Explanation of the possible cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Inventory Initiated command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
t2: VCD new request delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
: VCD new request delay in absence of a response from the LRI2K . . . 45
DocID12112 Rev 9
LRI2K Contents
DC and AC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Appendix A Anticollision algorithm (informative) . . . . . . . . . . . . . . . . . . . . . . . . 80
Algorithm for pulsed slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
CRC error detection method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
CRC calculation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Application family identifier (AFI) (informative) . . . . . . . . . . . . . . . . . . . . . 83
DocID12112 Rev 9
5
List of tables
List of tables
LRI2K
DocID12112 Rev 9
LRI2K List of tables
Get Multiple Block Security Status response format when Error_flag is NOT set . . . . . . . 63
Get Multiple Block Security Status response format when Error_flag is set . . . . . . . . . . . . 63
Fast Read Single Block response format when Error_flag is NOT set . . . . . . . . . . . . . . . . 68
Fast Read Multiple Block response format when Error_flag is NOT set. . . . . . . . . . . . . . . 72
DocID12112 Rev 9
7
List of figures
List of figures
LRI2K
Principle of comparison between the mask, the slot number and the UID . . . . . . . . . . . . . 40
READ Single Block frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . . 50
Read Multiple Block frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . . . . . 54
DocID12112 Rev 9
LRI2K List of figures
Get Multiple Block Security Status frame exchange between VCD and LRI2K . . . . . . . . . 63
Fast Read Single Block frame exchange between VCD and LRI2K. . . . . . . . . . . . . . . . . . 69
Fast Read Multiple Block frame exchange between VCD and LRI2K . . . . . . . . . . . . . . . . 73
DocID12112 Rev 9
9
Description
1 Description
LRI2K
The LRI2K is a contactless memory powered by the received carrier electromagnetic wave.
It is a 2048-bit electrically erasable programmable memory (EEPROM). The memory is organized as 64 blocks of 32 bits. The LRI2K is accessed via the 13.56 MHz carrier electromagnetic wave on which incoming data are demodulated from the received signal amplitude modulation (ASK: amplitude shift keying). The received ASK wave is 10% or
100% modulated with a data rate of 1.6 Kbit/s using the 1/256 pulse coding mode or a data rate of 26 Kbit/s using the 1/4 pulse coding mode.
Outgoing data are generated by the LRI2K load variation using Manchester coding with one or two subcarrier frequencies at 423 kHz and 484 kHz. Data are transferred from the LRI2K at 6.6 Kbit/s in low data rate mode and 26 Kbit/s fast data rate mode. The LRI2K supports
53 Kbit/s in high data rate mode with one subcarrier frequency at 423 kHz.
The LRI2K follows the ISO 15693 recommendation for radio-frequency power and signal interface.
Figure 1. Pad connections
LRI2K
2048 bit
EEPROM memory
Power
Supply
Regulator
ASK
Demodulator
Manchester
Load
Modulator
AC1
AC0
Signal name
AC1
AC0
AI12065
Table 1. Signal names
Function
Antenna coil
Antenna coil
DocID12112 Rev 9
LRI2K Description
Add
...
60
61
62
63
5
6
3
4
7
8
...
...
0
1
2
The LRI2K is divided into 64 blocks of 32 bits. Each block can be individually write-protected using the Lock command.
-
0
UID 0
UID 4
AFI
Table 2. LRI2K memory map
7 8 15 16
-
User area
User area
User area
User area
User area
User area
User area
User area
User area
User area
User area
User area
User area
User area
User area
User area
UID 1
UID 5
DSFID
UID 2
UID 6
Kill code
23 24
-
UID 3
UID 7
31
The User area consists of blocks that are always accessible in read mode. Write operations are possible if the addressed block is not protected. During a write operation, the 32 bits of the block are replaced by the new 32-bit value.
The LRI2K also has a 64-bit block that is used to store the 64-bit unique identifier (UID). The
UID is compliant to the ISO 15963 description, and its value is used during the anticollision sequence (Inventory). This block is not accessible by the user and its value is written by ST on the production line.
The LRI2K also includes an AFI register in which the application family identifier is stored, and a DSFID register in which the data storage family identifier used in the anticollision algorithm is stored. The LRI2K has an additional 32-bit block in which the kill code is stored.
DocID12112 Rev 9
84
Description LRI2K
1.2 Commands
The LRI2K supports the following commands:
• Inventory , used to perform the anticollision sequence.
• Stay Quiet , used to put the LRI2K in quiet mode, where it does not respond to any inventory command.
• Select , used to select the LRI2K. After this command, the LRI2K processes all
Read/Write commands with Select_flag set.
• Reset To Ready , used to put the LRI2K in the ready state.
• Read Block , used to output the 32 bits of the selected block and its locking status.
• Write Block , used to write the 32-bit value in the selected block, provided that it is not locked.
• Lock Block , used to lock the selected block. After this command, the block cannot be modified.
• Read Multiple Blocks , used to read the selected blocks and send back their value.
• Write AFI , used to write the 8-bit value in the AFI register.
• Lock AFI , used to lock the AFI register.
• Write DSFID , used to write the 8-bit value in the DSFID register.
• Lock DSFID , used to lock the DSFID register.
• Get System Info , used to provide the system information value
• Get Multiple Block Security Status , used to send the security status of the selected block.
• Initiate , used to trigger the tag response to the Inventory Initiated sequence.
• Inventory Initiated , used to perform the anticollision sequence triggered by the Initiate command.
• Kill , used to definitively deactivate the tag.
• Write Kill , used to write the 32-bit Kill code value
• Lock Kill , used to lock the Kill Code register.
• Fast Initiate , used to trigger the tag response to the Inventory Initiated sequence.
• Fast Inventory Initiated , used to perform the anticollision sequence triggered by the
Initiate command.
• Fast Read Block , used to output the 32 bits of the selected block and its locking status.
• Fast Read Multiple Blocks , used to read the selected blocks and send back their value.
DocID12112 Rev 9
LRI2K
1.3
Description
Initial dialogue for vicinity cards
The dialog between the vicinity coupling device (VCD) and the vicinity integrated circuit card or VICC (LRI2K) takes place as follows:
• activation of the LRI2K by the RF operating field of the VCD
• transmission of a command by the VCD
• transmission of a response by the LRI2K
These operations use the RF power transfer and communication signal interface described below (see
and
). This technique is called RTF
(reader talk first).
Power is transferred to the LRI2K by radio frequency at 13.56 MHz via coupling antennas in the LRI2K and the VCD. The RF operating field of the VCD is transformed on the LRI2K antenna as an AC voltage which is rectified, filtered and internally regulated. The amplitude modulation (ASK) on this received signal is demodulated by the ASK demodulator.
1.3.2 Frequency
The ISO 15693 standard defines the carrier frequency ( f c
13.56 MHz ±7 kHz.
) of the operating field as
The LRI2K operates continuously between H min
and H max
.
• The minimum operating field is H min
and has a value of 150 mA/m rms.
• The maximum operating field is H max
and has a value of 5 A/m rms.
A VCD must generate a field of at least H min volume.
and not exceeding H max in the operating
DocID12112 Rev 9
84
Communication signal from VCD to LRI2K
2 Communication signal from VCD to LRI2K
LRI2K
Communications between the VCD and the LRI2K take place using the modulation principle of ASK (amplitude shift keying). Two modulation indexes are used, 10% and 100%. The
LRI2K decodes both. The VCD determines which index is used.
The modulation index is defined as [a – b]/[a + b] where a is the peak signal amplitude and b the minimum signal amplitude of the carrier frequency.
Depending on the choice made by the VCD, a "pause" will be created as shown in
.
The LRI2K is operational for any degree of modulation index between 10% and 30%.
Figure 2. 100% modulation waveform a
105%
100%
95%
60%
Symbol hr hf
5% tRFF tRFR tRFSBL t
AI06683
Table 3. 10% modulation parameters
Parameter definition
0.1 x (a – b)
0.1 x (a – b)
Figure 3. 10% modulation waveform
Value max max hf hr a tRFF tRFSFL tRFR b t
AI06655
DocID12112 Rev 9
LRI2K
3
3.1
Data rate and data coding
Data rate and data coding
The data coding implemented in the LRI2K uses pulse position modulation. Both data coding modes that are described in the ISO 15693 are supported by the LRI2K. The selection is made by the VCD and indicated to the LRI2K within the start of frame (SOF).
Data coding mode: 1 out of 256
The value of one single byte is represented by the position of one pause. The position of the pause on 1 of 256 successive time periods of 18.88 µs (256/ f
C
), determines the value of the byte. In this case the transmission of one byte takes 4.833 ms and the resulting data rate is
1.65 Kbits/s ( f
C
/8192).
Figure 4 illustrates this pulse position modulation technique. In this Figure, data E1h (225
decimal) is sent by the VCD to the LRI2K.
The pause occurs during the second half of the position of the time period that determines
the value, as shown in Figure 5
.
A pause during the first period transmits the data value 00h. A pause during the last period transmits the data value FFh (255 decimal).
Figure 4. 1 out of 256 coding mode
Pulse
Modulated
Carrier
9.44 µs
18.88 µs
0 1 2 3 . . . . . . . . 2 . . . . . . . . . . . . . . . . . . . . . 2 2 2 2
. . . . . . . . . 2 . . . . . . . . . . . . . . . . . . . . . 5 5 5 5
. . . . . . . . . 5 . . . . . . . . . . . . . . . . . . . . . 2 3 4 5
4.833 ms
AI06656
DocID12112 Rev 9
84
Data rate and data coding LRI2K
Figure 5. Detail of one time period
9.44 µs
18.88 µs
Pulse
Modulated
Carrier
. . . . . . .
2
2
4
. . . . . . .
2
2
5
2
2
6
Time Period one of 256
AI06657
DocID12112 Rev 9
LRI2K
3.2
Data rate and data coding
Data coding mode: 1 out of 4
The value of 2 bits is represented by the position of one pause. The position of the pause on
1 of 4 successive time periods of 18.88 µs (256/ f
C
) determines the value of the 2 bits. Four successive pairs of bits form a byte, where the least significant pair of bits is transmitted first.
In this case the transmission of one byte takes 302.08 µs and the resulting data rate is
26.48 Kbit/s ( f
C
illustrates the 1 out of 4 pulse position technique and coding.
Figure 7 shows the transmission of E1h (225d - 1110 0001b) by the VCD.
Figure 6. 1 out of 4 coding mode
Pulse position for "00"
9.44 µs 9.44 µs
Pulse position for "01" (1=LSB)
75.52 µs
28.32 µs 9.44 µs
Pulse position for "10" (0=LSB)
75.52 µs
Pulse position for "11"
10
47.20 µs 9.44 µs
75.52 µs
75.52 µs
Figure 7. 1 out of 4 coding example
00 01
66.08 µs 9.44 µs
AI06658
11
75.52 µs 75.52 µs
DocID12112 Rev 9
75.52 µs 75.52 µs
AI06659
84
Data rate and data coding
3.3 VCD to LRI2K frames
LRI2K
Frames are delimited by a start of frame (SOF) and an end of frame (EOF). They are implemented using code violation. Unused options are reserved for future use.
The LRI2K is ready to receive a new command frame from the VCD 311.5 µs (t
2 sending a response frame to the VCD.
) after
The LRI2K takes a Power-On time of 0.1 ms after being activated by the powering field.
After this delay, the LRI2K is ready to receive a command frame from the VCD.
3.4 Start of frame (SOF)
The SOF defines the data coding mode the VCD is to use for the following command frame.
The SOF sequence described in Figure 8
selects the 1 out of 256 data coding mode.
The SOF sequence described in Figure 9
selects the 1 out of 4 data coding mode.
The EOF sequence for either coding mode is described in Figure 10 .
Figure 8. SOF to select 1 out of 256 data coding mode
9.44 µs
37.76 µs 37.76 µs
Figure 9. SOF to select 1 out of 4 data coding mode
9.44 µs
AI06661
9.44 µs
9.44 µs 9.44 µs
37.76 µs 37.76 µs
Figure 10. EOF for either data coding mode
AI06660
37.76 µs
DocID12112 Rev 9
9.44 µs 9.44 µs
AI06662
LRI2K
4
Communications signal from LRI2K to VCD
Communications signal from LRI2K to VCD
The LRI2K has several modes defined for some parameters, owing to which it can operate in different noise environments and meet different application requirements.
The LRI2K is capable of communication with the VCD via an inductive coupling area whereby the carrier is loaded to generate a subcarrier with frequency f
S generated by switching a load in the LRI2K.
. The subcarrier is
The load-modulated amplitude received on the VCD antenna shall be at least 10 mV when measured as described in the test methods defined in International Standard ISO 10373-7.
4.2 Subcarrier
The LRI2K supports the one-subcarrier and two-subcarrier response formats. These formats are selected by the VCD using the first bit in the protocol header. When one subcarrier is used, the frequency f
S1
of the subcarrier load modulation is 423.75 kHz ( f
When two subcarriers are used, frequency f
S1
484.28 kHz ( f
C
/28). When using the two-subcarrier mode, the LRI2K generates a continuous phase relationship between f
S1
and f
S2
.
C
/32).
is 423.75 kHz ( f
C
/32), and frequency f
S2
is
The LRI2K can respond using the low or the high data rate format. The selection of the data rate is made by the VCD using the second bit in the protocol header. It also supports the x2
mode available on all the Fast commands. Table 4 shows the different data rates produced
by the LRI2K using the different response format combinations.
Low
High
Data rate
Standard commands
Fast commands
Standard commands
Fast commands
Table 4. Response data rate
One subcarrier
6.62 Kbits/s ( f c
/2048)
13.24 Kbits/s ( f c
/1024)
26.48 Kbits/s ( f c
/512)
52.97 Kbits/s ( f c
/256)
Two subcarriers
6.67 Kbits/s ( f c
/2032) not applicable
26.69 Kbits/s ( f c
/508) not applicable
DocID12112 Rev 9
84
Bit representation and coding
5 Bit representation and coding
LRI2K
Data bits are encoded using Manchester coding, according to the following schemes. For the low data rate, the same subcarrier frequency or frequencies is/are used, in this case the number of pulses is multiplied by 4 and all times are increased by this factor. For the Fast commands using one subcarrier, all pulse numbers and times are divided by 2.
5.1 Bit coding using one subcarrier
A logic 0 starts with 8 pulses at 423.75 kHz ( f
C
18.88 µs as shown in Figure 11
.
/32) followed by an unmodulated time of
Figure 11. Logic 0, high data rate
37.76µs ai12076
For the Fast commands, a logic 0 starts with 4 pulses at 423.75 kHz ( f unmodulated time of 9.44 µs as shown in
.
C
/32) followed by an
Figure 12. Logic 0, high data rate x2
18.88µs ai12066
A logic 1 starts with an unmodulated time of 18.88 µs followed by 8 pulses at 423.75 kHz
( f
C
.
Figure 13. Logic 1, high data rate
37.76µs ai12077
For the Fast commands, a logic 1 starts with an unmodulated time of 9.44 µs followed by 4 pulses at 423.75 kHz ( f
C
Figure 14. Logic 1, high data rate x2
18.88µs ai12067
DocID12112 Rev 9
LRI2K
5.1.2
Bit representation and coding
Low data rate
A logic 0 starts with 32 pulses at 423.75 kHz ( f
C
75.52 µs as shown in Figure 15 .
/32) followed by an unmodulated time of
Figure 15. Logic 0, low data rate
151.04µs ai12068
For the fast commands, a logic 0 starts with 16 pulses of 423,75 kHz ( f
C
unmodulated time of 37,76 µs as shown in Figure 16 .
/32) followed by an
Figure 16. Logic 0, low data rate x2
75.52µs ai12069
A logic 1 starts with an unmodulated time of 75,52 µs followed by 32 pulses of 423,75 kHz
( f
C
.
Figure 17. Logic 1, low data rate
151.04µs ai12070
For the Fast commands, a logic 1 starts with an unmodulated time of 37.76 µs followed by
16 pulses at 423.75 kHz ( f
C
.
Figure 18. Logic 1, low data rate x2
5.2
75.52µs
Bit coding using two subcarriers
ai12071
(
A logic 0 starts with 8 pulses at 423.75 kHz ( f
C f
C
/32) followed by 9 pulses at 484.28 kHz
. For the Fast commands, the x2 mode is not available.
DocID12112 Rev 9
84
Bit representation and coding LRI2K
Figure 19. Logic 0, high data rate
37.46
µs ai12074
(
A logic 1 starts with 9 pulses at 484.28 kHz ( f
C f
C
/28) followed by 8 pulses at 423.75 kHz
. For the Fast commands, the x2 mode is not available.
Figure 20. Logic 1, high data rate
5.2.2
37.46
µs ai12073
Low data rate
(
A logic 0 starts with 32 pulses at 423.75 kHz ( f
C f
C
/32) followed by 36 pulses at 484.28 kHz
. For the Fast commands, the x2 mode is not available.
Figure 21. Logic 0, low data rate
149.84µs ai12072
(
A logic 1 starts with 36 pulses at 484.28kHz ( f
C f
C
/28) followed by 32 pulses at 423.75kHz
. For the fast commands, the x2 mode is not available.
Figure 22. Logic 1, low data rate
149.84µs ai12075
DocID12112 Rev 9
LRI2K
6
6.1
LRI2K to VCD frames
LRI2K to VCD frames
Frames are delimited by an SOF and an EOF. They are implemented using code violation.
Unused options are reserved for future use. For the low data rate, the same subcarrier frequency or frequencies is/are used. In this case the number of pulses is multiplied by 4.
For the Fast commands using one subcarrier, all pulse numbers and times are divided by 2.
SOF when using one subcarrier
The SOF includes an unmodulated time of 56.64 µs followed by 24 pulses at 423.75 kHz
( f
C
/32), and a logic 1 that consists of an unmodulated time of 18.88 µs followed by 8 pulses
at 423.75 kHz. The SOF is shown in Figure 23
.
Figure 23. Start of frame, high data rate, one subcarrier
113.28µs 37.76µs ai12078
For the Fast commands, the SOF comprises an unmodulated time of 28.32 µs, followed by
12 pulses at 423.75 kHz ( f
C
/32), and a logic 1 that consists of an unmodulated time of
9.44 µs followed by 4 pulses at 423.75 kHz as shown in
.
Figure 24. Start of frame, high data rate, one subcarrier x2
6.1.2
56.64µs 18.88µs ai12079
Low data rate
SOF comprises an unmodulated time of 226.56 µs, followed by 96 pulses at 423.75 kHz
( f
C
/32), and a logic 1 that consists of an unmodulated time of 75.52 µs followed by 32 pulses at 423.75 kHz as shown in
.
Figure 25. Start of frame, low data rate, one subcarrier
453.12µs 151.04µs ai12080
For the Fast commands, the SOF comprises an unmodulated time of 113.28 µs followed by
48 pulses at 423.75 kHz ( f
C
/32), and a logic 1 that includes an unmodulated time of 37.76
µs followed by 16 pulses at 423.75 kHz as shown in
.
DocID12112 Rev 9
84
LRI2K to VCD frames LRI2K
Figure 26. Start of frame, low data rate, one subcarrier x2
226.56µs
6.2 SOF when using two subcarriers
75.52µs ai12081
(
The SOF comprises 27 pulses at 484.28 kHz ( f
C
f
C
/28), followed by 24 pulses at 423.75 kHz
/32), and a logic 1 that includes 9 pulses at 484.28 kHz followed by 8 pulses at 423.75
For the Fast commands, the x2 mode is not available.
Figure 27. Start of frame, high data rate, two subcarriers
6.2.2
112.39µs 37.46µs ai12082
Low data rate
The SOF comprises 108 pulses at 484.28 kHz ( f
C
( f
C
423.75 kHz as shown in Figure 28 .
/28) followed by 96 pulses at 423.75 kHz
/32), and a logic 1 that includes 36 pulses at 484.28 kHz followed by 32 pulses at
For the Fast commands, the x2 mode is not available.
Figure 28. Start of frame, low data rate, two subcarriers
449.56µs 149.84µs ai12083
6.3 EOF when using one subcarrier
The EOF comprises a logic 0 that includes 8 pulses at 423.75 kHz and an unmodulated time of 18.88 µs, followed by 24 pulses at 423.75 kHz ( f
C
56.64 µs as shown in Figure 29 .
/32) and by an unmodulated time of
DocID12112 Rev 9
LRI2K LRI2K to VCD frames
Figure 29. End of frame, high data rate, one subcarrier
37.76µs 113.28µs ai12084
For the Fast commands, the EOF comprises a logic 0 that includes 4 pulses at 423.75 kHz and an unmodulated time of 9.44 µs, followed by 12 pulses at 423.75 kHz ( f
C
unmodulated time of 28.32 µs as shown in Figure 30 .
/32) and an
Figure 30. End of frame, high data rate, one subcarrier x2
6.3.2
18.88µs 56.64µs ai12085
Low data rate
The EOF comprises a logic 0 that includes 32 pulses at 423.75 kHz and an unmodulated time of 75.52 µs, followed by 96 pulses at 423.75 kHz ( f
C
/32) and an unmodulated time of
226.56 µs as shown in
Figure 31. End of frame, low data rate, one subcarrier
151.04µs 453.12µs ai12086
For the Fast commands, the EOF comprises a logic 0 that includes 16 pulses at 423.75 kHz and an unmodulated time of 37.76 µs, followed by 48 pulses at 423.75 kHz ( f
C unmodulated time of 113.28 µs as shown in
/32) and an
Figure 32. End of frame, low data rate, one subcarrier x2
75.52µs 226.56µs ai12087
DocID12112 Rev 9
84
LRI2K to VCD frames
6.4 EOF when using two subcarriers
The EOF comprises a logic 0 that includes 8 pulses at 423.75 kHz and 9 pulses at
(
484.28 kHz, followed by 24 pulses at 423.75 kHz ( f
C f
C
.
/32) and 27 pulses at 484.28 kHz
For the Fast commands, the x2 mode is not available.
Figure 33. End of frame, high data rate, two subcarriers
LRI2K
6.4.2
37.46µs 112.39µs ai12088
Low data rate
The EOF comprises a logic 0 that includes 32 pulses at 423.75 kHz and 36 pulses at
(
484.28 kHz, followed by 96 pulses at 423.75 kHz ( f
C f
C
/32) and 108 pulses at 484.28 kHz
For the fast commands, the x2 mode is not available.
Figure 34. End of frame, low data rate, two subcarriers
149.84µs 449.56µs ai12089
DocID12112 Rev 9
LRI2K
7
Unique identifier (UID)
Unique identifier (UID)
The LRI2Ks are uniquely identified by a 64-bit Unique Identifier (UID). This UID complies with ISO/IEC 15963 and ISO/IEC 7816-6. The UID is a read-only code, and comprises:
• the 8 MSBs are E0h
• the IC manufacturer code of ST 02h, on 8 bits (ISO/IEC 7816-6/AM1)
• a unique serial number on 48 bits.
Table 5. UID format
MSB
63 56 55 48 47
LSB
0
E0h 02h Unique serial number
With the UID each LRI2K can be addressed uniquely and individually during the anticollision loop and for one-to-one exchanges between a VCD and an LRI2K.
DocID12112 Rev 9
84
Application family identifier (AFI)
8 Application family identifier (AFI)
LRI2K
The AFI (application family identifier) represents the type of application targeted by the VCD and is used to identify, among all the LRI2Ks present, only the LRI2Ks that meet the required application criteria.
Figure 35. LRI2K decision tree for AFI
Inventory Request
Received
No
AFI Flag
Set ?
Yes
AFI value
= 0 ?
Yes
No
AFI value
= Internal value ?
Yes
No
Answer given by the LRI2K to the Inventory Request
No Answer
AI12091
The AFI is programmed by the LRI2K issuer (or purchaser) in the AFI register. Once programmed and Locked, it can no longer be modified.
The most significant nibble of the AFI is used to code one specific or all application families.
The least significant nibble of the AFI is used to code one specific or all application subfamilies. subfamily codes different from 0 are proprietary.
(See ISO 15693-3 documentation)
DocID12112 Rev 9
LRI2K
9
Data storage format identifier (DSFID)
Data storage format identifier (DSFID)
The data storage format identifier indicates how the data is structured in the LRI2K memory.
The logical organization of data can be known instantly using the DSFID.
It can be programmed and locked using the Write DSFID and Lock DSFID commands, respectively. It is coded on one byte.
9.1 CRC
The CRC used in the LRI2K is calculated as per the definition in ISO/IEC 13239.
The initial register contents are all ones: "FFFF".
The two-byte CRC is appended to each request and response, within each frame, before the EOF. The CRC is calculated on all the bytes between the SOF and the CRC field.
Upon reception of a request from the VCD, the LRI2K verifies that the CRC value is valid. If it is invalid, the LRI2K discards the frame and does not answer to the VCD.
Upon reception of a response from the LRI2K, it is recommended that the VCD verifies whether the CRC value is valid. If it is invalid, actions to be performed are left to the discretion of the VCD designers.
The CRC is transmitted least significant byte first.
Each byte is transmitted least significant bit first.
Table 6. CRC transmission rules
LSByte MSByte
LSBit MSBit LSBit MSBit
CRC 16 (8bits) CRC 16 (8 bits)
DocID12112 Rev 9
84
LRI2K protocol description
10 LRI2K protocol description
LRI2K
The transmission protocol (or simply protocol) defines the mechanism used to exchange instructions and data between the VCD and the LRI2K, in both directions. It is based on the concept of "VCD talks first".
This means that an LRI2K will not start transmitting unless it has received and properly decoded an instruction sent by the VCD. The protocol is based on an exchange of:
• a request from the VCD to the LRI2K
• a response from the LRI2K to the VCD
Each request and each response are contained in a frame. The frame delimiters (SOF,
EOF) are described in
Section 6: LRI2K to VCD frames .
Each request consists of:
• a request SOF (see
)
• flags
• a command code
• parameters, depending on the command
• application data
• a 2-byte CRC
• a request EOF (see
)
Each response consists of:
•
an answer SOF (see Figure 23 to
• flags
• parameters, depending on the command
• application data
• a 2-byte CRC
•
The protocol is bit-oriented. The number of bits transmitted in a frame is a multiple of eight
(8), i.e. an integer number of bytes.
A single-byte field is transmitted least significant bit (LSBit) first. A multiple-byte field is transmitted least significant byte (LSByte) first, with each byte transmitted least significant bit (LSBit) first.
The setting of the flags indicates the presence of the optional fields. When the flag is set (to one), the field is present. When the flag is reset (to zero), the field is absent.
Table 7. VCD request frame format
Request SOF Request Flags
Command code
Parameters Data 2 byte CRC
Request
EOF
Response
SOF
Table 8. LRI2K response frame format
Response
Flags
Parameters Data 2 byte CRC
Response
EOF
DocID12112 Rev 9
LRI2K
VCD
LRI2K
Request frame
)
Figure 36. LRI2K protocol timing
LRI2K protocol description
Request frame
(
Response frame
Response frame
Timing t
1 t
2 t
1 t
2
DocID12112 Rev 9
84
LRI2K states LRI2K
An LRI2K can be in one of 4 states:
• Power-off
• Ready
• Quiet
• Selected
Transitions between these states are specified in
The LRI2K is in the Power-off state when it does not receive enough energy from the VCD.
The LRI2K is in the Ready state when it receives enough energy from the VCD. When in the
Ready state, the LRI2K answers any request where the Select_flag is not set.
When in the Quiet state, the LRI2K answers any request except for Inventory requests with the Address_flag set.
In the Selected state, the LRI2K answers any request in all modes (see
• request in Select mode with the Select flag set
• request in Addressed mode if the UID matches
• request in Non-Addressed mode as it is the mode for general requests
DocID12112 Rev 9
LRI2K LRI2K states
Table 9. LRI2K response depending on request flags
Address_flag Select_flag
Flags
1
Addressed
0
Non addressed
1
Selected
0
Non selected
LRI2K in Ready or Selected state
(Devices in Quiet state do not answer)
LRI2K in Selected state
LRI2K in Ready, Quiet or Selected state (the device which match the UID)
Error (03h)
-
-
X
X
X
X
-
-
-
X
-
X
X
-
-
X
Figure 37. LRI2K state transition diagram
Power Off
In field
Out of field
Ready
Any other Command where Select_Flag is not set
Select (UID)
Reset to ready where
Select_Flag is set or
Select(different UID)
Stay quiet(UID)
Reset to ready
Select (UID)
Quiet
Stay quiet(UID)
Selected
Any other command where the
Address_Flag is set AND where Inventory_Flag is not set
Any other command
AI06681
1. The intention of the state transition method is that only one LRI2K should be in the selected state at a time.
DocID12112 Rev 9
84
Modes
12 Modes
LRI2K
The term “mode” refers to the mechanism used in a request to specify the set of LRI2Ks that will answer the request.
When the Address_flag is set to 1 (Addressed mode), the request contains the Unique ID
(UID) of the addressed LRI2K.
Any LRI2K that receives a request with the Address_flag set to 1 compares the received
Unique ID to its own. If it matches, then the LRI2K executes the request (if possible) and returns a response to the VCD as specified in the command description.
If its UID does not match, then it remains silent.
12.2 Non-Addressed mode (general request)
When the Address_flag is set to 0 (Non-Addressed mode), the request does not contain a
Unique ID. Any LRI2K receiving a request with the Address_flag set to 0 executes it and returns a response to the VCD as specified in the command description.
When the Select_flag is set to 1 (Select mode), the request does not contain an LRI2K
Unique ID. The LRI2K in the Selected state that receives a request with the Select_flag set to 1 executes it and returns a response to the VCD as specified in the command description.
Only LRI2Ks in the Selected state answer to a request where the Select Flag is set to 1.
The system design ensures in theory that only one LRI2K can be in the Select state at a time.
DocID12112 Rev 9
LRI2K Request format
The request consists of:
• an SOF
• flags
• a command code
• parameters and data
• a CRC
• an EOF
Table 10. General request format
S
O
F
Request flags Command code Parameters Data CRC
E
O
F
In a request, the "flags" field specifies the actions to be performed by the LRI2K and whether corresponding fields are present or not.
The flags field consists of eight bits.
The bit 3 (Inventory_flag) of the request flag defines the contents of the 4 MSBs (bits 5 to 8).
When bit 3 is reset (0), bits 5 to 8 define the LRI2K selection criteria.
When bit 3 is set (1), bits 5 to 8 define the LRI2K Inventory parameters.
Bit No Flag
Table 11. Definitions of request flags 1 to 4
Level Description
Bit 1
Bit 2
Bit 3
Subcarrier_flag
Data_rate_flag
Inventory flag
(1)
(2)
0 A single subcarrier frequency is used by the LRI2K
1 Two subcarriers are used by the LRI2K
0 Low data rate is used
1 High data rate is used
0
The meaning of Flags 5 to 8 is described in Table 12
1
The meaning of Flags 5 to 8 is described in Table 13
0 No Protocol format extension Bit 4 Protocol Extension flag
1.
Subcarrier_flag refers to the LRI2K-to-VCD communication.
2.
Data_rate_flag refers to the LRI2K-to-VCD communication.
DocID12112 Rev 9
84
Request format LRI2K
Bit No.
Flag
Table 12. Request flags 5 to 8 when bit 3 = 0
Level Description
Bit 5
Bit 6
Select_flag
(1)
Address_flag
(1)
0
0 -
0 -
Request is executed by any LRI2K according to the setting of
Address_flag
1 Request is executed only by the LRI2K in Selected state.
0
Request is not addressed. UID field is not present. The request is executed by all LRI2Ks.
1
Request is addressed. UID field is present. The request is executed only by the LRI2K whose UID matches the UID specified in the request.
Bit 7 Option flag
Bit 8 RFU
1. If the Select_flag is set to 1, the Address_flag is set to 0 and the UID field is not present in the request.
Bit No.
Bit 5 AFI flag
Bit 6 Nb_slots flag
Bit 7 Option flag
Bit 8 RFU
Flag
Table 13. Request flags 5 to 8 when bit 3 = 1
Level Description
1
0
0
0
1
0
AFI field is not present
AFI field is present
16 slots
-
-
1 slot
DocID12112 Rev 9
LRI2K Response format
The response consists of:
• an SOF
• flags
• parameters and data
• a CRC
• an EOF
Table 14. General response format
S
O
F
Response flags Parameters Data CRC
E
O
F
In a response, the flags indicate how actions have been performed by the LRI2K and whether corresponding fields are present or not. The response flags consist of eight bits.
Bit No.
Flag
Table 15. Definitions of response flags 1 to 8
Level Description
Bit 1 Error_flag
Bit 2 RFU
Bit 3 RFU
Bit 4 Extension flag
Bit 5 RFU
Bit 6 RFU
Bit 7 RFU
Bit 8 RFU
0
0
0
0
0
0
0
0
1
-
-
No error
Error detected. Error code is in the “Error” field.
-
-
-
-
No extension
DocID12112 Rev 9
84
Response format LRI2K
14.2 Response error code
If the Error_flag is set by the LRI2K in the response, the Error code field is present and provides information about the error that occurred.
Error codes not specified in
Table 16 are reserved for future use.
Error code
03h
0F
10h
11h
12h
13h
14h
Table 16. Response error code definition
Meaning
The command option is not supported
Error with no information given or a specific error code is not supported
The specified block is not available (does not exist)
The specified block is already locked and thus cannot be locked again
The specified block is locked and its contents cannot be changed
The specified block was not successfully programmed
The specified block was not successfully locked
DocID12112 Rev 9
LRI2K
15 Anticollision
Anticollision
The purpose of the anticollision sequence is to inventory the LRI2Ks present in the VCD field using their unique ID (UID).
The VCD is the master of communications with one or several LRI2Ks. It initiates LRI2K communication by issuing the Inventory request.
The LRI2K sends its response in the determined slot or does not respond.
When issuing the Inventory command, the VCD:
• sets the Nb_slots_flag as desired,
• adds the mask length and the mask value after the command field,
The mask length is the number of significant bits of the mask value.
The mask value is contained in an integer number of bytes. The mask length indicates the number of significant bits. The LSB is transmitted first.
If the mask length is not a multiple of 8 (bits), as many 0-bits as required will be added to the mask value MSB so that the mask value is contained in an integer number of bytes.
The next field starts on the next byte boundary.
Table 17. Inventory request format
MSB
SOF
-
Request_ flags
8 bits
Command Optional AFI
8 bits 8 bits
Mask length
8 bits
Mask value
0 to 8 bytes
CRC
16 bits
LSB
EOF
-
and Figure 38 , the mask length is 11 bits. Five 0-bits are added
to the mask value MSB. The 11-bit Mask and the current slot number are compared to the
UID.
Table 18. Example of the addition of 0-bits to an 11-bit mask value
(b
15
) MSB
0000 0
0-bits added
100 1100 1111
11-bit mask value
LSB (b
0
)
DocID12112 Rev 9
84
Anticollision LRI2K
Figure 38. Principle of comparison between the mask, the slot number and the UID
Mask value received in the Inventory command
MSB LSB
0000 0100 1100 1111 b 16 bits
MSB LSB
100 1100 1111 b 11 bits The Mask value less the padding 0s is loaded into the Tag comparator
The Slot counter is calculated
Nb_slots_flags = 0 (16 slots), Slot Counter is 4 bits
MSB LSB xxxx 4 bits
The Slot counter is concatened to the Mask value
Nb_slots_flags = 0
MSB LSB xxxx 100 1100 1111 b 15 bits
The concatenated result is compared with the least significant bits of the Tag UID.
b63
UID xxxx xxxx ..... xxxx xxxx x xxx xxxx xxxx xxxx b0 b
64 bits
Bits ignored Compare
AI06682
The AFI field is present if the AFI_flag is set.
The pulse is generated according to the definition of the EOF in ISO/IEC 15693-2.
The first slot starts immediately after the reception of the request EOF. To switch to the next slot, the VCD sends an EOF.
The following rules and restrictions apply:
• if no LRI2K answer is detected, the VCD may switch to the next slot by sending an
EOF,
• if one or more LRI2K answers are detected, the VCD waits until the complete frame has been received before sending an EOF for switching to the next slot.
DocID12112 Rev 9
LRI2K
16
Request processing by the LRI2K
Request processing by the LRI2K
Upon reception of a valid request, the LRI2K performs the following algorithm:
• NbS is the total number of slots (1 or 16)
• SN is the current slot number (0 to 15)
• LSB (value, n) function returns the n Less Significant Bits of value
• MSB (value, n) function returns the n Most Significant Bits of value
• "&" is the concatenation operator
• Slot_Frame is either an SOF or an EOF
SN = 0 if (Nb_slots_flag) then NbS = 1
SN_length = 0 endif else NbS = 16
SN_length = 4 endif label1: if LSB(UID, SN_length + Mask_length) =
LSB(SN,SN_length)&LSB(Mask,Mask_length) then answer to inventory request endif wait (Slot_Frame) if Slot_Frame = SOF then Stop Anticollision decode/process request exit endif if Slot_Frame = EOF if SN < NbS-1 then SN = SN + 1 goto label1 exit endif endif
DocID12112 Rev 9
84
Explanation of the possible cases
17 Explanation of the possible cases
Note:
LRI2K
summarizes the main possible cases that can occur during an anticollision sequence when the slot number is 16.
The different steps are:
• The VCD sends an Inventory request, in a frame terminated by an EOF. The number of slots is 16.
• LRI2K 1 transmits its response in Slot 0. It is the only one to do so, therefore no collision occurs and its UID is received and registered by the VCD;
• The VCD sends an EOF in order to switch to the next slot.
• In slot 1, two LRI2Ks, LRI2K 2 and LRI2K 3 transmit a response, thus generating a collision. The VCD records the event and remembers that a collision was detected in
Slot 1.
• The VCD sends an EOF in order to switch to the next slot.
• In Slot 2, no LRI2K transmits a response. Therefore the VCD does not detect any
LRI2K SOF and decides to switch to the next slot by sending an EOF.
• In slot 3, there is another collision caused by responses from LRI2K 4 and LRI2K 5
• The VCD then decides to send a request (for instance a Read Block) to LRI2K 1 whose
UID has already been correctly received.
• All LRI2Ks detect an SOF and exit the anticollision sequence. They process this request and since the request is addressed to LRI2K 1, only LRI2K 1 transmits a response.
• All LRI2Ks are ready to receive another request. If it is an Inventory command, the slot numbering sequence restarts from 0.
The decision to interrupt the anticollision sequence is made by the VCD. It could have continued to send EOFs until Slot 16 and only then sent the request to LRI2K 1.
DocID12112 Rev 9
Figure 39. Description of a possible anticollision sequence
VCD SOF
Inventory
Request
EOF
Slot 0
EOF
Slot 1
Response
2
EOF
Slot 2 Slot 3
EOF
Response
4
SOF
Request to
LRI2K 1
EOF
LRI2Ks
Timing
Comment
Time t1
Response
1
No collision t2
Response
3
Response
5 t1
Collision t2 t3
No
Response t1
Collision t2 t1
Response from
LRI2K 1
AI12090
Inventory Initiated command LRI2K
The LRI2K provides a special feature to improve the inventory time response of moving tags using the Initiate_flag value. This flag, controlled by the Initiate command, allows tags to answer to Inventory Initiated commands.
For applications in which multiple tags are moving in front of a reader, it is possible to miss tags using the standard inventory command. The reason is that the inventory sequence has to be performed on a global tree search. For example, a tag with a particular UID value may have to wait the run of a long tree search before being inventoried. If the delay is too long, the tag may be out of the field before it has been detected.
Using the Initiate command, the inventory sequence is optimized. When multiple tags are moving in front of a reader, the ones which are within the reader field will be initiated by the
Initiate command. In this case, a small batch of tags will answer to the Inventory Initiated command which will optimize the time necessary to identify all the tags. When finished, the reader has to issue a new Initiate command in order to initiate a new small batch of tags which are new inside the reader field.
It is also possible to reduce the inventory sequence time using the Fast Initiate and Fast
Inventory Initiated commands. These commands allow the LRI2Ks to increase their response data rate by a factor of 2, up to 53kbit/s.
DocID12112 Rev 9
LRI2K Timing definition
19.1 t
1
: LRI2K response delay
Upon detection of the rising edge of the EOF received from the VCD, the LRI2K waits for a time t
1nom
before transmitting its response to a VCD request or before switching to the next slot during an inventory process. Values of t
1
. The EOF is defined in
.
19.2 t
2
: VCD new request delay
t
2
is the time after which the VCD may send an EOF to switch to the next slot when one or more LRI2K responses have been received during an Inventory command. It starts from the reception of the EOF from the LRI2Ks.
The EOF sent by the VCD may be either 10% or 100% modulated regardless of the modulation index used for transmitting the VCD request to the LRI2K.
t
2
is also the time after which the VCD may send a new request to the LRI2K as described in
Table 36: LRI2K protocol timing .
Values of t
2
.
19.3 t
3
: VCD new request delay in absence of a response from the
LRI2K
t
3 is the time after which the VCD may send an EOF to switch to the next slot when no
LRI2K response has been received.
The EOF sent by the VCD may be either 10% or 100% modulated regardless of the modulation index used for transmitting the VCD request to the LRI2K.
From the time the VCD has generated the rising edge of an EOF:
• If this EOF is 100% modulated, the VCD waits a time at least equal to t
3min sending a new EOF.
before
• If this EOF is 10% modulated, the VCD waits a time at least equal to the sum of t
3min the LRI2K nominal response time (which depends on the LRI2K data rate and
+ subcarrier modulation mode) before sending a new EOF.
Value Minimum (min)
Table 19. Timing values
(1)
Nominal (nom) Maximum (max) t t t
1
2
3
318.6 µs
309.2 µs t
1max
(2)
+ t
SOF
(3)
320.9 µs
No t nom
No t nom
323.3 µs
No t
No t max max
1.
The tolerance of specific timings is ± 32/f
C
.
2.
t
1max
does not apply for write alike requests. Timing conditions for write alike requests are defined in the command description.
3. t
SOF
is the time taken by the LRI2K to transmit an SOF to the VCD. t
High data rate or Low data rate.
SOF
depends on the current data rate:
DocID12112 Rev 9
84
Commands codes LRI2K
The LRI2K supports the commands described in this section. Their codes are given in
Command code standard
22h
23h
25h
26h
27h
01h
02h
20h
21h
28h
29h
2Ah
2Bh
2Ch
Inventory
Stay Quiet
Read Single Block
Write Single Block
Lock Block
Read Multiple Block
Select
Reset to Ready
Write AFI
Lock AFI
Write DSFID
Lock DSFID
Get System Info
Get Multiple Block
Security Status
Table 20. Command codes
Function
Command code custom
C1h
C2h
C3h
D1h
D2h
A6h
B1h
B2h
C0h
Function
Kill
Write Kill
Lock Kill
Fast Read Single Block
Fast Inventory Initiated
Fast Initiate
Fast Read Multiple Block
Inventory Initiated
Initiate
DocID12112 Rev 9
LRI2K Commands codes
20.1 Inventory
When receiving the Inventory request, the LRI2K runs the anticollision sequence. The
Inventory_flag is set to 1. The meaning of flags 5 to 8 is shown in
The request contains:
• the flags,
• the Inventory command code (see
• the AFI if the AFI flag is set
• the mask length
• the mask value
• the CRC
The LRI2K does not generate any answer in case of error.
Request
SOF
Request flags
Table 21. Inventory request format
Inventory
Optional
AFI
Mask length
Mask value
8 bits 01h 8 bits 8 bits 0 - 64 bits
CRC16
16 bits
Request
EOF
-
The response contains:
• the flags
• the Unique ID
Table 22. Inventory response format
Response
SOF
Response flags
8 bits
DSFID
8 bits
UID
64 bits
CRC16
16 bits
Response
EOF
-
During an Inventory process, if the VCD does not receive an RF LRI2K response, it waits a time t
3
before sending an EOF to switch to the next slot. t
3
starts from the rising edge of the request EOF sent by the VCD.
• If the VCD sends a 100% modulated EOF, the minimum value of t
3
is: t
3 min = 4384/f
C
(323.3µs) + t
SOF
• If the VCD sends a 10% modulated EOF, the minimum value of t
3
is: t
3 min = 4384/f
C
(323.3µs) + t
NRT where:
• t
SOF
is the time required by the LRI2K to transmit an SOF to the VCD
• t
NRT
is the nominal response time of the LRI2K t
NRT
and t
SOF
are dependent on the LRI2K-to-VCD data rate and subcarrier modulation mode.
DocID12112 Rev 9
84
Commands codes LRI2K
On receiving the Stay Quiet command, the LRI2K enters the Quiet state and does NOT send back a response. There is NO response to the Stay Quiet command even if an error occurs.
When in the Quiet state:
• the LRI2K does not process any request if the Inventory_flag is set,
• the LRI2K processes any Addressed request
The LRI2K exits the Quiet state when:
• it is reset (power off),
• receiving a Select request. It then goes to the Selected state,
• receiving a Reset to Ready request. It then goes to the Ready state.
Table 23. Stay Quiet request format
Request
SOF
-
Request flags
8 bits
Stay Quiet
02h
UID
64 bits
CRC16
16 bits
Request
EOF
-
The Stay Quiet command must always be executed in the Addressed mode (Select_flag is reset to 0 and Address_flag is set to 1).
Figure 40. Stay Quiet frame exchange between VCD and LRI2K
VCD
LRI2K
Timing
SOF
Stay Quiet request
EOF
DocID12112 Rev 9
LRI2K Commands codes
20.3 Read Single Block
On receiving the Read Single Block command, the LRI2K reads the requested block and sends back its 32 bits value in the response. The Option_flag is supported.
Request
SOF
-
Table 24. Read Single Block request format
Request_flags
Read
Single
Block
UID
Block number
CRC16
8 bits 20h 64 bits 8 bits 16 bits
Request
EOF
-
Request parameters:
• Option_flag
• UID (Optional)
• Block number
Table 25. Read Single Block response format when Error_flag is NOT set
Response
SOF
Response_ flags
Block locking status
Data CRC16
Response
EOF
8 bits 8 bits 32 bits 16 bits -
Response parameter:
•
Block Locking Status if Option_flag is set (see Table 26
)
• 4 bytes of block data b
7 b
6 b
5 b
4
All 0
Table 26. Block Locking status b
3 b
2 b
1 b
0
0: Current Block not locked
1: Current Block locked
Table 27. Read Single Block response format when Error_flag is set
Response SOF
Response_
Flags
Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 0Fh: other error
– 10h: block address not available
DocID12112 Rev 9
84
Commands codes
Figure 41. READ Single Block frame exchange between VCD and LRI2K
LRI2K
VCD
LRI2K
SOF
Read Single
Block request
EOF
<-t
1
-> SOF
Read Single
Block response
EOF
DocID12112 Rev 9
LRI2K Commands codes
On receiving the Write Single Block Command, the LRI2K writes the data contained in the request to the requested block and reports whether the write operation was successful in the response. The Option_flag is supported.
During the write cycle t
W
, there should be no modulation (neither 100% nor 10%).
Otherwise, the LRI2K may not program correctly the data into the memory. The t
W equal to t
1nom
+ 18 × 302µs.
time is
Request
SOF
Request_ flags
8 bits
Table 28. Write Single Block request format
Write
Single
Block
UID
Block number
Data
21h 64 bits 8 bits 32 bits
CRC16
Request
EOF
16 bits -
Request parameters:
• UID (Optional)
• Block number
• Data
Table 29. Write Single Block response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
Response parameter:
• No parameter. The response is sent back after the write cycle.
Table 30. Write Single Block response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 10h: block address not available
– 12h: block is locked
– 13h: block not programmed
DocID12112 Rev 9
84
Commands codes
LRI2K
LRI2K
VCD
LRI2K
Figure 42. Write Single Block frame exchange between VCD and LRI2K
SOF
Write Single
Block request
EOF
<-t
1
-> SOF
Write Single
Block response
EOF Write sequence when error
<------------ t
W
------------><- t
1
-> SOF
Write Single
Block response
EOF
On receiving the Lock Block command, the LRI2K permanently locks the selected block.
The Option_flag is supported.
During the write cycle t
W
, there should be no modulation (neither 100% nor 10%).
Otherwise, the LRI2K may not lock correctly the memory block. The t
W
+ 18 × 302µs.
time is equal to t
1nom
Request
SOF
Request_ flags
8 bits
Table 31. Lock Single Block request format
Lock Block UID
Block number
CRC16
22h 64 bits 8 bits 16 bits
Request
EOF
-
Request parameters:
• (Optional) UID
• Block number
Table 32. Lock Block response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
Response parameter:
• No parameter.
Table 33. Lock Block response format when Error_flag is set
Response
SOF
Response_flags Error code CRC16
8 bits 8 bits 16 bits
Response
EOF
-
DocID12112 Rev 9
LRI2K Commands codes
Response parameter:
• Error code as Error_flag is set:
– 10h: block address not available
– 11h: block is locked
– 14h: block not locked
Figure 43. Lock Block frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Lock Block request
EOF
<-t
1
-> SOF
Lock Block response
EOF
Lock sequence when error
LRI2K <------------ t
W
------------><- t
1
-> SOF
Lock Block response
EOF
20.6 Read Multiple Block
When receiving the Read Multiple Block command, the LRI2K reads the selected blocks and sends back their value in multiples of 32 bits in the response. The blocks are numbered from '00 to '3F' in the request and the value is minus one (–1) in the field. For example, if the
“number of blocks” field contains the value 06h, 7 blocks will be read. The maximum number of blocks is fixed at 64. During Sequential Block Read, when the block address reaches 64, it rolls over to 0. The Option_flag is supported.
Request
SOF
Request_ flags
Table 34. Read Multiple Block request format
Read
Multiple
Block
UID
First block number
Number of blocks
8 bits 23h 64 bits 8 bits 8 bits
CRC16
16 bits
Request
EOF
-
Request parameters:
• Option_flag
• UID (Optional)
• First block number
• Number of blocks
Response
SOF
-
Table 35. Read Multiple Block response format when Error_flag is NOT set
Response
_flags
8 bits
Block Locking
Status
8 bits
(1)
Data
32 bits
(1)
CRC16
16 bits
Response
EOF
-
1. Repeated as needed.
DocID12112 Rev 9
84
Commands codes
Response parameter:
•
Block Locking Status if Option_flag is set (see Table 36
)
• N blocks of data b
7 b
6 b
5 b
4
All 0
Table 36. Block Locking status b
3 b
2 b
1 b
0
0: Current Block not locked
1: Current Block locked
LRI2K
Table 37. Read Multiple Block response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 0Fh: other error
– 10h: block address not available
Figure 44. Read Multiple Block frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Read Multiple
Block request
EOF
<-t
1
-> SOF
Read Multiple
Block response
EOF
DocID12112 Rev 9
LRI2K Commands codes
20.7 Select
When receiving the Select command:
• if the UID is equal to its own UID, the LRI2K enters or stays in the Selected state and sends a response.
• if the UID does not match its own, the selected LRI2K returns to the Ready state and does not send a response.
The LRI2K answers an error code only if the UID is equal to its own UID. If not, no response is generated.
Request
SOF
Request_ flags
8 bits
Select
25h
Table 38. Select request format
UID
64 bits
CRC16
16 bits
Request
EOF
-
Request parameter:
• UID
Table 39. Select Block response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
Response parameter:
• No parameter.
Table 40. Select response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 0Fh: other error
Figure 45. Select frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Select request
EOF
<-t
1
-> SOF
Select response
EOF
DocID12112 Rev 9
84
Commands codes LRI2K
20.8 Reset to Ready
On receiving a Reset to Ready command, the LRI2K returns to the Ready state. In the
Addressed mode, the LRI2K answers an error code only if the UID is equal to its own UID. If not, no response is generated.
Table 41. Reset to Ready request format
Request
SOF
Request_ flags
8 bits
Reset to Ready
26h
UID
64 bits
CRC16
16 bits
Request
EOF
-
Request parameter:
• UID (Optional)
Table 42. Reset to Ready response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
Response parameter:
• No parameter.
Table 43. Reset to ready response format when Error_flag is set
Response SOF
Response_ flags
Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 0Fh: other error
Figure 46. Reset to Ready frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Reset to Ready request
EOF
<-t
1
-> SOF
Reset to Ready response
EOF
DocID12112 Rev 9
LRI2K Commands codes
On receiving the Write AFI request, the LRI2K writes the AFI byte value into its memory. The
Option_flag is supported.
During the write cycle t
W
, there should be no modulation (neither 100% nor 10%).
Otherwise, the LRI2K may not write correctly the AFI value into the memory. The t
W equal to t
1nom
+ 18 × 302µs.
time is
Table 44. Write AFI request format
Request
SOF
Request
_flags
8 bits
Write AFI
27h
UID
64 bits
AFI
8 bits
CRC16
16 bits
Request
EOF
-
Request parameters:
• UID (Optional)
• AFI
Table 45. Write AFI response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
Response parameter:
• No parameter.
Table 46. Write AFI response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 12h: block is locked
– 13h: block not programmed
DocID12112 Rev 9
84
Commands codes LRI2K
Figure 47. Write AFI frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Write AFI request
EOF
<-t
1
-> SOF
Write AFI response
EOF
Write sequence when error
LRI2K
<------------ t
W
------------><- t
>
1
-
SOF
Write AFI response
EOF
On receiving the Lock AFI request, the LRI2K locks the AFI value permanently. The
Option_flag is supported.
During the write cycle t
W
, there should be no modulation (neither 100% nor 10%).
Otherwise, the LRI2K may not Lock correctly the AFI value in memory. The t
W to t
1nom
+ 18 × 302 µs.
time is equal
Table 47. Lock AFI request format
Request SOF
Request_ flags
8 bits
Lock AFI
28h
UID
64 bits
CRC16
16 bits
Request EOF
-
Request parameter:
• UID (Optional)
Table 48. Lock AFI response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
Response parameter:
• No parameter.
Table 49. Lock AFI response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
DocID12112 Rev 9
LRI2K Commands codes
Response parameter:
• Error code as Error_flag is set:
– 11h: block is locked
– 14h: block not locked
Figure 48. Lock AFI frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Lock AFI request
EOF
<-t
1
-> SOF
Lock AFI response
EOF
Lock sequence when error
LRI2K <------------ t
W
------------><- t
1
-> SOF
Lock AFI response
EOF
On receiving the Write DSFID request, the LRI2K writes the DSFID byte value into its memory. The Option_flag is supported.
During the write cycle t
W
, there should be no modulation (neither 100% nor 10%).
Otherwise, the LRI2K may not write correctly the DSFID value in memory. The t
W equal to t
1nom
+ 18 × 302µs.
time is
Request
SOF
Request_ flags
8 bits
Table 50. Write DSFID request format
Write
DSFID
UID DSFID
29h 64 bits 8 bits
CRC16
16 bits
Request
EOF
-
Request parameters:
• UID (Optional)
• DSFID
Table 51. Write DSFID response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
Response parameter:
• No parameter.
DocID12112 Rev 9
84
Commands codes LRI2K
Table 52. Write DSFID response format when Error_flag is set
Response SOF
Response_ flags
Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 12h: block is locked
– 13h: block not programmed
Figure 49. Write DSFID frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Write
DSFID request
EOF
<-t
1
-> SOF
Write DSFID response
EOF
Write sequence when error
LRI2K <------------ t
W
------------><- t
1
-> SOF
Write DSFID response
EOF
On receiving the Lock DSFID request, the LRI2K locks the DSFID value permanently. The
Option_flag is supported.
During the write cycle t
W
, there should be no modulation (neither 100% nor 10%).
Otherwise, the LRI2K may not lock correctly the DSFID value in memory. The t
W equal to t
1nom
+ 18 × 302µs.
time is
Table 53. Lock DSFID request format
Request SOF
Request_ flags
8 bits
Lock DSFID
2Ah
UID
64 bits
CRC16
16 bits
Request EOF
-
Request parameter:
• UID (Optional)
Table 54. Lock DSFID response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
DocID12112 Rev 9
LRI2K Commands codes
Response parameter:
• No parameter.
Table 55. Lock DSFID response format when Error_flag is set
Response SOF
Response_ flags
Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 11h: block is locked
– 14h: block not locked
Figure 50. Lock DSFID frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Lock
DSFID request
EOF
<-t
1
-> SOF
Lock DSFID response
EOF
Lock sequence when error
LRI2K <------------ t
W
------------><- t
1
-> SOF
Lock DSFID response
EOF
When receiving the Get System Info command, the LRI2K sends back its information data in the response.The Option_flag is supported and must be reset to 0. The Get System Info can be issued in both Addressed and Non Addressed modes.
Request SOF
Table 56. Get System Info request format
Request_ flags
Get System
Info
UID CRC16
8 bits 2Bh 64 bits 16 bits
Request EOF
-
Request parameter:
• UID (Optional)
Table 57. Get System Info response format when Error_flag is NOT set
Response
SOF
Response_ flags
Information flags
UID DSFID AFI
Memory size
IC reference
CRC16
Response
EOF
00h 0Fh 64 bits 8 bits 8 bits 033Fh 001000xx b
16 bits -
DocID12112 Rev 9
84
Commands codes LRI2K
Response parameters:
• Information Flags set to 0Fh. DSFID, AFI, Memory Size and IC reference fields are present.
• UID code on 64 bits
• DSFID value
• AFI value
• memory size. The LRI2K provides 64 blocks (3Fh) of 4 bytes (03h).
• IC Reference. Only the 6 MSBs are significant. The product code of the LRI2K is
00 1000 b
=8 d
Table 58. Get System Info response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
01h 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 03h: Option not supported
– 0Fh: other error
Figure 51. Get System Info frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Get System
Info request
EOF
<-t
1
-> SOF
Get System
Info response
EOF
When receiving the Get Multiple Block Security Status command, the LRI2K sends back the block security status. The blocks are numbered from '00 to '3F' in the request and the value is minus one (–1) in the field. For example, a value of '06' in the "Number of blocks" field requests to return the security status of 7 Blocks.
Table 59. Get Multiple Block Security Status request format
Request
SOF
Request_ flags
Get Multiple
Block Security
Status
UID
First block number
Number of blocks
CRC16
8 bits 2Ch 64 bits 8 bits 8 bits 16 bits
Request
EOF
-
DocID12112 Rev 9
LRI2K Commands codes
Request parameters:
• UID (Optional)
• First block number
• Number of blocks
Table 60. Get Multiple Block Security Status response format when Error_flag is NOT set
Response SOF Response_flags
Block Locking
Status
CRC16 Response EOF
8 bits 8 bits
(1)
16 bits -
1. Repeated as needed.
Response parameters:
• Block Locking Status (see
• N block of data b
7 b
6 b
5 b
4
All 0
Table 61. Block Locking status b
3 b
2 b
1 b
0
0: Current block not locked
1: Current block locked
Table 62. Get Multiple Block Security Status response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 03h: Option not supported
– 0Fh: other error
Figure 52. Get Multiple Block Security Status frame exchange between VCD and
LRI2K
VCD
LRI2K
SOF
Get Multiple
Block
Security
Status
EOF
<-t
1
-> SOF
Get Multiple
Block Security
Status
EOF
DocID12112 Rev 9
84
Commands codes LRI2K
20.15 Kill
On receiving the Kill command, in the Addressed mode only, the LRI2K compares the kill code with the data contained in the request and reports whether the operation was successful in the response. The Option_flag is supported. If the command is received in the
Non Addressed or the Selected mode, the LRI2K returns an error response.
t
During the comparison cycle equal to t
W
, there should be no modulation (neither 100% nor
10%). Otherwise, the LRI2K may not match the kill code correctly. The t
W
1nom interpret any other command.
time is equal to
+ 18 × 302µs. After a successful Kill command, the LRI2K is deactivated and does not
Request
SOF
Request_ flags
8 bits
Kill
A6h
Table 63. Kill request format
IC Mfg code
UID
Kill access
02h 64 bits 00h
Kill code CRC16
Request
EOF
32 bits 16 bits -
Request parameters:
• UID (Optional)
• Kill Code
Table 64. Kill response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
Response parameter:
• No parameter. The response is send back after the writing cycle
Table 65. Kill response format when Error_flag is set
Response SOF Response_flags Error code CRC16
8 bits 8 bits 16 bits
Response EOF
-
Response parameter:
• Error code as Error_flag is set:
– 0Fh: other error
– 14h: block not locked
DocID12112 Rev 9
LRI2K Commands codes
Figure 53. Kill frame exchange between VCD and LRI2K
VCD
LRI2K
SOF Kill request EOF
<-t
1
-> SOF Kill response EOF
Kill sequence when error
LRI2K <------------ t
W
------------><- t
1
-> SOF Kill response EOF
On receiving the Write Kill command, the LRI2K writes the kill code with the data contained in the request and reports whether the operation was successful in the response. The
Option_flag is supported. After a successful write, the kill code must be locked by a Lock Kill command to activate the protection.
During the write cycle t
W
, there should be no modulation (neither 100% nor 10%).
Otherwise, the LRI2K may not correctly program the data to the memory. The t
W equal to t
1nom
+ 18 × 302 µs.
time is
Request
SOF
Request_ flags
8 bits
Write
Kill
Table 66. Write Kill request format
IC Mfg code
UID
Kill access
Kill code CRC16
Request
EOF
B1h 02h 64 bits 00h 32 bits 16 bits -
Request parameters:
• UID (Optional)
• Kill Address (00h = Kill, other = Error)
• Data
Table 67. Write Kill response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
No parameter. The response is send back after the write cycle.
Table 68. Write Kill response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
DocID12112 Rev 9
84
Commands codes
Response parameter:
• Error code as Error_flag is set:
– 10h: block address not available
– 12h: block is locked
– 13h: block not programmed
Figure 54. Write Kill frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Write Kill request
EOF
<-t
1
-> SOF
LRI2K
Write Kill response
EOF
Write sequence when error
LRI2K <------------ t
W
------------><- t
1
-> SOF
Write Kill response
EOF
On receiving the Lock Kill command, the LRI2K locks the Kill code permanently. The
Option_flag is supported. RFU bit 8 of the request flag must be set to ‘1’.
During the write cycle t
W
, there should be no modulation (neither 100% nor 10%). t
Otherwise, the LRI2K may not lock the memory block correctly. The t
W
1nom
+ 18 × 302 µs.
time is equal to
Request
SOF
Request_ flags
8 bits
Lock
Kill
Table 69. Lock Kill request format
IC Mfg code
UID
Kill access
Protect
Status
CRC16
Request
EOF
B2h 02h 64 bits 00f 8 bits 16 bits -
Request parameters:
• (Optional) UID
• Kill Address (bit 8 = ‘1’: 00h = KILL, other = Error)
• Protect status (see table below) b
7
0 b
6
0 b
5
0 b
4
0 b
3
0 b
2
0 b
1
0 b
0
1
Table 70. Lock Kill response format when Error_flag is NOT set
Response SOF Response_flags CRC16 Response EOF
8 bits 16 bits -
DocID12112 Rev 9
LRI2K Commands codes
Response parameter:
• No parameter.
Table 71. Lock Kill response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 10h: block address not available
– 11h: block is locked
– 14h: block not locked
Figure 55. Lock Kill frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Lock Kill request
EOF
<-t
1
-> SOF
Lock Kill response
EOF
Lock sequence when error
LRI2K <------------ t
W
------------><- t
1
-> SOF
Lock Kill response
EOF
DocID12112 Rev 9
84
Commands codes LRI2K
20.18 Fast Read Single Block
On receiving the Fast Read Single Block command, the LRI2K reads the requested block and sends back its 32-bit value in the response. The Option_flag is supported. The data rate of the response is multiplied by 2.
Request
SOF
Table 72. Fast Read Single Block request format
Request_ flags
Fast Read
Single
Block
IC Mfg code
UID
Block number
CRC16
8 bits C0h 02h 64 bits 8 bits 16 bits
Request
EOF
-
Request parameters:
• Option_flag
• UID (Optional)
• Block number
Table 73. Fast Read Single Block response format when Error_flag is NOT set
Response
SOF
Response_ flags
Block locking status
Data CRC16
Response
EOF
8 bits 8 bits 32 bits 16 bits -
Response parameter:
• Block Locking Status if Option_flag is set
• 4 bytes of Block Data b
7 b
6 b
5
Table 74. Block Locking status b
4
All 0 b
3 b
2 b
1 b
0
0: Current Block not locked
1: Current Block locked
Table 75. Fast Read Single Block response format when Error_flag is set
Response SOF
Response_ flags
Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
Response parameter:
• Error code as Error_flag is set:
– 0Fh: other error
– 10h: block address not available
DocID12112 Rev 9
LRI2K Commands codes
Figure 56. Fast Read Single Block frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Fast Read Single
Block request
EOF
<-t
1
-> SOF
Fast Read Single
Block response
EOF
DocID12112 Rev 9
84
Commands codes LRI2K
20.19 Fast Inventory Initiated
Before receiving the Fast Inventory Initiated command, the LRI2K must have received an
Initiate or a Fast Initiate command in order to set the Initiate_ flag. If not, the LRI2K does not answer to the Fast Inventory Initiated command.
On receiving the Fast Inventory Initiated request, the LRI2K runs the anticollision sequence.
The Inventory_flag must be set to 1. The Meaning of Flags 5 to 8 is shown in
data rate of the response is multiplied by 2.
The request contains:
• the flags,
• the Inventory command code
• the AFI if the AFI flag is set
• the mask length
• the mask value
• the CRC
The LRI2K does not generate any answer if an error occurs.
Table 76. Fast Inventory Initiated request format
Request
SOF
Request
Flags
Fast
Inventory
Initiated
IC Mfg
Code
Optional
AFI
Mask length
Mask value CRC16
8 bits C1h 02h 8 bits 8 bits 0 - 64 bits 16 bits
Request
EOF
-
The response contains:
• The flags
• the Unique ID
Table 77. Fast Inventory Initiated response format
Response SOF Response Flags DSFID UID CRC16 Response EOF
8 bits 00h 64 bits 16 bits -
During an Inventory process, if the VCD does not receive an RF LRI2K response, it waits a time t
3
before sending an EOF to switch to the next slot. t
3
starts from the rising edge of the request EOF sent by the VCD.
• If the VCD sends a 100% modulated EOF, the minimum value of t
3
is: t
3 min = 4384/f
C
(323.3 µs) + t
SOF
• If the VCD sends a 10% modulated EOF, the minimum value of t
3
is: t
3 min = 4384/f
C
(323.3 µs) + t
NRT where:
• t
SOF
is the time required by the LRI2K to transmit an SOF to the VCD
• t
NRT
is the nominal response time of the LRI2K t
NRT
and t
SOF
are dependent on the LRI2K-to-VCD data rate and subcarrier modulation mode.
DocID12112 Rev 9
LRI2K Commands codes
On receiving the Fast Initiate command, the LRI2K sets the internal Initiate_flag and sends back a response. The command has to be issued in the Non Addressed mode only
(Select_flag is reset to 0 and Address_flag is reset to 0). If an error occurs, the LRI2K does not generate any answer. The Initiate_flag is reset after a power off of the LRI2K. The data rate of the response is multiplied by 2.
The request contains:
• No data
Table 78. Fast Initiate request format
Request SOF Request Flags Fast Initiate IC Mfg code CRC16
8 bits C2h 02h 16 bits
Request EOF
-
The response contains:
• the flags
• the Unique ID
Table 79. Fast Initiate response format
Response
SOF
Response_ flags
DSFID UID
8 bits 00h 64 bits
CRC16
16 bits
Response
EOF
-
Figure 57. Fast Initiate frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Fast Initiate request
EOF
<-t
1
-> SOF
Fast Initiate response
EOF
DocID12112 Rev 9
84
Commands codes LRI2K
20.21 Fast Read Multiple Block
On receiving the Fast Read Multiple Block command, the LRI2K reads the requested blocks and sends back their value in multiples of 32 bits in the response. The blocks are numbered from '00’ to '3F' in the request and the value is minus one (–1) in the field. For example, a value 06h in the “number of blocks” field causes the LRI2K to read 7 blocks. The maximum number of blocks is fixed at 64. During Sequential Block Read, when the block address reaches 64, it rolls over to 0. The Option_flag is supported. The data rate of the response is multiplied by 2.
Table 80. Fast Read Multiple Block request format
Request
SOF
Request_ flags
Fast Read
Multiple
Block
IC Mfg code
UID
First block number
Number of blocks
CRC16
8 bits C3h 02h 64 bits 8 bits 8 bits 16 bits
Request
EOF
-
Request parameters:
• Option_flag
• UID (Optional)
• First block number
• Number of blocks
Table 81. Fast Read Multiple Block response format when Error_flag is NOT set
Response
SOF
Response_flags
8 bits
1. Repeated as needed.
Block Locking
Status
8 bits
(1)
Data
32 bits
(1)
CRC16
16 bits
Response
EOF
-
Response parameters:
• Block Locking Status if Option_flag is set
• N block of data b
7 b
6
Table 82. Block Locking status if Option_flag is set b
5 b
4
All 0 b
3 b
2 b
1 b
0
0: Current block not locked
1: Current block locked
Table 83. Fast Read Multiple Block response format when Error_flag is set
Response SOF Response_flags Error code CRC16 Response EOF
8 bits 8 bits 16 bits -
DocID12112 Rev 9
LRI2K Commands codes
Response parameter:
• Error code as Error_flag is set:
– 0Fh: other error
– 10h: block address not available
Figure 58. Fast Read Multiple Block frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Fast Read
Multiple
Block request
EOF
<-t
1
-> SOF
Fast Read
Multiple Block response
EOF
DocID12112 Rev 9
84
Commands codes LRI2K
Before receiving the Inventory Initiated command, the LRI2K must have received an Initiate or a Fast Initiate command in order to set the Initiate_ flag. If not, the LRI2K does not answer to the Inventory Initiated command.
On receiving the Inventory Initiated request, the LRI2K runs the anticollision sequence. The
Inventory_flag must be set to 1. The Meaning of Flags 5 to 8 is given in
Table 13: Request flags 5 to 8 when bit 3 = 1
.
The request contains:
• the flags,
• the Inventory command code
• the AFI if the AFI flag is set
• the mask length
• the mask value
• the CRC
The LRI2K does not generate any answer if an error occurs.
Table 84. Inventory Initiated request format
Request
SOF
Request
Flags
Inventory
Initiated
IC Mfg code
Optiona l AFI
Mask length
Mask value CRC16
8 bits D1h 02h 8 bits 8 bits 0 - 64 bits 16 bits
Request
EOF
-
The response contains:
• the flags
• the Unique ID
Response
SOF
Response
Flags
Table 85. Inventory Initiated response format
DSFID UID CRC16
8 bits 00h 64 bits 16 bits
Response
EOF
-
During an Inventory process, if the VCD does not receive an RF LRI2K response, it waits a time t
3
before sending an EOF to switch to the next slot. t
3
starts from the rising edge of the request EOF sent by the VCD.
• If the VCD sends a 100% modulated EOF, the minimum value of t
3
is: t
3 min = 4384/f
C
(323.3 µs) + t
SOF
• If the VCD sends a 10% modulated EOF, the minimum value of t
3
is: t
3 min = 4384/f
C
(323.3 µs) + t
NRT where:
• t
SOF
is the time required by the LRI2K to transmit an SOF to the VCD
• t
NRT
is the nominal response time of the LRI2K t
NRT
and t
SOF
are dependent on the LRI2K-to-VCD data rate and subcarrier modulation mode.
DocID12112 Rev 9
LRI2K Commands codes
20.23 Initiate
On receiving the Initiate command, the LRI2K sets the internal Initiate_flag and sends back a response. The command has to be issued in the Non Addressed mode only (Select_flag is reset to 0 and Address_flag is reset to 0). If an error occurs, the LRI2K does not generate any answer. The Initiate_flag is reset after a power off of the LRI2K.
The request contains:
• No data
Table 86. Initiate request format
Request SOF Request Flags Initiate IC Mfg code CRC16
8 bits D2h 02h 16 bits
Request EOF
-
The response contain:
• the flags
• the Unique ID
Response
SOF
Response
Flags
Table 87. Initiate Initiated response format
DSFID UID CRC16
8 bits 00h 64 bits 16 bits
Response
EOF
-
Figure 59. Initiate frame exchange between VCD and LRI2K
VCD
LRI2K
SOF
Initiate request
EOF
<-t
1
-> SOF
Initiate response
EOF
DocID12112 Rev 9
84
Maximum ratings LRI2K
Stressing the device above the rating listed in the absolute maximum ratings table may cause permanent damage to the device. These are stress ratings only and operation of the device at these or any other conditions above those indicated in the operating sections of this specification is not implied. Exposure to absolute maximum rating conditions for extended periods may affect device reliability.
Symbol
T
STG
t
STG
I
CC
V
MAX
V
ESD
Table 88. Absolute maximum ratings
Parameter Min.
Max.
Storage temperature
Storage time
Wafer
(kept in its antistatic bag)
Wafer
(kept in its antistatic bag)
15
-
25
6
Supply current on AC0 / AC1
Input voltage on AC0 / AC1
-
-
–20
–7
20
7
Electrostatic discharge voltage Human Body Model (HBM) –1000 1000
Unit
°C months mA
V
V
DocID12112 Rev 9
LRI2K
22
DC and AC parameters
DC and AC parameters
This section summarizes the operating and measurement conditions, and the DC and AC characteristics of the device. The parameters in the DC and AC Characteristic tables that follow are derived from tests performed under the Measurement Conditions summarized in the relevant tables. Designers should check that the operating conditions in their circuit match the measurement conditions when relying on the quoted parameters.
Symbol
Table 89. AC characteristics (1) (2)
Parameter Condition Min Typ Max Unit f
CC
MI
CARRIER t
RFR
, t
RFF t
RFSBL
MI
CARRIER t
RFR
, t
RFF t
RFSBL t
JIT t
MIN CD
External RF signal frequency
10% carrier modulation index
10% rise and fall time
10% minimum pulse width for bit
100% carrier modulation index
100% rise and fall time
100% minimum pulse width for bit
Bit pulse jitter
Minimum time from carrier generation to first data
-
MI=(A-B)/(A+B)
-
-
MI=(A-B)/(A+B)
-
-
-
From H-field min
13.553 13.56 13.567 MHz
10
0.5
7.1
95
0.5
7.1
–2
-
-
-
-
-
-
-
-
0.1
30
3.0
9.44
100
3.5
9.44
+2
1
%
µs
µs
%
µs
µs
µs ms f
SH f
SL t
1 t
2 t
W
Subcarrier frequency high
Subcarrier frequency low
Time for LRI2K response
Time between command
Programming time
F
F
CC
CC
/32
/28
4224/F
4224/F
-
S
S
-
-
318.6
309
-
423.75
484.28
320.9
311.5
-
-
-
323.3
314
5.8
1. T
A
= –20 to 85°C.
2. All timing measurements were performed on a reference antenna with the following characteristics:
External size: 75 mm x 48 mm
Number of turns: 6
Width of conductor: 1 mm
Space between 2 conductors: 0.4 mm
Value of the tuning capacitor: 28.5 pF
Value of the coil: 4.3 µH
Tuning frequency: 13.8 MHz.
kHz kHz
µs
µs ms
DocID12112 Rev 9
84
DC and AC parameters LRI2K
Symbol
V
CC
V
RET
I
CC
C
TUN
Parameter
Table 90. DC characteristics (1)
Regulated voltage
Retromodulated induced voltage
Supply current
Read
Write
Internal tuning capacitor
Test conditions
-
ISO10373-7
V
CC
= 3.0 V f = 13.56 MHz for SBN18
Min.
Typ.
Max. Unit
-
-
1.5
10
-
-
-
-
-
-
21
97
3.0
50
150
-
-
-
V mV
µA
µA pF pF
1. T
A
= –20 to 85°C.
Symbol
T
A
Table 91. Operating conditions
Parameter Min.
Ambient operating temperature –20
Max.
85
Unit
°C
Figure 60. LRI2K synchronous timing, transmit and receive
A B tRFF tRFR fCC tRFSBL tMAX tMIN CD
AI06680
shows an ASK modulated signal, from the VCD to the LRI2K. The test condition for the AC/DC parameters are:
• Close coupling condition with tester antenna (1mm)
• LRI2K performance measured at the tag antenna
DocID12112 Rev 9
LRI2K Part numbering
Example:
Table 92. Ordering information scheme
LRI2K - SBN18/ 1 GE
Device type
LRI2K
Package
SBN18 = 180 µm ± 15 µm bumped and sawn wafer on 8-inch frame
Tuning capacitance
1 = 21 pF
3 = 97 pF
Customer code given by ST
GE = generic product xx = customer code after personalization
For further information on any aspect of this device, please contact your nearest ST sales office.
DocID12112 Rev 9
84
Anticollision algorithm (informative)
Appendix A Anticollision algorithm (informative)
LRI2K
The following pseudocode describes how anticollision could be implemented on the VCD, using recursivity.
A.1 Algorithm for pulsed slots
function push (mask, address); pushes on private stack function pop (mask, address); pops from private stack function pulse_next_pause; generates a power pulse function store( LRI2K _UID); stores LRI2K _UID function poll_loop (sub_address_size as integer) pop (mask, address) mask = address & mask; generates new mask
; send the request mode = anticollision send_request (Request_cmd, mode, mask length, mask value) for sub_address = 0 to (2^sub_address_size - 1) pulse_next_pause if no_collision_is_detected ; LRI2K is inventoried then store (LRI2K_UID) else ; remember a collision was detected push(mask,address) endif next sub_address if stack_not_empty ; if some collisions have been detected and then ; not yet processed, the function calls itself poll_loop (sub_address_size); recursively to process the last stored collision endif end poll_loop main_cycle: mask = null address = null push (mask, address) poll_loop(sub_address_size) end_main_cycle
DocID12112 Rev 9
LRI2K
Appendix B CRC (informative)
B.1
CRC (informative)
CRC error detection method
The cyclic redundancy check (CRC) is calculated on all data contained in a message, from the start of the Flags through to the end of Data. The CRC is used from VCD to LRI2K and from LRI2K to VCD.
CRC type Length
ISO/IEC 13239 16 bits
Table 93. CRC definition
CRC definition
Polynomial
X
16
+ X
12
+ X
5
+ 1 = 8408h
Direction Preset
Backward FFFFh
Residue
F0B8h
To add extra protection against shifting errors, a further transformation on the calculated
CRC is made. The one’s complement of the calculated CRC is the value attached to the message for transmission.
To check received messages the 2 CRC bytes are often also included in the re-calculation, for ease of use. In this case, the expected value for the generated CRC is the residue
F0B8h.
B.2 CRC calculation example
This example in C language illustrates one method of calculating the CRC on a given set of bytes comprising a message.
C-Example to calculate or check the CRC16 according to ISO/IEC 13239
#define POLYNOMIAL8408h// x^16 + x^12 + x^5 + 1
#define PRESET_VALUEFFFFh
#define CHECK_VALUEF0B8h
#define NUMBER_OF_BYTES4// Example: 4 data bytes
#define CALC_CRC1
#define CHECK_CRC0 void main()
{
unsigned int current_crc_value;
unsigned char array_of_databytes[NUMBER_OF_BYTES + 2] = {1, 2, 3, 4, 91h,
39h};
int number_of_databytes = NUMBER_OF_BYTES;
int calculate_or_check_crc;
int i, j;
calculate_or_check_crc = CALC_CRC;
// calculate_or_check_crc = CHECK_CRC;// This could be an other example
DocID12112 Rev 9
84
CRC (informative) LRI2K
if (calculate_or_check_crc == CALC_CRC)
{
number_of_databytes = NUMBER_OF_BYTES;
}
else // check CRC
{
number_of_databytes = NUMBER_OF_BYTES + 2;
}
current_crc_value = PRESET_VALUE;
for (i = 0; i < number_of_databytes; i++)
{
current_crc_value = current_crc_value ^ ((unsigned int)array_of_databytes[i]);
for (j = 0; j < 8; j++)
{
if (current_crc_value & 0001h)
{
current_crc_value = (current_crc_value >> 1) ^ POLYNOMIAL;
}
else
{
current_crc_value = (current_crc_value >> 1);
}
}
}
if (calculate_or_check_crc == CALC_CRC)
{
current_crc_value = ~current_crc_value;
printf ("Generated CRC is 0x%04X\n", current_crc_value);
// current_crc_value is now ready to be appended to the data stream
// (first LSByte, then MSByte)
}
else // check CRC
{
if (current_crc_value == CHECK_VALUE)
{
printf ("Checked CRC is ok (0x%04X)\n", current_crc_value);
}
else
DocID12112 Rev 9
LRI2K CRC (informative)
{
printf ("Checked CRC is NOT ok (0x%04X)\n", current_crc_value);
}
}
}
The AFI (application family identifier) represents the type of application targeted by the VCD and is used to extract from all the LRI2K present only the one meeting the required application criteria. It is programmed by the LRI2K issuer (the purchaser of the LRI2K).
Once locked, it cannot be modified.
The most significant nibble of the AFI is used to code one specific or all application families,
.
The least significant nibble of the AFI is used to code one specific or all application subfamilies. Subfamily codes different from 0 are proprietary.
Table 94. AFI coding (1)
AFI most significant nibble
'7
8
'9
'A
'B
'C
'D
'E
‘F’
‘1
'2
'3
'4
‘5’
'6
‘0’
‘X’
'X
‘0’
1. X = '1' to 'F', Y = '1' to 'F.
AFI least significant nibble
'‘0’, ‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
‘0’, ‘Y’
‘0’
'0
'‘Y’
‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
'‘0’, ‘Y’
‘0’, ‘Y’
'‘0’, ‘Y’
Meaning
VICCs respond from
Examples / Note
All families and subfamilies No applicative preselection
'All subfamilies of family X Wide preselection
Only the Y th
subfamily of family X -
Proprietary subfamily Y only -
Transport
Financial
Identification
Telecommunication
Medical
Multimedia
-
Mass transit, Bus, Airline etc.
IEP, Banking, Retail etc.
Access Control etc.
Public Telephony, GSM etc.
Internet services etc.
Gaming
Data storage
Item management
Express parcels
Postal services
Airline bags
RFU
RFU
RFU
-
-
-
-
-
-
-
-
Portable Files etc.
DocID12112 Rev 9
84
Revision history LRI2K
Date
17-Feb-2006
08-Feb-2007
15-Jun-2007
20-Jul-2007
31-Aug-2007
07-Sep-2007
08-Apr-2008
16-Sep-2008
26-Nov-2015
Revision
1
2
3
4
5
6
7
8
9
Table 95. Document revision history
Changes
Initial release.
Figure 2: UFDFPN8 (MLP) connections added.
Only bits set to ‘1’ are programmed to the AFI and DSFID Registers (see
.
C
TUN
typical value for W4/3 modified in Table 90: DC characteristics
.
Small text changes.
modified.
Document status promoted from Preliminary Data to full Datasheet.
Small text changes.
23.5 pF internal tuning capacitor (C
TUN
) value added (see Features on page 1
and Table 90: DC characteristics
.
V
ESD
max modified for MLP in Table 88: Absolute maximum ratings
.
V
ESD
min modified for MLP in Table 88: Absolute maximum ratings .
Response parameters modified in Section 20.14: Get Multiple Block
UFDFPN8 package mechanical data updated and dimensions in inches rounded to four decimal digits instead of three in Table 92: UFDFPN8 - 8lead ultra thin fine pitch dual flat package no lead (MLP) mechanical data .
LRI2K products are no longer offered in A1 inlays and A6 and A7 antennas.
T
STG
added for UFDPFN8 package in Table 88: Absolute maximum ratings
.
Table 92: Ordering information scheme
clarified.
Removed packaged device, hence updated figure on cover page, and removed former Figure 2: UFDFPN8 (MLP) connections and former
Section 23: Package mechanical data .
Updated
Updated
Table 88: Absolute maximum ratings
and Table 92: Ordering information scheme .
DocID12112 Rev 9
LRI2K
IMPORTANT NOTICE – PLEASE READ CAREFULLY
STMicroelectronics NV and its subsidiaries (“ST”) reserve the right to make changes, corrections, enhancements, modifications, and improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on
ST products before placing orders. ST products are sold pursuant to ST’s terms and conditions of sale in place at the time of order acknowledgement.
Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or the design of Purchasers’ products.
No license, express or implied, to any intellectual property right is granted by ST herein.
Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.
ST and the ST logo are trademarks of ST. All other product or service names are the property of their respective owners.
Information in this document supersedes and replaces information previously supplied in any prior versions of this document.
© 2015 STMicroelectronics – All rights reserved
DocID12112 Rev 9 85/85
85
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
