
Troubleshooting Guide (continued)
| Symptoms | Possible Causes | Solution | |
| The unit powers | Beeper disabled. No tone | 
 | |
| up, but does not | Enable beeper. Select tone | ||
| selected | |||
| scan/or beep | 
 | ||
| 
 | 
 | ||
| 
 | 
 | 
 | |
| 
 | 
 | 
 | |
| 
 | 
 | UPC/EAN, Code 39, interleaved 2 of | |
| The unit powers | Scanning a particular | 5, Code 93, Code 128 and Codabar | |
| up, but does not | symbology that is not | are enabled by default. Verify that | |
| scan and/or beep | enabled | the type of bar code being read has | |
| 
 | 
 | been selected | |
| 
 | 
 | 
 | |
| 
 | 
 | 
 | |
| 
 | The scanner has been | 
 | |
| 
 | programmed for a | Verify that the bar code that is being | |
| The unit powers | character length lock, or a | scanned falls into the criteria | |
| up, but does not | minimum length and bar | (Typical of  | |
| scan and/or beep | code being scanned does | The scanner defaults to a minimum | |
| 
 | not satisfy the | of 3 character bar code | |
| 
 | programmed criteria | 
 | |
| 
 | 
 | 
 | |
| 
 | 
 | 
 | |
| The unit scans a | The scanner is configured | If the scanner is setup to support | |
| bar code, but locks | ACK/NAK, RTS/CTS, XON/XOFF | ||
| to support some form of | |||
| up after the first | or D/E, verify that the host cable and | ||
| host handshaking but is | |||
| scan red LED | host are supporting the handshaking | ||
| not receiving the signal | |||
| stays on | properly | ||
| 
 | |||
| 
 | 
 | 
 | |
| 
 | 
 | 
 | |
| The unit scans, but | The scanner’s data format | Verify that the scanner’s data format | |
| the data | matches that required by the host. | ||
| does not match the host | |||
| transmitted to the | Most sure that the scanner is | ||
| system requirements | |||
| host is incorrect | connected to the proper host port | ||
| 
 | |||
| 
 | 
 | 
 | 
25
