> 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/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000001269.md).

# Troubleshooting NovaSeq 6000 optical alignment errors, BIRD warnings, and Objective Contamination

**Background**

The NovaSeq 6000 intensities are baselined at the BIRD (Built-in Remote Diagnostics) during installation to a specific intensity count for both red and green lasers. The BIRD is the onboard laser target and part of the DAD (Dual Actuation Deck).

Before each run, the NovaSeq Control Software checks the BIRD intensity readings and compares them to the baseline. This test is used to monitor a decrease in performance due to objective contamination.

If the pre-run check falls below 20% from the baseline, the following warning may appear.

**Warning:** The onboard optical alignment target indicates that maintenance might be required before the next run. The run can continue, but contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for help.\
![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-dd594d66bf6fa2cd40725e4492de5d5b4c20ab9e%2Fimage1.png?alt=media\&token=31902958-82c4-4b11-990c-4c83142839af)

If this warning appears, allow the run to continue, as this warning does not affect run performance impact. Then, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) as an Illumina Engineer visit is required before the next run.

\
\
\ <br>

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