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

# Troubleshooting RheodyneValve error on NextSeq 500/550

The following error on the NextSeq 500/550 may indicate an issue with the sippers controlled by the valves. Rheodyne valve failure is uncommon, and this error is typically caused by a transient communication error.

**Error in Fluidics.FlowCellFluidics1.LanePump.IxPassThroughRheodyneValve1: Reinit while recovering from error””. Originally caused by” Timeout waiting 60000ms within EventToBclockingConverter.WaitForData().**

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-439ea0058deb150b9f75e5805fd22b9b4c17989e%2Fimage1.png?alt=media\&token=8d18fa80-28bb-4122-9d72-0fb9ba3e594d)

**Troubleshooting steps:**

1. Power cycle the NextSeq 500/550, following the instructions in [How to Power Cycle the NextSeq 500/550](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001972.md).
2. From the System Checks, perform **ONLY** 'Valve Response Test'.
   * Select **Manage Instrument** > select **System Check**.
   * For further guidance on System Checks, follow [How to perform a NextSeq 500/550 system check](https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000001883.md).
3. Perform a manual quick wash for further testing.
   * For further guidance, see [How to perform washes on the NextSeq 500/550](https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-reference_material-list/000003076.md).
   * If the error does not recur, the instrument is clear for use.
   * If the error comes back during initialization, system check or during the wash, contact [Illumina Technical Support.](https://www.illumina.com/company/contact-us.html#/)

\
\
\ <br>

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