Attachment_0003_DoD Transponder Hardwire Electrical Interface and Data P....docx

DoD Transponder Hardwire Electrical Interface and Data Protocol Version 5.0 22 May 2018 Introduction This document describes the hardwire communications interface for an RFID-V compliant Active Transponder used in the Radio Frequency In-Transit Visibility (RF-ITV) system. Specifically addressed is the physical layer and communications protocol for the hardwire communications interface between a RFID-V complaint Active Transponder and a host computer. The hardwire protocol is different than the over-the-air ISO/IEC 18000-7 protocol.

Normative references The following documents are applicable to this document:

ISO/IEC 18000-7:2008 Information technology — Radio frequency identification for item management — Part 7: Parameters for active air interface communications at 433 MHz DoD Over Air Interface Guidelines DoD Interoperability Guidelines for the Over Air Interface USB Mini-B Connector ECN: USB 2.0 Specification Engineering Change Notice (ECN) #1: Mini-B connector, dated October 20, 2000. Available from USB Implementers Forum, Inc. (www.usb.org) USB 2.0 Standard: Universal Serial Bus Specification, Revision 2.0, dated April 27, 2000. Available from USB Implementers Forum, Inc. (www.usb.org) USB 1.1 Standard: Universal Serial Bus Specification, Revision 1.1, dated September 23, 1998. Available from USB Implementers Forum, Inc. (www.usb.org) FTDI FT232R Datasheet: FT232R USB UART I.C. Datasheet, revision 1.04 or later (www.ftdichip.com) FTDI CDM Drivers Release 2.02.04 or greater (www.ftdichip.com) Use of Terms in Document Within this document, the term ISO/IEC 18000-7 standard is used to explicitly reference ISO/IEC 18000-7:2008.

The term USB 2.0 Standard is used to explicitly reference Universal Serial Bus Specification, Revision 2.0, dated April 27, 2000.

The term RFID-V Compliant Active Transponder Protocol will be used to refer to the protocol defined by the ISO/IEC 18000-7:2008 standard with the changes and clarifications identified in the DoD Over Air Guidelines document and the DoD Interoperability Guidelines for the Over Air Interface document.

The term aRFID-V RF Protocol refers to the over-the-air communications portion of the RFID-V Compliant Active Transponder Protocol.

The term aRFID-V Hardwire Protocol refers to the over-wire communications portion of the RFID-V Compliant Active Transponder Protocol, covering communications between a RFID-V complaint Active Transponder and a host computer.

The ISO/IEC 18000-7 standard and related documents use the terms interrogator and reader interchangeably, DoD RFID-V Active RFID recommends use of the term interrogator exclusively. The ISO/IEC 18000-7 standard and related documents use the term tag for the component which the DoD Active RFID recommends use of the term transponder.

Physical Layer The hardwire interface shall use a Universal Serial Bus (USB) interface and standard USB connector as described in the following section.

USB Interface Type The transponder hardwire interface shall conform to the USB 2.0 Standard except as noted in section 4.2 below.

Permissible exceptions to conformance to USB standard USB-IF Logo Compliance Testing Not Required The transponder is not required to bear a USB-IF logo, or undergo USB-IF logo compliance testing, as long as a USB-IF compliant interface design is used. For example, use of the interface configuration defined by the FT232R datasheet interface configuration example: USB to MCU UART Interface, is sufficient.

USB Suspend Mode Not Required The transponder is not required to support the very low power Suspend mode.

USB Line Loading If the transponder derives power from the USB interface, the transponder shall not draw more than one unit load from the USB at any time. This configuration is referred to as a Bus Powered Low Power Device.

USB Connector The following sections describe connector type, accessibility and protection requirements.

Connector Type The transponder shall have a USB Series “Mini-B” receptacle as defined in USB 2.0 Specification Engineering Change Notice (ECN) #1.

Connector Accessibility and Protection When not in use, the USB connector shall be isolated from the environment. Environmental issues of interest are mud, snow, and water.

For use, the USB connector shall be easily accessible by hand, or if necessary, requiring only very commonly available tools.

The USB connector shall be mechanically supported to minimize potential for damage or removal of connector due to rough cable handling.

USB Identification String descriptors shall be implemented for Vendor Name and Product Name (and referenced in the Standard Device Descriptor) for the transponder USB interface. The string descriptors shall contain the text shown in Table 1 in United States English (LANGID Code 0x0409):

Table 1 – Required USB String Descriptors

“DoD Active RFID Transponder”

Use of the USB device descriptor Vendor ID and Product ID values shown in Table 2 are recommended provided a FTDI USB IC device is used.

Table 2 – Recommended USB Device Descriptor ID Values

The Vendor ID and Product ID values shown in Table 2 shall be used to minimize host configuration and driver installation and management issues of widely distributed host workstation user base.

Recommended practice is to disable the USB Serial Number. This is done to prevent reduce the number of virtual serial port numbers on the host computer and to avoid confusion between USB and Transponder serial numbers.

Use of alternate Product or Vendor ID values imposes significant additional FSE effort to insure interoperability in a multivendor environment.

USB Driver The vendor shall provide a USB virtual communications port driver compatible with FTDI’s CDM Driver, including virtual communications port.

Virtual COM Port The vendor shall provide a USB driver or drivers which present to host computer application software a standard asynchronous communications (COM) port application interface, commonly known as a virtual COM port. The virtual COM port shall operate at the parameters shown in Table 3.

Table 3 — Virtual COM Port Parameters

Break Signal Must Be Supported The virtual COM port driver must support the ability to send a break signal to the transponder, and the transponder must support the detection of a break signal.

A break signal is a continuous space condition of the serial line, whose duration exceeds the combined durations of the start bit, the data bits and the stop bit of a serial character. The DoD hardwire interface break signal duration shall be within the range specified in Table 4.

Table 4 -- Break Signal Duration

Other Communication Paradigms May Be Supported Higher baud rates or other communications paradigms beyond the Virtual COM Port may be supported by the Transponder, however all standard DoD features and capabilities must be accessible via the interface and protocol defined in this document.

The transponder can provide to the host an alternative higher baud rate value to the default value defined in Table 3, as part of the initialization sequence as described in section 5.6.3, however the host is not required to use the provided alternative higher baud rate for communications with the transponder.

Communication Sequence Communication between the host and transponder over the hardwire interface consists of three phases; an Initiation phase, a communication and data transfer phase, and a disconnection phase.

Initiation Phase The transponder shall initiate communications over the hardwire interface upon receipt of an initiation signal as described in section 5.6.3.

Communication and Data Transfer Phase Once the hardwire connection has been established, all communications shall be handled in a command/response manner analogous to the aRFID RF Protocol used for the over-the-air interface. Commands are sent by the host to the transponder. The transponder executes the command, and if successful the transponder returns a response to the host. If the transponder is unable to execute command, it issues a Negative Acknowledge and error message. Commands and formats are detailed in section While in the hardwire connected state, the transponder shall disable its RF communications circuitry Disconnection Phase The interrogator shall signal the end of its communications with a transponder by sending the Disconnect command as described in section 5.6.6. Upon receiving the Disconnect command, the transponder shall terminate hardwire communications, and re-enable its RF communications circuitry. The tag shall detect accidental physical disconnection from the Host USB port, and re-enable its RF communications circuitry.

The hardwire interface supports three different messaging schemes, Hardwire control messages, Hardwire versions of aRFID-V RF Protocol messages, and Manufacturer specific messages.

The generic form of the messaging is presented, followed by sections detailing the specifics of each of the messaging schemes.

Generalized Hardwire Message Formats Just as with aRFID-V RF Protocol, hardwire communications are of the Master-Slave type; the host sends command messages to the transponder, which replies with a response message.

The generalized message descriptions which follow show the format and structure of command and response messages.

Generalized Hardwire Host-to-Transponder Command Format The host shall send commands to the transponder with command messages formatted as shown in Table 5.

Table 5 — Hardwire Host-to-Transponder Command Format

SOM (Start of Message) Byte The SOM Byte field is a fixed single-byte value that is the first byte of every hardwire host-to-transponder command message. This SOM Byte flag value of (0x16) indicates a command message.

Protocol ID This field identifies the type of command message. Table 6 defines the Protocol ID interpretation for the hardwire interface.

Table 6 — Protocol ID values

Packet Length The packet length is a byte count of all bytes in the message, from the SOM byte to the LRC byte inclusive.

Command Code The Command Code indicates the command being sent. The interpretation of the command code depends upon the Protocol ID field (see Table 6). See the messaging formats specific to the messaging type for more details.

Command Arguments The Command Arguments field holds command parameters which may be required depending upon the command specified by the Command Code.

LRC (Longitudinal Redundancy Check) Byte The LRC Byte is the single byte exclusive-or (XOR) sum of all the bytes in the message from the SOM byte up to but not including the LRC byte. The LRC computation starts with an initialization value of zero.

Generalized Hardwire Transponder-to-Host Response Format The transponder shall send responses to the host with response messages formatted as shown in Table 7.

Table 7 — Hardwire Transponder-to-Host Response Format)

Status Packet Length

Byte

SOM (Start of Message) Byte The SOM Byte field is a fixed single-byte value that is the first byte of every hardwire transponder-to-host response message. This SOM Byte flag value of 0x17 indicates a response message.

Protocol ID This field identifies the type of response message. Table 6 defines the Protocol ID values and interpretation for response messages. Response messages always use the Protocol ID used in the preceeding Command Message.

Transponder Status This field holds a 16 bit status word. Data is in big endian format, with the most significant byte before the least significant byte in the message. The format and contents of the Transponder Status word are specific to the messaging type identified by the Protocol ID field, except that NACK shall always be indicated by setting bit 8 of the Transponder Status Word.

Packet Length The packet length is a byte count of all bytes in the message, from the SOM byte to the LRC byte.

Response Code The Response Code indicates the type of response being sent. The specific Response Code is defined by the messaging type identified by the Protocol ID field.

Response Data The Response Data field holds data or results. The contents of this field are dependent upon the messaging type identified by the Protocol ID field, and specific message identified by the Response Code field.

LRC (Longitudinal Redundancy Check) Byte The LRC Byte is the single byte exclusive-or (XOR) sum of all the bytes in the message from the SOM byte up to but not including the LRC byte. The LRC computation starts with an initialization value of zero.

aRFID-V Hardwire Protocol Message Format The aRFID-V Hardwire Protocol command and response message formats are shortened forms of the over-the-air aRFID-V RF Protocol messages. A number of fields including Transponder Manufacturer ID and Transponder Serial Number are not present in the hardwire messages, to reduce communications overhead.

All aRFID-V RF Protocol point-to-point messages are supported, however the Sleep command (command code 0x15) is used as the Disconnection command to terminate data transfer. See section 5.6.6.

aRFID-V RF Protocol broadcast messages are not supported by the hardwire interface. Use the point-to-point variants of commands. The Collection command is functionally replaced by the Initiation signal (see section 5.6.3).

aRFID-V Hardwire Protocol Command Format An aRFID-V RF Protocol command shall be formatted as shown in Table 8.

Transponders shall recognize the host-to-transponder command format shown in Table 8 for the hardwire command equivalent of RFID-V RF Protocol point-to-point commands.

Table 8 — aRFID-V Hardwire Protocol Host-to-Transponder Command Format

Differences between aRFID-V RF Protocol and aRFID-V Hardwire Protocol Command Formats A SOM Byte prefix is added to indicate a hardwire interface format command. The packet options byte, Transponder Manufacturer ID, Transponder Serial Number, and Session ID (Interrogator ID), and the CRC field values are not included in the aRFID-V Hardwire Protocol message. The Protocol ID, Command Code and Command Arguments fields from the over-the-air aRFID-V RF Protocol command format are used in the aRFID-V Hardwire Protocol message. Packet length and LRC are computed.

An Initiation Signal is used in place of a Collection command to retrieve Transponder Manufacturer ID and Transponder Serial Number from the transponder connected via the hardwire interface. The Initiation Signal is defined in section 5.6.3. The Initiation response also contains the maximum hardware packet the transponder can support, which can be up to 255 bytes.

Table 9 -- aRFID-V Hardwire Protocol Messages Which Have Size Restrictions Relaxed

To take advantage of larger permissible hardwire Packet Lengths, the data length restrictions of the over-the-air aRFID-V RF Protocol commands identified in Table 9 have been relaxed to permit more data to be transferred in a single message.

The maximum Packet Length which can be accepted by transponder is communicated to the host during the Initiation sequence (see section 5.6.3).

Packet Length The packet length is a byte count of all bytes in the hardwire formatted message. Hardwire messages have fewer bytes than the equivalent aRFID-V RF Protocol packet.

Command Code The command code used is the same as the aRFID-V RF Protocol formatted message Command Arguments The Command Arguments are the same arguments as the aRFID-V RF Protocol over-the-air form of the command, with the same length and format.

Example of an aRFID-V Hardwire Protocol Command Message Shown in Table 10 is the encoding of the aRFID-V Hardwire Protocol Model Number command.

Table 10 — aRFID-V Hardwire Protocol Model Number Command as example

0x5D aRFID-V Hardwire Protocol Response Format In response to a host-to-transponder command, the transponder shall transmit a transponder-to-host response with the format shown in Table 11 unless one of the following cases is true:

· the point-to-point host-to-transponder command is explicitly specified in this standard as requiring no response

· the value of the LRC Byte field of the received host-to-transponder command does not match the value computed by the transponder as described in section 0.

Table 11 — aRFID-V Hardwire Protocol Transponder-to-Host Response Message Format

Status Packet Length

Differences between aRFID-V RF Protocol and aRFID-V Hardwire Protocol Response Formats A SOM Byte prefix is added to indicate a hardwire interface response message. The Interrogator ID, Transponder Manufacturer ID, and Transponder Serial Number are not included in the hardwire response message. The remaining fields and data from the over-the-air response format are used. A LRC byte is substituted for the CRC bytes of the over-the-air format. The packet length is corrected to reflect the length of the hardwire response.

Hardwire Response Packet Lengths are limited to 255 bytes, the data length restrictions of the over-the-air aRFID-V RF Protocol commands identified in Table 9 have been relaxed to permit more data to be transferred in a single message .

An Initiation Signal is used in place of a Collection command to retrieve Transponder Manufacturer ID and Transponder Serial Number from the transponder connected via the hardwire interface. On reception of the Initiation Signal, the transponder shall respond with the Initiation Signal Response Message defined in section 5.6.3.

Transponder Status This field holds the aRFID-V RF Protocol Transponder Status word. This field is the same size and appears in the byte order as the over-the-air aRFID-V RF Protocol Transponder Status Word. On Command Error or Command Failure, the transponder shall respond with the Transponder Status Word NACK bit set.

Packet Length The packet length is a byte count of all bytes in the hardwire formatted message. Hardwire messages have fewer bytes than the equivalent aRFID-V RF Protocol packet.

Response Code This value is the same value referred to in the aRFID-V RF Protocol response message format as the Command Code.

Response Data The Response Data is the same data as the aRFID-V RF Protocol form of the command, with the same length and format.

Example of aRFID-V Hardwire Protocol Response Message Shown in Table 12 is the encoding of an aRFID-V Hardwire Protocol Model Number response for a transponder model number 0x132B.

Table 12 — aRFID-V Hardwire Protocol Model Number response

Status Packet Length

Byte

aRFID-V Error Messages All aRFID-V RF Protocol required error messages shall also be implemented for the Hardwire Interface.

Hardwire Control Messages A limited number of hardwire specific commands shall be handled by the transponder. This section describes the commands which must be implemented.

Generic Hardwire Control Message Formats Hardwire Control Command Format The command format for Hardwire Control commands is shown in Table 26.

Table 13 — Hardwire Control Command Format

Protocol ID This field shall contain (0xFF) to identify the messaging type as a Hardwire Control command as defined in Table 6.

Command Code This field shall contain one of the valid Hardwire Control commands listed in Table 14 Table 14 -- Hardwire Control Command Code List

Hardwire Control Response Format Table 15 – Hardwire Control Response Format

Status Packet Length

This field shall contain (0xFF) to identify the messaging type as a Hardwire Control response as defined in Table 6.

Transponder Status Word This field holds the NACK flag and Service Request flag as shown in Table 16. The NACK flag, when set (‘1’) indicates an error or failure to execute the received command, a cleared flag (‘0’) indicates command success. The Service Request flag, when set (‘1’) indicates the transponder has detected a hardware-related fault condition. All other bits in this word are reserved for future use, and shall be in the cleared (‘0’) state.

Table 16 — Hardwire Control Transponder Response Message Status Word Transponder Status Word – High Order Bits

Transponder Status Word – Low Order Bits

Response Code This field shall contain one of the valid Hardwire Control response codes listed in Table 17

Table 17 -- Hardwire Control Response Code List

Hardwire Communications, Initiation and Disconnection The transponder shall require an initiation signal to recognise and communicate with the hardwire interface, and shall expect but not require a Disconnect Command to terminate hardwire communications.

Initiation Signal The host shall initiate communications with the transponder over the hardwire interface by issuing a break signal as described in section 4.7.

Initiation Signal Response Upon receipt of the break signal, the transponder shall set its communication parameters to the defaults shown in Table 3 and transition to the Hardwire Connected State. When the transponder is ready to accept command messages, it shall return an Initiation Response Message to the host. The Initiation Response Message contains Transponder Identification and described hardwire communications capabilities.

If the transponder receives a break signal when it is already in the Hardwire Connected State, the transponder shall set its communication parameters to the defaults shown in Table 3 and must return an Initiation Response Message to the host.

The Initiation Response shall have the format shown in Table 18.

Table 18 — Initiation Signal Response Message Format

Status Packet Length

Table 19 — Initiation Signal Response Data Format

Transponder Manufacturer ID This is the aRFID-V RF Protocol r Manufacturer ID value from the Transponder. This is included in the Initiation Signal Response rather than each individual message in the hardwire interface.

Transponder Serial Number This is the aRFID-V RF Protocol Serial Number value from the Transponder. This is included in the Initiation Signal Response rather than each individual message in the hardwire interface Maximum Command Length This is the maximum size command message the transponder can handle over the hardwire interface, and includes the entire message (from the SOM byte through the LRC byte). The size specified for Maximum Command Length must be large enough to accommodate the largest aRFID-V RF Protocol over-the-air message. The Maximum Command Length parameter must be no greater than 255 bytes.

Alternate Communication Speed This field is an opportunity for the transponder to provide to the host an alternative higher baud rate value for communications. The host is not required to use the provided alternative higher baud rate for communications with the transponder. This higher baud rate must be a standard serial communications baud rate, such as 57600, 115200, 230400, 460800 etc).

The alternate communications speed is encoded in units of 100 baud, so 38400 baud is represented as 384 (0x0180), and 115200 baud is represented as 1152 ( 0x0480) The value of 0x0000 is reserved to indicate no alternate baud rate is provided.

Reserved This field is reserved for future use, and shall be set to 0x00.

Example of Initiation Signal Response Message Shown in Table 20 is the encoding of an Initiation Response Message for a transponder with a manufacturer ID of 0x11FF and Serial Number 0x12345678, a maximum command size of 254 bytes, and an alternate communication speed of 115200 baud.

Table 20 – Example Initiation Signal Response Message

Status Packet Length

Disconnect Command The Disconnect command shall be issued to the transponder at the conclusion of communications, prior to physically disconnecting the hardwire cable from the transponder. The hardwire Disconnect command shall have the format shown in Table 21. Note that the Disconnect Command is a hardwire interface formatted Sleep command.

Table 21 — Disconnect Command Format

On receipt of this command, the transponder shall not send a response to the hardwire interface, but shall leave the hardwire connected state and re-enable its RF communications circuitry. Following receipt of this command, the transponder shall not respond to further commands over the hardwire interface until an Initiation Signal is received.

The transponder shall detect accidental physical disconnection from the hardwire cable and the transponder shall leave the hardwire connected state and re-enable its RF communications circuitry. Following this command, an Initiation Signal is necessary before resuming communications with the transponder.

Get Transponder Identification The Get Transponder Identification command is used to retrieve the Manufacturer ID and Transponder Serial Number from the Transponder. The Get Transponder Identification command shall have the format shown in Table 22.

Table 22 -- Get Transponder Identification Command Format

The transponder shall respond to a Get Transponder Identification command with the same data and format as the Initiation Signal Response shown in Table 18 and the response payload data formatted as shown in Table 19.

Change Communication Speed The transponder may provide an alternate communication speed to the host as part of the initiation response message (see Table 18). If the transponder elects to provide an alternate communication speed to the host, it must support the Change Communication Speed command to support moving to the higher speed.

Change Communication Speed Command The transponder shall use the command message shown in Table 23 to command the transponder to a new communication speed.

Table 23 — Change Communication Speed Command

New Communication Speed Argument This field is the new speed the host shall expect the transponder use on receipt of this message, and should be the value the transponder provided.

Successful Change Communication Speed Response If that transponder is capable of changing speed to the New Communication Speed indicated, and willing to, the transponder shall acknowledge with the response shown in Table 24.

Table 24 — Successful Change Communication Speed Response

Status Packet Length

Byte

LRC

The NACK flag in the Transponder Status Flag is clear (‘0’) to indicate the transponder shall change its transmission speed to the speed indicated in the Change Communications Speed in the received command.

The host upon receiving this message shall change its communications speed to the new communications speed and attempt to contact the transponder with regular hardwire command such as Get Model Number (see section 5.5.1.5).

Unable to Change Communication Speed Response If that transponder is unwilling or incapable of changing speed to the New Communication Speed indicated, the transponder shall Negative Acknowledge the command the response shown in Table 25.

Table 25 — Unable to Change Communication Speed Response

Status Packet Length

Byte

LRC

The NACK flag in the Transponder Status Flag is set (‘1’) to indicate the transponder cannot change its transmission speed, and the command failed.

Recovery if Host unable to Re-establish Contact with Transponder If following the Change Speed Command, the host is unable to establish contact with the transponder at the new communication speed, the host shall issue a new initiation signal as described in section 5.6.3. The transponder must re-configure its communication speed to the default shown in Table 3and respond as defined.

It is recommended the host allow the transponder reasonable time to perform the speed change and then use a 18000-7 type messaging command (such as Read Model Number) to verify transponder communications, and make at least two communication before reissuing the Initiation signal.

Manufacturer Specific Messaging A transponder manufacture may implement custom commands using Manufacturer Specific Messaging formats. Any proprietary commands or commands not defined in aRFID-V RF Protocol or in this document must be added as Manufacturer Specific Messaging, which is identified by the use of a Protocol ID value of 0x00.

Manufacturer Specific Command Format The command format for Manufacturer Specific Messaging commands must be as shown in Table 26.

Table 26 — Hardwire Manufacturer Specific Command Format

Manufacturer Specific Command Response Format Table 27 — Hardwire Manufacturer Specific Response Format

Status Packet Length

This field shall contain (0x00) to identify the messaging type as a Manufacturer Specific as defined in Table 6.

Transponder Status Word The Transponder Status Word must implement the NACK flag and as shown in Table 28. The NACK flag, when set (‘1’) indicates an error or failure to execute the received command, a cleared flag (‘0’) indicates command success. The manufacturer is free to use other bits within the Transponder Status Word.

Table 28 — Manufacturer Specific Response Transponder Status Word Transponder Status Word – High Order Bits

Transponder Status Word – Low Order Bits

Unrecognised Manufacturer Specific Command Response It a transponder receives a non-recognised Manufacturer Specific Command, or does not implement any Manufacturer Specific Commands, it must respond with the response shown in Table 29.

Table 29 — Unrecognised Manufacturer Specific Command

Status Packet Length

LRC

Communication Sequence

Hardwire Communications, Initiation and Disconnection The transponder shall require an initiation signal to recognise and communicate with the hardwire interface, and shall expect but not require a Disconnect Command to terminate hardwire communications.

Once hardwire communications have been initiated, the transponder shall disable its RF communications circuitry until hardwire communications have terminated.

Additional Requirements Transponder shall operate on hardwire interface with missing or dead battery The transponder hardwire interface shall operate with no battery or a dead battery installed in the transponder, as long as it is connected to the Host USB port.

Attachment 3

Appendix I

DoD Transponder Hardwire Electrical Interface and Data Protocol – Version 5.0

DoD Transponder Direct-Connection Cable Guidelines Version 1.0

Summary This appendix defines the cable for use between a Field Data Unit (FDU) and RFID-V compliant Active Transponder. This applies only to active transponders that provide a hardwire interface connector.

Guidelines

The cable shall be a Tyco Electronics 1496476-1 or equivalent. The cable may be of a different length if required. The datasheet for the Tyco Electronics 1496476-1 is shown in Figure A-1 below.

The cable described herein is a common standard USB Series A to USB Series “Mini-B” cable.

Comments Note that some Cellular Telephone, PDA, and digital camera charging and data cables have similar connectors, but are not true USB Series A to USB Series “Mini-B” cable, due to internal circuitry in the connector housings or the use of non-standard signals and voltages.

In addition, the USB Series “Mini-B” connector using on RFID-V compliant Active Transponders has 5 pins, and is not to be confused with a proprietary USB connector which has 4 pins but is also sometimes also marketed as a USB Mini-B connector.

USB Document identifying the standard USB Mini-B connector is:

USB Mini-B Connector ECN: USB 2.0 Specification Engineering Change Notice (ECN) #1: Mini-B connector, dated October 20, 2000. Available from USB Implementers Forum, Inc. (www.usb.org)

Figure A- 1 -- Tyco Electronics 1496476-1 datasheet image1.emf