> 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/general/instrumentation-general-troubleshooting-list/000001446.md).
# Troubleshooting Lane Pump Errors on the MiSeq
**Background**
The following error messages can occur if the pump that pulls reagents through the MiSeq fluidics system does not respond to commands sent by the MiSeq Control Software.
This error may result from hardware or communication errors on the MiSeq. Potential hardware-related causes include pump, pump controller, or syringe failure. In some cases, this is a temporary situation that requires no action. Note that an error mentioning the “Cavro” pump is a different issue, see Knowledge Article [Troubleshooting Cavro Pump Error on MiSeq](https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000001454) for details.
**Figure 1:** Error in LanePump. Syringe pump valve failed to move: Valve overload. Command = '/1Q\r', reply = 'j'
**Troubleshooting Actions**
1. Power cycle the MiSeq instrument.
1. See Knowledge Article [How to shut down or power cycle the MiSeq](https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-reference_material-list/000001894) for details.
2. If MiSeq Control Software initializes as expected, perform **ONE** of the following options:
* Option 1: Perform a System Check
* See Knowledge Article [How to Perform a System Check on the MiSeq](https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-reference_material-list/000001777/?utm_source=agent\&utm_medium=email\&utm_campaign=kb) for details.
* If the system check passes, users may setup the next run on the instrument and continue normal operation.
* Option 2: Perform a maintenance wash and measure the waste output to ensure the fluidics system is operating normally. The maintenance wash is expected to output 51.75 ml +/- 10% wash volume waste.
* See Knowledge Article [Wash best practices for the MiSeq](https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-reference_material-list/000001679) for details.
* If the maintenance wash successfully completes and returns the appropriate amount of waste, users may set up the next run on the instrument and continue normal operation.
3. If the lane pump error is not resolved by power cycling or persists in the System Checks or Maintenance wash, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/) for further assistance.
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #1446), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001446%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/general/instrumentation-general-troubleshooting-list/000001446.md?ask=&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.