User Guide

complexity, But since many more RF-tag interactions are necessary it will affect the

necessary time the tag is in the antenna rf field pattern - and depending on many factors

may slow down the throughput speed somewhat. A user must weigh the advantages and

disadvantages in determining the configuration to use with their tag transport mechanism

and host software control system.

Program Flow of the System Types -

All systems start off in DISENAGE mode - in this mode the TRIGGER is disabled. All

timing, trigger, and general RF control commands should be sent. A suggested and

superior way to perform all of these setup tasks is through the use of a reader STARTUP

MACRO (described in a different document)

To start operation of all system types an ENGAGE command must be sent. The system

will then wait for a valid trigger to indicate interaction with a tag should begin.

All operations with a GEN2 tag must first INVENTORY the tag to get it into OPEN or

SECURE state, all system types will perform the necessary RF operations for this

process. See description at end of this document for details of these operations, and

controls a user can issue. Most users can just use default operational settings. The

INVENTORY will return the EPC data of length defined by the PC word, and the

HANDLE to be used in all subsequent operations - see GEN2 specification.

If the INVENTORY operation fails there is no way to interact with this tag - the

programming loop will terminate with no further actions. The status message will

indicate this has occurred.

If a system type is configured as a VERIFIER

After tag reaches OPEN/SECURE, a read of 6 words starting at address 0 of the TID

memory bank is performed.

If the TID READ fails, the loop terminates and a status message is sent indicating this

failure. Since to get to this point the INVENTORY was by definition successful, the EPC

data acquired will be reported along with a message indicating the TID read failure.

The HSP3.0 extends VERIFIER operation beyond the 2.0 system. If the TID read is

successful, the four READ descriptors in the TR65 are checked. If any are enabled

further reads of up to four memory areas defined in these read descriptors is performed.

This allows memory areas such as passwords, or user memory, or EPC memory beyond

the length defined by the PC word to be also be read during the triggered operation. Of

course any additional RF operations enabled require extra time to execute and will impact

the throughput rate of the verifier.

The setup of the read descriptors is beyond the scope of this document - refer to the

normal TR65 user manual.

Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.com 408-782-7111