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

Syntax, Fields, Examples, <TYPE> = This field may be TRIGGER, TRIGGERACTION, RADIO, TAG

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

Chapter 4 - BRI Commands Syntax: All event messages use the following format: EVT: The depends on the : EVT:TRIGGER EVT:TRIGGERACTION "TRIGGER_NAME" MACRO_OUTPUT EVT:RADIO DUTY_CYCLE TIMELEFT EVT:TAG EVT:BATTERY LOW|OPERATIONAL|CHARGED EVT:THERMAL OVERTEMP|NORMAL EVT:RESET EVT: BRISERVICE NOSESSIONS EVT: ANTENNA FAULT EVT: ANTFAULT Fields: = This field may be TRIGGER, TRIGGERACTION, RADIO, TAG, BATTERY, THERMAL, or RESET. = This field specifies the name associated with the event, like the name of the trigger. = This field identifies the event that occurred. = This field contains data, like the state of the GP inputs on the reader. Examples: Example 1: The following is an example of a TRIGGER event message: EVT:TRIGGER ExampleTRIGGER GPIO 15 Example 2: The following is an example of a TRIGGERACTION event message: EVT:TRIGGERACTION "GPIO_1" H6861681 EVT:TRIGGERACTION "GPIO_1" OK> Example 3: The following is an example of a RADIO event message: EVT:RADIO DUTY_CYCLE TIMELEFT xxx The event message above is generated when the reader must turn off the radio in order to comply with country regulations. The response is type RADIO with the name DUTY_CYCLE. The event was TIMELEFT and the xxx is a decimal value in seconds representing the remaining that the radio can be turned ON and actively looking for tags. Example 4: The following is an example of the TAG event message from "READ TAGID REPORT=EVENT": EVT:TAG H112210101122334411221122 Basic Reader Interface Programmer Reference Manual 111

  • 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
111
Syntax:
All event messages use the following format:
EVT:<TYPE> <TYPE_SPECIFIC_PART>
The <TYPE_SPECIFIC_PART> depends on the <TYPE>:
EVT:TRIGGER <NAME> <EVENT> <DATA>
EVT:TRIGGERACTION “TRIGGER_NAME” MACRO_OUTPUT
EVT:RADIO DUTY_CYCLE TIMELEFT <TIME>
EVT:TAG <TAG DATA>
EVT:BATTERY LOW|OPERATIONAL|CHARGED
EVT:THERMAL OVERTEMP|NORMAL <TEMPERATURE>
EVT:RESET
EVT: BRISERVICE NOSESSIONS
EVT: ANTENNA FAULT <ANTENNA NUMBER>
EVT: ANTFAULT <ANTENNA NUMBER>
Fields:
<TYPE> = This field may be TRIGGER, TRIGGERACTION, RADIO, TAG,
BATTERY, THERMAL, or RESET.
<NAME> = This field specifies the name associated with the event, like the name of
the trigger.
<EVENT> = This field identifies the event that occurred.
<DATA> = This field contains data, like the state of the GP inputs on the reader.
Examples:
Example 1:
The following is an example of a TRIGGER event message:
EVT:TRIGGER ExampleTRIGGER GPIO 15<CRLF>
Example 2:
The following is an example of a TRIGGERACTION event message:
EVT:TRIGGERACTION “GPIO_1” H6861681<CRLF>
EVT:TRIGGERACTION “GPIO_1” OK><CRLF>
Example 3:
The following is an example of a RADIO event message:
EVT:RADIO DUTY_CYCLE TIMELEFT xxx<CRLF>
The event message above is generated when the reader must turn off the radio in
order to comply with country regulations. The response is type RADIO with the
name DUTY_CYCLE. The event was TIMELEFT and the
xxx
is a decimal value in
seconds representing the remaining that the radio can be turned ON and actively
looking for tags.
Example 4:
The following is an example of the TAG event message from “READ TAGID
REPORT=EVENT”:
EVT:TAG H112210101122334411221122<CRLF>