HSP 3.0 Guide Copyright 2014 Thinkify LLC. All Rights Reserved. Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.
Table of Contents Note Regarding RF Exposure................................................................................................................3 FCC Notice and Cautions......................................................................................................................3 Compliance FCC Part 90 ......................................................................................................................3 Acceptable Frequencies..............................................
Note Regarding RF Exposure. This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance of 20cm between the radiator (antenna) and your body. This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.
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.
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.
The STATUS message As the set of operations performed in response to a trigger is concluded, a status message is sent indicating the success/failure of all operations performed during the interaction with this tag. This is similar to the HSPDONE message in the 2.0 system, but since a different set of operations is now available to be performed the syntax of this response is changed somewhat. It is also modified in an attempt to be a more informative.
Programmer3.
Ethernet Communication between HOST and THINKIFY HSP3.0 The communication between a HOST system and the Thinkify HSP3.0 system is performed over 3 Ethernet PORT connections. These port connections are simple ASCII protocol Telnet type connections.
The system default for the port numbers are 5000 for the CMD port, 5001 for the DATA port and 5003 for the DIAG port, but these can be changed to any desired available port number in the config.ini file provided. Syntax of the messaging formats is described in other documents but in general all messaging is simple ASCII with CRLF delimiting. Copyright 2014 Thinkify LLC. All Rights Reserved. Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.
Output and Status Messaging in the Thinkify HSP3.0 system As each triggered programming loop terminates one or more messages are sent out to inform the host of the data and status of the event in that loop. The type and format of the messages varies dependant on the SYSTEMTYPE. All three system types allow the option of defining extra memory reads through the setup of the four READ DESCRIPTORS in the TR65. If enabled these reads will occur at the very end of the programming loop.
Only one termination message is given indicating status ENCDONE=ALL,OPN,TID,EPC,KIL : ,ACC: ,USR: ,PCW,LCK: The values and meanings of the statusbyte fields is given at the end of this document. If the SYSTEMTYPE is STANDALONE If the OPEN of the tag was successful the first message sent will be the EPC data read during the ACK command.
In the final status message the fields are ALL: - this is the code for the overall success/fail of all enabled actions the entire loop OPN: - this is the success/fail of the OPEN sequence to bring the tag to OPEN/SECURE TID: - success/fail of the read of the TID memory area EPC: - success/fail of the write to the EPC memory area KIL: - success/fail of the write to the KILL password memory area ACC: - success/fail of the wrie to the ACCESS password memory area USR - success/fail of the write to the USER memo
IO and Timing control in the Thinkify HSP3.0 System The TR65 module in the Thinkify HSP3.0 has two logic level inputs and 2 logic level outputs. In the HSP3.0 system INPUT0 is used to as the source of the trigger input signal that initiates a programming loop for any specific tag. The two outputs provide signals indicating the programming loop is in progress, and at the end of the loop the success or failure of operation in the loop. Trigger input The INPUT0 is a TTL level driven signal.
Commands to further adjust timing within the programming loop HC[] 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.
adjusted for worst case timing of all retries occurring. This setting is a tradeoff off between throughput time and throughput success rate. This command is more useful in a STOP-AND-GO transport mechanism than in a continuous flow transport mechanism. Two parameters are supported - the ACTION retry count, and the OPEN retry count. The ACTION retry will apply to any6 read/write actions enabled after the tag OPEN sequence is performed.
System Type Functions and control in the Thinkify HSP3.0 system The firmware in the PI and TR65 in the HSP3.0 system allows configuring for 3 specific purposes. These are VERIFIER, ENCODE, and STANDALONE. This document describes the control commands to specify the system type, and program flow differences between the three types. The system type can be specified in the config.
complexity, But since many more RF-tag interactions are necessary it will affect the necessary time the tag is in the antenna rf field pattern - and depending on many factors may slow down the throughput speed somewhat. A user must weigh the advantages and disadvantages in determining the configuration to use with their tag transport mechanism and host software control system. Program Flow of the System Types All systems start off in DISENAGE mode - in this mode the TRIGGER is disabled.
The system then issues a series of messages and returns to looping waiting for a trigger. These messages will include the EPC data from the INVENTORY (if successful), The TID data from the READ, any data from descriptor driven reads and finally a status message indicating the failure/success of all operations. If a system type is configured as an ENCODER After tag reaches OPEN/SECURE, the programming structure database is checked for having a valid entry.
In most cases the user can just use the default settings for the inventory process. There are two aspects of this that can be controlled for fine tuning a system if desired. These include controlling the SELECT used and allowing an ACCESS operation to occur.
Using the LOCK function in Thinkify HSP3.0 In any 3.0 system configured as an ENCODER or STANDALONE the GEN2 LOCK functionality can be added to any tag programmed. See GEN2 spec for the full description of the LOCK functionality. If the LOCK is enabled it will be the last thing programmed to the tag after all other enabled memory areas are complete. Since the 3.0 programming aborts on any error this means only tags fully programmed with all desired data will be issued a LOCK command.
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.
GENERATE=
address within the bank. Multiple word in either bank will then be written at contiguous addresses from the start address. If no address modifier is given it is assumed the start address for the EPC is address2 of bank1, and the start address for the USR is address0 of bank3. To specify a non-default start address surround 4 ASCII hex characters in parenthesis immediately after the 3 character memory area specifier and before the data field. In the GENERATE command there is one further data modifier.
As the data entry commands are executed they will be written to the database in ascending order in a circular addressing fashion from 0x0000 to 0xFFFF, and conversely when triggers occur entries will retrieved in a FIFO manner - the oldest unused database entry will be used first. Four other commands will affect the database. RESETBUFFER is somewhat self explanatory - all entries in the database will be reset to NULL length and the available buffer entry count will be set to zero.
