Enter 94 End
*/$%ENTR* *ZEND*
Setting up your Operation Modes
7
7-1.
Output String Structure
On the whole, a complete output string is composed of a couple of data fields, starting with
Preamble code
followed in order by
Prefix Code, Code Name, Code Data,
and
Suffix
Code
, ending with
Postamble Code
. Except for
Code Data
filed as an indispensable and
non-configurable part of output data, the rest are optional transmit elements which you can
define on your terms. The relevant configuration on the output formatting parameters will be
elaborated in order throughout this chapter.
Take an output string,
<\n>20140610(Code-39)B13449872156 0882StaffName<\n>
, as an
example. In general, it can be broken down into several data fields as the below illustration
shows:
<\n>
20140610
(Code-39) B13 449872156 0882 Mathew <\n>
Output String Structure
Preamble
Code
Prefix Code
Code Name
Code ID
Code Data
Suffix Code
Postamble
Code
<\n>
20140610
(Code-39)
B13
449872156 0882
Mathew
<\n>
Preamble Code
is used to insert a line
before the barcode is transmitted.
Code ID
is an identification number in
reference to the specified symbology.
Prefix code
, in the example, is configured to indicate the
date the barcode is scanned.
Code Data
refers to the decoded message.
Code Name
indicates symbology name.
Suffix Code
is used to specify the person who conducts
the scan.
Postamble Code
is used to insert the line after the
barcode is transmitted.
Example