> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/t30-readers-restart-several-times-after-a-reset-with-mobile-wallet-enabled.md).

# T30 readers restart several times after a reset with Mobile Wallet enabled

Stop T30 readers on a Controller 6000 restarting several times after a reset override when Mobile Wallet is enabled.

**Applies to:** T30 firmware v4.80.24, v4.70.20 · Command Centre vEL9.20.1420+

With the **Mobile Wallet** feature enabled (Server Properties, Card Security), T30 readers connected to a **C6000** controller may restart several times after a reset override is sent. Two to three restarts are typical; up to nine have been seen.

It does not need a downgrade or upgrade to reproduce: enabling Mobile Wallet and sending a reset override to the T30 reader is enough.

![Server Properties, Card Security: Permitted Card Technology with Mobile Wallet ticked and highlighted (the crypt seed value is covered; the key fields are blurred in the source)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-10444ebf3292bdfd2313a2054e08cc475e403466%2FSECHUB-TS-T30-ISSUES-01-mobile-wallet-card-security.png?alt=media)

### Workaround

Untick **Mobile Wallet** before sending the reset override. The extra restarts then do not happen.

{% hint style="info" %}
As of 2025-04-23: until a formal patch or update is provided, disable Mobile Wallet with the affected configurations or features. The development team is aware of the issues and investigating a long-term solution.
{% endhint %}


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/t30-readers-restart-several-times-after-a-reset-with-mobile-wallet-enabled.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.
