Overview
The Alarm Reporting Communications Task enables the Integriti controller to report alarms to a Central Monitoring Station (CMS) via a selected alarm delivery device and/or communication protocol.
Supported Protocols:
- CSL DualCom (formerly WebWayOne) — RS232 serial interface
- Trikdis — TTL serial interface (G16 device)
- IRIS — RS232 serial interface (Chiron IRIS Touch)
- SIA IP Reporting (UDP/TCP-2021) — direct Ethernet connection to CMS, no onsite device needed
Supported Alarm Formats:
- ContactID (all protocols)
- SIA (CSL DualCom, IRIS, SIA IP Reporting — NOT available via Trikdis)
Document Version: Integriti Software v23.1.0 / Controller Firmware v23.1.0.38985
Prerequisites
- Integriti System Designer software
- Appropriate alarm delivery device (except for SIA IP Reporting which uses the controller’s Ethernet port directly)
- Client code / account number from the monitoring station
- For SIA IP Reporting: CMS receiver IP address, port, and encryption key (if using encryption)
- Controller serial port available (RS232 or TTL depending on protocol)
- EN50131 compliance: refer to Integriti_Application_Note-EN50131_Recommended_programming
Step-by-Step
1. Create the Communications Task
- In Integriti System Designer, navigate to Communications Tasks tab and click Add.
- Enter a Name for the task and any notes.
- Under Comms Task Setup, set the Type drop-down to Alarm Reporting.
2. Basic Configuration
- Expand the Configuration section.
- Enter the designated Client Code for identifying the site to the monitoring station.
- Expand the Settings section.
- Optionally assign an Input to reflect comms task status (C01:Z33-Z99 are recommended — the input alarms if the task fails).
- Expand the Options section.
- Configure the Review Filter to control which alarms are reported:
- General Open/Close — include open/close events
- Xmit Historic — transmit historic events
- Report Timeout Minutes — timeout for report attempts
3. Select Alarm Protocol
- Expand the Configurations section.
- Set the Alarm Protocol to match your equipment:
CSL DualCom
- Communication Port: Select RS232 serial port. Default: 19200, 8, N, 1.
- Alarm Format: ContactID or SIA.
- ContactID: Select the ContactID map.
- SIA options: Send Time, Send ASCII, Send Peripheral Identifier, Decimal Address, Obey Address.
Trikdis (G16)
- Communication Port: Select TTL serial port. Default: 19200, 8, N, 1.
- ContactID Map: Standard, Access, or Sims II.
- Note: SIA format is NOT available via Trikdis.
IRIS (Chiron IRIS Touch)
- Communication Port: Select RS232 serial port. Default: 9600, 8, N, 1.
- Alarm Format: ContactID or SIA (same SIA options as CSL DualCom).
- Receiver IP Configuration: Set the IP endpoint for the IRIS communicator.
- GPRS Authentication (optional): Configure APN, username, and password.
SIA IP Reporting (UDP/TCP-2021)
- Alarm Format: ContactID or SIA.
- ContactID: Select the ContactID Map.
- SIA Options: Send RTC (time), Send ASCII, Send Peripheral Identifier, Decimal Address, Obey Address, Send Brief ASCII.
- Primary Receiver: IP Address, Port, optional Domain Name, Protocol (UDP-2021 or TCP-2021).
- Secondary Receiver (optional): IP Address, Port, optional Domain Name, Protocol.
- Client Code (3-8 hex characters, required).
- Account Prefix and Receiver Number (optional).
- Supervise Connection: Enable and set Supervision Period (10 sec to 18 hours).
- Encryption: Enable AES 128-bit encryption and set Encryption Key if required.
4. EN50131 Configuration (Optional)
- Configure up to 8 Verify Groups. A group is enabled when both “All Path Fault” and “Single Path Fault” inputs are configured.
- The comms task’s Verify Group value is tested against Verify Group values in Areas.
5. Save
- Click OK to save and close the dialog.
Verification
- The comms task status input (if configured) remains sealed when the connection is healthy.
- Three internal inputs are available for monitoring:
| Input Name | Sealed State | Unsealed State |
|---|---|---|
| Online | Protocol online/polling/working | Protocol offline/not working |
| Fail | Alarm reported successfully | Alarm failed to report |
| Backup | Backup comms task not executing | Backup comms task is delivering alarms |
- Verify that test alarms appear at the Central Monitoring Station.
- For SIA IP Reporting, verify supervision messages are exchanged within the configured period.
Troubleshooting
- No communication with alarm delivery device: Verify serial port selection, baud rate, data bits, parity, and stop bits match the device specifications.
- Alarms not reaching CMS: Confirm client code/account number is correct and matches the CMS configuration.
- SIA IP connection fails: Check IP address, port, and protocol selection. Ensure the controller has network connectivity to the CMS receiver.
- Trikdis wiring: Refer to Appendix 1 in the PDF for Trikdis G16 TTL connection pinout (Port0 Power=1, Tx=2, Rx=3, spare=4, Ground=5; G16: +DC, -DC, CLK, DATA).
- Encryption failures: Verify encryption key matches on both ends (SIA IP Reporting).
- Backup comms task engaging: Indicates primary reporting path has failed — check the primary alarm delivery device.