|
Frequently Asked Questions: PSC /
Percon Products
PSC Decoders
How can I easily
configure my decoder (or SnapShot) to read bar codes?
My decoder outputs
11 digits of my UPC label. Can the decoder be set to output
either ten or twelve digits?
Why won't my
decoder read a Code 39 label that I printed myself?
How do I know
which cable is correct for my decoder?
What are Keyboard
Wedge and Serial Eavesdrop?
The decoder on my
IBM terminal outputs double digits (112233 instead of 123) to the
screen. How can I correct this?
My new PowerWedge
decoder performs differently from my old Series 10/20/Plus. Are
there any significant differences I should know about?
What should I do
if my decoder will not power up?
How do I add a
Carriage Return ("Enter") or Tab to data being scanned?
How do I program
my decoder or decoded scanner?
What is input
editing?
Can my
decoder/scanner read two bar code labels at a time, but output them as
a single string of data?
What procedures
can I follow to try and troubleshoot the problems I'm experiencing
with my decoder?
What should I do
if my wand has trouble reading my bar code labels?
How do I program
my Series 10 wedge?
1. How can I easily configure my decoder (or
SnapShot) to read bar codes?
Auto-Learn is the simplest method of
customizing your PSC decoder. With Auto-Learn, you "teach" the
decoder to accept the types of bar codes you use.
The following steps guide you through
Auto-Learn:
- Enter programming mode by scanning the
"Start" bar code located on the bottom of the decoder or
in the Auto-Learn section of the User's Guide. (Note: the Mini
PowerWedge does not contain a bar code menu; older decoders will
require you to scan both the start and the program bar codes).
- Regardless of the model of decoder,
enabling programming mode should produce a beep (or short series of
beeps) and the LED(s) on the decoder should blink alternating green
and red.
- Scan samples of the bar code types
that you would like the decoder to recognize. The decoder will read
the sample and reprogram itself to read this bar code type
thereafter. Also, the decoder will set the minimum and maximum
length parameters based on the samples it encounters while in
programming mode so be sure that your samples include both the
longest and shortest labels you are likely to use. You can change
these settings later using Auto-Learn or another programming method.
- When using Auto-Learn to enable your
bar code type, the decoder should emit two quick confirming beeps
with each read, however, the decoder will not output any of the
information contained in the bar code labels to your computer's
display.
- To make the changes permanent you must
save the settings that have been set during the Auto-Learn
programming session. This is done by scanning the "E" bar
code twice. The decoder will emit a series of 5 beeps to indicate
that the new programming parameters have been saved. Once this is
done, the decoder should show a steady green light and be ready to
read your labels.
Related Information
PSC decoders are programmed with
default settings (see "Predefined Defaults" in the User's
Guide) that allow them to work with a variety of common bar code types
(symbologies) and most PC computers. While PSC decoders can handle
nearly any type of standard bar code, the default settings are for only
the most popular types such as Code 39, I 2 of 5, and UPC. These
defaults also set certain specific parameters, such as a minimum and
maximum length, for the specific bar code type that is read. If your
labels require different parameters, then these must be programmed into
the decoder.
The default settings limit the maximum
number of characters that the decoder will read of a given bar code
type. The default upper limit varies with the bar code symbology (e.g.
20 for Code 39; 10 for I 2 of 5). Default settings for specific bar code
types are available in the User's Guide. Most users find that the upper
limit is well above the number typically encountered with most labels.
These settings ensure optimal decoding performance under the most
typical conditions but sometimes need to be altered for additional bar
codes to be read.
Resources: Mini PowerWedge User's Guide
PowerWedge 10 User's Guide
PowerWedge 20 User's Guide
SnapShot User's Guide
Click here for product manuals.
2. My decoder outputs 11 digits of my UPC
label. Can the decoder be set to output either ten or twelve
digits?
Yes. A UPC bar code consists of the
first digit (NSD or Number System Digit), the last digit (Check Digit)
and the "inner 10" which are the core digits of the bar coded
information. The decoder can be programmed to output the first and/or
last digits to the host along with the core digits (by default, neither
are output). For example, to get only the last 11 digits of the bar
code, you would enable the "send check digit" function, while
leaving "send system digit" disabled.
The programming labels required to change
these parameters are located in the UPC-A section of your User's Guide.
You may also create Code 39 bar code labels using the values found below
to program your PowerWedge, decoded Snapshot, and Series 10 Plus/20/20
Plus decoders.
Series 10 users: you must first scan the
"Start" and "Program" bar codes prior to scanning
the bar code(s) that change the system or check digit parameters.
PowerWedge and Series 10 Plus/20/20
Plus
Output System (NSD) Digit
*$+$-311EE*
Output Check Digit
*$+$-321EE*
Series 10
Output System (NSD) Digit
*71BEE*
Output Check Digit
*72BEE*
Resources: Mini PowerWedge User's Guide
PowerWedge 10 User's Guide
PowerWedge 20 User's Guide
SnapShot User's Guide
Click here for product manuals.
3. Why won't my decoder read a Code 39 label
that I printed myself?
Code 39 is one of the most widely
used bar code symbologies. It can accommodate both alpha and numeric
characters and, very conveniently, Code 39 fonts are widely available to
create labels with common word-processing programs.
Like all bar codes, Code 39 contains
start and stop characters that define the beginning and end of a string
of information on a label. Code 39 uses an asterisk (*) for both the
start and the stop characters. If you use a dedicated bar code label
program, the start/stop characters should be automatically added.
However, if you are using a bar code font in a word-processing
program, you must add these characters manually. The final bar code
label must read, for example, *123abc*, not 123abc.
4. How do I know which cable is correct for my
decoder?
Our fixed station decoders and
decoded scanners interface with over 300 different computers and
terminal models. We also make a line of dedicated decoders for keyboard
wedge configuration with specific models of Wyse and HP terminals.
If your keyboard or terminal does not
function when the decoder is connected, you may be using the wrong
cable. The required cabling differs for each type of connection
and decoder/terminal combination. Contact your reseller for
assistance in obtaining the correct cable for your application.
5. What are Keyboard Wedge and Serial
Eavesdrop?
While PowerWedge 20, decoded
Snapshot, or Series 20/Plus decoders may be connected either serially or
as a keyboard wedge, the PowerWedge 10 and Mini PowerWedge cannot.
A dedicated PowerWedge 10 (with a separate power supply) is required for
serial use and the Mini PowerWedge can be used only as a keyboard wedge.
A dedicated keyboard wedge or serial model cannot be used in a
configuration other than the one for which it is designed.
Keyboard Wedge Configuration
The most common way to connect a decoder
to a host computer is with a keyboard wedge configuration cable. With
this type of connection, the decoder output data stream is introduced
directly into the communication path of a keyboard and computer. Output
data from the decoder, from the point of view of the computer, is
identical to that of the keyboard. Normal operation of the keyboard is
maintained with the decoder attached.
The wedge configuration cable resembles a
"Y," with each of the short legs going to the decoder and the
keyboard, and the long leg to the computer keyboard port. Once cable
connections have been made, the decoder should be configured to emulate
the keyboard type specific to the host computer. Once configuration is
complete, scanned bar code data will appear to the computer as input
from that type of keyboard. Consequently, any data from the decoder will
also appear in any application as though it were keyed in. The decoder
alone handles the emulation function and reconfiguration of the host
computer or device drivers are not required.
Serial Eavesdrop Configuration
Serial eavesdrop is very similar to
keyboard wedge configuration. Both methods involve, in effect,
splicing the decoder into an existing communication path leading to the
host computer. However, with serial eavesdrop, the decoder is wedged
into a serial communication stream between the host computer and a
terminal. The decoder output is accepted as concurrent serial data and
does not interfere with communications between host and terminal. Since
the decoder is sending serial data, a very large number of terminal-host
interfaces are available.
Serial Configuration
In order to set up a decoder for serial
transmission of data there is a sequence of scans one performs
using the programming bar codes on the bottom of the decoder box or on
the Bar Code Menu in the User's Guide.
- Scan start (start and program for
older models), C, 8, E, E.
- The decoder should beep several times
on the last 'E' and the LED should return to a steady green state.
This sets the decoder box to serial
transmission at 9600, 8N1 and no flow control. If your serial parameters
differ from this, you will want to set the decoder box to the same
settings as your terminal or serial port. Bar codes for setting the
serial parameters can be found in the User's Guide.
Resources: Mini PowerWedge User's Guide
PowerWedge 10 User's Guide
PowerWedge 20 User's Guide
SnapShot User's Guide
Click here for product manuals.
6. The decoder on my IBM terminal outputs
double digits (112233 instead of 123) to the screen. How can I
correct this?
Doubling of output data on an IBM
terminal indicates that the decoder is emulating the incorrect keyboard.
By default, decoders are set to emulate an AT-PS/2 style PC keyboard, so
the emulation settings must be changed to match those of the keyboard
attached to your terminal. If your keyboard has a single row of function
keys, then it is a "102 keyboard"; if there are two rows, it
is a "122 keyboard."
To enable your decoder to emulate the
appropriate keyboard for your terminal, create Code 39 bar codes using
the bar code values below or locate the bar codes in your User's Guide.
After scanning these setup codes, the decoder should emit a series of
confirmation beeps and a solid green light, indicating that the decoder
was successfully programmed and is ready for use. At this point, simply
turn power to the decoder off then back on and rescan the codes.
IBM 102 Keyboard Setup Code
*$+$-C015EE*
IBM 122 Keyboard Setup Code
*$+$-C017EE*
Notes: You can use the Bar Code Menu,
located on the bottom of your decoder or in the User's Guide, with the
sequence indicated above. The sequence must be preceded by scanning the
"Start" bar code and concluded by scanning the "E"
bar code twice. Scanning "Start" saves the programming
sequence and scanning "E" exits the programming routine.
If you own a Mini PowerWedge there is not
a bar code menu on the decoder, so you must use either these setup codes
or the Bar Code Menu in your product's User's Guide. For bar code
menu programming of older decoders, use both the "Start" and
"Program" commands.
Resources: Mini PowerWedge User's Guide
PowerWedge 10 User's Guide
PowerWedge 20 User's Guide
SnapShot User's Guide
Click here for product manuals.
7. My new PowerWedge decoder performs
differently from my old Series 10/20/Plus. Are there any
significant differences I should know about?
Data Transfer Rate
For the most part, the PowerWedge
decoder family functions in the same way as the Series 10/20/Plus
family. Since the PowerWedge decoder family is newer, its performance is
superior to the prior generation of PSC decoders. However, PowerWedge
decoders may have some initial problems working properly with older
computers that use a slow keyboard data transfer rate. In such cases,
the decoder may appear to "drop" or omit certain characters
from a scanned label. This symptom appears more often with older
Macintosh computers than with PCs of the same vintage.
The problem can be solved by increasing
the intercharacter delay, i.e., allowing more time between the
transmission of each decoded character through the keyboard interface.
Experimentation will show exactly how long a delay is needed to correct
the problem with a given computer, but a 20 millisecond delay should
suffice for most computers and could be used as a starting point for
testing purposes.
Other Changes
The PowerWedge decoder family has been
enhanced to handle Code 93 symbology (the Series family decoders handled
this symbology; PowerWedge decoders initially did not). Keyboard support
for a very small number of old and relatively rare IBM terminals has
been dropped with the PowerWedge family.
The PowerWedge 20 decoder (the only
PowerWedge decoder that is input-edit capable) will not perform an
input-edit from a keyboard command or control code. An input edit can be
triggered on this decoder only by a scan or serial input. Hence, to edit
the input from a scale, for example, a PowerWedge 20 would
"trap" the scale input and parse the data string according to
a programmed definition that matched the characteristics of that string.
Unlike the Series 20 Plus decoder, a PowerWedge 20 will not perform an
input-edit based solely on a keyboard command or corresponding control
code.
Series 20 Plus decoders are still
available on a special order basis for customers who require any of its
distinct features.
8. What should I do if my decoder will not
power up?
Keyboard Wedge Configuration
- Make certain the decoder is connected to
the host computer with the correct interface cable and that all the
connections are tight.
- If you have a Series 20/Plus, make sure
that the A/B switch on the back of the box is in the B position.
- If you have a Wyse or HP dedicated
decoder (model #s 22-050-00, 22-055-00, 23-050-00, or 23-055-00), make
sure to use it with a PSC power supply or equivalent 9V, 500mA,
negative center, power supply.
- If you are using a PC with a PS/2-style
keyboard, make sure that the keyboard wedge cable is plugged into the
keyboard port, rather than to the mouse port, of the computer. It is
not uncommon to plug the interface cable accidentally into the mouse
port.
- Try disconnecting the input device
(wand, laser, or ccd scanner). If doing so allows the decoder to power
up, then the decoder may be incompatible with it. Contact your
reseller with the model name and number of your input device and
decoder.
Serial and Serial Eavesdrop
Configuration
Make certain the decoder is using a PSC
power supply (or any 9V, 500mA, negative center, power supply).
Decoders connected serially cannot use the host computer as a power
source.
If you have a Series 20/Plus decoder,
make sure that the "A/B" switch on the rear of the unit is
set in the "A" position
Try disconnecting the input device
(wand, laser, or ccd scanner). If doing so allows the decoder to power
up, then the decoder may be incompatible with it. Contact your
reseller with the model name and number of your input device and
decoder.
9. How do I add a Carriage Return ("Enter")
or Tab to data being scanned?
If bar code decoders and scanners did
nothing other than read and decipher bar coded labels and send the
information they contained to a computer, they would still be incredibly
useful and time-saving devices. In comparison to a keyboard, bar code
technology offers a vastly more efficient and accurate method for
handling repetitive data entry tasks.
However, rarely does a decoder/scanner
simply decode and pass along only the information contained in a bar
code label. Since most decoded data is ultimately put into a software
application running on the host computer, a keyboard command, such as a
carriage return or tab, is usually required to signal the end of one
unit of data (such as a field or record) and the beginning of the next.
When data is keyed into to an application, the end-of-field command is
executed by pressing the Enter or Tab keys.
Reducing or eliminating the need for
keyboard input is a major advantage of bar coding technology. Hence, PSC
has designed its decoders to transmit what is called an autoterminator
(by default, PSC decoders send a carriage return, the equivalent of
pressing the Enter key on the keyboard, immediately behind the data).
This transmitted command causes the computer to automatically execute a
keyboard command. This might have the effect of moving the insertion
point in an application from one field to the next after the data is
received, or causing the application to process the data in some way.
While carriage return or tab termination
meets the needs of most applications, a significant number of users
require other kinds of commands (called control codes) or characters to
be added to the decoder's data stream. In response to this need, PSC's
decoders can be programmed to transmit a variety of additional keyboard
commands, ASCII characters or strings, or, alternately, be set to omit
termination altogether.
Since the most commonly required commands
are for a carriage return, tab, or to turn termination off (allowing the
host application to automatically process data inputs), we offer simple
and direct control over these kinds of terminators through the
autoterminator settings (see your User's Guide for bar code programming
and other details about these functions). However, the autoterminator is
limited to transmitting a single command or ASCII character.
The preamble and postamble
functions may be used, like the autoterminator, to transmit any single
keyboard command or character as well as a sequence of commands or
character string. Preamble and postamble commands can be used
either with or without an autoterminator.
In addition to autoterminator, preamble,
and postamble functions, our input-editing capable decoders (PowerWedge
20, decoded Snapshot, Series 20 Plus) also allow you to insert keyboard
commands or characters at any point in a point in a data string. In
effect, these decoders allow you to parse a data string in almost any
way, and so provide an extra level of data output control over our
standard decoders.
Quick Reference: Preamble,
Postamble, and Autoterminator Functions
Preamble: Inserts a keyboard command(s), ASCII character or
string (ex: "This is my data") before the output data string
Postamble: Inserts keyboard
command(s), ASCII character or string (ex: "This is my data")
after the data string
Autoterminator: Sends a
standard end-of-field/advance-to-next field command or single ASCII
character at the end of the transmitted data string. May be set to send
a carriage return (Enter), a tab, or no termination at all.
Auto-termination can be used in conjunction with a preamble or
postamble.
Resources: Mini PowerWedge User's Guide
PowerWedge 10 User's Guide
PowerWedge 20 User's Guide
SnapShot User's Guide
Click here for product manuals.
10. How do I program my decoder or decoded
scanner?
Programming a decoder refers to
controlling how it either interfaces with an input device or host, or
how it reads and processes bar code data. All of PSC's decoders and
decoded scanning devices have some type of programming capability. They
can be programmed to work with a wide variety of host computers, from
PCs to terminals, and most work out-of-the-box with standard undecoded
scanners, wands, badge readers, and magnetic stripe readers (MSR). In
addition to the most common bar codes types, PSC decoders can be
programmed to read less common ones or to change the read-parameters of
a given type.
In addition to programming control over
input device, host, and bar code type, all PSC decoders offer basic
control over ASCII characters and/or keyboard commands (such as a tab
and or carriage return) that precede or follow the output bar code data.
Moreover, the PowerWedge 20, Series 20/Plus, and decoded Snapshot have
advanced programming capability , called input editing, that allows the
user to program the decoder to parse a string of data into separate
fields and control the output to an application running on the host
computer. Input editing is not available in the PowerWedge 10, Mini, or
Series 10 decoders.
All of PSC's decoders may be programmed
using the programming bar codes found in the User's Guide or on the
bottom of the decoder. All PowerWedge family decoders and decoded
Snapshot scanners can be programmed using the On-screen programming
method in conjunction with a text editor, such as Microsoft Windows
Notepad (or DOS Edit). On-screen programming can also be performed with
a serially connected decoder or decoded scanner using Windows
Hyperterminal. None of our decoders require PC or other software or
hardware drivers.
The programming methods described in this
FAQ are documented in the product user's guides
Resources: Mini PowerWedge User's Guide
PowerWedge 10 User's Guide
PowerWedge 20 User's Guide
SnapShot User's Guide
Click here for product manuals.
11. What is input editing?
Input editing functionality,
available in PowerWedge 20, decoded Snapshot, and Series 20 Plus, allows
the user to have full control over the output format of a data string.
A single string of data, e.g. 12345678, can be broken down into separate
fields which can then be output in any sequence the user might desire.
In addition, you have the option of omitting any characters in the
string or inserting keyboard commands or ASCII characters at any point.
Input editing is very useful for
"trapping" data of a specific type, length, or makeup. For
example, an input edit can be defined to trap and output only data that
originates from a Code 128 label and is no longer than 8 characters,
with the number 1 in the first position and 8 in the last. Hence, a Code
128 label with the character string, 12345678, would be output to the
host, whereas, the string 23456789, while also 8 characters long, would
not. Data from bar code labels using symbologies other than Code 128
would be automatically rejected, even if they met the other criteria.
For more information see Chapter 4:
Input Editing in the PowerWedge 20 or decoded Snapshot User's Guides.
Resources:
PowerWedge 20 User's Guide
SnapShot User's Guide
Click here for product manuals.
12. Can my decoder/scanner read two bar code
labels at a time, but output them as a single string of data?
Yes. We have created a
programming bar code to allow PowerWedge decoders to use the
"concatenation" function built into the Code 128 symbology.
With this function enabled, PowerWedge decoders can read and join
together two separate 128 labels, rather than treating them as separate
labels. This will work if the two labels are of the proper size to fit
within the scan path of your bar code reader.
1. Create a Code 39 bar code using the following values:
*$+$-431EE*
2. Scan the bar code to enable the concatenation feature.
13. What procedures can I follow to try and
troubleshoot the problems I'm experiencing with my decoder?
See the Fixed Station Decoder
Troubleshooting Guide for step-by-step guidelines on how to diagnose
problems with your decoder.
14. What should I do if my wand has trouble
reading my bar code labels?
A properly functioning wand should be
able to read any bar code label within the specification of a given
symbology (such as Code 39 or UPC) and within the size and density
limits of the wand tip aperture.
Over time, however, wand performance may
deteriorate because the tip becomes worn or, more typically, dust
collects inside it.
Diagnosis
Before inspecting the wand tip, try to
determine whether the reading difficulty lies with the wand or the
decoder. Properly functioning decoders will beep whenever a
programming bar code is read. If the decoder beeps when the wand reads
one of these, then the decoder is probably not properly set up to read
your label (for setup information see FAQ #001). If you are able to
read a programming bar code successfully, try reading it repeatedly to
ensure that the wand is not reading intermittently.
Experiment with your wanding technique.
Be sure that the tip of the wand contacts the surface of the bar code
you wish to scan. When scanning, start in the white space to the left
of the bar coded information, move the tip quickly over the bar code,
and stop once you have moved the tip into the white space after the
bar coded information. If the wand seems unable to read the bar code,
try varying the scanning angle. For best performance, the wand should
be held in the near vertical position, but it may sometimes require
slight to moderate tilt - especially with bar codes of marginal
quality.
If the wand is still unable to read a
programming bar code (no beep from decoder) or reads it
intermittently, try cleaning the tip with alcohol. If the tip of your
wand is not removable, then check the cable connection to the scanner
and move or jiggle the wand cable while attempting to scan a bar code.
Sometimes a loose or faulty connection will make itself apparent with
this technique.
If your wand has a small black ring
above the tip, then the tip may be removed and cleaned internally.
Take a coin or other tool and pry the tip loose and remove it from the
wand. Inspect the inside of the tip for dust or debris. Blow the
inside of the tip out with compressed or canned air or simply blow
forcefully into the tip orifice. Then, using a cotton swab dipped in
alcohol, gently clean the inside of the wand tip.
If this doesn't solve the problem, then
there is probably something wrong with either the wand itself or the
cable that connects to the decoder. Contact your reseller for
help with these issues.
15. How do I program my Series 10 wedge?
Series 10 programming guidelines are
available for download.
Included are instructions on how to set a user defined value, a
Programming Label Chart, a Complete Parameter Listing, and the Code 39
Full ASCII Table.
1-800-432-1255 or 1-973-579-0009
|
