Datalogic MAGELLAN 900i - Programming Session

ABOUT PROGRAMMING YOUR SCANNER
14 MAGELLAN™ 900I
Programming Session
A typical programming session is conducted as follows:
1. Scan the Enter/Exit Programming Mode bar code to place the scanner in Program-
ming Mode. Depending upon its current programming, the scanner may emit a beep
or beeps, indicating it has read the bar code and the green LED will flash on and off
slowly while the scanner remains in Programming Mode. Normal scanning functions
are disabled.
Scan the programming bar code(s) to make the desired changes. The beeper will sound as
programming barcode labels are scanned, indicating progress during scanner configuration.
The beep may vary depending upon the feature being configured.
Additionally, when programming a feature requiring you to scan single digits to set a
multi-digit number, such as Minimum Label Length, do not scan bar code (or any item
tag/item value bar code) before completing all input. To do so will result in an error
tone and cause the scanner to exit Programming Mode. Under these circumstances,
the current feature you were trying to set is not applied, but any previous bar codes
scanned during the session will still take effect.
2. Scan the Enter/Exit Programming Mode bar code to save any new settings and exit
Programming Mode. The scanner will sound a beep and reset upon exiting Program-
ming Mode, and the green LED will return to its usual state (on steady or off).
3. Maintain a good record of all changes made to ensure that you know if the original
factory settings have been changed.
NOTE
Not all features are available for all interfaces and the scanner will sound an error tone
when scanning programming bar codes for features invalid to the current interface.
Only features supported by the currently active interface will be implemented.
NOTE
If a bar code is scanned that changes the scanner’s interface, all previous configura-
tion items scanned in the programming session are lost.
NOTE
It is recommended that programming sessions be limited to one feature at a time.
Should you make a mistake in the programming sequence, it can be difficult to dis-
cover where an error has been made if several features are programmed at once. Addi-
tionally, it can be confusing to determine which features may or may not have been
successfully set following such a session.