 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| 1. general description the epc global uhf generation 2 standard allows the commercialised provision of mass adaption of uhf epc technology for passiv e smart tags and labels. main fields of applications will be especially the supply chain management and logistics for worldwide use with especial consideration of european and us regulations to ensure that operating distances of several me ters can be realized. the ucode epc g2 ic is a dedicated chip for passive, intelligent tags and labels supporting the epcglobal class 1 generation 2 uhf rfid standard. it is especially suited for applications where operating distances of several meters and hi gh anti-collision rates are required. the ucode epc g2 ic is a product out of the nxp semiconductors ucode product family. the entire ucode product family offers anti-collis ion and collision arbitration functionality. this allows a re ader to simultaneously operate mu ltiple labels / tags within its antenna field. a ucode epc g2 based label / tag requires no external power supply. its contactless interface generates the power supply via the antenna circuit by propagative energy transmission from the interrogator (rea d / write device), while the system clock is generated by an on-chip oscillator. data transmitted fr om interrogat or to label / tag is demodulated by the interface, and it also modulates the interrogator?s electromagnetic field for data transmission from label / tag to interrogator. a label / tag can be operated without the need for line of sight or battery, as long as it is connected to a dedicated antenna for the targeted frequency range. when the label / tag is within the interrogator?s operating range, the high-speed wireless interface allows data transmission in both directions. sl3 ics 10 ucode epc g2 rev. 3 .0 ? 7 september 2006 product data sheet 109930 public
109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 2 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 2. features 2.1 key features ? interface fully compatible with uhf epc g2 standard ? long-range solutions ? suitable for uhf rfid, allowing one ic to be used worldwide ? fast data rate ? forward link: 40 - 160 kbits/s ? return link: 40 - 640 kbits/s ? 512 bit of on-chip memory ? 96 bit epc ? 64 bit tag identifier ? 224 bit programmable user memory ? 32 bit access password ? 32 bit kill password ? runs on the same hardware infrastructure as the ucode hsl and the ucode epc1.19 2.2 key benefits ? tags / labels and readers available from various suppliers ? first uhf epc product operating worldwide ? highly advanced anti-co llision resulting in highest identification speed ? reliable and robust rfid technology suitab le for dense reader and noisy environment ? secure uhf communication; readers do not transmit epc data ? broadest industry back-up ? epcglobal and iso 18000-6c ? reader portfolio covers all regional demands 2.3 rf interface features ? contact-less transmission of data and supply energy (no battery needed) ? long-range operating distance ? operating frequency within the released operating bands from 860 mhz to 960 mhz ? high data integrity: 16 bit crc, framing ? high anti-collision and inventory speed ? data rates: ? r -> t: 40 ? 160 kbps, ? t -> r: 40 ? 465 kbps (divide ratio dr = 8) or 95 ? 640 kbps (dr = 64/3) ? uses a slotted random anti-collision algo rithm where the ucode epc g2 ic loads a random (or pseudo-random) number into a sl ot counter, decrement this slot counter based on interrogator commands, and reply to the interrogator when their slot counter reaches zero. supports the full mandatory command set as well as optional and customer commands acco rding to the standard 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 3 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 2.4 memory features ? 96 bit epc numbers supported ? 64 bit tag identifier (tid) ? 32 bit kill password to permanently disable the tag ? 32 bit access password to allow a transition into t he secured transmission state ? 224 bit user memory with free definable memory organization ? inventoried flags and selected flag support the handling of persistence information 2.5 security features ? lock mechanism (write protection) for individual passwords and individual memory banks allow for permanent lock (permalock) status of a password or memory bank. 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 4 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 3. applications ? supply chain management ? asset management ? container identification ? pallet & case tracking 4. quick reference data the sl3 ics 10 supports global operation in different frequency bands. in principle, the sl3 ics 10 has no restriction on the operat ing frequency. based on regulation requirements the sl3 ics 10 is released for the following frequency band. table 1: quick reference data symbol parameter conditions min typ max unit uhf frequency band 860 - 960 mhz 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 5 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 5. block diagram the sl3 ics 10 ic consists of three major blocks: analog rf interface digital controller eeprom the analog part provides stable supply voltage and demodulates data received from the reader for being processed by the digital pa rt. further, the modulation transistor of the analog part transmits data back to the reader. the digital section includes the state mach ines, processes the protocol and handles communication with the eeprom, which co ntains the epc and the user data. fig 1. block diagram of tag ic 32 bit analogue rf interface digital control eeprom sequencer charge pump vdd data in data out r/w anticollision read/w rite control access control eeprom interface control rf interface control pad vreg v rect demod mod pad rows 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 6 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 6. functional description 6.1 power transfer the reader provides an rf field that powers the ucode epc g2 tag, which contains the sl3 ics 10 connected to an antenna. the tag ant enna transforms the impedance of free space to the chip input impedance in order to get the maximum possible power for the sl3 ics 10 on the tag. the rf field, which is oscillating on the ope rating frequency provided by the reader, is rectified to provide a smoothed dc voltage to the analog and digital modules of the ic. the antenna that is attached to the chip may use a dc connection between the two antenna pads. therefore the ucode epc g2 ic also enables loop antenna design. possible examples of supported antenna struct ures can be found in the antenna design guide. 6.2 data transfer 6.2.1 reader to tag link an interrogator transmits info rmation to the ucode epc g2 tag by modulating an rf signal in the 860 mhz ? 960 mhz frequency ra nge. the tag receives both information and operating energy from this rf signal. tags ar e passive, meaning that they receive all of their operating energy from the interrogator?s rf waveform. an interrogator is using a fixed modulation and data rate for the duration of at least an inventory round. it communicates to the tags by modulating an rf carrier using dsb-ask, ssb-ask or pr-ask with pie encoding. for further details refer to section 11 , ref. 1 , section 6.3.1.2. interrogator-to-tag (r=>t) communications. 6.2.2 tag to reader link an interrogator receives information from the ucode epc g2 tag by transmitting a continuous-wave rf signal to the tag; the tag responds by modulating the reflection coefficient of its antenna, thereby backscattering an information signal to the interrogator. the system is reader talks first (rtf) system , meaning that a tag modulates its antenna reflection coefficient with an information signal only after being directed by the interrogator. ucode epc g2 ic backscatt er uses a combination of ask and psk modulation depending on the tuning and bias point. the backscattered data is either modulated with fm0 baseband or miller subcarrier. for further details refer to section 11 , ref. 1 , section 6.3.1.3. tag-to-interrogator (t=>r) communications. 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 7 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 6.3 operating distances rfid tags based on the ucode epc g2 sl3 ics 10 silicon may achieve maximum operating distances according the following formula: (1) (2) note: p tag ....minimum required rf power for the tag g tag.... gain of the tag antenna eirp .... transmitted rf power .... wavelength r max ....maximum achieved operating distance for a /2-dipole. .... loss factor assumed to be 0.5 considering matching and package losses [1] cept/etsi regulations [cept1], [etsi1]. [2] new cept/etsi regulations. [etsi3]. [3] fcc 47 part 15 regulation [fcc1]. [4] these read distances are maximum values for general tags and labels. practical usable values may be lower due to damping by object materials and environm ental conditions. a special tag antenna design can help achieve higher values. [5] the maximum write distance is around 70% of the read distance. 6.4 air interface standards the sl3 ics 10 fully supports all parts of the ?s pecification for rfid air interface epcglobal, epctm radio-frequency identity protocols, class-1 generation-2 uhf rfid, protocol for communications at 860 mhz ? 960 mhz, version 1.0.9". table 2. operating distances for ucode epc g2 based tags and labels in released frequency bands frequency range region available power calculated read distance single antenna [4] [5] unit 868.4 to 868.65 mhz (uhf) europe [1] 0.5 w erp 3.6 m 865.5 to 867.6 mhz (uhf) europe [2] 2 w erp 7.1 m 902 to 928 mhz (uhf) america [3] 4 w eirp 7.5 m p tag eirp g tag 4 r ---------- ?? ?? 2 ?? = r max eirp g tag 2 ?? 4 () 2 p tag --------------------------------------- ? = 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 8 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 7. physical layer and signaling the interrogator transmits information to the ucode epc g2 tag by modulating an rf signal in the 860 ? 960 mhz frequency range. the tag receives both information and operating energy from this rf signal. tags ar e passive, meaning that they receive all of their operating energy from the interrogator?s rf waveform. an interrogator receives information from t he tag by transmitting a continuous-wave rf signal to the tag; the tag responds by modula ting the reflection coefficient of its antenna, thereby backscattering an information signal for the interrogator. the system is rtf (reader talks first), meaning that a tag modulates its antenna coefficient with an information signal only after being directed to do so by an interrogator. 7.1 reader to tag communication 7.1.1 physical layer for interrogator-to-tag link modulation refer to section 11 , ref. 1 , annex h.1 baseband waveforms, modulated rf, and detected waveforms. 7.1.2 tag population management layer an interrogator manages tag populations using three basic operations: select: the operation of choosing a tag population for inventory and access. a select command may be applied success ively to select a particular tag population based on user-specified criteria. this operation is analogous to selecting records from a database. inventory: the operation of identifying tags . an interrogator begins an inventory round by transmitting a query command in one of four sessions. one or more tags may reply. the interrogator detects a single tag reply and requests the pc, epc, and crc-16 from the tag. invent ory comprises multiple commands. an inventory round operates in one and only one session at a time. access: the operation of communicating with (reading from and/or writing to) a tag. an individual tag must be uniquely identified prior to access. access comprises multiple commands, some of which employ one-time-pad based cover-coding of the r=>t link. 7.1.3 modulation an interrogator sends information to one or more tags by modulating an rf carrier using double-sideband amp litude shift keying (dsb-ask), si ngle-sideband am plitude shift keying (ssb-ask) or phase -reversal amplitude shift keying (pr-ask) using a pulse-interval encoding (pie) format. tags receive their operating energy from this same modulated rf carrier. section 11 , ref. 1 : annex h, as well as chapter 6.3.1.2.2. the ucode epc g2 ic is capable of dem odulating all three modulation types. 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 9 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 7.1.4 data encoding the r=>t link is using pie. for the definition of the therefore relevant reference time interval for interrogator-to-tag signaling (tari) refer to section 11 , ref. 1 , chapter 6.3.1.2.3. the tari is specified as the duration of a data-0. 7.1.5 data rates interrogators shall communicate using tari values between 6.25 s and 25 s, inclusive. for interrogator compliance evaluation the preferred tari values of 6.25 s, 12.5 s or 25 s should be used. for further details refer to section 11 , ref. 1 , chapter 6.3.1.2.4. 7.1.6 rf envelope for r=>t a specification of the relevant rf en velope parameters can be found in section 11 , ref. 1 , chapter 6.3.1.2.5. 7.1.7 interrogator power-up/down waveform for a specification of the interrogator power-up and power-down rf envelope and waveform parameters refer to section 11 , ref. 1 , chapters 6.3.1. 2.6 and 6.3.1.2.7. 7.1.8 preamble and frame-sync an interrogator shall begin all r=>t signaling with either a preamble or a frame-sync. a preamble shall precede a query command and de notes the start of an inventory round. for a definition and explanation of the relev ant r=>t preamble and frame-sync refer to section 11 , ref. 1 , chapter 6.3.1.2.8. 7.2 tag to reader communication an interrogator receives information from a tag by transmitting an unmodulated rf carrier and listening for a backscattered reply. the uco de epc g2 ic backscatters by switching the reflection coefficient of its antenna betwee n two states in accordance with the data being sent. for further details refer to section 11 , ref. 1 , chapter 6.3.1.3. 7.2.1 modulation the ucode epc g2 tags communicate info rmation by backscatter-modulating the amplitude and/or phase of the rf carrier. interrogators shall be capable of demodulating either demodulation type. 7.2.2 data encoding the encoding format, selected in response to interrogator commands, is either fm0 baseband or miller-modulated subcarrier. the interrog ator commands the encoding choice. 7.2.2.1 fm0 baseband fm0 inverts the baseband phase at every symbol boundary; a data-0 has an additional mid-symbol phase inversion. for fm0 basis fu nctions and generator state diagram, fm0 symbols and sequences and how fm0 transmissions should be terminated refer to section 11 , ref. 1 , chapter 6.3.1.3.2.1. 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 10 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 7.2.2.2 fm0 preamble t=>r fm0 signaling begin with one of two defi ned preambles, depending on the value of the trext bit specified in the query command that initiated the inventory round. for further details refer to section 11 , ref. 1 , chapter 6.3.1.3.2.2. 7.2.2.3 miller-modulated subcarrier baseband miller inverts its phase between two data-0s in sequence. baseband miller also places a phase inversion in the middle of a data-1 symbol. for a detailed explanation of the miller basis functions, generator state diag ram, subcarrier seq uences and terminating subcarrier transmissions refer to section 11 , ref. 1 , chapter 6.3.1.3.2.3. 7.2.2.4 miller subcarrier preamble t=>r subcarrier signaling begins with o ne of the two defined preambles. the choice depends on the value of the trext bit specified in the query command that initiated the inventory round. for further details refer to section 11 , ref. 1 , chapter 6.3.1.3.2.4. 7.2.3 data rates the sl3 ics 10 ic supports tag to interrogator data rates and link frequencies as specified in section 11 , ref. 1 , chapter 6.3.1.3.3. 7.3 link timing for the interrogator interacting with a ucode epc g2 tag population exact link and response timing requirements must be fulfilled, which can be found in section 11 , ref. 1 , chapter 6.3.1.5. 7.3.1 regeneration time the regeneration time is the time required if a tag is to demodulate the interrogator signal, measured from the last falling edge of the last bit of th e tag response to the first falling edge of the interrogator transmission. this time is referred to as t2 and can vary between 3.0 tpri and 20 tpri. for a more detailed description refer to section 11 , ref. 1 , chapter 6.3.1.5. 7.3.2 start-up time for a detailed description refer to section 11 , ref. 1 , chapter 6.3.1.3.4. 7.3.3 persistence time an interrogator chooses one of four sessions and inventories tags within that session (denoted s0, s1, s2, and s3). the interrogator and associated ucode epc g2 tag population operate in one and only one session for the duration of an inventory round (defined above). for each session, tags ma intain a corresponding inventoried flag. sessions allow tags to keep tra ck of their inventoried status separately for each of four possible time-interleaved inventory processes, using an independent inventoried flag for each process. two or more interrogators can use sessions to independently inventory a common ucode epc g2 tag population. a session flag indicates whether a tag may respond to an interrogator. tags maintain a separate inventoried flag for each of four sessions; each flag has symmetric a and b values. within any given session, interrogat ors typically inventory tags from a to b followed by a re-inventory of tags from b back to a (or vice versa). 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 11 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public additionally, the ucode epc g2 ic has implemented a selected flag, sl, which an interrogator may assert or deassert using a select command. for a description of inventoried flags s0 ? s3 refer to section 11 , ref. 1 chapter 6.3.2.2 and for a description of the selected flag refer to section 11 , ref. 1 , chapter 6.3.2.3. for tag flags and respective persistence time refer to section 11 , ref. 1 , table 6.15. 7.4 bit and byte ordering the transmission order for all r=>t and t=>r communications re spects the following conventions: ? within each message, the most-significa nt word is transmitted first, and ? within each word, the most-signific ant bit (msb) is transmitted first, whereas one word is composed of 16 bits. to represent memory addresses and mask lengths ebv-8 values are used. an extensible bit vector (ebv) is a data structure with an extensible data range. for a more detailed explanation refer to section 11 , ref. 1 , annex a. 7.5 data integrity the ucode epc g2 ic ignores invalid co mmands. in general, ?invalid? means a command that (1) is incorrect given the cu rrent the ucode epc g2 ic state, (2) is unsupported by the ucode epc g2 ic, (3 ) has incorrect parameters, (4) has a crc error, (5) specifies an incorrect session, or (6) is in any other way not recognized or not executable by the ucode epc g2 ic. the actual definition of ?invalid? is state-specific and defined, for each tag state, in section 11 , ref. 1 annex b and annex c. all ucode epc g2 ic backscatter error codes are summarized in section 11 , ref. 1 error codes, annex i. for a detailed description of the individual backscatter error situations which are command specific please refer to the section 11 , ref. 1 individual command description section 6.3.2.10. 7.6 crc a crc-16 is a cyclic-redundancy check that an interrogator uses when protecting certain r=>t commands, and the ucode epc g2 ic uses when protecting certain backscattered t=>r sequences. to generate a crc-16 an interrogator or the ucode epc g2 ic first generates th e crc-16 precursor shown in section 11 , ref. 1 table 6.14, then take the ones-complement of the gener ated precursor to form the crc-16. for a detailed description of the crc-16 generation and handling rules refer to section 11 , ref. 1 , chapter 6.3.2.1.3. the crc-5 is only used to protect the query command (out of the mandatory command set). it is calculated out of x5 + x3 + 1. for a more detailed crc-5 description refer to section 11 , ref. 1 , table 6.17. for exemplary schematic diagrams for crc-5 and crc-16 encoder/decoder refer to section 11 , ref. 1 , annex f. for a crc calculation example refer to section 9.1 , ta b l e 15 and ta b l e 16 . 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 12 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8. tag selection, inventory and access this section contains all information including commands by which a reader selects, inventories, and accesses a tag population. an interrogator manages ucode epc g2 tag populations using three basic operations. each of these operations comprises one or more commands. the operations are defined as follows: select: the process by which an interrogator selects a tag population for inventory and access. interrogators may use one or more select commands to select a particular tag population prior to inventory. inventory: the process by which an interrogator identifies ucode epc g2 tags. an interrogator begins an inventory round by transmitting a query command in one of four sessions. one or more tags may reply. the interrogator detects a single tag reply and requests the pc, epc, and crc-16 from the tag. an inventory round operates in one and only one session at a time. for an example of an interrogator inventorying and accessing a single tag refer to section 11 , ref. 1 , annex e. access: the process by which an interrogator transacts with (reads from or writes to) individual tags. an individual tag must be uniquely identified prior to access. access comprises multiple commands, some of which employ one-time-pad based cover-coding of the r=>t link. 8.1 tag selection, inventory and access for a detailed description refer to section 11 , ref. 1 , section 6.3.2. 8.1.1 tag memory for the general memory layout according to the standard section 11 , ref. 1 , refer to figure 6.17. the tag memory is logically subdivided into four distinct banks. in accordance to the standard section 11 , ref. 1 , section 6.3.2.1. the tag memory of the sl3 ics 10 is organized in follo wing 4 memory sections: ? reserved memory ? epc memory ? tid memory ? user memory the logical address of all memory banks begin at zero (00h). 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 13 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.1.1.1 memory details [1] this is the initial memory cont ent when delivered by nxp semiconductors [2] contents of this memory area is not defined during chip production table 3. memory details address type content initial [1] remark 00h ? 1fh reserved kill password: refer to section 11 , ref. 1 , chapter 6.3.2.1.1 all 00h unlocked memory 20h ? 3fh reserved access password: refer to section 11 , ref. 1 , chapter 6.3.2.1.2 all 00h unlocked memory 00h ? 0fh epc crc-16: refer to section 11 , ref. 1 , chapter 6.3.2.1.3 memory mapped calculated crc 10h ? 14h epc protocol-control bits: refer to section 11 , ref. 1 , chapter 6.3.2.1.4 all 00h unlocked memory 15h ? 16h epc rfu: refer to section 11 , ref. 1 , chapter 6.3.2.1.4 00b unlocked memory; to be set to 00b for class-1 tags 17h ?1fh epc nsi: refer to section 11 , ref. 1 , chapter 6.3.2.1.4 00h unlocked memory 20h - 7fh epc epc: refer to section 11 , ref. 1 , chapter 6.3.2.1.2.3 or 6.3.2.1.5 undefined [2] unlocked memory 00h ? 07h tid allocation class identifier: refer to section 11 , ref. 1 , chapter 6.3.2.1 1110 0010b locked memory 08h ? 13h tid tag mask designer identifier: refer to section 11 , ref. 1 , chapter 6.3.2.1 0000 0000 1100b locked memory 14h ? 1fh tid tag model number: refer to section 11 , ref. 1 , chapter 6.3.2.1 tmnr locked memory 20h ? 3fh tid serial number: refer to [ section 11 , ref. 1 , chapter 6.3.2.1 snr locked memory 00h ? dfh user user memory: refer to section 11 , ref. 1 , chapter 6.3.2.1 undefined [2] unlocked memory 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 14 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.1.1.2 user memory the user memory bank contains a sequential block of 224 bits of unspecific user data. 8.1.1.3 supported epc types the epc types are defined in the epc tag standards document from epcglobal. these standards define completely that port ion of epc tag data that is standardized, including how that data is encoded on the epc tag itself (i.e. the epc tag encodings), as well as how it is encoded for use in the in formation systems layers of the epc systems network (i.e. the epc uri or uniform resource identifier encodings). the epc tag encodings include a header field followed by one or more value fields. the header field defines the overall length and fo rmat of the values fields. the value fields contain a unique epc identifier and optional f ilter value when the latter is judged to be important to encode on the tag itself. 8.1.2 sessions and inventoried flags for a description refer to section 11 , ref. 1 , section 6.3.2.2. 8.1.3 selected flag for a description refer to section 11 , ref. 1 , section 6.3.2.3. 8.1.4 tag states and slot counter for a description refer to section 11 , ref. 1 , section 6.3.2.4. table 4. sequential rows of user memory, each comprised of 4 bytes memory row byte order / row 3 2 1 0 6 user_27 user user user 5 user user user user 4 user user user user 3 user user user user 2 user user user user 1 user user user user 0 user user user user_0 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 15 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.1.5 tag state diagram for a description refer to section 11 , ref. 1 , section 6.3.2.4 tag states and slot counter. ? ready state ? arbitrate state ? reply state ? acknowledged state ? open state ? secured state ? killed state ? slot counter please find the tag state diagram in section 11 , ref. 1 , figure 6.19. refer also to section 11 , ref. 1 , annex b for the associated state-transition tables and to section 11 , ref. 1 , annex c for the associated command-response tables. 8.2 managing tag populations for a detailed description on how to manage an ucode epc g2 tag population refer to section 11 , ref. 1 , chapter 6.3.2.6. 8.3 selecting tag populations for a detailed description of the ucode epc g2 tag population selection process refer to section 11 , ref. 1 , section 6.3.2.7. 8.4 inventorying tag populations for a detailed description on accessing individual tags based on the ucode epc g2 ic refer to section 11 , ref. 1 , section 6.3.2.8. 8.5 accessing individual tags for a detailed description on accessing individual tags based on the ucode epc g2 ic refer to section 11 , ref. 1 , section 6.3.2.9. please find an example inventory and a ccess of a single ucode epc g2 tag in section 11 , ref. 1 , annex e.1. 8.6 interrogator commands and tag replies for a detailed description refer to section 11 , ref. 1 , section 6.3.2.10. 8.6.1 commands please find an overview of interrogator to tag commands in section 11 , ref. 1 , table 6.16. please note that all mandatory commands are implemented on the ucode epc g2 ic according to the standard. additionally the optional commands access and blockwrite are supported by the ucode epc g2 ic (for details refer to section 8.10 ? optional access command ? . besides also customer commands are implemented on the sl3 ics 10 (for details refer to section 8.11 ? custom commands ? . 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 16 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.6.2 state transition tables the ucode epc g2 ic responses to interrogator commands are defined by state annex b transition tables in section 11 , ref. 1 . following states are implemented on the ucode epc g2 ic: ? ready, for a description refer to section 11 , ref. 1 , annex b.1. ? arbitrate, for a description refer to section 11 , ref. 1 , annex b.2. ? reply, for a description refer to section 11 , ref. 1 , annex b.3. ? acknowledged, for a description refer to section 11 , ref. 1 , annex b.4. ? open, for a description refer to section 11 , ref. 1 , annex b.5. ? secured, for a description refer to section 11 , ref. 1 , annex b.6. ? killed, for a description refer to section 11 , ref. 1 , annex b.7. 8.6.3 command response tables the ucode epc g2 ic responses to interrogator commands are described in following annex c sections of section 11 , ref. 1 : ? power-up, for a description refer to section 11 , ref. 1 , annex c.1. ? query, for a description refer to section 11 , ref. 1 , annex c.2. ? queryrep, for a description refer to section 11 , ref. 1 , annex c.3. ? queryadjust, for a description refer to section 11 , ref. 1 , annex c.4. ? ack, for a description refer to section 11 , ref. 1 , annex c.5. ? nak, for a description refer to section 11 , ref. 1 , annex c.6. ? req_rn, for a description refer to section 11 , ref. 1 , annex c.7. ? select, for a description refer to section 11 , ref. 1 , annex c.8. ? read, for a description refer to section 11 , ref. 1 , annex c.9. ? write, for a description refer to section 11 , ref. 1 , annex c.10. ? kill, for a description refer to section 11 , ref. 1 , annex c.11. ? lock, for a description refer to section 11 , ref. 1 , annex c.12. ? access, for a description refer to section 11 , ref. 1 , annex c.13. ? blockwrite, for a description refer to section 11 , ref. 1 , annex c.14. ? t2 timeout, for a description refer to section 11 , ref. 1 , annex c.16. ? invalid command, for a description refer to section 11 , ref. 1 , annex c.17. 8.6.4 example data-flow exchange for data flow-exchange examples refer to section 11 , ref. 1 , annex k: ? k.1 overview of the data-flow exchange ? k.2 tag memory contents and lock-field values ? k.3 data-flow exchange and command sequence 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 17 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.7 mandatory se lect commands select commands select a particular ucode epc g2 tag population based on user-defined criteria. 8.7.1 select for a detailed description of the mandatory select command refer to section 11 , ref. 1 , section 6.3.2.10.1.1. 8.8 mandatory inventory commands inventory commands are used to run the collision arbitration protocol. 8.8.1 query for a detailed description of the mandatory query command refer to section 11 , ref. 1 , section 6.3.2.10.2.1. 8.8.2 queryadjust for a detailed description of the mandatory queryadjust command refer to section 11 , ref. 1 , section 6.3.2.10.2.2. 8.8.3 queryrep for a detailed description of the mandatory queryrep command refer to section 11 , ref. 1 , section 6.3.2.10.2.3. 8.8.4 ack for a detailed description of the mandatory ack command refer to section 11 , ref. 1 , section 6.3.2.10.2.4. 8.8.5 nack for a detailed description of the mandatory nack command refer to section 11 , ref. 1 , section 6.3.2.10.2.5. 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 18 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.9 mandatory access commands access commands are used to read or writ e data from or to the ucode epc g2 ic memory. for a detailed description of the mandatory access command refer to section 11 , ref. 1 , section 6.3.2.10.3. 8.9.1 req_rn access commands are used to read or writ e data from or to the ucode epc g2 ic memory. for a detailed description of the mandatory access command refer to section 11 , ref. 1 , section 6.3.2.10.3.1. 8.9.2 read for a detailed description of the mandatory req_rn command refer to section 11 , ref. 1 , section 6.3.2.10.3.2. 8.9.3 write for a detailed description of the mandatory write command refer to section 11 , ref. 1 , section 6.3.2.10.3.3. 8.9.4 kill for a detailed descripti on of the mandatory kill command refer to section 11 , ref. 1 , section 6.3.2.10.3.4. 8.9.5 lock for a detailed description of the mandatory lock command refer to section 11 , ref. 1 , section 6.3.2.10.3.5. 8.10 optional access command 8.10.1 access for a detailed description of the optional access command refer to section 11 , ref. 1 , section 6.3.2.10.3.6. 8.10.2 blockwrite for a detailed description of the mandatory blockwrite command refer to section 11 , ref. 1 , section 6.3.2.10.3.7. 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 19 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.11 custom commands 8.11.1 blocklock blocklock supports an additional locking mechanism, which allows the locking of individual 32 bit blocks (rows) in the 224 bit user memory. once locked these locks cannot be unlocked. both, the permalock for the user memory and the state of the individual block locks are checked, before ex ecuting a write or a blockwrite command addressing the user memory. if either lock applies for the addressed memory, the write command will fail and the response according to ta b l e 8 should be performed. each eeprom row can be addr essed by either of the two related wordpointers: if ucode epc g2 ic receives a blocklock, the blo cklock succeeds only in secured state. if a ucode epc g2 ic whose addr essed eeprom block (row) is already locked receives a blocklock, it shall not write to the eeprom, but backscatter the reply shown in ta b l e 7 . if an interrogator issues a blocklock comma nd to an ucode epc g2 ic whose user memory is permalocked or the wordpointe r addresses a nonexist ent eeprom row, the ucode epc g2 ic ignores the entire bloc klock command and in stead backscatter an error code. a blocklock shall be prepended with a frame-sync. after issuing a blocklock an interrogator sh all transmit cw for th e lesser of treply or 20ms, where treply is the time between the interrogator?s blocklock command and the ucode epc g2 tag?s backscattered reply. an interrogator may observe several possible outcomes from a blocklock, depending on the success or failure of the tag?s memory-write operation: ? the blocklock succeeds: af ter completing the blockl ock a ucode epc g2 tag backscatters the reply shown in table 7 comprising a header (a 0-bit), the tag?s handle, and a crc-16 calculated over t he 0-bit and handle. if the in terrogator observes this reply within 20ms then the blocklock completed successfully. ? the tag encounters an error: the ucode epc g2 tag backscatters an error code during the cw period rather than the reply shown in ta b l e 7 (see section 11 , ref. 1 , annex i for error-code definitions and for the reply format ? the blocklock does not succeed: if the inte rrogator does not observe a reply within 20ms then the blocklock did not complete successfully. the interrogator may issue a req_rn command (containing t he tag?s handle) to verify that the tag is still in the interrogator?s field, and may reissue the blocklock command. table 5. either of two wordpointers can address one single user memory row wordpointer user eeprom row 0 or 1 0 2 or 3 1 4 or 5 2 6 or 7 3 8 or 9 4 10 or 11 5 12 or 13 6 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 20 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public the ucode epc g2 tag?s reply to the bl ocklock command uses the extended preamble shown in section 11 , ref. 1 , figure 6.11 or figure 6.15), as appropriate (i.e. the tag replies as if trext=1 regardless of the trext value in the query that initiated the round. table 6. blocklock command command wordpointer rn crc-16 # of bits 16 ebv 16 16 description 11100000 00000000 corresponding word address for a ee row handle table 7. tag reply to a successful blocklock command header rn crc-16 # of bits 1 16 16 description 0 handle table 8. blocklock command-response table starting state condition response next state ready all ? ready arbitrate, reply, acknowledged all ? arbitrate open all ? open secured invalid address or permalocked backscatter error code secured valid handle & user memory not locked & row already locked backscatter handle secured valid handle & user memory not permalocked backscatter handle, when done secured invalid handle ? secured killed all ? killed 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 21 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.11.2 changeeas changeeas allows an interrogator to set or reset the eas system bit. tags execute changeeas from the secured state. the changeeas command further includes the tag?s handle and a crc-16. the crc-16 is calculated over the first command code bit up to the last handle bit. a changeeas shall be prepended with a frame-sync. if a ucode epc g2 tag in the open or secured stat es receives a changeeas with a valid crc-16 but an inva lid handle, it ignores the changeeas and remains in its current state. after issuing a changeeas an inte rrogator shall tran smit cw for the lesser of treply or 20ms, where treply is the time betwee n the interrogator?s changeeas co mmand and the tag?s backscattered reply. an interrogator may observe several possible outcomes from a changeeas, dep ending on the success or failure of the tag?s memory write operation: ? the write succeeds: after completing the changeeas a ucod e epc g2 tag backscatters the reply shown in ta b l e 10 made up of a header (a 0-bit), the tag?s handle, and a crc-16 calculated over the 0-bit and the handle. if the interrogator observes this reply within 20ms then the changeeas completed successfully. ? the tag encounters an error: the ucode epc g2 tag backscatters an error code during the cw period rather than the reply shown in table 10 (see section 11 , ref. 1 , annex i for error-code definitions and for the reply format). ? the write does not succeed: if the interrogator does not observe a reply within 20ms then the changeeas did not complete successfully . the interrogator may issue a req_rn command (containing the tag?s handle) to verify th at the tag is still in the inte rrogator?s fiel d, and may then reissue the changeeas command. the ucode epc g2 tag?s reply to a successful changeeas uses the extended preamble, as appropriate. a tag replies as if trext=1 regardless of the trext value in the query that initiated the round. table 9. changeeas command command changeeas rn crc-16 # of bits 16 1 16 16 description 11100000 00000011 1 ... set eas system bit 0 ... reset eas system bit handle table 10. tag reply to a successful changeeas command header rn crc-16 # of bits 1 16 16 description 0 handle 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 22 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 8.11.3 easalarm easalarm causes the ucode epc g2 ic to ba ckscatter its alarm code. to enable this command the corr esponding prior changeeas command must have been carried out successfully (to set the eas system bit). if the eas system bit is set, the ucode epc g2 ic backscatters the eas code. if the eas system bit is reset, the ucode epc g2 ic ignores this command. ucode epc g2 tags execute easalarm only from the ready state. easalarm includes the following fields: ? dr (trcal divide ratio) sets the t=>r link frequency as described in section 11 , ref. 1 , section 6.3.1.2.8 and table 6.11. ? m (cycles per symbol) sets the t=>r data rate and modulation format as shown in section 11 , ref. 1 , table 6.12. ? trext chooses whether the t=>r preamble is prepended with a pilot tone as described in section 11 , ref. 1 , sections 6.3.1.3.2.2 and 6.3.1.3.2.4. interrogators shall prepend a easal arm with a preamble (see section 11 , ref. 1 , section 6.3.1.2.8). the eas code is generated by means of the crc-5 generator. upon receiving an easalarm, the crc-5 register is preloaded with b01001 . to generate the 64 bit code the register is clocked 64 times with its input fixed to logic 1. the eas code is derived from the so-generated sequence by taking the msbit of the crc-5 register value at each clock cycle. the ucode epc g2 tag?s reply to an easala rm is protected by an crc-16, calculated from the header bit to the last eas code bit. table 11. changeeas command-response table starting state condition response next state ready all ? ready arbitrate, reply, acknowledged all ? arbitrate open all ? open secured valid handle backscatter handle, when done secured invalid handle ? secured killed all ? killed table 12. easalarm command command inv_command dr m trext crc-16 # of bits 16 16 1 2 1 16 description 11100000 00000100 00011111 11111011 0: dr=8 1: dr=64/3 00: m=1 01: m=2 10: m=4 11: m=8 0: no pilot tone 1: use pilot tone 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 23 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public [1] if eas eeprom system bit is reset, ignore this command. table 13. tag reply to a successful easalarm command header eas code crc-16 # of bits 1 64 16 description 0 crc5(msb) table 14. easalarm command-response table starting state condition response next state ready eas system bit is set backscatter alarm code ready eas system bit is reset ? ready arbitrate, reply, acknowledged, open, secured [1] eas system bit is set - arbitrate killed all ? killed 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 24 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 9. support information 9.1 crc calculation example old rn = 3d5bh table 15. practical example of crc calculation for a 'req_rn' command by the reader crc calculated @ reader cmd code for req_rn f f f f 1 f f f e 1 f f f c 0 e f d 9 0 c f 9 3 0 8 f 0 7 0 0 e 2 f 0 1 c 5 e 1 2 8 9 9 first byte of rn 0 5 1 3 a 0 a 2 7 4 1 4 4 e 8 1 9 9 f 1 1 3 3 e 2 1 7 7 e 5 0 e f c a 1 d f 9 4 second byte of rn 0 a f 0 9 1 5 e 1 2 0 b c 2 4 1 7 8 4 8 1 e 0 b 1 0 d 1 4 3 1 a 2 8 6 1 4 5 0 c -> ones complement: b a f 3 => command-sequence: c1 3d 5b ba f3 hex 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 25 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public table 16. practical example of crc calculation for a 'req_rn' command by the reader crc calculated @ tag cmd code for req_rn f f f f 1 f f f e 1 f f f c 0 e f d 9 0 c f 9 3 0 8 f 0 7 0 0 e 2 f 0 1 c 5 e 1 2 8 9 9 first byte of rn 0 5 1 3 a 0 a 2 7 4 1 4 4 e 8 1 9 9 f 1 1 3 3 e 2 1 7 7 e 5 0 e f c a 1 d f 9 4 second byte of rn 0 a f 0 9 1 5 e 1 2 0 b c 2 4 1 7 8 4 8 1 e 0 b 1 0 d 1 4 3 1 a 2 8 6 1 4 5 0 c first byte of crc 1 9 a 3 9 0 2 4 5 3 1 5 8 8 7 1 a 1 2 f 1 4 2 5 e 0 8 4 b c 1 0 9 7 8 0 1 2 f 0 second byte of crc 1 3 5 c 1 1 7 b a 3 1 e 7 6 7 1 c e c e 0 8 d b d 0 0 b 5 b 1 0 6 9 7 1 1 d 0 f -> residue ok 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 26 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 10. abbreviations table 17. abbreviations acronym description crc cyclic redundancy check cw continuos wave eeprom electrically erasable programmable read only memory epc electronic product code (containing header, domain manager, object class and serial number) fm0 bi phase space modulation g2 generation 2 ic integrated circuit lsb least significant byte/bit msb most significant byte/bit nrz non-return to zero coding rf radio frequency rtf reader talks first ta r i type a reference interval (iso 18000-6) uhf ultra high frequency xx hex value in hexadecimal notation 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 27 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 11. references the following referenced documents are indispensable to the application of this specification. for dated refer ences, only the edition cited applies. for undated references, the latest edition (including any amendments) applies. [1] epcglobal: epc radio-frequency identity protocols class-1 generation-2 uhf rfid protocol for communications at 860 mhz ? 960 mhz, version 1.0.9 ref. 1 [2] epcglobal: epc tag data standards [3] epcglobal (2004): fmcg rfid phys ical requirements document (draft) [4] epcglobal (2004): class-1 generation-2 uhf rfid implementation reference (draft) [5] european telecommunications standards institute (etsi), en 302 208: electromagnetic compatibility and radio spectrum matter s (erm) ? radio-frequency identification equipment operating in the band 865 mhz to 868 mhz with power levels up to 2 w, part 1 ? technical characteristics and test methods [6] european telecommunications standards institute (etsi), en 302 208: electromagnetic compatibility and radio spectrum matter s (erm) ? radio-frequency identification equipment operating in the band 865 mhz to 868 mhz with power levels up to 2 w, part 2 ? harmonized en under article 3.2 of the r&tte directive [7] [cept1]: cept rec 70-03 annex 1 [8] [etsi1]: etsi en 330 220-1, 2 [9] [etsi3]: etsi en 302 208-1, 2 v<1.1. 1> (2004-09-electrom agnetic compatibility and radio spectrum matters (erm) radio frequency identification equipment operating in the band 865 - mhz to 868 mhz with power levels up to 2 w part 1: technical characteristics and test methods. [10] [fcc1]: fcc 47 part 15 section 247 [11] iso/iec directives, part 2: rules for th e structure and drafting of international standards [12] iso/iec 3309: information technology ? telecommunications and information exchange between systems ? high-level data link control (hdlc) procedures ? frame structure [13] iso/iec 15961: information technology, automatic identification and data capture ? radio frequency identification (rfid) for item management ? data protocol: application interface [14] iso/iec 15962: information technology, automatic identification and data capture techniques ? radio frequency identification (rfid) for item management ? data protocol: data encoding rules and logical memory functions [15] iso/iec 15963: information technology ? radio frequency identification for item management ? unique identification for rf tags [16] iso/iec 18000-1: information technology ? radio frequency identification for item management ? part 1: reference architecture and definition of parameters to be standardized [17] iso/iec 18000-6: information technology automatic identification and data capture techniques ? radio frequency identification for item management air interface ? part 6: parameters for air interface communications at 860?960 mhz 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 28 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public [18] iso/iec 19762: information technology aidc techniques ? harmonized vocabulary ? part 3: radio-frequency identification (rfid) [19] u.s. code of federa l regulations (cfr), title 47, chapter i, part 15: radio-frequency devices, u.s. federal communications commission. 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 29 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 12. revision history table 18. revision history document id release date data sheet status change notice doc. number supersedes modifications: 7 september 2006 product data sheet - 109930 revision 2.0 ? the format of this data sheet has been redesigned to comply with the new identity guidelines of nxp semiconductors. ? legal texts have been adapted to the new company name where appropriate. ? section 2.1 ? key features ? on page 2 : - long-range solutions; removed: ?( 7. 5 m in the us and 7.1 m in europe)? ? section 2.3 ? rf interface features ? on page 2 : - operating distance, depending on antenna geometry and local regulation; removed: ? 7.5 m for a single antenna? ? section 6.3 ? operating distances ? on page 7 : - rewording note of ? ? ? section 7.3 ? link timing ? on page 10 : - corrected reference ?section 11, ref. 1, chapter 6.3.1.6 to ? chapter 6.3.1.5 ? ? section 7.3.1 ? regeneration time ? on page 10 : - corrected reference ?section 11, ref. 1, chapter 6.3.1.6 to ? chapter 6.3.1.5 ? ? section 7.3.3 ? persistence time ? on page 10 : - corrected reference ?section 11, ref. 1, table 6.14 to ? table 6.15 ? ? section 7.6 ? crc ? on page 11 : - corrected references ?section 11, ref. 1, table 6.11 to ? table 6.14 ? and section 11, ref. 1, table 6.12 to ? table 6.17 ? and added in: for a crc calculation example refer to section 9.1, ?table 15 and table 16? . ? section 8.1.1.1 ? memory details ? on page 13 : - ta b l e 3 : corrected references, address of epc: 20h - 80h to ? 20h - 7fh ? and initial of tid: 0000 0000 01b to? tmnr ? ? section 8.6.2 ? state transition tables ? on page 16 : - added in the first paragraph ? annex b ? ? section 8.6.3 ? command response tables ? on page 16 : - added in the first paragraph ? annex c ? ? section 8.6.4 ? example data-flow exchange ? on page 16 : - added in the first paragraph ? annex k ? ? section 8.11 ? custom commands ? on page 19 : - renamed section title ? section 8.11.3 ? easalarm ? on page 22 : - corrected references of table 6.9 to ? table 6.11 ? and table 6.10 to ? table 6.12 ? ? section 11 ? references ? on page 27 : - corrected in reference [1]: version 1.1.0 -> ?version 1.0.9? modifications: 29 june 2006 preliminary data sheet - 109920 revision 1.2 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 30 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public ? section 2.1 ? key features ? on page 2 : - corrected: long-range solutions (up to 7 m in the us and 6.6 m in europe) to ? ( 7. 5 m in the us and 7.1 m in europe) ? ? section 2.3 ? rf interface features ? on page 2 : - corrected: operating distance, depending on antenna geometry and local regulations, up to 7 m for a single antenna ->? 7.5 m for a single antenna ? ? section 6.3 ? operating distances ? on page 7 : - corrected formula of: ?p tag and r max ? and rewording note of ?r max ? and added note ? ? ? section 7.3 ? link timing ? on page 10 : - corrected reference ?section 11, ref. 1, chapter 6.3.1.5 to ? chapter 6.3.1.6 ? ? section 7.3.1 ? regeneration time ? on page 10 : - corrected reference ?section 11, ref. 1, chapter 6.3.1.5 to ? chapter 6.3.1.6 ? ? section 7.3.2 ? start-up time ? on page 10 : - corrected reference ?section 11, ref. 1, chapter 6.3.2.16 and 6.3.2.1.7 to ? chapter 6.3.1.3.4 ? ? section 7.3.3 ? persistence time ? on page 10 : - corrected reference ?section 11, ref. 1, table 6.25 to ? table 6.14 ? ? section 7.5 ? data integrity ? on page 11 : - corrected references ?section 11, ref. 1, table 6.14 to ? table 6.11 ? and section 11, ref. 1, table 6.17 to ? table 6.12 ? ? section 7.6 ? crc ? on page 11 : - corrected references ?section 11 , ref. 1, chapter 6.3.1.5 -> ? chapter 6.3.2.1.3 ? ? section 8.1.1 ? tag memory ? on page 12 : - rewording and co rrected references ? section 8.1.1.1 ? memory details ? on page 13 : - ta b l e 3 : corrected references, address of epc: 20h - 5fh to ? 20h - 80h ? and initial of tid: 0000 0000 01b to? 0000 0000 1100 b? ? section 8.4 ? inventorying tag populations ? on page 15 : - corrected references ? section 8.6.3 ? command response tables ? on page 16 : - removed ?blockerase? ? section 8.9.1 ? req_rn ? on page 18 : - corrected reference ? section 8.9.2 ? read ? on page 18 : - corrected reference ? section 8.11.2 ? changeeas ? on page 21 : - ta b l e 9 : corrected ?changeeas? ? section 8.11.3 ? easalarm ? on page 22 : - corrected references of table 6.11 to ? table 6.9 ? and table 6.12 to ? table 6.10 ? - table 8 ? blocklock command-response table ? on page 20 : rewording conditions of secured modifications: 20 february 2006 objective data sheet - 109912 revision 1.1 ? section 6.1 ? power transfer ? on page 6 : - rewording last paragraph: ? the antenna that is attached .....? ? section 7.1.5 ? data rates ? on page 9 : - corrected following values of: 6.25 s, 12.5 s, 25 s -> ? s? table 18. revision history ?continued document id release date data sheet status change notice doc. number supersedes 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 31 of 33 nxp semiconductors sl3 ics 10 ucode epc g2 public 13. legal information 13.1 data sheet status [1] please consult the most recently issued document before initiating or completing a design. [2] the term ?short data sheet? is explained in section ?definitions?. [3] the product status of device(s) described in this document may have changed since this document was published and may differ in case of multiple device s. the latest product status information is available on the internet at url http://www.nxp.com . 13.2 definitions draft ? the document is a draft versi on only. the content is still under internal review and subject to formal approval, which may result in modifications or additions. nxp semiconductors does not give any representations or warranties as to the accuracy or completeness of information included herein and shall hav e no liability for the consequences of use of such information. short data sheet ? a short data sheet is an extract from a full data sheet with the same product type number(s) and title. a short data sheet is intended for quick reference only and should not be relied upon to contain detailed and full information. for detailed and full information see the relevant full data sheet, which is available on request vi a the local nxp semiconductors sales office. in case of any inconsistency or conflict with the short data sheet, the full data sheet shall prevail. 13.3 disclaimers general ? information in this document is believed to be accurate and reliable. however, nxp semiconductors d oes not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information and shall have no liability for the consequences of use of such information. right to make changes ? nxp semiconductors reserves the right to make changes to information published in this document, including without limitation specifications and product descriptions, at any time and without notice. this document supersedes and replaces all information supplied prior to the publication hereof. suitability for use ? nxp semiconductors products are not designed, authorized or warranted to be suitable for use in medical, military, aircraft, space or life support equipment, nor in applications where failure or malfunction of a nxp semiconductors product can reasonably be expected to result in personal injury, death or severe property or environmental damage. nxp semiconductors accepts no liability for inclusion and/or use of nxp semiconductors products in such equi pment or applications and therefore such inclusion and/or use is at the customer?s own risk. applications ? applications that are described herein for any of these products are for illustrative purpos es only. nxp semiconductors makes no representation or warranty that such applications will be suitable for the specified use without further testing or modification. limiting values ? stress above one or more limiting values (as defined in the absolute maximum ratings system of iec 60134) may cause permanent damage to the device. limiting values are stress ratings only and operation of the device at these or any other conditions above those given in the characteristics sections of this document is not implied. exposure to limiting values for extended periods may affect device reliability. terms and conditions of sale ? nxp semiconductors products are sold subject to the general terms and condit ions of commercial sale, as published at http://www.nxp.com/profile/terms , including those pertaining to warranty, intellectual property rights infringement and limitation of liability, unless explicitly otherwise agreed to in writ ing by nxp semiconductors. in case of any inconsistency or conflict between information in this document and such terms and conditions, the latter will prevail. no offer to sell or license ? nothing in this document may be interpreted or construed as an offer to sell products t hat is open for acceptance or the grant, conveyance or implication of any lic ense under any copyrights, patents or other industrial or intellectual property rights. 13.4 trademarks notice: all referenced brands, produc t names, service names and trademarks are the property of their respective owners. 109930 ? nxp b.v. 2010. all rights reserved. product data sheet rev. 3.0 ? 7 september 2006 32 of 33 continued >> nxp semiconductors sl3 ics 10 ucode epc g2 public 15. tables table 1: quick reference data . . . . . . . . . . . . . . . . . . . . . 4 table 2. operating distances for ucode epc g2 based tags and labels in released frequency bands . . .7 table 3. memory details. . . . . . . . . . . . . . . . . . . . . . . . .13 table 4. sequential rows of user memory, each comprised of 4 bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 table 5. either of two wordpointers can address one single user memory row . . . . . . . . . . . . . . . . . .19 table 6. blocklock command . . . . . . . . . . . . . . . . . . . .20 table 7. tag reply to a su ccessful blocklock command 20 table 8. blocklock command-response table . . . . . . . .20 table 9. changeeas command . . . . . . . . . . . . . . . . . . .21 table 10. tag reply to a successful changeeas command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 11. changeeas command-response table . . . . . . 22 table 12. easalarm command . . . . . . . . . . . . . . . . . . . . 22 table 13. tag reply to a successful easalarm command 23 table 14. easalarm command-response table . . . . . . . . 23 table 15. practical example of crc calculation for a 'req_rn' command by the reader . . . . . . . . . 24 table 16. practical example of crc calculation for a 'req_rn' command by the reader . . . . . . . . . . 25 table 17. abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . 26 table 18. revision history . . . . . . . . . . . . . . . . . . . . . . . . 29 16. figures fig 1. block diagram of tag ic . . . . . . . . . . . . . . . . . . . .5 17. contents 1 general description . . . . . . . . . . . . . . . . . . . . . . 1 2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.1 key features . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.2 key benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.3 rf interface features. . . . . . . . . . . . . . . . . . . . 2 2.4 memory features . . . . . . . . . . . . . . . . . . . . . . . 3 2.5 security features . . . . . . . . . . . . . . . . . . . . . . . 3 3 applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4 quick reference data . . . . . . . . . . . . . . . . . . . . . 4 5 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6 functional description . . . . . . . . . . . . . . . . . . . 6 6.1 power transfer . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.2 data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.2.1 reader to tag link . . . . . . . . . . . . . . . . . . . . . . 6 6.2.2 tag to reader link . . . . . . . . . . . . . . . . . . . . . . . 6 6.3 operating distances . . . . . . . . . . . . . . . . . . . . . 7 6.4 air interface standards . . . . . . . . . . . . . . . . . . . 7 7 physical layer and signaling . . . . . . . . . . . . . . 8 7.1 reader to tag communication . . . . . . . . . . . . . 8 7.1.1 physical layer . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.1.2 tag population management layer . . . . . . . . . . 8 7.1.3 modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.1.4 data encoding . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.1.5 data rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.1.6 rf envelope for r=>t . . . . . . . . . . . . . . . . . . . 9 7.1.7 interrogator power-up/down waveform . . . . . . . 9 7.1.8 preamble and frame-sync . . . . . . . . . . . . . . . . 9 7.2 tag to reader communication . . . . . . . . . . . . . 9 7.2.1 modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.2.2 data encoding . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.2.2.1 fm0 baseband . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.2.2.2 fm0 preamble . . . . . . . . . . . . . . . . . . . . . . . . 10 7.2.2.3 miller-modulated subcarrier . . . . . . . . . . . . . . 10 7.2.2.4 miller subcarrier preamble . . . . . . . . . . . . . . . 10 7.2.3 data rates . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 7.3 link timing. . . . . . . . . . . . . . . . . . . . . . . . . . . 10 7.3.1 regeneration time. . . . . . . . . . . . . . . . . . . . . 10 7.3.2 start-up time . . . . . . . . . . . . . . . . . . . . . . . . . 10 7.3.3 persistence time . . . . . . . . . . . . . . . . . . . . . . 10 7.4 bit and byte ordering. . . . . . . . . . . . . . . . . . . . 11 7.5 data integrity . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7.6 crc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 8 tag selection, inventory and access. . . . . . 12 8.1 tag selection, inventory and access . . . . . . . 12 8.1.1 tag memory . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.1.1.1 memory details . . . . . . . . . . . . . . . . . . . . . . . 13 8.1.1.2 user memory . . . . . . . . . . . . . . . . . . . . . . . . . 14 8.1.1.3 supported epc types . . . . . . . . . . . . . . . . . . 14 8.1.2 sessions and inventoried flags . . . . . . . . . . . 14 8.1.3 selected flag . . . . . . . . . . . . . . . . . . . . . . . . . 14 8.1.4 tag states and slot counter . . . . . . . . . . . . . . 14 8.1.5 tag state diagram . . . . . . . . . . . . . . . . . . . . . 15 8.2 managing tag populations . . . . . . . . . . . . . . . 15 nxp semiconductors sl3 ics 10 ucode epc g2 ? nxp b.v. 2010. all rights reserved. for more information, please visit: http://www.nxp.com for sales office addresses, please send an email to: sales.addresses@www.nxp.com date of release: 7 september 2006 document identifier: 109930 please be aware that important notices concerning this document and the product(s) described herein, have been included in section ?legal information?. public 8.3 selecting tag populations . . . . . . . . . . . . . . . . 15 8.4 inventorying tag populations. . . . . . . . . . . . . . 15 8.5 accessing individual tags . . . . . . . . . . . . . . . . 15 8.6 interrogator commands and tag replies . . . . . 15 8.6.1 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 8.6.2 state transition tables . . . . . . . . . . . . . . . . . . 16 8.6.3 command response tables. . . . . . . . . . . . . . . 16 8.6.4 example data-flow exchange . . . . . . . . . . . . . 16 8.7 mandatory select commands . . . . . . . . . . . . 17 8.7.1 select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.8 mandatory inventory commands . . . . . . . . . . 17 8.8.1 query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.8.2 queryadjust . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.8.3 queryrep . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.8.4 ack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.8.5 nack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.9 mandatory access commands. . . . . . . . . . . . 18 8.9.1 req_rn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.9.2 read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.9.3 write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.9.4 kill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.9.5 lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.10 optional access command . . . . . . . . . . . . . . 18 8.10.1 access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.10.2 blockwrite. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 8.11 custom commands . . . . . . . . . . . . . . . . . . . . 19 8.11.1 blocklock . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8.11.2 changeeas . . . . . . . . . . . . . . . . . . . . . . . . . . 21 8.11.3 easalarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 9 support information . . . . . . . . . . . . . . . . . . . . 24 9.1 crc calculation example . . . . . . . . . . . . . . 24 10 abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . 26 11 references . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 12 revision history . . . . . . . . . . . . . . . . . . . . . . . . 29 13 legal information. . . . . . . . . . . . . . . . . . . . . . . 31 13.1 data sheet status . . . . . . . . . . . . . . . . . . . . . . 31 13.2 definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 13.3 disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 13.4 trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . 31 14 contact information. . . . . . . . . . . . . . . . . . . . . 31 15 tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 16 figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 17 contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 |
Price & Availability of SL3ICS1001FW
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |