Texas Instruments HFDEMOKITII Inductive Tag Reader User Manual 11 06 21 700
Texas Instruments Inc Inductive Tag Reader 11 06 21 700
Manual
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 182522 |
| Application ID | PRz7XgUGyOAHAfUoW01D1w== |
| Document Description | Manual |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 23.95kB (299387 bits) |
| Date Submitted | 2001-12-07 00:00:00 |
| Date Available | 2001-12-06 00:00:00 |
| Creation Date | 2001-10-16 09:29:16 |
| Producing Software | Acrobat PDFWriter 4.05 for Windows |
| Document Lastmod | 0000-00-00 00:00:00 |
| Document Title | 11-06-21-700 |
| Document Creator | Microsoft Word - 11-06-21-700 |
HF Reader System Series 6000 S6350 Multi-Protocol Reader Modules: RI-STU-TRDC-01 & 02 Reference Guide 11-06-21-700 September 2001 A TEXAS INSTRUMENTS TECHNOLOGY September 2001 S6350 Reader Reference Guide Second Edition - September 2001 This is the second edition of this manual. It describes the S6350 Reader (formerly published as the Series 5000 RI-STU-TRDC-00 Reader Reference Guide). It contains a description of the following reader modules: Reader Module with Right-Angle Connector RI-STU-TRDC-01 Reader Module with Straight Connector RI-STU-TRDC-02 Texas Instruments (TI) reserves the right to make changes to its products or services or to discontinue any product or service at any time without notice. TI provides customer assistance in various technical areas, but does not have full access to data concerning the use and applications of customer’s products Therefore, TI assumes no liability and is not responsible for customer applications or product or software design or performance relating to systems or applications incorporating TI products. In addition, TI assumes no liability and is not responsible for infringement of patents and/or any other intellectual or industrial property rights of third parties, which may result from assistance provided by TI. TI products are not designed, intended, authorized or warranted to be suitable for life support applications or any other life critical applications which could involve potential risk of death, personal injury or severe property or environmental damage. The RFID Systems logo, TIRIS logo, the words RFID Systems, TIRIS and Tag-it are trademarks or registered trademarks of Texas Instruments Incorporated (TI). Copyright © 2001 Texas Instruments Incorporated (TI). This document may be downloaded onto a computer, stored and duplicated as necessary to support the use of the related TI products. Any other type of duplication, circulation or storage on data carriers in any manner not authorized by TI represents a violation of the applicable copyright laws and shall be prosecuted. Preface Read This First About This Manual This reference guide for the S6350 High-frequency (13.56Mhz) Reader is designed for use by TI customers who are engineers experienced with RFID Systems and Radio Frequency Identification Devices (RFID). Device Name RI-STU-TRDC-01 RI-STU-TRDC-02 Firmware Version 1.4 (ISO 15693-3) 1.4 (ISO 15693-3) Hardware Configuration Right-Angle Connector Straight Connector Regulatory, safety and warranty notices that must be followed are provided in Chapter 4. Conventions The following pictograms and designations are used in the operating instructions: WARNING: A WARNING IS USED WHERE CARE MUST BE TAKEN, OR A CERTAIN PROCEDURE MUST BE FOLLOWED, IN ORDER TO PREVENT INJURY OR HARM TO YOUR HEALTH. CAUTION: This indicates information on conditions, which must be met, or a procedure, which must be followed, which if not needed could cause permanent damage to the system. Note: Indicates conditions, which must be met, or procedures which must be followed, to ensure proper functioning. Information: Indicates conditions or procedures that should be followed to ensure proper functioning of the system. September 2001 S6350 Reader Reference Guide If You Need Assistance Application Centers are located in Europe, North and South America, the Far East and Australia to provide direct engineering support. For more information, please contact your nearest TI-RFID Systems Sales and Application Center. The contact addresses can be found on our home page: http://www.ti-rfid.com. Numerical Representations Unless otherwise noted, numbers are represented as decimal. Hexadecimal numbers are represented with the suffix hex , e.g. A5F1hex Binary numbers are represented with the suffix 2, e.g. 10112 Byte representations: the least significant bit (lsb) is bit 0 and the most significant bit (msb) is bit 7. September 2001 S6350 Reader Reference Guide Document Overview Chapter 1: Introduction......................................................................................................6 1.1 Description..................................................................................................7 1.1.1 Programming Interface...........................................................................7 1.2 Summary of Chapters and Appendixes .........................................................7 Chapter 2: Harware Description.........................................................................................8 2.1 General Specification...................................................................................9 2.1.1 Functional Requirements........................................................................9 2.1.2 Power Supply ........................................................................................9 2.1.3 Output Power ........................................................................................9 2.1.4 Required Antenna Parameters.............................................................. 10 2.1.5 Input / output pins (CN1 pins 3 and 4) ................................................... 10 2.1.6 Baseband receiver ............................................................................... 11 2.1.7 Connector Details ................................................................................ 11 2.1.8 16-pin Header Connector CN1.............................................................. 11 2.1.9 RI-STU-TRDC-01 (CN1) Pin Assignments............................................. 12 2.1.10 RI-STU-TRDC-02 (CN1) Pin Assignments............................................ 13 2.2 Mechanical Specifications .......................................................................... 14 2.2.1 RI-STU-TRDC-01 with 16-pin Right-Angle Connector............................. 14 2.2.2 RI-STU-TRDC-02 with 16-pin Straight Header Connector....................... 15 Chapter 3: Reader Protocol ............................................................................................. 16 3.1 Serial Protocol Definition ............................................................................ 17 3.1.1 Request Packet Format (Host to Reader).............................................. 17 3.1.2 Response Packet Format (Reader to Host)............................................ 18 3.1.3 Command Flags Request..................................................................... 18 3.1.4 Command Flags Response .................................................................. 19 3.1.5 BCC.................................................................................................... 19 3.1.6 Example Request Packet ..................................................................... 19 3.2 Command Definitions................................................................................. 20 3.2.1 Tag-it™ HF Command Definitions......................................................... 20 3.2.2 Miscellaneous Commands.................................................................... 23 3.2.3 ISO/IEC FCD 15693 Part 3 Transmission Protocol................................. 26 3.2.3.1 ISO/IEC 15693-3 Command Codes.................................................... 26 3.2.3.2 Request/Response Packet Format for ISO/IEC 15693-3...................... 26 3.2.3.3 Mandatory Commands ...................................................................... 30 3.2.3.4 Optional Commands.......................................................................... 32 Chapter 4: Regulatory and Warranty Notices.................................................................. 42 4.1 FCC Conformity......................................................................................... 43 4.2 ETSI Conformity ........................................................................................ 43 4.3 CE Conformity........................................................................................... 43 4.4 Warranty and Liability ................................................................................ 43 Appendix B: Downloading Data to FLASH Memory ......................................................... 44 Appendix B: Error Codes................................................................................................. 45 September 2001 S6350 Reader Reference Guide Chapter 1 Introduction Topic Page 1.1 Description..................................................................................................7 1.1.1 Programming Interface...........................................................................7 1.2 Summary of Chapters and Appendixes .........................................................7 September 2001 S6350 Reader Reference Guide 1.1 Description This document describes the features and operational characteristics of the RI-STU-TRDC-01 & -02 S6350 High Frequency Multi-Protocol Readers. The RI-STU-TRDC-02 reader is shown in Figure 1. The S6350 Reader operates at a frequency of 13.56MHz and is compatible with both standard and ISO/IEC 15693 Tag-it inlays and tags. This reference guide provides the details that are necessary to properly interface and use the reader as a part of an integrated system. In compliance with the ISO/IEC 15693 standard, a global open standard for optimal use under different regulatory and noise environments around the world, the S6350 Reader allows for the interoperability of inlays and tags from multiple manufacturers. Figure 1: S6350 High Frequency Reader 1.1.1 Programming Interface The S6350 Reader is designed to operate as a part of a host-based reader system, which essentially relegates the reader to be a slave to the host. Host-to-Tag-it reader serial communications are accomplished within data packets whereby communications from the host to the reader are known as requests, and replies from the reader to the host are known as responses. This communication occurs at RS-232 levels using 57,000 baud, 8 data bits, 1 start bit, 1 stop bit and no parity. By definition, the host is always the primary station and initiates all communication sequences. These sequences consist of request/response pairs where the host waits for a response prior to continuing. 1.2 Summary of Chapters and Appendixes Chapter 1: Introduction Chapter 2: Hardware Description Chapter 3: Reader Protocol Chapter 4: Regulatory & Warranty Notices Appendix A: Downloading Data Appendix B: Error Codes Chapter 2 Hardware Description Topic Page 2.1 General Specification...................................................................................9 2.1.1 Functional Requirements........................................................................9 2.1.2 Power Supply ........................................................................................9 2.1.3 Output Power ........................................................................................9 2.1.4 Required Antenna Parameters.............................................................. 10 2.1.5 Input / output pins (CN1 pins 3 and 4) ................................................... 10 2.1.6 Baseband receiver ............................................................................... 11 2.1.7 Connector Details ................................................................................ 11 2.1.8 16-pin Header Connector CN1.............................................................. 11 2.1.9 RI-STU-TRDC-01 (CN1) Pin Assignments............................................. 12 2.1.10 RI-STU-TRDC-02 (CN1) Pin Assignments............................................ 13 2.2 Mechanical Specifications .......................................................................... 14 2.2.1 RI-STU-TRDC-01 with 16-pin Right-Angle Connector............................. 14 2.2.2 RI-STU-TRDC-02 with 16-pin Straight Header Connector....................... 15 September 2001 S6350 Reader Reference Guide 2.1 General Specification This chapter describes the electrical and mechanical specifications of the S6350 RI-STU-TRDC-02 reader. Operating at a frequency of 13.56 MHz, this low profile, low power device is designed to be easily integrated into many systems as an embedded device. All reader I/O is accomplished through the use of a 16-pin header connector (labeled as CN1), to include all communication, which is asynchronous RS232 as controlled by a host system. 2.1.1 Functional Requirements The following parameters define the functional requirements and operational environment of the S6350 reader. Parameter Specifications Operating temperature Storage temperature (500 hours) -20 C to +70 C Thermal shock Mechanical shock Vibration Humidity Operating frequencies Transponder types Standard compliance -40 C to +85 C -40 C to +85 C, using MIL-STD-810E, Method 503.3, for 100 cycles duration, 30 minutes per temperature. 5 Gs at 10 ms, half sinusoidal waves, 6 axes (MIL STD801E, Method 516.3) 15 Hz to 500 Hz, 1 g peak, 30 minutes sweep, logarithmic (MIL-STD-810E, Method 514.4) 500 hours at 80% humidity, non-condensing at 70 C 13.56 MHz up-link and down-link 13.56 MHz TI Tag-it™ tag (Standard & ISO tag) FCC Part 15, Subpart C, “Intentional Radiator” 2.1.2 Power Supply Input Voltage 5 ± .5 VDC Average quiescent current 90mA Average current during read (Dependent on read rate) 200mA (for TAG-IT tags) Maximum current during read 250mA 2.1.3 Output Power Output Power 120mW into 50 Ohms (Typical) CAUTION: The S 6350 reader is an intentional radiator, and when integrated, the integrator is subject to meeting FCC Part 15, Subpart C, and similar tenets under European Standard EN 300330. September 2001 S6350 Reader Reference Guide 2.1.4 Required Antenna Parameters 50Ω ± 5Ω at 13.56 MHz 10 < Q < 30 Impedance Loaded Q Note: As no standard antenna is provided by Texas Instruments for the S6350 reader, the noted required antenna parameters must be closely followed by the integrator for the reader to operate properly. 2.1.5 Input / output pins (CN1 pins 3 and 4) Pins 3 and 4 on CN1 may be configured by software commands to read a logic level input or to switch an external load to ground (no pull-up is provided). Figure 2: Example Circuit Diagram of an IO pin When used as a switch to ground the following ratings should not be exceeded: Maximum voltage Maximum current 20V 50mA CAUTION: Exceeding this Voltage and Current limit could cause permanent damage to the reader. Note: That if an output has been set by a software command the state will always read back as a logic 0. 10 September 2001 S6350 Reader Reference Guide 2.1.6 Baseband receiver Minimum data pulse width 5uS Maximum data pulse width 500uS Typical settling time 50uS from the first transition Note: The receiver extracts the mean level of the incoming data stream as a reference. This takes approximately 50uS; therefore the data output of the receiver is not valid until after this time. 2.1.7 Connector Details All reader input and output is provided through a 16-pin header connector that is mounted on the backside of the reader for the RI-STU-TRDC-02 and on the component side for the RI-STUTRDC-01. The details and orientation of each connector pin are provided in the following tables. 2.1.8 16-pin Header Connector CN1 Pin 10 11 12 13 14 15 16 Function 0 Volts +5 Volts Open collector output / data input 2 Open collector output / data input 1 RS232 TxD (output from reader) RS232 RxD (input to reader) No connection (antenna guard) Antenna screen Antenna signal No connection (antenna guard) RS232 ground No connection (reserved for future expansion) No connection (reserved for future expansion) No connection (reserved for future expansion) No connection (reserved for future expansion) No connection (reserved for future expansion) CAUTION: Only pins 8 and 9 of connector CN1 should be used for the antenna connection. 11 September 2001 2.1.9 S6350 Reader Reference Guide RI-STU-TRDC-01 (CN1) Pin Assignments PCB Figure 3: 16-pin Right-Angle Header Connector (CN1) 16 15 14 13 12 11 10 PCB Component Side 12 September 2001 S6350 Reader Reference Guide 2.1.10 RI-STU-TRDC-02 (CN1) Pin Assignments Figure 4: 16-pin Header Connector (CN1) viewed from component side. 16 15 14 13 12 11 10 COMPONENT SIDE 13 September 2001 S6350 Reader Reference Guide 2.2 Mechanical Specifications 2.2.1 RI-STU-TRDC-01 with 16-pin Right-Angle Connector Figure 5: Note: All dimensions are in metric 14 September 2001 S6350 Reader Reference Guide 2.2.2 RI-STU-TRDC-02 with 16-pin Straight Header Connector Figure 6: Note: All dimensions are in inches COMPONENT SIDE 15 Chapter 3 Reader Protocol Topic Page 3.1 Serial Protocol Definition ............................................................................ 17 3.1.1 Request Packet Format (Host to Reader).............................................. 17 3.1.2 Response Packet Format (Reader to Host)............................................ 18 3.1.3 Command Flags Request..................................................................... 18 3.1.4 Command Flags Response .................................................................. 19 3.1.5 BCC.................................................................................................... 19 3.1.6 Example Request Packet ..................................................................... 19 3.2 Command Definitions................................................................................. 20 3.2.1 Tag-it™ HF Command Definitions......................................................... 20 3.2.2 Miscellaneous Commands.................................................................... 23 3.2.3 ISO/IEC FCD 15693 Part 3 Transmission Protocol................................. 26 3.2.3.1 ISO/IEC 15693-3 Command Codes.................................................... 26 3.2.3.2 Request/Response Packet Format for ISO/IEC 15693-3...................... 26 3.2.3.3 Mandatory Commands ...................................................................... 30 3.2.3.4 Optional Commands.......................................................................... 32 16 September 2001 S6350 Reader Reference Guide 3.1 Serial Protocol Definition The S6350 reader accepts and sends data at RS232 levels, 57600 baud, 8 data bits, 1 start bit, 1 stop bit and no parity. The data packet from the host to the reader is known as the request and the reply from the reader to the host as the response. The host is always the primary station and initiates all communication sequences. These consist of request/response pairs where the host waits for a response before continuing. The S6350 reader does not use the node address. 3.1.1 Request Packet Format (Host to Reader) Field Name Field Size Field Value Purpose SOF 1 byte 01hex Start of Frame Field Name Field Size Field Value Purpose Length 2 byte LSB first Packet dependent Describes the length of the whole packet including SOF Field Name Field Size Field Value Purpose Node Address 2 byte LSB first 0000hex Must be 0000hex for upward compatibility Field Name Field Size Field Value Purpose Command flags 1 byte Varies by command Specifies the action to be taken by the reader Field Name Field Size Field Value Purpose Command 1 byte Varies by command Specifies the action to be taken by the reader Field Name Field Size Field Value Purpose Data 0 to xx bytes Command dependent Contains the parameters and data for the command Field Name Field Size Field Value Purpose BCC 2 bytes 16 bit LRC of the preceding packet including the SOF Allows the reader to validate the correct reception of the request packet 17 September 2001 S6350 Reader Reference Guide 3.1.2 Response Packet Format (Reader to Host) Field Name Field Size Field Value Purpose SOF 1 byte 01hex Start of Frame Field Name Field Size Field Value Purpose Length 2 byte LSB first Packet dependent Describes the length of the whole packet including SOF Field Name Field Size Field Value Purpose Node Address 2 byte LSB first 0000hex always 0000hex Field Name Field Size Field Value Purpose Command flags 1 byte Varies by command Specifies the action just taken by the reader Field Name Field Size Field Value Purpose Command 1 byte Varies by command Specifies the action just taken by the reader Field Name Field Size Field Value Purpose Data 0 to 23 bytes Command dependent Contains the parameters and data for the command just processed Field Name Field Size Field Value Purpose BCC 2 bytes 16 bit LRC of the preceding packet including the SOF Allows the host to validate the correct reception of the response packet 3.1.3 Command Flags Request The command flags in the request packet control the actions of the reader. The meanings of the bits are defined below. Bits 0-3 Reserved for future use and should be set to ‘0’ for upward compatibility. Bit 4 Is the address flag and if set, the command is only performed on transponders whose address matches the data section of the packet. Bits 5-7 Reserved for future use and should be set to ‘0’ for upward compatibility. 18 September 2001 S6350 Reader Reference Guide 3.1.4 Command Flags Response The command flags in the response packet report the actions of the reader. The meanings of the bits are defined below. Bits 0-3 Reserved for future use. Bit 4 Error flag. If this flag is set the command was unsuccessful and the data section of the response packet contains the error code. (See section Appendix B for a list of error codes.) Bits 5-7 Reserved for future use. 3.1.5 BCC A Block Check Character (BCC) is used for error detection and is attached to the end of the packet. The 16 bit BCC is calculated on all the bytes of the packet including the SOF. The BCC consists of two parts: the LSbyte is a Longitudinal Redundancy Check (LRC) and the MSbyte is the ones compliment of the LRC. The LRC is calculated by performing a cumulative ExclusiveOR operation on all the bytes of the packet. 3.1.6 Example Request Packet 01 hex 0A hex 00 hex 00 hex 00 hex 00 hex 02 hex 01 hex 08 hex F7 hex SOF LSbyte of length MSbyte of length LSbyte of node address MSbyte of node address Command flags (Not addressed) TM Command (Tag-it Read block) Data (Block number 1) LSbyte of Checksum MSbyte of Checksum 19 September 2001 S6350 Reader Reference Guide 3.2 Command Definitions 3.2.1 Tag-it™ HF Command Definitions Command Function (Tag-it HF) Read Single Non-addressed & Addressed Block Write Single Non-addressed & Addressed Block Lock Single Non-addressed & Addressed Block Read Transponder Details Special Read Block Command Command Code 02hex 03hex 04hex 05hex 0Fhex Read Block Command (02hex) TM Reads a single block of data from a Tag-it transponder. If the address flag is set, the address forms the first part of the data section (LSbyte first), followed by a single byte containing the block number to be read. If the address flag is clear the data section only contains the block number. Example TM Read block 3 of a Tag-it transponder whose address is 0134A4D5hex Request packet 01 0E 00 00 00 10 02 D5 A4 34 01 03 5A A5hex The response packet is similar to the request packet, with the data section containing the data received from the transponder (LSbyte first) followed by a single byte indicating the lock status and then another single byte containing the block address. The two LSB’s of the lock status byte reflect the two lock bits in the transponder. Example Response packet 01 0F 00 00 00 00 02 33 22 11 00 00 03 0F F0 hex TM 00112233hex read from unlocked block 3 of a Tag-it transponder. Write Block Command (03hex) TM Writes a single block of data to a Tag-it transponder. If the address flag is set, the address forms the first part of the data section, followed by a single byte containing the block number to be written. The data to be written follows the block number. If the address flag is clear the data section only contains the block byte and the data to be written. Example TM Write Block 4 of a Tag-it transponder whose address is 000134A4hex with data 01234567hex Request packet 01 12 00 00 00 10 03 A4 34 01 00 04 67 45 23 01 95 6A hex The response packet is similar to the request packet; with the data section containing 00hex for a successful write operation. 20 September 2001 S6350 Reader Reference Guide Example Response packet 01 0A 00 00 00 00 03 00 08 F7hex Successful write. Lock Block Command (04hex) TM Locks a single block of data in a Tag-it transponder. If the address flag is set, the address forms the first part of the data section, followed by a single byte containing the number of the block to lock. Example TM Lock Block 4 of a Tag-it transponder whose address is 000134A4hex Request packet 01 0E 00 00 00 10 04 A4 34 01 00 04 8E 71hex The response packet is similar to the request packet, with the data section containing 00hex for a successful lock operation. Example Response packet 01 0A 00 00 00 00 04 00 0F F0hex Successful lock. Read Transponder Details Command (05hex) Reads the details of a Tag-it forms the data section. TM transponder. If the address flag is set, the address Example TM Read the details of a Tag-it transponder non-address Request packet 01 09 00 00 00 00 05 0D F2hex The response packet is similar to the request packet, with the data section containing the transponder address (4 bytes), manufacturers code (1 byte), transponder version number (2 bytes), the number of blocks (1 byte) and the number of bytes per block (1byte). Example Response packet 01 12 00 00 00 00 05 A4 34 01 00 01 05 00 08 04 8F 70hex Transponder ID 000134A4hex Manufacturers Number 01hex Version Number 0005hex Number of blocks 08hex Number of bytes per block 04hex Special Read Block Command (0Fhex) TM Reads blocks of data from a Tag-it transponder. The address flag should not be used. The data section contains a single byte detailing the blocks to be read. Each bit of this byte represents a block of data (bit 0 = block 0 etc) if a bit is set then that block is read. If the data byte is zero then only the SID is returned. The SID is always retrieved first and then used to read the selected blocks in addressed mode. 21 September 2001 S6350 Reader Reference Guide Example TM Read blocks 0, 3 & 4 of a Tag-it transponder (data byte = 00011001bin = 19hex ) Request packet 01 0A 00 00 00 00 0F 19 1D E2hex The data section of the response packet contains: The SID address (LSbyte first), Block 0 data (if selected) followed by a single byte indicating the lock status and then another single byte containing the block address, Block 1 data (if selected) followed by a single byte indicating the lock status and then another single byte containing the block address, Block 7 data (if selected) followed by a single byte indicating the lock status and then another single byte containing the block address, (The two LSB’s of the lock status bytes reflect the blocks two lock bits in the transponder.) Example Response packet 01 1F 00 00 00 00 0F 23 4F 10 00 EF CD AB 89 00 00 33 22 11 00 00 03 67 45 23 01 00 04 6A 95 hex 00104F23hex 89ABCDEFhex 00112233hex 01234567hex SID TM read from unlocked block 0 of a Tag-it transponder. TM read from unlocked block 3 of a Tag-it transponder. TM read from unlocked block 4 of a Tag-it transponder. 22 September 2001 S6350 Reader Reference Guide 3.2.2 Miscellaneous Commands Command Function Initiate FLASH Loader Command Send Data to FLASH Command Reader Version Command Read Inputs Command Write Reader Outputs Command RF Carrier on/off Command Command Code D0hex D8hex F0hex F1hex F2hex F4hex Initiate FLASH Loader Command (D0 hex) This command is used to initialize and transfer control to the FLASH loader software. Example Request packet 01 09 00 00 00 00 D0 D8 27hex The response packet is similar to the request packet with the data section containing ‘00’ if successful. Example Response packet 01 0A 00 00 00 00 D0 00 DB 24hex FLASH loader initialised and control transferred. Send Data to FLASH Command (D8hex) This command is used to load data into the FLASH memory. Example Request packet 01 8D 00 00 00 00 D8 <132 bytes of data> <2 byte checksum> hex The Data section must always contain 132 bytes The response packet data section contains ‘00’ if successful. Example Response packet 01 0A 00 00 00 00 D8 00 D3 2Chex The section of FLASH memory was programmed correctly. Reader Version Command (F0hex) Requests the version number of the reader. The flags are ignored for this command. Example Get the version number of the reader. Request packet 01 09 00 00 00 00 F0 F8 07hex The response packet is similar to the request packet with the data section containing the 2 byte version number LSB first followed by a single byte representing the reader type. 23 September 2001 S6350 Reader Reference Guide Reader Type Example Response packet 01 0C 00 00 00 00 F0 40 01 07 BB 44hex The version number is 1.4 The reader type response can be defined as follows: Type 07 = Indicates that the reader has been successfully loaded with the noted application firmware version number (in this example, version 1.4). Type 00 = Indicates that the reader has not been loaded with application firmware, but does have the boot-loader firmware in place with which to download the appropriate application firmware. (Please refer to Appendix A: Downloading Data to FLASH Memory) Reader inputs Command (F1hex) Reads the state of the reader inputs. The flags are ignored for this command. Example Get the status of the reader inputs. Request packet 01 09 00 00 00 00 F1 F9 06hex The response packet is similar to the request packet with the data section containing a byte representing the state of the inputs. Bit 0 of this byte represents input 1 and bit 1 represents input 2 all other bits are reserved. Example Response packet 01 0A 00 00 00 00 F1 01 FB 04hex Input 1 is at Logic 1 Input 2 is at Logic 0 Write reader outputs Command (F2hex) Writes the state of the reader outputs. The flags are ignored for this command. The data section contains 1 byte with bits defined as follows: Bit Bit Bit Bit Bit Bit Bit Bit 1 = Output 1 switched on (output is pulled to ground) 1 = Output 2 switched on (output is pulled to ground) Reserved Reserved 1 = Bit 0 enabled (output 1 is controlled) 1 = Bit 1 enabled (output 2 is controlled) Reserved Reserved Example Switch output 2 on without affecting output 1. Request packet 01 0A 00 00 00 00 F2 22 DB 24hex 24 September 2001 S6350 Reader Reference Guide The response packet is similar to the request packet with the data section containing ‘00hex ’ for a successful write operation. Example Response packet 01 0A 00 00 00 00 F2 00 F9 06hex Write successful. RF Carrier on/off Command (F4hex) Switches the RF carrier on or off. The data section contains one byte FFhex to turn the carrier on or 00hex to turn the carrier off. Example Switch the carrier on. Request packet 01 0A 00 00 00 00 F4 FF 00 FFhex The response packet is similar to the request packet with the data section containing ‘00hex ’ for a successful operation. Example Response packet 01 0A 00 00 00 00 F4 00 FF 00hex Command successful. 25 September 2001 S6350 Reader Reference Guide 3.2.3 ISO/IEC FCD 15693 Part 3 Transmission Protocol TM In addition to supporting the Tag-it protocol outlined within the preceding section, the S6350 Mid-Range HF-I Reader complies with the standard RF interface and transmission protocol of ISO/IEC IS 15693-2 & 3. Please note that each of the ISO protocol command and response packets outlined within the following sections are contained within the standard reader protocol as outlined within Section 3.1. It should also be noted that the details of the individual ISO 15693-3 commands are not provided within this document, but are covered within the ISO/IEC IS 15693-3:2001(E) Anti-Collision and Transmission Protocol document. The ISO 15693-3 commands that are specifically applicable to the S6350 Reader are defined within the following table. 3.2.3.1 ISO/IEC 15693-3 Command Codes Command Function Inventory (Mandatory Command) Stay Quiet (Mandatory Command) Read Single Block Write Single Block* Lock Block* Read Multiple Blocks Write AFI* Lock AFI* Write DSFID* Lock DSFID* Get Multiple Block Security Status Command Code 01hex 02hex 20hex 21hex 22hex 23hex 27hex 28hex 29hex 2Ahex 2Chex Note: * Bit 7 of the ISO 15693 protocol Option_Flag must be set to 1 for all Write and Lock commands to respond properly. 3.2.3.2 Request/Response Packet Format for ISO/IEC 15693-3 The data packet from the host to the reader is known as the request and the reply from the reader to the host as the response. The host is always the primary station and initiates all communication sequences. These consist of request/response pairs where the host waits for a response before continuing. All ISO/IEC 15693-3 command request packets are contained within the standard reader command request packet format. In all cases, reader command 60hex is used to pass through ISO 15693 Part 3 commands to the reader. 26 September 2001 S6350 Reader Reference Guide The Configuration Byte (ISO Command Data Byte 0) As detailed in ISO/IEC 15693-2, the Configuration Byte (ISO Command Data Byte 0) is an 8bit byte that is used to configure the Data Coding Mode and Modulation Depth of the reader. Modulation Depth Bit 4 of the Configuration Byte is used to set Modulation Depth. When set high the reader is configured for 100% Modulation Depth, when set low the reader will operate at 10% to 30% (with a 20% nominal setting) Modulation Depth. Data Coding Mode Bit 0 of the Configuration Byte is used to set the Data Coding Mode. When set high the reader is configured for Data Coding Mode 1 / 4; when set low the reader is configured for Data Coding Mode 1 / 256. Request Packet Format for ISO/IEC 15693-3 The request packet consists of the header, packet length, node address, command flags, reader command (60hex ), ISO/IEC 15693-3 command/data bytes 0 to some number “n” (where byte 0 is the configuration byte) and the checksum. ISO 15693 Command Data Request Structure The structure of the ISO 15693 Command Data Request is contained within the Data section of the ISO Command Data, bytes 1 - n. Specific to the S6350 reader, the ISO 15693 SOF, CRC16 and EOF fields must not be included in the message data packet. Please refer to ISO/IEC 15693-3 for details about the ISO packet format). Specific to the S6350 reader, the ISO 15693 SOF, CRC16 and EOF fields must not be included. Note: The protocol of S 6350 reader does not use the ISO 15693 SOF, CRC16 and EOF fields within its message packet. Note: Please refer to ISO/IEC 15693-3 for details about the ISO message packet. 27 September 2001 S6350 Reader Reference Guide Request Packet Format Standard reader Request Packet Format (See Section 3.1) Header Packet Length Node Address Command Flag Command ‘01hex’ 1 byte LSB MSB 2 bytes LSB MSB 2 bytes Flags 1 byte ‘60hex’ 1 byte ISO Command Data Config. Data Byte XXhex Data Byte 0 bytes 1-n 1 byte bytes Checksum Byte 1 Byte 2 2 bytes Request Packet Description Field Header Packet Length Node Address Command Flags Command Length 1 byte 2 bytes 2 bytes 1 byte 1 byte Data 0-n bytes 2 bytes Checksum Description Defines the start of the packet (01hex ). Defines the length of the packet, including checksum. Defines the Node address of the reader. Defines how a command will be executed. Defines the command for the reader to execute (60hex for ISO 15693-3 commands) Defines the data required by the reader for a command. Byte 1 is an XOR checksum of all elements from the header to the last byte Response Packet Format for ISO/IEC 15693-3 Similar to the request packet, the response packet consists of the header, packet length, node address, command flags, reader command (60hex ), ISO/IEC 15693-3 command/data bytes 0 to some number “m” and the checksum. The ISO Response Data packet can come in one of two possible generic formats: (a) One for the ISO Inventory Response, and (b) all other ISO responses. These will be highlighted in the following sections. Note: With the exception of the ISO Inventory Response packet, the format for each standard response packet is the same. The Error Byte (ISO Response Data Byte 0) There are three possible reader errors that can be generated in response to an ISO 15693 command. This error code will be returned within the Error Byte (Byte 0) of the ISO Response Data. The error codes are as follows: 01hex 02hex 04hex Transponder not found Command not supported Invalid flags 28 September 2001 S6350 Reader Reference Guide Response Packet Format Standard reader Response Packet Format (See Section 3.1) Header ‘01hex’ Packet Length LSB 1 byte MSB 2 bytes Node Address LSB MSB 2 bytes Response Flags Command Flags ‘60hex’ 1 byte 1 byte ISO Response Data Data bytes 0 - ‘m’ ‘m’ bytes Checksum Byte 1 Byte 2 2 bytes Response Packet Description Field Header Packet Length Node Address Response Flags Length 1 byte 2 bytes Description Defines the start of the packet (01hex ). Defines the length of the packet, including checksum. 2 bytes Defines the Node address of the reader. 1 byte Command 1 byte Data 0-m bytes 2 bytes Defines the response of the reader to the request. Bit 4 defines the error status; a set value indicates that an error has occurred. (Other values reserved for future use) Defines the command that the reader executed (60hex for ISO 15693-3 commands) Defines the data returned by the reader in response to a command. Checksum Byte 1 is an XOR checksum of all elements from the header to the last byte of the data field. Byte 2 is calculated as (FFhex ) XOR (byte 1) 29 September 2001 S6350 Reader Reference Guide 3.2.3.3 Mandatory Commands The data packet from the host to the reader is known as the request and the reply from the reader to the host as the response. The host is always the primary station and initiates all communication sequences. These consist of request/response pairs where the host waits for a response before continuing. All ISO/IEC 15693-3 command request packets are contained within the standard reader command request packet format. In all cases, reader command 60hex is used to pass through ISO 15693 Part 3 commands to the reader. Inventory: Command Code (01hex) ISO Inventory Request Command Packet Header Packet Node Cmd Cmd Length Address Flag ‘01hex’ 2 bytes SOF Flags Not Used byte 2 bytes byte ISO Command Data Config. Byte Data Byte 0 bytes 1-n ‘60hex’ ISO Inventory Request Format Inventory Opt. Mask Mask Command AFI Length Value ‘O1hex’ byte 1 byte 0-7 bytes Check -sum bytes CRC16 EOF Not Used Not Used ISO Inventory Response Packet The inventory response packet format, while complying with ISO 15693, is unique to the reader reader and is described within the following illustrations. All other ISO 15693 packet responses contain ISO 15693 data as detailed within ISO/IEC FDIS 15693-3. Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ ISO Response Data Data bytes 0-m SOF ISO Inventory Response Format Valid Data Collision 80-bit response to Flags Flags Inventory Command Not Used 2 bytes LSB/MSB 2 bytes LSB/MSB st Data returned from 1 valid time slot 30 Check sum 2 bytes Etc… CRC16 EOF Etc… Not Used Not Used September 2001 S6350 Reader Reference Guide Valid Data & Collision Flags Valid Data Flags: This 16-bit field corresponds to whether valid data was received in the 16 possible Time Slots. Bits 0 to 7 of the LSB respectively correspond to Time Slots 1 to 8, while bits 0 to 7 of the MSB correspond to Time Slots 9 to 16 respectively. A set bit corresponds to valid data being received in that particular Time slot. Collision Flags: This 16-bit field corresponding to whether a collision occurred in the 16 possible Time Slots. Bits 0 to 7 of the LSB respectively correspond to Time Slots 1 to 8, while bits 0 to 7 of the MSB correspond to Time Slots 9 to 16 respectively. A set bit corresponds to a collision being detected in that particular Time Slot. Note: It is possible to issue the Inventory Command for just 1 Time Slot instead of 16. In this case, the preceding packet structure is still valid; the required Valid Data flag and Collision flag reside in bit 0 of the LSB of their respective fields. It follows that issuing the Inventory Command for a single Time Slot will result in a maximum of one 80-bit response being returned If both a Valid Data flag and its corresponding Collision flag are both clear then this indicates that no transponder was detected for that particular Time Slot. Starting from Time Slot 1 and progressing to Time Slot 16, for each Time Slot where a transponder was successfully read (without collision), its 80-bit data is appended to the Data section of the message packet. 31 September 2001 S6350 Reader Reference Guide ISO Stay Quiet Request Command Packet: Command Code (02hex) Upon receipt of the Stay Quiet command, the ISO tag will enter the quiet state and will not initiate a response. Note: There is no response to the Stay Quiet command. The Stay Quiet command is always executed in the Addressed mode: Select_flag set to 0 Addressed_flag set to 1 Header ‘01hex’ Packet Length Node Address Cmd Flag Cmd 2 bytes 2 bytes byte ‘60hex’ SOF Flags Not Used 1 byte ISO Command Data Config. Byte Data Byte 0 bytes 1-n ISO Stay Quiet Request Format Stay Quiet UID Command ‘O2hex’ Check -sum 8 bytes bytes CRC16 EOF Not Used Not Used 3.2.3.4 Optional Commands Read Single Block: Command Code (20hex) ISO Read Single Block Request Command Packet Header Packet Node Cmd Cmd ISO Command Data Length Address Flag Config. Data Byte ‘01hex’ 2 bytes 2 bytes ‘60hex’ Byte 0 bytes byte 1-n SOF Flags Not Used 1 byte ISO Request Format Read UID Single Block ‘20hex’ 8 bytes 32 Check -sum bytes Block number CRC16 EOF 1 byte Not Used Not Used September 2001 S6350 Reader Reference Guide ISO Read Single Block Response Packet Header ‘01hex’ SOF Not Used Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ ISO Response Data Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 0-m Check sum 2 bytes CRC16 EOF Not Used Not Used CRC16 EOF Not Used Not Used OR SOF Not Used Response when Error_flag is not set Flags Block Security Data status 1 byte 1 byte 33 Block length September 2001 S6350 Reader Reference Guide ISO Write Single Block: Command Code (21hex) ISO Write Single Block Request Command Packet Header ‘01hex’ Packet Length Node Address Cmd Flag Cmd 2 bytes 2 bytes byte ‘60hex’ SOF *Flags Not Used 1 byte ISO Command Data Config. Byte Byte 0 ISO Request Format Write UID Single Block ‘21hex’ 8 bytes Checksum Data bytes 1-n 2 bytes Block number CRC16 EOF 1 byte Not Used Not Used ISO Write Single Block Response Packet Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ SOF Not Used ISO Response Data Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 1-m Check sum 2 bytes CRC16 EOF Not Used Not Used OR SOF Response when Error_flag is not set Flags Not Used 1 byte CRC16 EOF Not Used Not Used Note: * Bit 7 of the ISO 15693 protocol Option_Flag must be set to 1 for all Write and Lock commands to respond properly. 34 September 2001 S6350 Reader Reference Guide ISO Lock Block: Command Code (22hex) ISO Lock Block Request Command Packet Header ‘01hex’ Packet Length Node Address Cmd Flag Cmd 2 bytes 2 bytes byte ‘60hex’ SOF *Flags Not Used 1 byte ISO Command Data Config. Byte Data Byte 0 bytes 1-n ISO Request Format Lock UID Block ‘22hex’ Checksum 8 bytes 2 bytes Block number CRC16 EOF 1 byte Not Used Not Used ISO Lock Block Response Packet Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ SOF Not Used ISO Response Data Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 1-m Check sum 2 bytes CRC16 EOF Not Used Not Used OR SOF Response when Error_flag is not set Flags Not Used 1 byte CRC16 EOF Not Used Not Used Note: * Bit 7 of the ISO 15693 protocol Option_Flag must be set to 1 for all Write and Lock commands to respond properly. 35 September 2001 S6350 Reader Reference Guide ISO Read Multiple Blocks: Command Code (23hex) ISO Read Multiple Blocks Request Command Packet Header ‘01hex’ Packet Length Node Address Cmd Flag Cmd 2 bytes 2 bytes byte ‘60hex’ SOF Flags Not Used 1 byte ISO Command Data Config. Byte Byte 0 ISO Request Format st Read UID Multiple Block Blocks ‘23hex’ 1 byte bytes Checksum Data bytes 1-n 2 bytes # of blocks CRC1 EOF 1 byte Not Used Not Used ISO Read Multiple Blocks Response Packet Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ SOF Not Used ISO Response Data Check sum Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 1-m bytes CRC16 EOF Not Used Not Used OR SOF Flags Not Used 1 byte Response when Error_flag is not set Block Data Security Status 1 byte Block length Repeat as needed 36 CRC16 EOF Not Used Not Used September 2001 S6350 Reader Reference Guide ISO Write AFI: Command Code (27hex) ISO Write AFI Request Command Packet Header ‘01hex’ Packet Length Node Address Cmd Flag Cmd 2 bytes 2 bytes byte ‘60hex’ SOF *Flags Not Used 1 byte ISO Command Data Config. Byte Data Byte 0 bytes 1-n ISO Request Format Write UID AFI ‘27hex’ Chec k-sum 8 bytes bytes AFI CRC16 EOF 1 byte Not Used Not Used ISO Write AFI Response Packet Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ SOF Not Used ISO Response Data Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 1-m Check sum 2 bytes CRC16 EOF Not Used Not Used OR SOF Response when Error_flag is not set Flags Not Used 1 byte CRC16 EOF Not Used Not Used Note: * Bit 7 of the ISO 15693 protocol Option_Flag must be set to 1 for all Write and Lock commands to respond properly. 37 September 2001 S6350 Reader Reference Guide ISO Lock AFI: Command Code (28hex) ISO Lock AFI Request Command Packet Header Packet Node Cmd Length Address Flag ‘01hex’ 2 bytes 2 bytes Cmd byte ISO Command Data Config. Byte Byte 0 ‘60hex’ SOF *Flags ISO Request Format Lock UID AFI Not Used 1 byte ‘28hex’ 8 bytes Checksum Data bytes 1-n 2 bytes AFI CRC16 EOF 1 byte Not Used Not Used ISO Lock AFI Response Packet Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ SOF Not Used ISO Response Data Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 1-m Check sum 2 bytes CRC16 EOF Not Used Not Used OR SOF Response when Error_flag is not set Flags Not Used 1 byte CRC16 EOF Not Used Not Used Note: * Bit 7 of the ISO 15693 protocol Option_Flag must be set to 1 for all Write and Lock commands to respond properly. 38 September 2001 S6350 Reader Reference Guide ISO Write DSFID: Command Code (29hex) ISO Write DSFID Request Command Packet Header ‘01hex’ Packet Length Node Address Cmd Flag Cmd 2 bytes 2 bytes byte ‘60hex’ SOF *Flags Not Used 1 byte ISO Command Data Config. Byte Data Byte 0 bytes 1-n ISO Request Format Write UID DSFID ‘29hex’ 8 bytes Checksum 2 bytes DSFID CRC16 EOF 1 byte Not Used Not Used ISO Write DSFID Response Packet Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ SOF Not Used ISO Response Data Check sum Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 1-m 2 bytes CRC16 EOF Not Used Not Used OR SOF Response when Error_flag is not set Flags Not Used 1 byte CRC16 EOF Not Used Not Used Note: * Bit 7 of the ISO 15693 protocol Option_Flag must be set to 1 for all Write and Lock commands to respond properly. 39 September 2001 S6350 Reader Reference Guide ISO Lock DSFID: Command Code (2Ahex) ISO Lock DSFID Request Command Packet Header ‘01hex’ Packet Length Node Address Cmd Flag Cmd 2 bytes 2 bytes byte ‘60hex’ SOF *Flags Not Used 1 byte ISO Command Data Config. Byte Byte 0 ISO Request Format Lock UID DSFID ‘2Ahex’ 8 bytes Data bytes 1-n CRC16 EOF Not Used Not Used Checksum 2 bytes ISO Lock DSFID Response Packet Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ SOF Not Used ISO Response Data Check sum Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 1-m 2 bytes CRC16 EOF Not Used Not Used OR SOF Response when Error_flag is not set Flags Not Used 1 byte CRC16 EOF Not Used Not Used Note: * Bit 7 of the ISO 15693 protocol Option_Flag must be set to 1 for all Write and Lock commands to respond properly. 40 September 2001 S6350 Reader Reference Guide ISO Get Multiple Block Security Status: Command Code (2Chex) ISO Get Multiple Block Security Status Request Command Packet Header ‘01hex’ Packet Length Node Address Cmd Flag Cmd 2 bytes 2 bytes byte ‘60hex’ SOF Flags Not Used 1 byte ISO Command Data Config. Byte Byte 0 ISO Request Format st Get Multiple UID Block Security Block Status ‘2Chex’ bytes Data bytes 1-n Checksum 2 bytes # of Blocks CRC16 EOF bytes Not Used Not Used ISO Get Multiple Block Security Status Response Packet Header ‘01hex’ Packet Length Node Address Response Flags Command 2 bytes 2 bytes 1 byte ‘60hex’ SOF Not Used ISO Response Data Check sum Data Response when Error_flag is set Flags Error Code 1 byte 1 byte bytes 1-m 2 bytes CRC16 EOF Not Used Not Used OR SOF Not Used Response when Error_flag is not set Flags Block Security Status 1 byte 1 byte Repeat as needed 41 CRC16 EOF Not Used Not Used Chapter 4 Regulatory and Warranty Notices Topic Page 4.1 FCC Conformity......................................................................................... 43 4.2 ETSI Conformity ........................................................................................ 43 4.3 CE Conformity........................................................................................... 43 4.4 Warranty and Liability ................................................................................ 43 42 July 2001 Series 6350 Reader Reference Guide 4.1 FCC Conformity The S 6350 reader is an intentional radiator. The transmitter portion operates at 13.56 MHz and is subject to FCC Part 15, Subpart C, “Intentional Radiator,” paragraph 15.225 (13.55313.567MHz). Radiated emissions from the device are subject to the limits in Section 15.209 of the Rules outside of the 13.56 +/- 0.007 MHz band. Note: Any device or system incorporating the S 6350 reader, in full or in part, needs to obtain FCC certification as part of the system within which this reader unit resides. A system containing this product may be operated only under an experimental license or final approval issued by the relevant approval authority. Before any such device or system can be marketed, an equipment authorization must be obtained form the relevant approval authority. 4.2 ETSI Conformity Any device or system incorporating the S 6350 reader, in full or in part, may need to comply with European Standard EN300330. It is the responsibility of each system integrator to have their complete system tested and to obtain approvals as required from the local authorities before operating or selling this system. 4.3 CE Conformity Any device or system incorporating the S 6350 reader, in full or in part, may need to have a CE Declaration of Conformity stating that it meets European EMC directive 99/5/EC. This must be issued by the system integrator or user of such a system prior to marketing or operating it in the European community. 4.4 Warranty and Liability The "General Conditions of Sale and Delivery" of Texas Instruments Incorporated or a TI subsidiary apply. Warranty and liability claims for defect products, injuries to persons and property damages are void if they are the result of one or more of the following causes: § § § § § § § § Improper use of the reader module. Unauthorized assembly, operation and maintenance of the reader module. Operation of the reader modules with defective and/or non-functioning safety and protective equipment. Failure to observe the instructions during transport, storage, assembly, operation, maintenance and setting up of the reader modules. Unauthorized changes to the reader modules. Insufficient monitoring of the reader modules' operation or environmental conditions. Improperly conducted repairs. Catastrophes caused by foreign bodies and acts of God. 43 Appendix A Downloading Data to FLASH Memory The S 6350 Reader FLASH memory contains two areas: the application area for the Reader application firmware and a boot-loader area for the boot-loader firmware. The boot-loader memory is factory locked. After a reset the boot-loader firmware runs the following sequence: • Control registers are initialized • IO ports are initialized • Application memory is scanned and verified • If the application memory checksums are valid then control is transferred to the application memory • If the checksums fail then the boot-loader takes control of the communications. The boot-loader will only accept the following commands: • Initiate FLASH Loader Command (D0 hex ) • Send Data to FLASH Command (D8hex ) • Read reader Version Command (F0hex ) The boot loader only operates at 57600 baud with 8 data bits, 1 start bit, 1 stop bit and no parity. The application firmware will always accept the Initiate FLASH Loader Command (D0 hex). When this command is received by the application firmware, control is transferred to the bootloader. If the boot-loader does not receive a Send Data to FLASH Command (D8hex) within 5 seconds of the Initiate FLASH Loader Command (D0 hex) then a system reset is generated. The application firmware is provided in a single file and contains all the necessary checksums. The file will always contain 29700 bytes of data. The file must be sent to the reader in one session if any errors occur the whole file must be resent. The file is sent in 225 segments, 132 bytes at a time (225 x 132 = 29700). Each segment is sent using the Send Data to FLASH Command (D8hex). The 132 bytes of data are contained in the data section of the packet. 44 Appendix B Error Codes Code number 01hex 02hex 03hex 04hex 05hex 06hex 07hex 0Fhex Meaning Transponder not found Command not supported Packet BCC invalid Packet flags invalid for command General write failure Write failure due to locked block Transponder does not support function Undefined error 45
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.2 Linearized : No Page Count : 45 Creator : Microsoft Word - 11-06-21-700 Create Date : 2001:10:16 09:29:16 Title : 11-06-21-700 Producer : Acrobat PDFWriter 4.05 for WindowsEXIF Metadata provided by EXIF.tools