INfinity 510 Protocol Reference Guide - Sirit

More documents

Recommendations

Info

Chapter 4 – Reader Behavior READER SETUP NOTE Modification to the "setup" variables may result in the reader changing a number of other variables which are derived from the setup configuration. Any script or operational procedure which modifies the setup variables must also perform those actions prior to any detailed customization of other configuration variables Region Sub-Region The reader provides a small set of high level configuration variables that are used to ease the initial configuration process. These configuration variables reside in the setup namespace and control basic properties of the reader. These basic properties are used to derive the entire detailed configuration set for the reader. When you first receive your reader, use the setup variables to initially configure the reader for a general application and then customize a few of the specific settings. In most cases, the detailed configuration automatically applied by the reader will be sufficient for effective use of the reader. The following user settable variables exist in the setup namespace and determine the basic properties of the reader: Region Sub-region Protocols Operating Mode Install Type Tag Volume Always set these variables in the order in which they appear in the list. The setup.region variable sets the regulatory mode for the geographic region where the reader is deployed. On some readers, you may be able to modify this setting. Other readers, such as those following the FCC regulatory standards, have a fixed value for this setting that you cannot modify. The setup.sub_region variable sets the secondary regulatory mode for geographic region where the reader is deployed. You can modify this setting, if there is more than one option available under the current region setting. In the FCC region, there are four different sub-region settings under Part 15 operation. The first three (FCC_A, FCC_B, FCC_C) provide different subbands in the FCC band (902 to 928MHz) and utilize 200 KHz channelization. There is some overlap between these 50 channel subbands. The fourth sub-region (FCC_DENSE) utilizes the entire FCC band with 50 channels at 500 KHz channelization. 16 INfinity 510 Protocol Reference Guide
Chapter 4 - Reader Behavior Operating Mode NOTE Data fields displayed in an event.tag.report event may include some or all fields requested by any of the following variables: tag.reporting.report_field, tag.reporting.arrive_field, tag.reporting.depart_field, tag.reporting.taglist_field. Any software receiving this event should ignore those fields not needed for event handling. In the ETSI region, there are also four different sub-regions. The first setting (EN300220) is for operation complying with the EN300220 standard which uses a transmit frequency of 869.525 MHz. The other three settings (EN302208_NO_LBT, EN302208, EN302208_DENSE) provide operation that complies with variations on the EN302208 standard. You must ensure that the specific sub-region setting is allowed in the local regulatory region. EN302208_NO_LBT – Utilizes the standard frequency band of 865 to 868MHz with 200 KHz channelization but does not perform the listen before talk (LBT) function prior to transmitting on a frequency. This mode can only be used in select countries of the EU. EN302208 – Utilizes the standard frequency band of 865-868MHz with 200 KHz channelization and provides support for all aspects of the standard. This mode can only be used in select countries of the EU. EN302208_DENSE – Utilizes the standard frequency band of 865 to 868 MHz but with 600 KHz channelization and performs the LBT function prior to transmitting on a frequency. This mode can only be used in select countries of the EU. The setup.operating_mode variable controls the operational mode of the reader. There are four operational modes for the reader: active, standby, autonomous, and polled. active – Reader is continuously attempting to singulate tags, stores singulated tags in the database and automatically reports any singulated tag via an asynchronous event. The host application can either register for these events or poll the tag database, or use any combination of these two methods. The "active" mode supercedes the previous autonomous and polled modes. standby –Reader is not transmitting any energy, unless processing a tag related command. The RF transmitter is enabled at the beginning of the command processing, any protocol operations required for the command are performed, and then the RF transmitter is turned back off. In this mode, a host application could scan the reader’s field of view for tags by performing the tag.db.scan_tags(1000) command where the parameter value of 1000 represents the amount of scan time, in milliseconds. autonomous – Superceded by active mode. Reader is continuously attempting to singulate tags and automatically reports any singulated tag via an asynchronous event notification on the event channel. polled – Superceded by active mode. Reader is continuously attempting to singulate tags. INfinity 510 Protocol Reference Guide 17
Page 2 and 3: INfinity 510 Protocol Reference Gui
Page 4 and 5: Conventions used in this manual The
Page 6 and 7: Contents Tag Operations............
Page 8 and 9: Chapter 1 - Introduction TYPES OF I
Page 10 and 11: Chapter 2 - User Interface Overview
Page 12 and 13: Chapter 2 - User Interface Overview
Page 14 and 15: Chapter 3 - Command Overview COMMAN
Page 16 and 17: Chapter 3 - Command Overview DATA T
Page 18 and 19: Chapter 3 - Command Overview unauth
Page 20 and 21: Chapter 4 - Reader Behavior Creatin
Page 24 and 25: Chapter 4 - Reader Behavior Protoco
Page 26 and 27: Chapter 4 - Reader Behavior Specify
Page 28 and 29: Chapter 4 - Reader Behavior Reading
Page 30 and 31: Chapter 4 - Reader Behavior The fol
Page 32 and 33: Chapter 4 - Reader Behavior Write T
Page 34 and 35: Chapter 4 - Reader Behavior Lock an
Page 36 and 37: Chapter 4 - Reader Behavior The fol
Page 38 and 39: Chapter 4 - Reader Behavior Tag Dat
Page 40 and 41: Chapter 4 - Reader Behavior A tag i
Page 42 and 43: Chapter 5 - Embedded Reader Applica
Page 48 and 49: Chapter 6 - Tag Protocol Support Ph
Page 50 and 51: Chapter 7 - Reader Namespace READER
Page 52 and 53: Chapter 7 - Reader Namespace reader
Page 62 and 63: Chapter 7 - Reader Namespace The fo
Page 72 and 73:
Chapter 8 - Setup Namespace SETUP N
Page 74 and 75:
Chapter 8 - Setup Namespace setup.p
Page 76 and 77:
Chapter 8 - Setup Namespace setup.s
Page 78 and 79:
Chapter 8 - Setup Namespace setup.v
Page 80 and 81:
Chapter 9 - Info Namespace INFO NAM
Page 82 and 83:
Chapter 9 - Info Namespace info.loc
Page 84 and 85:
Chapter 9 - Info Namespace info.ser
Page 86 and 87:
Chapter 9 - Info Namespace info.tim
Page 88 and 89:
Chapter 10 - Version Namespace vers
Page 90 and 91:
Chapter 11 - Com Namespace COM NAME
Page 92 and 93:
Chapter 11 - Com Namespace com.even
Page 94 and 95:
Chapter 11 - Com Namespace com.netw
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Chapter 11 - Com Namespace com.seri
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Chapter 12 - Tag Namespace Tag Comm
Page 114 and 115:
Chapter 12 - Tag Namespace tag.lock
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Chapter 12 - Tag Namespace tag.read
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Chapter 12 - Tag Namespace tag.writ
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Chapter 12 - Tag Namespace tag.db.g
Page 136 and 137:
Chapter 12 - Tag Namespace tag.db.s
Page 138 and 139:
Chapter 12 - Tag Namespace tag.filt
Page 140 and 141:
Chapter 12 - Tag Namespace tag.filt
Page 142 and 143:
Chapter 12 - Tag Namespace tag.repo
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Chapter 13 - DIO Namespace dio.in.
Page 154 and 155:
Chapter 13 - DIO Namespace dio.out.
Page 156 and 157:
Chapter 14 - Antennas Namespace ant
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Chapter 15 - Modem Namespace Modem
Page 168 and 169:
Chapter 15 - Modem Namespace Modem
Page 170 and 171:
Chapter 15 - Modem Namespace modem.
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Chapter 15 - Modem Namespace The fo
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Chapter 15 - Modem Namespace >>> mo
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Chapter 17 - Errors Namespace ERROR
Page 220 and 221:
Chapter 17 - Errors Namespace error
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Chapter 18 - Events Namespace Event
Page 234 and 235:
Chapter 18 - Events Namespace event
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Chapter 18 - Events Namespace demod
Page 248 and 249:
Page 250 and 251:
Chapter 19 - Enum Namespace DIAG NA
Page 252 and 253:
Chapter 20 - Enum Namespace ENUM NA
Page 254 and 255:
Chapter 20 - Enum Namespace definit
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Index INDEX OF FUNCTIONS AND VARIAB
Page 272 and 273:
Index modem.protocol.easalarm.contr
Page 274 and 275:
This page intentionally left blank.
show all

INfinity 510 Protocol Reference Guide - Sirit

Create successful ePaper yourself

Delete template?

Save as template?