Specifications
14-2
LS 2208 Product Reference Guide
For instance, a data formatting rule could be the following:
Criteria: When scan data is Code 39, length 12, and data at the start position is
the string “129”,
Actions: pad all sends with zeros to length 8,
send all data up to X,
send a space.
If a Code 39 bar code of 1299X1559828 is scanned, the following is transmitted:
00001299<space>. If a Code 39 bar code of 1299X15598 is scanned, this rule is ignored
because the length criteria has not been met.
The rule specifies the editing conditions and requirements before data transmission occurs.
Using ADF Bar Codes
When you program a rule, make sure the rule is logically correct. Plan ahead before you
start scanning.
To program each data formatting rule:
• Start the Rule. Scan the Begin New Rule bar code on page 14-8.
• Criteria. Scan the bar codes for all pertinent criteria. Criteria can include code type
(e.g., Code 128), code length, or data that contains a specific character string (e.g.,
the digits “129”). These options are described in Criteria on page 14-12.
• Actions. Scan all actions related to, or affecting, these criteria. The actions of a
rule specify how to format the data for transmission. These options are described
in ADF Bar Code Menu Example on page 14-3.
• Save the Rule. Scan the Save Rule bar code on page 14-9. This places the rule
in the “top” position in the rule buffer.
• If you make errors during this process, some special-purpose bar codes may be
useful: Erase Criteria and Start Again, Erase Actions and Start Again, Erase
Previously Saved Rule, etc.
Criteria, actions, and entire rules may be erased by scanning the appropriate bar code (see
page 14-9).
Beeper Definitions on page 2-2 help guide you through the programming steps.










