Alarm transmitters

Alarm transmitter hardware

For New Zealand and Australia sites, the Permaconn PM54 is the available alarm transmitter. For North American sites, the Alula BAT-Connect is available.

NZ/AUS: Permaconn PM54 The Permaconn PM54 can also function as an alarm communicator, transmitting alarms from the Gallagher SMB Controller to a monitoring station using the Contact ID alarms transmission protocol. The Permaconn PM54 is powered by the Gallagher SMB Kit and provides connection to the site's WAN or Wi-Fi.

North America: Alula BAT-Connect The Alula BAT-Connect is an alarm communicator, transmitting alarms from the Gallagher SMB Controller to a monitoring station using the Contact ID alarms transmission protocol. The Alula BAT-Connect is powered by the Gallagher SMB Kit and provides connection to the site's WAN, cellular, or Wi-Fi.

Configuring an alarm transmitter

If the customer requires third-party monitoring, configure the alarm transmitter.

  1. In the SMB Installer Portal, click the MONITORING tab.

  2. Enter the Account Code received from the monitoring station and click SAVE.

    The Alarm Transmitter item displays.

  3. Enable the toggle next to the Alarm Transmitter.

    Note: If you are also enabling the IP Alarm Transmitter, select which transmitter is the primary one from the Primary option (next to the 'Account Code' field).

  4. Click on the Alarm Transmitter to open its properties. The Alarm Transmitter lightbox displays.

  5. Enter the transmitter device's serial number or MAC address (this is an optional field).

  6. To enable periodic dialling tests, enable the Periodic Dialling toggle.

  7. To set the frequency of dialling tests, select either Dial daily at or Dial every.

    • Dial daily at: Select this option to have a periodic dial occur at the same specified time each day. Consider selecting a unique time for each site so the load on monitoring stations is spread throughout the day. If you change the periodic dial time, notify the monitoring station of the new test time. The time will automatically adjust for daylight savings.

    • Dial every: Select this option if you require more frequent periodic test dials. This means that a test dial will occur at the interval specified, starting at the time that has been specified. Any time can be entered as the start time. Daylight savings corrections will be applied when the Controller's clock is updated.

  8. If required, select the Skip periodic dial following successful alarm dial check box.

    With this option selected, the periodic dial test will be skipped if there has been a successful alarm dial since the last periodic dial test. If the periodic dial is skipped, the next time you can expect a periodic dial is at the configured time the next day or after the periodic dial interval, depending on how it is configured.

  9. Click OK to complete the configuration.

For more information about your alarm transmitter, refer to the appropriate installation note:

About Periodic Dialling

A timer test (also known as the ‘periodic test’ or ‘24 hour’ test) is an affirmation to the monitoring station that the alarm system is capable of sending Contact ID. Most alarm systems send one test per day. The signal is fixed in its format and will be sent with an XYZ (Contact ID event code) of 602 and it will be sent in the (GG) partition or Alarm Zone 00. Only one periodic test can be enabled per account number for accurate reporting of line status (this is a consideration when using multiple Diallers using single client code reporting). It may be necessary to configure periodic tests from different diallers into different account numbers. It will also be reported as a new event and will have a CCC of 000, (e.g. 123418160200000, where 1234 is the account number).

If a test is not received when it should have been, action is taken by the monitoring station staff.

Publishing with an alarm transmitter

Publishing configuration with monitoring enabled pushes the monitoring-related configuration to the controller. This publishing is also the trigger for the controller to carry out dial checks and construct and send messages to the monitoring station.

THE MONITORING STATION WILL RECEIVE ALARMS FROM THE SITE WHENEVER MONITORING IS ENABLED AND A PERMACONN IS CONNECTED OR THE IP ALARM TRANSMITTER IS ENABLED (even if installation and configuration are still underway).

Monitoring Report

Generating the report Once a site is activated, a Monitoring Report will be available to download and send to the monitoring station. The Monitoring Report outlines the XZY Codes, GG Codes, Zone list CCC Codes, and User CCC Codes.

  1. Under Site Actions on the right-hand side of the screen, click Download Monitoring Report.

    A warning appears: Only published changes will appear in the report. NOTE: This report contains personal data. Please respect privacy laws.

  2. Click Download.

    The Monitoring Report downloads as a CSV file.

  3. Send the file to the monitoring station.

As no users are created for the site yet, the User List CCC Codes will only contain the Key Account Holder. The Monitoring Report can be downloaded at any stage, and you may wish to wait until the Site is set up with more users before downloading and sending the report.

Users' CCC codes If an incident occurs and the monitoring station doesn’t know who the user is by name, they will have a CCC code. In the SMB app, the customer can search for this code.

For the Site Manager to find which user the CCC code is related to:

  1. Log into the SMB customer app.

  2. Select Team from the navigation bar.

  3. In the search field, enter the CCC code.

    The user with the related CCC code appears in the search results.

Last updated