> 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/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000001383.md).

# Troubleshooting flow cell registration failed to find fiducial on the NextSeq 500/550

This notification indicates a fiducial was not found during flow cell registration. The fiducial measures a baseline X and Y distance between each of the cameras relative to camera 2. It is designed to detect gross misalignment between cameras. The XY registration test is performed to find the fiducial on the flow cell, which occurs before the run starts during the pre-run checks. The cameras do not reference the fiducial during sequencing runs, and a failing XY registration test does not correlate to a run failure.

Fiducials do not require clustering for detection the NextSeq 500/550. These notifications do not affect run performance and are transient communication issues. The NextSeq 500/550 flow cell has 6 fiducials and the instrument requires reading of 1 to start the run.

**Example notification in NextSeq 500/550 Control Software**

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-b3fd9c3d77d745986918a6376d49cd22c02ec36b%2Fimage1.png?alt=media\&token=1c89d610-75e5-4535-9e51-18f54ebe75d9)

**Troubleshooting steps:**

1. Allow the run to start.
2. After the run completes, confirm run performance was not affected by the error.
3. Power cycle\* NextSeq 500/550.
4. If the system initializes without issue, proceed with the next sequencing run.

\*For further information, see [How to Power Cycle the NextSeq 500/550](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001972.md).

\
\
\ <br>

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