> 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-reference_material-list/000009870.md).
# Ordering the HD/LCG/HTS Multi-Sample Alignment Fixture vs XT/EX Flow-through Chamber Assembly Tray
The Infinium Multi-sample Alignment Fixture and the XT Flow-through Chamber Assembly Tray both serve the same function for their respective Infinium workflows--to provide a place to align and assemble the components required for the Teflow flow-through chambers used in the xstain process of the Infinium assay. Both consist of
* a rectangular buffer tray, so that the components can be assembled under buffer.
* raised beds, flanked by vertical rectangular posts, on and between which the flow chambers are assembled.
However, there are key differences to accommodate the different hardware used in assembly of the flow chambers.
The Infinium Multi-sample Alignment Fixture (catalog number WG-15-310) is used with HD, LCG, and HTS beadchips and workflows.
There are raised beds to assemble 4 flow chambers. The proper assembly requires the use of a spacer bar, because the glass backplates used in forming the flow chamber are shorter than the beadchips, and proper positioning of the glass backplate relative to the beadchip during assembly requires the bar.
The XT Flow-through Chamber Assembly Tray, (catalog number 20011760), is used with the Infinium XT and Infinium EX workflows.
The tray has space for assembly of up to 6 flow chambers at a time. The tray does not include a spacer bar, because the glass backplate is the same length as the beadchip, so aligning the beadchip and glass backplate is as simple as placing them between the vertical raised rectangular bars at the ends of the beds. The lack of a spacer bar makes this tray inappropriate for assembly of the HD/LCG/HTS flow chambers.
\
\
\
| |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #9870), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000009870%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 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/microarray/general/microarray-general-reference_material-list/000009870.md?ask=&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.