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

Examples, high. The latter four examples show that trigger conditions can be con d

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

Chapter 4 - BRI Commands For example, one trigger could start doing READs in continuous mode, while another event is also sent to the application about the trigger condition.This event could be used to inform the application to start reading the collected data. The application could then send a READ POLL followed by a READ STOP to retrieve the data collected since the initial trigger. This makes it possible to validate the contents of the macro, and if it is invalid, an ERR is returned by the TRIGGER command. Note that ACTIONs are neglected while the reader is in READER CONTINUOUS mode. Examples: These examples demonstrate how to use the TRIGGER command. The first two examples are set up as a dock-door solution. They define one trigger that waits for input 1 to go high and a second trigger that waits for input 2 to go high. The latter four examples show that trigger conditions can be configured to combine several inputs. The inputs 2 and 3 are used by these triggers and any combination of values on these generate a trigger event, but the event generated depends on the combined value. Example 1: TRIGGER RESET OK> TRIGGER "Dock door #43" GPIOEDGE 1 1 FILTER 0 OK> TRIGGER Dock door #43 GPIOEDGE 1 1 FILTER 0 OK> TRIGGER "Dock door #44" GPIOEDGE 2 2 FILTER 0 OK > TRIGGER "Special 00" GPIOEDGE 12 0 FILTER 0 OK > TRIGGER "Special 01" GPIOEDGE 12 4 FILTER 0 OK > TRIGGER "Special 10" GPIOEDGE 12 8 FILTER 0 OK > TRIGGER "Special 11" GPIOEDGE 12 12 FILTER 0 OK> Example 2: The TRIGGER command with no parameters displays the currently programmed triggers as shown in the following example: TRIGGER Dock door #43 GPIOEDGE 1 1 FILTER 0 Dock door #44 GPIOEDGE 2 2 FILTER 0 Special 00 GPIOEDGE 12 0 FILTER 0 Special 01 GPIOEDGE 12 4 FILTER 0 Special 10 GPIOEDGE 12 8 FILTER 0 Special 11 GPIOEDGE 12 12 FILTER 0 OK> Basic Reader Interface Programmer Reference Manual 65

  • 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
65
For example, one trigger could start doing READs in continuous mode, while
another event is also sent to the application about the trigger condition.This event
could be used to inform the application to start reading the collected data. The
application could then send a READ POLL followed by a READ STOP to retrieve the
data collected since the initial trigger. This makes it possible to validate the contents
of the macro, and if it is invalid, an ERR is returned by the TRIGGER command.
Note that ACTIONs are neglected while the reader is in READER CONTINUOUS
mode.
Examples:
These examples demonstrate how to use the TRIGGER command.
The first two examples are set up as a dock-door solution. They define one trigger
that waits for input 1 to go high and a second trigger that waits for input 2 to go
high. The latter four examples show that trigger conditions can be configured to
combine several inputs. The inputs 2 and 3 are used by these triggers and any
combination of values on these generate a trigger event, but the event generated
depends on the combined value.
Example 1:
TRIGGER RESET<CRLF>
OK><CRLF>
TRIGGER “Dock door #43” GPIOEDGE 1 1 FILTER 0<CRLF>
OK><CRLF>
TRIGGER<CRLF>
Dock door #43 GPIOEDGE 1 1 FILTER 0<CRLF>
OK><CRLF>
TRIGGER “Dock door #44” GPIOEDGE 2 2 FILTER 0<CRLF>
OK ><CRLF>
TRIGGER “Special 00” GPIOEDGE 12 0 FILTER 0<CRLF>
OK ><CRLF>
TRIGGER “Special 01” GPIOEDGE 12 4 FILTER 0<CRLF>
OK ><CRLF>
TRIGGER “Special 10” GPIOEDGE 12 8 FILTER 0<CRLF>
OK ><CRLF>
TRIGGER “Special 11” GPIOEDGE 12 12 FILTER 0<CRLF>
OK><CRLF>
Example 2:
The TRIGGER command with no parameters displays the currently programmed
triggers as shown in the following example:
TRIGGER<CRLF>
Dock door #43 GPIOEDGE 1 1 FILTER 0<CRLF>
Dock door #44 GPIOEDGE 2 2 FILTER 0<CRLF>
Special 00 GPIOEDGE 12 0 FILTER 0<CRLF>
Special 01 GPIOEDGE 12 4 FILTER 0<CRLF>
Special 10 GPIOEDGE 12 8 FILTER 0<CRLF>
Special 11 GPIOEDGE 12 12 FILTER 0<CRLF>
OK><CRLF>