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

# Troubleshooting "Compensator Move and/or Sensor Failed" errors on the MiSeq

Users may encounter a compensator error during a MiSeq run, system check, or Control Software initialization. This error indicates that the compensator on the instrument, which allows the cameras to change focus between the top and bottom of the flow cell, is not functioning properly. This can result from a communication error on the instrument or may indicate a hardware issue on the instrument.

Error message: *Compensator Move and/or Sensor Failed on retry #3 /3: Moving to OutOfPath, StartCurrent =...*

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-98b6b4ec17fd0564cb6a0043fb117463bdf12dd6%2Fimage1.jpg?alt=media\&token=33a49ac6-a292-435b-881a-32b2c5b57719)

**Troubleshooting Steps**:

1. Perform the post-run wash.
2. Power cycle the MiSeq. For reference, see [How to Power Cycle the MiSeq](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md) or [How To Power Cycle the MiSeq Video](https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005871.md).
3. Restart the MiSeq Control Software (MCS). If no issues with re-initialization, perform the **Compensator test five times.**
   1. Start the system check with the used flow cell loaded on the instrument (alternatively, the previous wash flow cell can be used). See the following Knowledge Base article for more information on [How to perform a System Check on the MiSeq.](https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-reference_material-list/000001777.md)
   2. Select Compensator test.
      1. MCS v4.0 and above: From **Main Menu** and then select **System Check**.
      2. MCS v3.1 and below: From Welcome Screen, select **Manage Instrument**, and then select **System Check**.
   3. Follow the prompts on the screen to start the test, and repeat the test four more times (five times total).
4. If all Compensator test replicates pass, continue with normal sequencing.
5. If the system fails to initialize or any of the five replicates of the Compensator test 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 #8020), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000008020%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/000008020.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.
