User Guide

Commands to further adjust timing within the programming loop

HC[<delay (2 ASCII HEX)>] controls the minimum time of the programming loop. The

elapsed time a programming loop - defined as the time between the trigger and the final

output messages indicating completion - can vary widely dependant on what operations

are performed and the success or failure of these operations. For example if a tag fails to

OPEN the loop can complete in just a few milliseconds compared with 100 or more if all

operations in the loop succeeds. This variation in timing can cause problems with host

systems. By setting the minimum time for the loop these variations can be minimized.

Normal setting would be somewhat less than the normal elapsed time for the current set

of programming actions being performed if they all succeed.

examples

HC GETS the current setting for loop time CORRECTION

HC64 sets the minimum time between trigger and output messages to 100ms

HQ[<delay (1 ASCII HEX)>] allows the insertion of a small delay to be inserted after

the tag OPEN sequence completes and the READS/WRITES defined in the current

programming loop occur. The purpose of this delay is to allow host systems a bit more

time the input the desired programming data. In most cases this can be left at 0. Units are

milliseconds from 0x0 to 0xF

HW[<delay (1 ASCII HEX)>] controls the ASYNC RESPONSE DELAY for write and

lock operations. The GEN2 specification states the tag will respond with a status at any

time within 20ms from the end of any command that changes internal EE memory of the

tag. In normal operation an interrogator must always wait until either a response is

received or this timeout occurs. However in reality most tags return their status response

much more quickly than this - many within just a few milliseconds. This command can

be used to shorten the time the TR65 will wait looking for a response from the tag in any

write or lock operation. This is to minimize the time added to the loop in the case of a

missed response. However user must be aware this setting does cause operational

violation of the specification the tag is designed to - care must be taken to ensure that for

the particular tag IC being used, the wait time is long enough for any normal response to

be acquired

examples

HW GETS the current setting for async response WAIT

HWA sets the maximum time for the async response WAIT to 10ms

HI<ACTION RETRY COUNT (1 ASCIIHEX)><OPEN RETRY COUNT

(1 nibble)> controls RETRY iteration control of the actions within a programming loop.

Since the programming loop consists of several RF modulated commands to tag, then

reception of backscatter response from tag, it is possible random events can cause an

operation to fail. If a failure occurs in any of these discrete RF interactions, the entire

programming loop is deemed to have failed. This command makes it possible to retry any

failed event N times. However user must be aware that each retry can cause elapsed time

of loop to increase - if retry is enabled, the spacing between trigger events must be

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