User Manual

Chapter 8 System Parameters and Comm ands
Hi-G-Tek Ltd. Micro electronics & Asset Tracking Technology - 213 -
 The application may send the acknowledge after it has written the
message to a database. This ensures that no data will be lost even in
case of application crash or DataReader's reset.
 The application can send only one acknowledge to every burst message
even if many DataReaders received it or more than one retry was
received.
 The application can choose the most appropriate timing for sending the
acknowledge.
The disadvantages of the manual Burst acknowledge are:
 Because it is a normal RF command it takes the 3 seconds of the
Reader Interrogation Header (Th w ) .
 It is not automatic. Nevertheless, DataSealLib sends it automatically by
default .
Note that more than one DataReader may receive the same Burst message,
and that each DataReader may receive more than one retry of the same
burst message. It is the application's responsibility to correlate equal Burst
messages.
There are 2 formats of Burst messages: one is older, an always included
only the Short Status of the DataSeal. The new format can include any
parameter and/or User Data. See the description of the Alert Burst Data
Descriptor, Cl ose Bu rs t Da ta Des cri pt o r and the arguments of the Start
Forced Burst RF command for informat ion about how t o define which
parameters and User Data will be included in each type of message. In
addition, the new format includes a sequential number for each event that
caused a Burst message. This way you can easily correlate messages that
are received by different DataReader, or 2 retries of the same message. T he
Forced Burst messages also contain a special Use r C o de argument that the
user can use to define the purpose of the Burst message. In DataSealLib,
y o u receiv e t h e Bur st m essages t hr ough th e Rea de r .Bu rs t Ex event , and