> 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/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000006373.md).

# Troubleshooting pre-run checks with Temperature sensor check failed: Board 0/1 on NextSeq 500/550

In rare instances, it is possible for the NextSeq 500/550 to fail to successfully complete the pre-run check with a "Temperature sensor check failed: Originally caused by: Temperature is out of range for Board 0 and/or Board 1 Temperature Probe" error message.

The Main Board (MPCA) assists with connecting the onboard computer with the instrument hardware and includes two temperature sensors integrated into the MPCA. This error may display as a result of a communication error, or potentially a defective sensor.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-d29490e51d801bfc633e784441293db4c361aa64%2Fimage1.jpg?alt=media)

**Troubleshooting steps:**

1. Power cycle the NextSeq 500/550.
   * Search Knowledge Base Article **How to Perform a NextSeq 500/550 Power Cycle**.
2. Repeat the run setup.
3. If error returns after a power cycle, or returns on subsequent run setup, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for additional assistance.

\
\
\ <br>

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