REFERENCES
129

5

5.7.2 Power-Off Timeout
If this command is enabled, after the desired timeout in hours, the GRYPHON™
batteries are disconnected and all power consumption ceases. To restore power,
press the trigger once. The reader will now be ready to read codes.
Power-off does not effect configuration parameters.
5.7.3 Beeper Control for Radio Response
For M-Series readers, the data entry good read tone normally results in two beeps;
the first indicates that the reader has decoded the code, the second indicates
whether OM-GRYPHON™ has received the data.
This can be changed according to the following selections:

♦

Normal: both good decode and good reception are signaled (two beeps).

♦

Only Good Decode: only the first beep indicating a good read is signaled.

♦

Only Good Reception: only the second beep indicating a good reception is
signaled.

♦

Off: Neither good read nor good reception beeps are signaled.

For all configurations, any transmission errors will always be signaled.

5.7.4 Single Store
When single store mode is enabled, if the GRYPHON™ M fails to transmit a code to
the cradle, it enters a special operating mode that prevents the user from reading
barcodes. When such operating mode is entered, the trigger no longer enables
barcode reading but is used to retry transmission itself for the number of attempts
selected in configuration. Once the transmission is successful the reader returns to
the standard mode. If transmission is not successful after the number of configured
attempts, the code is discarded.
Single store may be useful if you often read codes at the limit of the coverage area
and there is a chance that code transmission can fail. In such case single store
allows you to move to a more favorable position or location (i.e. closer to the cradle)
and retry transmission without the necessity of re-reading the code since it is already
stored in the reader.
Conversely, if single store is disabled, and the user wants to retry transmission, the
code must be read again, and therefore the attempt must be made from basically the
same location. If the user gives up, he does not know if the transaction was
successful. (Actually the transmission could have been successful but the cradle
may have been unable to acknowledge the message). There are applications in
which there is no risk of transmission failure. In such cases it may be better to
disable single store so that the user perceives a more consistent behavior of the
trigger in that it always corresponds to code reading.