> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001913.md).

# Troubleshooting MiSeq "Z Motor The Z stage amp Op-amp might not be wired correctly" Error

Users may encounter a "Z stage/amp/Op-amp might not be wired correctly" error at any point during a MiSeq run. This issue may be caused by a communication error or by issues with the Z-stage itself.

**To troubleshoot this issue :**

1. Perform the post-run wash as indicated.
2. Power Cycle the MiSeq following the instructions in the Illumina Knowledge Article [How to Power Cycle the MiSeq](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md).
3. Navigate to the System Checks Menu and perform the Z-Stage test five times. The rest of the checks may be de-selected. For more details, see [How to perform a System Check on the MiSeq](/instrumentation/miseq/instrumentation-miseq-reference_material-list/000001777.md).
4. If error persists, instrument fails to initialize, or one of the Z-Stage test replicates fail, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support).
5. If the instrument initializes without any error and all five Z-Stage tests pass, proceed with using the MiSeq system for sequencing.
6. If the next run fails with the same error, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support).

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1913), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001913%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001913.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.