06.01.2015 Views

INfinity 510 Protocol Reference Guide - Sirit

INfinity 510 Protocol Reference Guide - Sirit

INfinity 510 Protocol Reference Guide - Sirit

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 12 - Tag Namespace<br />

tag.reporting.arrive_generation<br />

The arrive event generally occurs when the first tag report is seen.<br />

Unfortunately, this often occurs on the edge of the RF field and results in<br />

some of the requested fields being blank as they were not able to be<br />

determined in time for the first report to be generated.<br />

If this field is set to its default of NO_WAIT, the arrival event will occur<br />

coincident with the first tag report. Otherwise, the arrival event will be<br />

stalled until the requested data is obtained.<br />

For example, if WAIT_FOR_TID is chosen, the arrival event will not occur<br />

until the TID has been obtained via the tag report mechanism.<br />

WAIT_FOR_DATA stalls the arrival event until the user data has been<br />

properly obtained and the WAIT_FOR_ALL stalls the event until both the<br />

user data and the TID have been obtained properly.<br />

Type<br />

Permissions<br />

Data Type<br />

Default<br />

Enum<br />

var<br />

guest=r,admin=rw<br />

enum<br />

no_wait<br />

no_wait wait_for_tid wait_for_data wait_for_both<br />

138 <strong>INfinity</strong> <strong>510</strong> <strong>Protocol</strong> <strong>Reference</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!