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

# Troubleshooting "Camera exception, error= 360: Failed to perform sBCa" error on the MiSeq

The "Camera exception, error=-360: Failed to perform sBCa\_LibraryReinitialize(60000) call." error during a MiSeq sequencing run could indicate a transient communication issue between the hardware and software.

![](/files/3dWYBRqk6ZqHX1r4gq82)

**Troubleshooting steps**:

1. Contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) (<techsupport@illumina.com>) and provide the information from the section below titled **Information to Provide to Illumina Technical Support** prior to troubleshooting.
2. Complete the post-run wash.
3. Power cycle the MiSeq (note that if a run is in progress, it will not be able to be resumed).
   1. Review the Knowledge Base article [How to Power Cycle the MiSeq](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md) for detailed instructions.
   2. Leave the instrument off for 5 minutes to allow all parts to completely power down.
   3. Turn on the instrument using the power switch on the back panel. The control software will initialize on its own once Windows fully loads.
4. If the control software fails to initialize, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support).
5. If the instrument initializes without error, proceed with the next run.

**Information to provide to Illumina Technical Support:**

1. System uptime: Minimize the Control Software, search for "Task Master" in the Windows menu and open Task Master. Move to the "Performance" tab to see the the system uptime.
2. Software uptime: In the MiSeq Control Softawere (MCS), select **About** and note the Software uptime.
3. MCS version: Available on the MiSeq Control Software About screen.
4. FPGA version: Available on the 'iSeq Control Software About screen.
5. MiSeq Control Software logs: D:\Illumina\MiSeq Control Software\Logs
6. Run cycle logs, if error occurred during a sequencing run: D:\Illumina\MiSeqTemp\[run folder]\Logs folder
7. Run type, if applicable, when the error happened: Chemistry version and length of the run.

* example: v2 500 cycle kit, 251 x 8 x 8 x 251

8. Instrument usage rate: On average, how many runs were performed in the last month?

\
\
\ <br>

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