> 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/instrumentation-miseq-troubleshooting-list/000007442.md).
# Troubleshooting "Initialize Cameras before capturing images" error on the MiSeq
Users may encounter an "Initialize Cameras before capturing images" error message during the first cycle of a MiSeq run. This error may occur if the previous run on the instrument ended early due to a communications error that caused the cameras to shut down.
An example of this type of error is an FPGA error; see more in the Knowledge Base article[Troubleshooting FPGA Timeout Errors on the MiSeq](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-troubleshooting-list/000001444.md). If the user did not power cycle after such an error, this can cause an "Initialize Cameras before capturing images" error to occur.
**Note**: This error may cause a cycle 1 failure and mark consumables as "used". If this is the case, please contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for assistance.
**Troubleshooting steps:**
* **Power cycle** the instrument in order to re-initialize the cameras.
* For further information, see the Knowledge Base articles [How to Power Cycle the MiSeq](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md) and [How To Power Cycle the MiSeq Video](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005871.md).
* Check D:\ **drive space**. If an earlier run prematurely terminated, there may be old files taking up space in the old **MiSeqTemp** and **MiSeqAnalysis** run folder locations:
* D:\Illumina\MiSeqTemp\<old run folder> and D:\Illumina\MiSeqAnalysis\<old run folder>
* Delete older data from any prematurely terminated runs.
* Additionally, detele any older run folders present from completed runs. Ensure they are backed up off-instrument before being deleted.
* For further information, review the Knowledge Base articles [Run folder sizes and Disk Space on the MiSeq](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000006711.md) and [Troubleshooting Free Disk Space errors during Pre-run Checks on MiSeq](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-troubleshooting-list/000003753.md)
If the instrument fails to initialize or the error persists, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support).
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7442), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007442%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/instrumentation-miseq-troubleshooting-list/000007442.md?ask=&goal=
```
`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.