> 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/configuration-client/integrated-systems/aperio-integration/troubleshooting-aperio-integration.md).

# Troubleshooting - Aperio Integration

The following table describes some of the known issues that can occur, and possible causes:

<table><thead><tr><th width="198">Problem</th><th>Possible Causes</th></tr></thead><tbody><tr><td>Bad Packet Alarm</td><td><ul><li><p>The configuration of the Aperio Door in Gallagher doesn't match the configuration of the Aperio reader in the Aperio Programming Application Protocol (PAP).</p><p>For example, it could be that the Aperio reader has been configured to send only the MIFARE CSN, but the Gallagher Controller is expecting Gallagher sector data, or it could be that the cylinder has been configured to send only, Gallagher sector data, but the Gallagher Controller is expecting the MIFARE CSN.</p></li><li><p>The cylinder could be configured to send any portion of bytes from any sector on the card.</p><p>For example, a site using their own MIFARE keys could configure the cylinder manually and might accidentally select the wrong number of bytes, or the wrong offset in the Aperio PAP. The Gallagher Controller will then receive the wrong number of bytes.</p></li></ul></td></tr><tr><td>Lock giving unusual set of flashes after presenting a card</td><td><p>There are multiple possible causes.</p><p>Please consult the <em>Aperio Installation Manual</em> section 5.5 to ascertain which state or issue that the lock flash sequence refers to.</p></td></tr><tr><td>Mobile Connect does not see the Aperio Reader in the Access Door list</td><td><p>Check that the Mobile Connect app is current, with at least 16.03.049 for iOS and 16.03.038 for Android.</p><p>If the Mobile Connect app was upgraded after the Command Centre server, the Cardholders Mobile Credentials state will need to be set to Disabled (manually) and enabled again to resend the Aperio key. This process can be completed with a Bulk Change for multiple cardholders.</p></td></tr></tbody></table>


---

# 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/configuration-client/integrated-systems/aperio-integration/troubleshooting-aperio-integration.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.
