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
The concept approach in the 3.0 system is WYEIWYP (What You Enter Is What You
Program).. A structure of 65536 (0x10000) programming database entries is maintained
as a circular FIFO buffer. Each of these database entries can hold varying length data
fields for the EPC and USER fields, data for the password fields, and data for the PC
word. When a system trigger occurs to initiate a programming sequence, the next
available entry is popped from the FIFO, and whatever data is included in that particular
database entry is used in programming operations to the tag. Any programming
operations for data fields of NULL length are simply not executed.
In this way all operational control on a tag that has triggered the system, for any
operations, depends solely on the data entered for that particular database entry - there is
no need for modes and setup commands etc.
In the initial release of the 3.0 system, this programming database can be created in two
ways - through a series of WRITEITEM commands, or the system can automatically
create a programming sequence list through a GENERATE command. Further control
commands of this database include GETBUFFERCOUNT, READBUFFER,
RESETBUFFER, and AUTOCLEAR.
One further operation beyond the data programming which can optionally be performed
during a triggered loop is LOCKING the tag.
A separate document describes details of these database control commands, along with
program flow and the LOCK operation control details.
System Type -
Three different system types are supported in the 3.0 system. Any PI/TR65 combination
can be defined as a VERIFIER, an ENCODER, or STANDALONE system. The
specification of the system type is best done in the config.ini file, but a command also
exists to specify the type during runtime.
The exact differences in operations for these three types is described in a separate
document.
Config.ini File -
A file will exist in the /home/pi/HSP_3_0 folder of the Pi Linux file system. This file
will specify parameters the program will initialize at reset for general system setup. It
will allow setting the TCP port numbers used, the USB com port the TR65 is attached to,
the overall system type, and the initial settings of the AUTOCLEAR mode and the
TRIGGER type. The file is a simple text file and can be edited with any text editor. It is
expected that parameters set in this file rarely change after initial system setup.
Copyright 2014 Thinkify LLC. All Rights Reserved.
Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.com 408-782-7111