User's Manual Part 2
Table Of Contents
- Page 1
- Page 2
- Page 3
- Page 4
- Page 5
- Page 6
- Page 7
- Page 8
- Page 9
- Page 10
- Page 11
- Page 12
- Page 13
- Page 14
- Page 15
- Page 16
- Page 17
- Page 18
- Page 19
- Page 20
- Page 21
- Page 22
- Page 23
- Page 24
- Page 25
- Page 26
- Page 27
- Page 28
- Page 29
- Page 30
- Page 31
- Page 32
- Page 33
- Page 34
- Page 35
- Page 36
- Page 37
- Page 38
- Page 39
- Page 40
- Page 41
- Page 42
- Page 43
- Page 44
- Page 45
- Page 46
- Page 47
- Page 48
- Page 49
- Page 50
- Page 51
- Page 52
- Page 53
- Page 54
- Page 55
- Page 56
- Page 57
- Page 58
- Page 59
- Page 60
- Page 61
- Page 62
- Page 63
- Page 64
- Page 65
- Page 66
Hi-G-Tek Ltd. Microelectronics & Asset Tracking Technology
54
5
System
Table 5.3. below shows some examples of the Verify command using
different retransmissions and Reader Sessions. In this example,
Thw=3 sec; Ts=21 msec; Taw=105 msec.
Table 5.3.
Reducing the Reader Interrogation Header - Thw increases the
speed of the Verify session. Increasing the speed of the process is
in conflict with the battery lifetime of the seal. (Higher speed = lower
battery lifetime). When designing an application, careful attention
should be paid to optimizing the correct tradeoffs between system
response time, battery lifetime and number of seals.
Taw is calculated for 5 slots of Ts.
Table 5.4 demonstrates the impact of Thw on response time and
battery life. The scenario for the results in the table is a GATE
concept, whereby a seal is exposed to a reader for 6 minutes per
24 hours and: Ts=21 msec; Taw=105 msec.