User Guide

GENERATE=<datalist>,NUM<number of entries to create>

The WRITEITEM command is used to enter the data for one database indexed structure.

The GENERATE command can automatically create an arbitrary number of database

structure entries - up to the full 0x10000 allowed with one command.

The GENERATE command was created in HSP3.0 because it was noted that a common

tag programming scenario is to program a fixed set of data and one incrementing word

into tags as they trigger the system. The GENERATE command allows filling the

database with data that follows this pattern. Using it frees up the host system from having

to enter data for every tag as it triggers the system - instead the database can be created

for a whole field of tags with one command. This relaxes the communication timing

requirements of the system considerably. The command would be sent before the

transport mechanism is started, then as tags trigger the programming loop subsequent

enteries would be programmed into each tag.

The WRITEITEM command can be sent at any time as tags are triggering the system -

the only requirement is that at least database entry has been filled at the time the GEN2

OPEN sequence of RF commands is complete. If there is no database entry available at

this time an UNDERFLOW will occur and the tag will not be programmed. The

condition will be flagged in the STATUS message, and in the diagnostic stream.

Multiple memory area data can be entered as sub-fields into the <datalist> of either

command. Each memory area sub-field is comma delimited in the <datalist>. To specify

the memory area to be used for the data in the comma delimited sub-field the first three

characters must be one of the following

EPC for data in bank1 of the GEN2 tag

USR for data in bank3 of the GEN2 tag

KIL for the kill password

ACC for the access password

PCW for the PC word

Following this 3 character memory area code, data should be entered as ASCII HEX. All

data is WORD based so must be in multiples of 4 ASCII HEX characters. EPC and USR

fields may have any number of words from 1 to 8 (4 to 32 characters). Passwords must

have exactly two words (8 characters). PC word must be exactly 4 characters for one

word.

These sub field specifiers may be sent in any order inside the <datalist> as long as they

are comma delimited. Any sub-field not specified within a <datalist> will result in a

NULL length field for that database entry - when this entry is used as a tag triggers the

system, no programming action will occur for that memory area.

There is a data modifier for the EPC and the USR sub-fields which will specify the start

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