> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/zebra-scanners/troubleshooting-zebra-scanners.md).

# Troubleshooting Zebra Scanners

| Issue                                                  | Possible Cause                                     | Possible Solution                                                                           |
| ------------------------------------------------------ | -------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| Aiming Dot is not working.                             | Scanner has no power.                              | Make sure cable is connected to POS and to the Scanner.                                     |
| Aiming Dot is not working.                             | Incorrect cable used.                              | Make sure that the correct cable is being used.                                             |
| Aiming Dot is not working.                             | Scanner is disabled.                               | Check the configuration on the POS.                                                         |
| Aiming Dot is working but is not reading the bar code. | Bar code is unreadable.                            | Try another bar code of the same product.                                                   |
| Aiming Dot is working but is not reading the bar code. | Aiming dot not centered on the bar code.           | Center the aiming dot on the bar code.                                                      |
| Unable to hear the beep or is too low.                 | Volume is turned down.                             | Use the Volume Adjustment section to increase the beep volume.                              |
| USB scanner configured but scanner isn't working       | The POS has not been rebooted after configuration. | Reboot the POS. Confirm the scan codes are properly configured to support USB connectivity. |

{% hint style="info" %}
Navigate to the manufacturer's website below for additional information and documentation.

* [DS9208 support page](https://www.zebra.com/us/en/support-downloads/scanners/general-purpose-scanners/ds9208.html)
* [DS457 support page](https://www.zebra.com/us/en/support-downloads/scanners/fixed-mount-scanners/ds457.html)
* [DS9308 support page](https://www.zebra.com/us/en/support-downloads/scanners/general-purpose-scanners/ds9308.html)
* [DS55 Series support page](https://www.zebra.com/ap/en/products/scanners/fixed-mount-scanners/ds55-series/ds55.html)
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://commanderhelp.verifone.com/feature-references/features-and-products-references/zebra-scanners/troubleshooting-zebra-scanners.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
