> 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-ruo/instrumentation-miseq-ruo-troubleshooting-list/000001449.md).

# Troubleshooting a Focus Mirror Error on the MiSeq

The following error relates to the M3 focus mirror failing to move during flow cell scanning and leading to a premature run stop.

* This error usually mentions the M3 or focus mirror.
* If this component is not working correctly, the MiSeq will not be able to image clusters correctly.

**Error Message:** FocusMirror: Focus mirror move and/or sensor failed: The FPGA reported an error while executing command "FOCMRRFOC" error message: "Focus Mirror sensor not found"\
![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-e85ffc278b88ec7d81cef4b523005bb1624df553%2Fimage1.png?alt=media\&token=48c193d6-b659-40c9-8839-6f3a603aaea8)

**Troubleshooting steps:**

1. Complete the post-run wash.
2. Power cycle the MiSeq. Reference articles of [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. If the system initializes, run the M3 Mirror Test in the System checks 5 times to verify the mirror moving correctly.
   * MiSeq Control Software (MCS) v4.0: 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 4 more times (5 times total).

Note: How to perform system check also can reference article of [How to perform a System Check on the MiSeq](https://github.com/illumina-swi/illumina-knowledge/tree/master/docs/Instrumentation/MiniSeq/Reference_Material/000001777.md).

4. If all five M3 mirror tests pass, continue with the next run.
5. If the system does not initialize or any of the M3 Mirror 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 #1449), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001449%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-ruo/instrumentation-miseq-ruo-troubleshooting-list/000001449.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.
