User's Manual

Library L100 Reader User's Guide
10 Calibration
The L-L100 Reader features an innovative technology based on Digital Signal Processing (DSP) to
optimize long-distance reading and writing performances.
In particular, the L-L100 Reader is very efficient even in industrial and noisy environments.
Environmental conditions can vary significantly according to the application-specific factors such as
antenna size, output power, machines close to the L-L100 Reader, etc. Such parameters can
create noise around the RFID system.
In order to optimize the performance of your RFID system, it is possible to calibrate the L-L100
Reader. The calibration consists of selecting the best trigger threshold used to capture and decode
a smart label signal. The trigger threshold value corresponds to the sensitivity of the L-L100
Reader making it possible to differentiate a smart label signal from a noise signal.
If the trigger threshold value is too low, the L-L100 Reader may start decoding a signal which
actually is a noise signal. In this case, the decoding efficiency of the L-L100 Reader may decrease.
If the trigger threshold value is too high, the L-L100 Reader will not decode a low-magnitude smart
label signal (because it treats it as an ambient noise signal). In this case, reading distance
performance may decrease.
Ultimately, a compromise must be selected to find the best trigger threshold value.
The L200 Explorer application defines the optimized trigger threshold value. Please refer to the
L200 Explorer User’s Guide for further information.
Default trigger threshold values stored in the L-L100 Reader upon delivery depend on the smart
label type. These trigger values are optimized for Aero-LI, L-SA1 and L-SA2 antennas at middle-
range power.
The calibration process is only available for C210, C220 and C240 tag types.
CAUTION: C210 and C240 decoding algorithms have been modified to improve L-L100
Reader performances. It is possible that trigger values optimized for L-L100 Reader
Firmware releases previous to version 3.0 must be changed when using version 3.0 or more
recent.
34/45 Revision 3.1b April 2003