Intermec IV7 Basic Reader Interface Programmer's Reference Manual (BRI version - Page 107

RPTTIMEOUT, SCHEDULEOPT, SCHEDULEOPT Value Descriptions

Get Intermec IV7 PDF manuals and user guides View all Intermec IV7 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 107 highlights

Chapter 4 - BRI Commands RPTTIMEOUT SCHEDULEOPT Sets the time period (ms) to delay the reporting of tag events when the reader is in Continuous mode (REPORT=EVENT). Range is 0 to 65534. Default is 0. If RPTTIMEOUT is set to 0, there is no delay. A report is sent for each tag found in the ID round directly after the completion of the ID round. If RPTTIMEOUT is set to a non-zero value, a timer is loaded with the value upon: • a continuous operation starts, such as READ REPORT=EVENT command. • a new RPTTIMEOUT value is set with the ATTRIBUTE command. • a new report is available and the timer expired flag is set. When the started timer expires, the timer is stopped and a new timer expired flag is set. The timer expired flag is cleared each time the time is started. Determines how antennas are switched during the inventory process. This attribute controls the behavior of the inventory scheduling parameters such as ANTTIMEOUT, ANTTRIES, IDTIMEOUT, and IDTRIES. This attribute can have a value of either 0, 1, or 2. Default is 0. "Understanding the Timeouts and Tries" on page 99, describes the behavior of timeout and tries attributes when SCHEDULEOPT is 0. SCHEDULEOPT Value Descriptions Value 0 1 2 Description Legacy "normal" BRI operation Simplified "normal" BRI operation Simplified "normal" BRI operation with EPCC1G2 A/B toggling When SCHEDULEOPT is set to 1, the TIMEOUT attribute is ignored. The ANTTIMEOUT and ANTTRIES attribute work together to determine how much time is spent on a given antenna. When ANTTIMEOUT is 0, the value of ANTTRIES defines the number of inventory rounds run on an antenna before stepping to the next antenna. When ANTTIMEOUT is not 0, the value of ANTTRIES is ignored and ANTTIMEOUT defines the amount of time spent on an antenna before stepping to the next antenna. The IDTIMEOUT and IDTRIES attributes work together to determine how much time is spent trying to read tags. When IDTIMEOUT is zero, the value of IDTRIES defines the number of attempts used to read tags before a response is returned from a read or write command. When IDTIMEOUT is not zero, the value of IDTRIES is ignored and IDTIMEOUT defines the amount of time attempting to read tags before a response is returned. Basic Reader Interface Programmer Reference Manual 95

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
Chapter 4 — BRI Commands
Basic Reader Interface Programmer Reference Manual
95
RPTTIMEOUT
Sets the time period (ms) to delay the reporting of tag events when the reader is in
Continuous mode (REPORT=EVENT). Range is 0 to 65534. Default is 0.
If RPTTIMEOUT is set to 0, there is no delay. A report is sent for each tag found in
the ID round directly after the completion of the ID round.
If RPTTIMEOUT is set to a non-zero value, a timer is loaded with the value upon:
•
a continuous operation starts, such as READ REPORT=EVENT command.
•
a new RPTTIMEOUT value is set with the ATTRIBUTE command.
•
a new report is available and the timer expired flag is set.
When the started timer expires, the timer is stopped and a new timer expired flag is
set. The timer expired flag is cleared each time the time is started.
SCHEDULEOPT
Determines how antennas are switched during the inventory process. This attribute
controls the behavior of the inventory scheduling parameters such as
ANTTIMEOUT, ANTTRIES, IDTIMEOUT, and IDTRIES. This attribute can have a
value of either 0, 1, or 2. Default is 0.
“Understanding the Timeouts and Tries” on
page 99
, describes the behavior of timeout and tries attributes when
SCHEDULEOPT is 0.
When SCHEDULEOPT is set to 1, the TIMEOUT attribute is ignored. The
ANTTIMEOUT and ANTTRIES attribute work together to determine how much
time is spent on a given antenna. When ANTTIMEOUT is 0, the value of ANTTRIES
defines the number of inventory rounds run on an antenna before stepping to the
next antenna. When ANTTIMEOUT is not 0, the value of ANTTRIES is ignored and
ANTTIMEOUT defines the amount of time spent on an antenna before stepping to
the next antenna.
The IDTIMEOUT and IDTRIES attributes work together to determine how much
time is spent trying to read tags. When IDTIMEOUT is zero, the value of IDTRIES
defines the number of attempts used to read tags before a response is returned from
a read or write command. When IDTIMEOUT is not zero, the value of IDTRIES is
ignored and IDTIMEOUT defines the amount of time attempting to read tags
before a response is returned.
SCHEDULEOPT Value Descriptions
Value
Description
0
Legacy “normal” BRI operation
1
Simplified “normal” BRI operation
2
Simplified “normal” BRI operation with EPCC1G2 A/B toggling