> 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/mobile-connect-reader-ble-calibration.md).

# Calibrate reader Bluetooth range

Set reader Bluetooth transmit power and connection ranges for Mobile Connect access.

The transmit power for a reader is configured in Command Centre. Increasing the transmit power increases the reader's Bluetooth read range.

![BLE Connect Range diagram](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-722cd4c37f01486c07408a5a746b019942327f20%2FSECHUB-MOBILE-BLE-07-ble-connect-range-diagram.png?alt=media)

### Connection modes

* **Auto connect.** The access request is automatically made when the user enters the auto connect field. Configure a low auto connect value to prevent unwanted reads, for example when multiple readers are installed in close proximity.
* **Manual connect.** The user must initiate the access request. The reader name is displayed in the app. Use manual connect for readers located at a distance, for example boom gates or readers away from the door opening.

**Reader identification:** an operator can display the reader's name in the app. If name display is disabled, for example for privacy, a generic identifier incorporating the last five digits of the reader's HBUS serial number is used (for example, Reader: 50030).

### Reference connection distances

Open field, direct line of sight, iPhone 5S / iOS 10.1.1 / Gallagher Mobile Connect 7.60.105:

| Setting                 | T11/T12/T15/T20 — Default | T11/T12/T15 — Maximum | T20 — Maximum |
| ----------------------- | ------------------------- | --------------------- | ------------- |
| Transmit power          | -26 dBm                   | 8 dBm                 | 8 dBm         |
| Auto connect range      | 45 dBm                    | —                     | —             |
| Manual connect range    | 75 dBm                    | 120 dBm               | 120 dBm       |
| Auto connect distance   | 5-15 cm                   | —                     | —             |
| Manual connect distance | 2-3 m                     | 55 m                  | 40 m          |

### Calibrate reader Bluetooth range

You need an operator with privileges to adjust reader settings in Command Centre, and a user to read the dB and RSSI values on the Reader Calibration screen in the app.

Notes before you start:

* The calibration distances are approximate and will have a greater margin of error the farther you are from the reader.
* Access cannot be requested when the Reader Calibration screen is shown.
* Bluetooth must be enabled in the reader's properties in Command Centre before starting.

1. In the Mobile Connect app, go to Settings and select **Reader Calibration**. Nearby readers will be displayed.
2. Stand where you'd like your **maximum manual connect distance** to be.
3. In Command Centre (Bluetooth settings tab in the Configuration Client), adjust the **Transmit Power** value until the RSSI reading on the app is near **-85**.
4. Set the **path loss (dB) value** shown on the app as your **manual connect range**. The higher the value, the less accurate the connect range will be.
5. Move to stand where you'd like your **auto connect distance** to be.
6. Set the new **path loss (dB) value** shown on the app as your **auto connect range**.

![BLE calibration step 1a](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2b4d802bcd83b087ca042c856d347bf7c5800f8d%2FSECHUB-MOBILE-BLE-01a-ble-calibration-01a.png?alt=media)

![BLE calibration step 1b](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e38da667e92876be091508dc8ee69ae157c59e76%2FSECHUB-MOBILE-BLE-01b-ble-calibration-01b.png?alt=media)

![BLE calibration step 2](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0deb7bab5a7a60c57aa9a6ae3d1b3d6eb6082c6e%2FSECHUB-MOBILE-BLE-02-ble-calibration-02.png?alt=media)

![BLE calibration step 3](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0af2820975a6aa293b660ccf9599ebe7880c4bd4%2FSECHUB-MOBILE-BLE-03-ble-calibration-03.png?alt=media)

![BLE calibration step 4](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b1344faa0194f4ad40be77baad1f894e5f949241%2FSECHUB-MOBILE-BLE-04-ble-calibration-04.png?alt=media)

![BLE calibration step 5](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3d3eefdf3be7faaf94dd373e471671364ba189ae%2FSECHUB-MOBILE-BLE-05-ble-calibration-05.png?alt=media)

![BLE calibration step 6](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b217b6f2b77bdd98c26a3a11d79100761f50c9bc%2FSECHUB-MOBILE-BLE-06-ble-calibration-06.png?alt=media)

### Troubleshooting

| Issue                                                                             | Analysis / Resolution                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Delayed access                                                                    | Users must request access one at a time. Multiple users cannot connect to the same reader simultaneously. A back-off timer ignores subsequent access requests for approximately 5 seconds after each transaction.                                                                                                                                                                                                                                                                                   |
| Only one Registration Service per site (per license serial number) can be created | If moving Command Centre servers, delete the old Registration Service item before creating a new one. If not done, Gallagher Technical Support must re-establish the connection between Command Centre and the Registration Service in the cloud.                                                                                                                                                                                                                                                   |
| Variable connection distances                                                     | The greater the connect range, the more likely there will be variation in read range experienced. The Reader Calibration screen pathloss values are averaged (the reader sends 20 advertisements per second; Gallagher samples these, removes the highest and lowest, and averages the remainder). Absolute path loss values fluctuate, so users may experience some variation in auto connect read range, and readers may appear and disappear at the edge of the configured manual connect range. |

***

🔗 **Related**

* [06. Autoconnect not working for some phones](/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-06-autoconnect-not-work.md). When some phones will not auto connect.
* [04. Apple Pay coming up when presenting iPhone to reader](/knowledge-hub/products/cc-hardware/credentials/mobile-connect/troubleshoot/mobile-connect-04-apple-pay-coming-up.md). When the auto connect range is too tight.


---

# 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/mobile-connect-reader-ble-calibration.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.