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
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. The OPEN retry will apply to the actions need to move the tag to
OPEN/SECURE. Units are N+1 where N can be a count value of 0x0 to 0xF
HI GETS the ITERATION counts
HI12 would iterate 1 time on all loop action failures after open, and iterate 2 times on
OPEN failures
STATUS Outputs
Hardware signals are provide to allow user to monitor the timing of the programming
loop, and receive an indication of the overall success of failure of the loop with any
particular tag. if desired.
The signal on OUTPUT0 of the TR65 will go high on reception of a valid trigger and will
go low after the loop terminates (the final status message is sent)
If the program loop was successful in all operations OUTPUT1 of the TR65 will go high
2ms before the falling edge of OUPUT0. In this way OUTPUT0 falling edge can be used
to latch the status of the loop indicated on OUTPUT1.
Copyright 2014 Thinkify LLC. All Rights Reserved.
Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.com 408-782-7111