Programming Session

A typical programming session is conducted as follows:

1.Scan the SET bar code at the beginning of each set of program- ming bar codes to place the scanner in Programming Mode. The scanner will emit three 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.

2.Scan the programming label(s) that is (are) specially encoded to make the desired changes. With few exceptions1, the scanner will emit a triple beep each time you scan a valid programming bar code.

 

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

NOTE

supported by the currently active interface will

be implemented.

 

If a label is scanned that changes the scan-

 

ner’s interface, all previous configuration

 

items scanned in the programming session

NOTE

are lost.

 

Additionally, when programming a feature requiring you to scan single digits to set a multi-digit number, such as Minimum Label Length, scanning the END bar code (or any item tag/item value bar code) before completing all input 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 thrown out; any previous bar codes scanned during the session will take effect.

1.Some features, such as Minimum Label Length, require you to select the label’s length by scan- ning a series of single-digit bar codes. A single ‘good read’ beep is sounded when scanning these single digits in Programming Mode. Only the final required digit in the sequence will produce a tri- ple beep when scanned, indicating a successfully programmed feature.

Programming Guide

7