> 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-reference_material-list/000002420.md).

# NovaSeq 6000 library tube information

The NovaSeq 6000 library tube is a tube within a tube, where the internal tube is sloped and the bottom less deep shorter than the external tube dimensions

* Library tube box dimensions: 5" x 1.6" x 1"
* Library tube internal depth: \~58mm
* Library tube width: \~16mm
* The tube fits into position #8 of the cluster cartridge.
* Position #8 is labeled Library Tube and circled in orange for easy identification.
* The tube has a threaded cap that allows storage of libraries when necessary. Make sure that the cap has been removed before loading into the cluster cartridge.

The library tube is used one of two ways, depending on workflow.

1. Standard
   * Pooled and denatured libraries are added to the library tube, which is then loaded uncapped into the cluster cartridge.
   * After the run begins, the instrument mixes the libraries with ExAmp reagents in the library tube, which are then transferred automatically to the flow cell.
2. NovaSeq Xp
   * The empty, uncapped library tube is loaded into the cluster cartridge.
   * During the run, reagents are mixed in the library tube before distribution to the flow cell.
   * The library tube has a RFID chip on bottom and must be present for Xp workflow to start a run, even though the library tube is empty.

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

* Library tube serial number for RUO NovaSeq 6000 instruments will start with NV followed by 7 numbers and end with -LIB.

\
\
\ <br>

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