> 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/000002241.md).

# Troubleshooting Z Motor Positive soft limit too nonlinear at innermost test point on the MiSeq

**Background**

The following Z stage/motor error indicates either a temporary communication loss between the stage and software or an issue with the stage hardware. This error usually occurs at cycle 1 of a sequencing run, after a power cycle, or at the start of a wash.

**Error**

“Z Motor: Positive soft limit too nonlinear even at innermost test point: Target = -20.000 um, actual = -16.287 um, error = 3.713 um, tolerance = 0.100 um (System.Exception)”.

**Troubleshooting Steps**

1. Complete the post-run wash if not already completed.
2. Power cycle the instrument following the instructions in the Knowledge Base articles [How to Power Cycle the MiSeq](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md) and [How To Power Cycle the MiSeq Video](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005871.md).
3. If the system initializes, run the Z stage Test in the System checks five times to verify the stage is moving correctly.
   * MiSeq Control Software (MCS) v4.0 and above: From Main Menu, select System Check.
   * MCS v3.1 and older: From Welcome Screen, select Manage Instrument, select System Check.
   * Follow the prompts on the screen to start the test, and repeat the test four more times (five times total).
4. If all five Z stage tests pass, continue with the next run.
5. If the system does not initialize or if any of the Z stage tests fail, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for further assistance.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2241), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002241%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/000002241.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.
