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
Migrating from Thinkify HSP2_0 to HSP3_0 firmware
The 3.0 firmware command interface is similar, but not backwards compatible with the
interface used in the 2.0 system. Changes were made to add functionality, and improve
the usability and consistency of the command structure.
At the end of this document is a list of commands supported by the 3.0 system. Further
details of these commands will be described in additional documents.
Overall command entry -
In the 2.0 system several commands were redundantly provided both as PI level
commands and TR65 commands, but were actually just pass through commands to the
TR65 module. Then later on in the development of the 2.0 system it was determined there
was just too many commands to support this way of doing things, and the concept of
sending a command preceded by a '!' would result in a command directly sent to the
TR65.
The 3.0 system no longer supports this. For any command sent, the command interface
parser in the 3.0 will first determine if this command is meant to be processed by the PI.
If it is not recognized as a valid PI command it is then sent to the TR65. If the TR65
recognizes it as a valid command it executes it, otherwise reports UNKNOWN
COMMAND.
Therefore the whole concept of preceding the commands intended for the TR65 with a '!'
is eliminated. and the PI does not support any commands that are really direct TR65
control commands, but instead just directly sends these on to the TR65. Some examples
of the commands this applies to are setting the attenuation and radio parameters and
setting the trigger and delay parameters.
Data entry of programming data -
The development process in the 2.0 evolved as time went on. In the beginning only 96 bit
EPC programming was supported along with passwords. As development proceeded it
became apparent that further functionality was desired - examples being the size of the
EPC memory data field and the ability to program USER memory data. As these were
attempted to be added to the 2.0 command interface, the control structure got
cumbersome and difficult to use. There were multiple commands and setup procedures
depending on the desired actions to the tags currently being run which were unable to be
changed easily etc. The 3.0 system attempts to correct this.
Copyright 2014 Thinkify LLC. All Rights Reserved.
Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.com 408-782-7111