> 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/general/library-preparation-general-reference_material-list/000002045.md).

# Illumina DNA/RNA Unique Dual (UD) Index Compatibility on the MiniSeq

Illumina DNA/RNA Unique Dual (UD) Indexes are 10 bp each.

Currently the MiniSeq Reagent Cartridges are not able to complete dual 10 bp index reads without also reducing the insert read lengths to compensate for the additional index cycles.

(For the maximum number of cycles that can be configured for each reagent kit, refer to [How many cycles of SBS chemistry are in my kit?](/instrumentation/general/instrumentation-general-reference_material-list/000007002.md))

* In order to sequence the dual 10 bp indexes on the MiniSeq with a 300-cycle kit, set up the run with four fewer sequencing cycles, either 151+10+10+147 or 149+10+10+149.
* For FASTQ generation on Local Run Manager (LRM), use the definition files for the index kits to create a custom library prep kit if they are not included in the version of Local Run Manager being used. Refer to the following guide for instructions: [How to use a custom library prep kit in Local Run Manager v2](/software/local-run-manager/software-local-run-manager-reference_material-list/000001317.md).
  * Definition files for Illumina DNA/RNA UD Indexes (v3) can be found [here](https://support.illumina.com/downloads/illumina-dna-rna-udi-lrm-v2-lp-kit-files.html).
  * Definition files for IDT for Illumina DNA/RNA UD Indexes (v2) can be found [here](https://support.illumina.com/sequencing/uniquedualindex.html) (note: these index kits are obsolete and no longer sold).

\
\
\ <br>

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