> 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-troubleshooting-list/000001297.md).

# Troubleshooting NovaSeq 6000 reagent RFID failures

**Background**: NovaSeq 6000 consumables are labeled with Radio-frequency identification (RFID) tags that the instrument uses to identify them. Occasionally a run setup error can occur where the instrument is unable to read the RFID from the loaded consumable. This article describes how to troubleshoot this error.

**To troubleshoot a cartridge RFID failure:**

* Load a previously used consumable.
  * If the used consumable is detected as previously used, the sensor is working as expected. In that case, load new reagent/buffer cartridge and contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for further assistance. Provide the cartridge product number, lot number, and serial number to Illumina Technical Support.
  * If the used consumable replicates the "RFID cannot be read" error, the sensor may be offline. If the instrument is idle on the other side, perform a power cycle\*. Once the instrument initializes:\
    \- Retry the pre-run check with the same used cartridge to check if the sensor is online.\
    \- If the used cartridge is now detected as "used," load the original cartridge and start the pre-run check again.\
    \- If the error persists after trying a used consumable and power cycling the instrument, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for the next steps.

\*For further information, see Knowledge Base article [How to Power Cycle the NovaSeq 6000.](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-reference_material-list/000002470)

**To troubleshoot a**flow cel**l RFID failure:**

* Inspect flow cell visually to identify any debris or glass shards on the surface and underside.
  * If debris or glass shards are present:\
    \- Clean the bottom of the flow cell and flow cell stage with an alcohol wipe. Pat dry excess alcohol with a lint-free wipe. Make sure only to clean the glass surface of the flow cell.\
    \- Inspect the flow cell mount for debris or shards. Attempt to clean this area like the flow cell, avoiding pushing any debris into the vacuum holes on the mount\
    \- Retry the pre-run check after performing the above steps with the same flow cell.\
    \- If the pre-run check fails again with the same error, try setting up the run with a new flow cell. Contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for further assistance. Provide flow cell product number, lot number, and serial number.
  * If debris or glass shards are not present:\
    \- Exit out of run setup and from the control software and [power cycle the instrument.](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-reference_material-list/000002470)\
    \- Launch the NovaSeq Control Software (NVCS) and retry run setup\
    \- If error persists with the original flow cell, attempt the cleaning procedure above and then retry run setup with the original flow cell\
    \- If the error persists, try a new flow cell. If the run starts with a new flow cell, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for further assistance.\
    \- If the error persists with a newflow cell, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for assistance.

\
\
\ <br>

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