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

GPIO or GPIOEDGE MASK, entered after expiration of the delay time

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 76 highlights

Chapter 4 - BRI Commands = This parameter specifies the name of the trigger. You must enclose the name in double quotes. The affect of the parameter depends on the optional parameters: • When you include optional parameters such as GPIO or MASK, the trigger is created and stored in the reader with the name given in the parameter. If a trigger already exists with the given name, it is updated with the new parameter information, and the trigger is reset if it is currently active. • When you omit optional parameters, the trigger with the name specified is deleted. [GPIO or GPIOEDGE MASK value FILTER delay] = These optional parameters are defined in the following description of how a trigger operates. When a trigger has been created, it immediately enters the DETECTION state. In the DETECTION state, the GPIO inputs are scanned until a fire condition is detected: • When GPIO is used, the fire condition occurs when the current GP input state masked (ANDed) with the mask parameter is equal to the value. • When GPIOEDGE is used, the fire condition is the transition from the state where the input state masked (ANDed) with the mask parameter is not equal to the value to a state where the input state masked (ANDed) with the mask parameter is equal to the value. When this input condition is true, a trigger event is stored on an internal queue and the trigger enters the FIRED state. The trigger remains in the FIRED state for the number of milliseconds given by the FILTER delay parameter, after which it re-enters the DETECTION state. If level triggering is used, when the DETECTION state is reentered after expiration of the delay time, the input state may not have changed (the fire condition still exists) and that causes a new "firing" of the trigger. GPIOEDGE trigger event messages, radio event messages, and tag event messages are sent directly without any internal queueing. Trigger event messages from level triggered GPIO triggers are queued internally in the reader. This queue has two states: • BLOCKED • READY The queue is initially in the BLOCKED state. Every 200 milliseconds, the event queued is monitored to determine whether the queue is in the READY state and there is at least one event queued. If both conditions are met, then a queued event is reported asynchronously from the reader to the host and the queue is returned to the BLOCKED state. The host must issue a TRIGGERREADY command to transition the queue to the READY state. The reader stores up to ten events. If more than ten events are held, the oldest event is overwritten. [ACTION] = This parameter allows the commands given by the macro to be executed upon detection of the fire condition. 64 Basic Reader Interface Programmer Reference Manual

  • 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
64
Basic Reader Interface Programmer Reference Manual
<NAME> = This parameter specifies the name of the trigger. You must enclose the
name in double quotes. The affect of the <“NAME”> parameter depends on the
optional parameters:
•
When you include optional parameters such as GPIO or MASK, the trigger is
created and stored in the reader with the name given in the <NAME> parameter.
If a trigger already exists with the given name, it is updated with the new
parameter information, and the trigger is reset if it is currently active.
•
When you omit optional parameters, the trigger with the name specified is
deleted.
[GPIO or GPIOEDGE MASK
value
FILTER
delay
] = These optional parameters are
defined in the following description of how a trigger operates.
When a trigger has been created, it immediately enters the DETECTION state. In
the DETECTION state, the GPIO inputs are scanned until a fire condition is
detected:
•
When GPIO is used, the fire condition occurs when the current GP input state
masked (ANDed) with the
mask
parameter is equal to the
value
.
•
When GPIOEDGE is used, the fire condition is the transition from the state
where the input state masked (ANDed) with the
mask
parameter is not equal to
the
value
to a state where the input state masked (ANDed) with the
mask
parameter is equal to the
value
.
When this input condition is true, a trigger event is stored on an internal queue and
the trigger enters the FIRED state. The trigger remains in the FIRED state for the
number of milliseconds given by the FILTER
delay
parameter, after which it re-enters
the DETECTION state. If level triggering is used, when the DETECTION state is re-
entered after expiration of the delay time, the input state may not have changed (the
fire condition still exists) and that causes a new “firing” of the trigger.
GPIOEDGE trigger event messages, radio event messages, and tag event messages
are sent directly without any internal queueing.
Trigger event messages from level triggered GPIO triggers are queued internally in
the reader.
This queue has two states:
•
BLOCKED
•
READY
The queue is initially in the BLOCKED state. Every 200 milliseconds, the event
queued is monitored to determine whether the queue is in the READY state and
there is at least one event queued. If both conditions are met, then a queued event is
reported asynchronously from the reader to the host and the queue is returned to
the BLOCKED state. The host must issue a TRIGGERREADY command to
transition the queue to the READY state. The reader stores up to ten events. If more
than ten events are held, the oldest event is overwritten.
[ACTION] = This parameter allows the commands given by the macro to be
executed upon detection of the fire condition.