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
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.
From a power up reset the LOCK functionality is disabled. If desired a TR65 STARTUP
MACRO command could override this and enable the LOCK by setting a payload. Or at
any time the host can issue a command to enable and specify the LOCK function.
The LOCK command is a TR65 command - HL[<payload>]. HL alone returns the
current setting of the lock PAYLOAD. If the command is entered with a payload of OFF
the lock is disabled. If the payload is 5 ASCII HEX characters the LOCK function is
enabled and the payload entered defines the characteristic of the lock as defined in the
GEN2 specification.
Any LOCK payload setting is applied to all subsequent tags until explicitly overwritten
or a reset of the TR65 occurs.
Interest has been expressed in the possible addition of other command formats to
minimize the need for the user to fully understand how a lock payload is formed. This
may be added in future versions, but the direct payload entry will always be supported.
It is a characteristic of the GEN2 specification that there is no means to read back the
value of the lock payload as set into the tag. If the tag returns a valid response of either
OK or ERROR in response to a LOCK command then the status of the lock payload in
the tag is deterministic - if the response is missed or unreadable then the status is
undetermined. The status message at the end of the programming loop will indicate the
result.
Copyright 2014 Thinkify LLC. All Rights Reserved.
Thinkify, LLC, 18450 Technology Drive, Suite E1, Morgan Hill, Ca. 95037, www.thinkifyit.com 408-782-7111