> 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-software/configure/alarm-transmission/alarm-transmission-connecting-a-contro.md).

# Permaconn diallers

Connect and configure Permaconn diallers with Gallagher controllers.

A Permaconn dialler connects directly to the serial port of a controller and **acts as an analog dialler**. Configure it as a standard dialler and add the **`atX0`** command (as in the Analog Dialler section), then wire it per the diagram.

Configuration of the Permaconn dialler itself is up to the Channel Partner / monitoring facility.

![Permaconn to Gallagher panel wiring](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-9a41a6ed344238503d3baa1fdda76881d50c27a7%2FSECHUB-CCS-ALARM-permaconn-01-wiring-diagram.jpg?alt=media)

> **Verify with Permaconn that the serial wiring is correct.** There are many Permaconn dialler models, and wiring differs between them.

***

### Permaconn PM1048 v3 (3G/4G) and PM54

These models provide serial data communication via RS232 between the Gallagher panel's **RX** and **TX** terminals.

* Set up Gallagher dialler commands as normal in Command Centre. The PM1048 and PM54 **emulate** the Gallagher dialler.
* Enable **Periodic Dial Tone** and set it to check **every one minute**.
* Set **Redial Attempts** to the maximum of **99 times**.

The PM1048 and PM54 should come with their own RS232 connection cable.

![Periodic dial tone setting](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3a4cd56e94c740b0c98c64cdbf32f8b7e1b8d4e0%2FSECHUB-CCS-ALARM-permaconn-02-periodic-dial-tone.jpg?alt=media)

![Redial attempts set to 99](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-aa985b7f1d2c38a262b347f28911914b4b6d8c13%2FSECHUB-CCS-ALARM-permaconn-03-redial-attempts.jpg?alt=media)

***

### Permaconn PM 45 4G

The PM 45 4G requires a **firmware update** and the **RX and TX connections reversed** on the Permaconn before the unit communicates correctly.

If the dialler does not respond as expected in the **Status and Overrides** dialog, investigate:

1. The wiring connecting the 6000 and the Permaconn unit is not correct.
2. Contact the Technical Support site for the facility that supplied the Permaconn unit.


---

# 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-software/configure/alarm-transmission/alarm-transmission-connecting-a-contro.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.