> 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/microarray/general/microarray-general-troubleshooting-list/000005236.md).
# How to configure the NextSeq 550 for BeadArray Scanning
Scanning CytoSNP, MethylationEPIC, or Karyomap\* BeadChips on the NextSeq 550 requires configuring the settings in the NextSeq Control Software (NCS):
1. Open the NCS
2. From the NCS Home Screen navigate to **Manage Instrument** → **System Configuration** → **BeadChip Scan Configuration** (Figure 1)
3. In the BeadChip Scan Configuration, complete the required fields (Figure 2):
* **dMap Location:** Browse to the location where the dMaps for the BeadChips are stored
* **Output Location:** Browse to the location where the BeadChip scan folder will be stored
* **Saved Image Type:** Select among **jpeg,png** and **tiff**
* **Output File Type:** two options, **gtc only**, **gtc and idat**\
**Note:** default is gtc only, it is recommended to select **gtc and idat**.gtcs are required for analysis of CytoSNP-850K in BlueFuse Multi. MethylationEPIC BeadChips will only generate idat files as they are not for genotyping.
4. Click **Save** to proceed to the next screen for Scan File Configuration (Figure 3)
* The BeadChips that can be scanned on the NextSeq 550 will be listed on this screen. If the beadchip of your interest is not in the list please check with illumina Technical Support
* For each BeadChip type and version, browse to the location of the Manifest and Cluster file
* Once completed, click **Save**
**Figure 1:** Navigating to the BeadChip Scan Configuration Settings on the NextSeq 550
**Figure 2:** Setting the BeadChip Scan Configurations on the NextSeq 550
**Figure 3:** Scan File Configuration on the NextSeq 550
**Note:** For further reference, consult the Scan Setup section from the [NextSeq 550 Sequencing System Guide](https://support.illumina.com/downloads/nextseq-500-550-systems-product-documentation.html).\
\*Karyomap v2 BeadChips are sold and supported by Vitrolife
**Additional information:**\
[Which Infinium BeadChip types can be scanned using the NextSeq 550?](https://knowledge.illumina.com/microarray/general/microarray-general-faq-list/000003871)
\
\
\
| |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5236), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005236%20-%20Microarray%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/microarray/general/microarray-general-troubleshooting-list/000005236.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.