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

# Troubleshooting Cavro Pump Error on MiSeq

A MiSeq Cavro Pump error can result from an instrument hardware issue or software communication issue on the MiSeq. Potential hardware-related causes include pump, pump controller, or syringe failure.

**Error**: Cavro pump error: Volume will exceed syringe capcity.Error in LanePump. Invalid argument. Command = '1V400IP1500R\r', reply = 'c'\
![](/files/L02i94o9y7UklzBqPiZL)

**Troubleshooting Steps**:

1. Power cycle the MiSeq.
   1. For power cycling guidance, see [How to Power Cycle the MiSeq](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md) or [How To Power Cycle the MiSeq Video](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005871.md).
   2. **Note**: If a run is in progress, it will **NOT** be able to be resumed.
2. Perform a post-run wash to ensure fluidics are operating normally.
   * For more information, see [Best Practices for Washes on the MiSeq.](/instrumentation/general/instrumentation-general-reference_material-list/000001679.md)
   * Optionally, perform a volume test within the MiSeq System Check. For more information, see [How to perform a System Check on the MiSeq](/instrumentation/miniseq/instrumentation-miniseq-reference_material-list/000001777.md).
3. If post-run wash or volume test is successful, proceed with next run.
4. If the instrument fails to initialize or there is an error during the post-run wash, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/) for further assistance.

**Note:** If a Lane pump error does not include the Cavro pump error, refer to article [Troubleshooting Lane Pump Errors on the MiSeq.](/instrumentation/general/instrumentation-general-troubleshooting-list/000001446.md)

\
\
\ <br>

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.illumina.com/instrumentation/miseq-ruo/instrumentation-miseq-ruo-troubleshooting-list/000001454.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.