> 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/cloud-services/command-centre-mobile-client/configure/mobile-client-enabling-mobile-reader-u.md).

# Enable Mobile Reader with Mobile Client

Configure and operate the legacy Mobile Reader with the Command Centre Mobile Client.

{% hint style="warning" %}
⚠️ **The Mobile Reader hardware below is obsolete and no longer available from August 2026.** It is retained for support of existing deployments only. Do not specify it in new BOMs.
{% endhint %}

The Mobile Client must be configured and working before the Mobile Reader will function.

**Enable the reader for a device:** Command Centre Client → Administration → Mobile Devices → select the device the reader connects to → check **Enable Mobile Access Reader**.

**Enable access zones in the reader:** Command Centre Client → Administration → Mobile Devices → **System Settings** (above devices) → **Access Reader** → add the access zone(s).

**Enable cardholder data in the reader:** Command Centre Client → Administration → Mobile Devices → **System Settings** → **Cardholders** → add the Photo PDF to display.

![Mobile Devices → System Settings → Cardholders tab - configuring the cardholder data and Photo PDF shown on the reader](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c7f83f5c7333f4b745526f8075794204babf6094%2FSECHUB-cc-mobile-client-mobile-reader-enable.png?alt=media)

## Using the Mobile Reader

Two reader models are available for iOS devices: **C861300** and **C861301**. Both read 125 kHz, MIFARE Classic, Plus and DESFire **Gallagher-encoded** cards (not third-party encoded), and **neither is available in North America**.

* **C861300** - case or sleeve form factor (see image below).
* **C861301** - Q-series form factor; the iPhone docks into the reader (see image below).

**Power (C861300):** must be charged to function. It does **not** draw power from the connected device. Charging takes up to **8 hours** from flat.

**Lights:**

* Bottom-right: Red = trying to read; Blue = reading; double Red flash = connecting; single Blue flash = connected.
* Left side: press the button below the lights for charge level. 5 green LEDs = full, none = flat. When plugged in, a flashing LED shows the current charge point.

**Buttons:** two buttons about halfway up each side. When connected to the device and logged into the server, press both together to activate the reader and prompt for a card.

**Reading a card:** press the side buttons together, or use the read-card icon at the bottom of the Cardholder screen.

## Using the Grabba Browser to collect data

The Grabba hardware manufacturer publishes **Grabba Browser** on the Apple App Store. Run it while plugged into the Grabba hardware to read the device's Serial, Hardware version, Firmware version and Driver version. Firmware updates come from either Grabba Browser or Gallagher Mobile Command Centre. If in doubt, run Grabba Browser and it will update the firmware.

![Grabba Browser app icon on the Apple App Store](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-911a2e8d67cea2756f87cc992dedab9907dd0306%2FSECHUB-cc-mobile-client-grabba-software-icon.jpg?alt=media)

![Grabba Browser showing the device hardware and firmware information](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c9b29a56acc36c2a03435c5976ac8ae2a60bdb5a%2FSECHUB-cc-mobile-client-grabba-hardware-firmware.jpg?alt=media)


---

# 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/cloud-services/command-centre-mobile-client/configure/mobile-client-enabling-mobile-reader-u.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.