> 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-faq-list/000009708.md).

# Can a Tecan/IAPS mock run be completed while the instrument is connected to Illumina LIMS?

The purpose of a Tecan mock run is to rule out any potential issues with the Tecan/Illumina Automated Pipetting System (IAPS) robot, the water circulator, the computer, and the Illumina Automation Control (IAC) software/Illumina Lab Automation Solution Software (ILASS).

Mock runs are typically performed while the Tecan is disconnected from the Illumina Laboratory Information Management System (LIMS) so that the run does not get logged into the system.

Illumina LIMS primarily records workflow transactions and does not directly control the operation of the Tecan software. Its presence or absence does not affect the components and functions that a mock run is intended to verify.

Mock runs can be completed while connected to Illumina LIMS, however, the software will require the BeadChip and reagent barcode information to initiate the run. Any BeadChip barcodes used for this purpose must correspond to a valid, accessioned BeadChip recognized by Illumina LIMS. If the BeadChip had been previously processed, the new scan would overwrite the existing data. To avoid this, use BeadChip barcodes that have not previously been used in Illumina LIMS.

If a mock run finishes successfully without errors, even while the Tecan is disconnected from Illumina LIMS, this means that the Tecan hardware and control software are functioning as expected.

**References:**

* [Illumina LIMS Documentation](https://support.illumina.com/array/array_software/illumina_lims/documentation.html)
* [Infinium RoMA (IAPS with ILASS) User Guide](https://support-docs.illumina.com/RT/IAPS/Content/RT/FrontPages/IAPS.htm)
* [Infinium Automated Pipetting System with Illumina Automation Control](https://support-docs.illumina.com/ARR/InfLabSetup/Content/ARR/SetupandProcedures/IAPS_IAC_Usage_fINF.htm)

\
\
\ <br>

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