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 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. If it has one, it is read from the FIFO and any non-NULL length
fields will drive write operations. The check for non-NULL length and RF operations will
occur in the order
EPC
KILL PASSWORD
ACCESS PASSWORD
USER MEMORY
PCWORD
In the event any of these operations are enabled but fail (as indicated by either nonreception
of the tag status message or reception of the tag status message with error
indication) the ENCODE loop will terminate immediately and no subsequent
programming operations will occur even if enabled by non-NULL length fields. The
status message will indicate this failure and any operations enabled but not performed.
If all programming operations are successful, the status of the LOCK enable is checked.
If it is enabled a LOCK operation will occur. A separate document will describe enabling
the lock and setting the lock payload.
If the LOCK operation is successful the 3.0 system again extends the functionality of the
system by checking the TR65 4 READ descriptors as described above for the VERIFIER.
The ENCODER will always terminate it's loop with the status message and then idle
waiting for the next trigger to occur.
If a system type is configured as STANDALONE
After tag reaches OPEN/SECURE, the actions of both the verifier and encoder are
performed.
The TID is read, the programming data base is accessed, all enabled programming
actions occur, the lock occurs. A standalone system will then do final read of the EPC
data, then do the check of the 4 read descriptors. upon success of all these operations the
ENTRY EPC is reported, the TID read is reported, the EXIT EPC is reported, any READ
descriptor results are reported and finally a status message is sent indicating all success
and failures.
Appendix - description and control of the INVENTORY process
Copyright 2014 Thinkify LLC. All Rights Reserved.
Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.com 408-782-7111