> 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/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001528.md).

# How to generate RFID bypass codes for the MiSeq

**Background**

MiSeq reagents are equipped with a radio-frequency identification (RFID) tag to enable accurate consumable tracking. Independent tracking of the flow cell, reagent cartridge, and PR2 bottle occurs at the beginning of the sequencing run, when sensors at these three positions read and write to the RFID. If the RFID fails to be detected, a run can be started using a bypass code created by the MiSeq Self-Service tool available through your MyIllumina account.

For detailed instructions, watch the

{% embed url="<https://www.youtube.com/watch?v=_8Fyi6fHC14&ab_channel=Illumina>" %}

in MyIllumina on the Illumina YouTube channel.

To generate the code:

1. Log in to [MyIllumina](https://dashboard.my.illumina.com/).
2. Select the **Tools** dropdown from the top bar, then select **MiSeq Self-Service**.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-c062cb97a05a85e338a05600a40634dcef4b6e7b%2Fimage1.jpg?alt=media\&token=1be437f8-e8ca-4c43-b08a-2ffe5c44a303)
3. Enter the serial number of the instrument (format: M#####).
4. Select **Request Code**. The code populates near the top in a green banner.\
   ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-949b8e57f452e77f1ee755d9edf9e3eec0ed0486%2Fimage2.jpg?alt=media\&token=0d7e1c16-e1c0-4b5b-ba48-0bb3e5294b5f)

The bypass code is entered directly into MiSeq Control Software and is valid for 7 days. Follow the prompts to enter the barcode and part number for the consumable. The location of this information on the reagent label is outlined below. The barcode number is highlighted in blue and the part number in yellow.

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

Multiple RFID failures for the same consumable type could indicate a faulty sensor.

For persistent issues, email Illumina Technical Support at <techsupport@illumina.com>.

\
\
\ <br>

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