> 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/novaseq-6000/instrumentation-novaseq-6000-reference_material-list/000002490.md).

# Troubleshooting Focus Camera (FTM) system check failure on the NovaSeq 6000

A Focus Camera failure during the NovaSeq 6000 system checks can be caused by a transient instrument communication issue or it can be indicative of an instrument hardware issue.

**Troubleshooting steps:**

1. Perform a power cycle on the instrument.
   1. For more information on power cycling, follow the guidance in the Knowledge Base article[How to Power Cycle the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000002470.md)?
   2. **Note**: Focus Camera test on system check will fail if it is performed immediately after a run failure. Power cycling the instrument is **required** to reset communication pathways.
2. Repeat the system check after the power cycle. Select only **Motion and Optics tests** > **Focus camera**. For additional details, search for Knowledge Base article [How to perform system checks on the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-reference_material-list/000002495.md)?
3. Contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html) if the Focus Camera test fails after the power cycle.

\
\
\ <br>

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