> 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/library-preparation/dna-enrichment-based-library-prep/library-preparation-dna-enrichment-based-library-prep-faq-list/000009492.md).

# Sequencing FAQ for Illumina FFPE DNA Prep with Exome 2.5 Enrichment

**Which instruments does Illumina support for sequencing?**

* NovaSeq X series : 1.5B
* NovaSeq 6000: SP, S1, and S2
* NextSeq 2000: P3 and P4 (XLEAP)

**What is the recommended number of samples per run?**

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-f18eb673096c22681f0d400803b763ac6107167c%2Fimage1.png?alt=media)

Similar information can also be found in the [Denature and Dilute Protocol Generator](https://support-docs.illumina.com/IN/dnd-wizard/Content/dnd/landing.htm). \*\*What is the targeted reads per sample to achieve 150X normal/500X tumor. Is it 28M reads to normal and \~72M reads to tumor? (M = million)\*\*28M for Normal, and \~100M for Tumor single-end reads.

\*\*Is PhiX spike in recommended?\*\*Spike-in of PhiX is not required. However, customers can follow the general guidelines of spiking in 1-2% PhiX for additional sequencing metrics, if desired.

\*\*What is the recommended read length?\*\*2x151 with 10 bp indexes.

**What is the recommended loading concentration for all supported Illumina Platforms?**

* Note: users may need to optimize loading concentrations, though the following can be used as a general starting point:
* NextSeq 2000: 750 pM
* NovaSeq 6000 (SP, S1, S2): 500 pM (0.5 nM) pooled library concentration; 100 pM final library concentration. Must use Standard loading so one pool goes into both lanes to achieve sequencing depth requirements
* NovaSeq X series (1.5B only): 40 pM final loading concentration. One pool goes into both lanes to achieve sequencing depth requirements

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                              |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #9492), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000009492%20-%20Library%20Preparation%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/library-preparation/dna-enrichment-based-library-prep/library-preparation-dna-enrichment-based-library-prep-faq-list/000009492.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.
