User Guide
Table Of Contents
- Note Regarding RF Exposure.
- FCC Notice and Cautions
- Compliance FCC Part 90
- Acceptable Frequencies
- Migrating from Thinkify HSP2_0 to HSP3_0 firmware
- Ethernet Communication between HOST and THINKIFY HSP3.0
- Output and Status Messaging in the Thinkify HSP3.0 system
- IO and Timing control in the Thinkify HSP3.0 System
- System Type Functions and control in the Thinkify HSP3.0 system
- Using the LOCK function in Thinkify HSP3.0
- Controlling the programming list database in the Thinkify HSP 3.0 system
Controlling the programming list database in the Thinkify HSP 3.0 system
The data to be programmed in to a series of tags in the HSP3.0 system is controlled by a
database of data strings for the various fields supported by the EPC gen2 specification.
This database exists in systems that have been defined as ENCODERS or
STANDALONE, Systems defined as VERIFIERS do not support this database.
This database is organized as a circular FIFO of 0x10000 entries, with each entry a
structure possibly holding data to be written into the EPC memory bank, the USER
memory bank, The ACCESS PASSWORD, the KILL PASSWORD, and the PC word.
The EPC and the USER data fields in each structure can be varying length - in unit of 16
bit words, from 1 word to 8 words. Further the base address of the first word in the field
can be specified - then all other words will be written to consecutive addresses.
The Password fields must be exactly 2 16 bit words, and the PC field must be exactly 1
16 bit word.
Any field can also have NULL length if it is desired to not do operations on that memory
area for this particular tag.
As tags are processed by the system in response to input triggers, the next available
programming structure is popped from FIFO database, and the data of any field of non-
NULL length is attempted to be written into the tag memory.
If the database UNDERFLOWS - i.e. there is no available entry when a valid trigger
occurs an ERROR will be logged in the status message and diagnostic stream. No
programming operations will occur.
If the database OVERFLOWS - i.e. more entries than the 0x10000 allowed are attempted
to be entered, an error message will indicate this condition and the entry will be ignored.
In the sequence of operations on any particular tag - if any error occurs all subsequent
operations will be aborted. The status message will show the results of all possible
operations.
As an entry in the database is used for a programming sequence, all fields in that entry
will be reset to NULL length so they cannot be reused. Some interest has been expressed
in allowing the reuse of an entry in the case of a tag failing a programming operation,
such that the next tag will then use the same database entry - this is being evaluated and
may be added in future versions.
Two commands exist to enter data fields into the database structure entries.
WRITEITEM=<datalist>
and
Copyright 2014 Thinkify LLC. All Rights Reserved.
Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.com 408-782-7111