Privacy Policy

Cookie Preferences

We use cookies and other tracking technologies to improve your browsing experience on our website, show you personalised content, and analyse our website traffic. Privacy Policy

Privacy Policy
Choose Language:

Technical Notes

Overview

Learn about specific development topics through these in-depth technical articles.

Update

  • DigiAir Pro 3

    08.11.23

    Firmware v3.3.1

     

    Firmware  V3.3.1 has now been released on My Base for DigiAir Pro 3 devices.

    This supersedes v3.0.1 and will shortly also be the default version for units shipping from the factory.

    The release improves stability of the DigiAir Pro 3 devices, in particular the DigiAir Pro 3 Radio.

    It also includes a fix for non-encrypted DC09 panels and changes to support Linx.

  • All Products

    23.08.23

    PinLearn EOL Pins 1-12


    Enables DualCom Pro devices to monitor all pins in EOL mode rather than just pins 1 and 2.

    Traditionally in the UK, Fire panels have connected up pins 1 and 2 in EOL mode for the DualCom Pro to monitor.

    Recent changes in legislation in Scotland have resulted in requests for additional pins to be monitored to allow, for example, Confirmed Fire to be communicated to the ARC. This new pin profile enables the Installer to configure the CSL DualCom Pro device to deliver this.

    Usage

    When purchasing a DualCom Pro Fire, it will be configured to use a pin profile of PinLearnFire. This and PinLearnFire No-A Block are configured to put pins 1 and 2 in EOL mode.

    Pin Profile PinLearn EOL Pins 1-12 is configured to put all 12 pins on a DualCom Pro 2 and all 8 pins on a DigiAir Pro 3 into EOL mode.

    This does not affect the monitoring for tamper and short circuit in Fire mode which, by default, is pins 1 and 2. If you require additional pins to be monitored for tamper and short circuit then currently this needs to be configured by Tech Support.

    Similarly, output relay 1 will only trigger by default if pins 1 and 2 are triggered with. If an additional pin should trigger output relay 1 then this needs to be configured by Tech Support. Making this change will also result in any additional pins reporting ARC Ack on output relay 2.

     

    Contact ID Alarm Protocol

    The DualCom Pro range supports Intruder Panels using SIA, Fast Format and Contact ID protocols.

    When integrating the DualCom Pro range with an Intruder Panel, our recommendation is to use either SIA or Fast Format (6.8.1, 6.16.1 or 6.32.1) protocols.

    If Contact ID is to be used to pass events to the ARC, please be aware that it will only use the least significant 4 digits of the ARC account ID. The ARC must supply this prior to installation.

    If the ARC does not support this then one of the other signalling formats should be used.

    For reference, please see the below breakdown of a Contact ID alarm message constructed from several fixed length message blocks.

    These are defined as follows:

    18AAAAQXYZGGCCC

    Where:

    18 – Contact ID type identifier.

    AAAA signalling ID – 4-digit account number.

    Q - Event type - E (new alarm event), R (new restore event) or P (previously reported alarm).

    XYZ - Event number – Defines the type of event that has occurred.

    GG - Area number – Set to 00 if no areas defined.

    CCC - Zone or User Number – Dependent on the type of event defined by the event number.

    This fixed length account number field restricts the required 6-digit account number entered in the intruder panel being presented to the Alarm Receiving Centre. Resulting in events being misinterpreted.

© Copyright CSL 2024