Intrepid Communications Task
Overview
The Intrepid Communications Task provides a high-level TCP-based interface between the Integriti controller and the Intrepid fence detection system. It uses the Intrepid HLI (High-Level Interface) protocol to report Intrepid fence segment alarms in Integriti via virtual modules.
Alarms from Intrepid modules (fence segments, tampers, faults, etc.) are mapped to Integriti virtual module inputs. The integration also supports “many-to-one” automation points, where a sequential range of Intrepid points can be aggregated into a single Integriti Automation Point.
Prerequisites
- Integriti Controller Firmware V4.3.0 or later
- Pre-V20: No comms task license required; virtual modules licensed via virtual module quantity licenses
- V20 and later: High-Security Fence Integration License (unlocks the comms task and unlimited virtual modules)
- Network connectivity to the Intrepid controller (IP address and TCP port)
- Intrepid controller credentials (Username and Password)
Step-by-Step
Step 1: Create the Communications Task
- In Integriti System Designer, navigate to Communications Tasks.
- Create a new Communications Task.
- Enter a name and any notes.
- Under Comms Task Setup, set the Type to Intrepid.
Step 2: Configure Connection Details
- IP Address: Enter the IP address of the Intrepid controller.
- Port: Enter the TCP port used by the Intrepid controller.
- Username: Enter the username for authenticating with the Intrepid controller.
- Password: Enter the password for authenticating with the Intrepid controller.
Step 3: Configure Online Input (Optional)
Optionally, set an Online Input that reflects the communications task status. This input goes into alarm when the TCP connection to the Intrepid system is lost.
Step 4: Configure Fence Modules
For each Intrepid module to be monitored:
- Fence Module ID: Enter the device address of the Intrepid module.
- Type: Select the module type (RPM II, PM II, ROMII16, ROMII8, AIMII, MTPII, MOD330).
- Inputs 1-512: For each bank of 32 Intrepid alarms, map to a Virtual Module (which has 32 inputs). Each module type has different input mappings (see reference tables below).
Step 5: Auto-Rename Inputs
After mapping Virtual Modules, use the auto-rename feature:
- Right-click on the Intrepid Comms Task.
- Select Set Associated Input Names To Default.
- This renames the virtual module inputs to their corresponding Intrepid alarm names for easier commissioning.
Step 6: Save the Communications Task
Save and close the editor window.
Intrepid Many-to-One Automation Points
A sequential range of Intrepid points can be mapped to a single Automation Point. The Automation Point goes active when one or more of the associated Intrepid inputs enter alarm, and goes inactive only when all associated inputs are clear.
Creating an Automation Point
- Navigate to the Automation tab.
- Create a new Automation Point.
- Under Automation Setup, set the Type to Intrepid Fence Input.
- Configure:
- Module ID: The Intrepid module address.
- Starting Input: The first input number in the range (refer to mapping tables).
- Ending Input: The last input number in the range (refer to mapping tables).
- Mapped Entity: Select a virtual module input to map to.
- Update Entity, Qualifier, Associated Action: Not used; leave as default.
- Save and close.
Virtual Module Input Mapping Reference
RPM II
| Input Range | Mapping |
|---|---|
| 1 | RPMII (x) - Tamper Alarm |
| 2 | RPMII (x) - Low Input Voltage Alarm |
| 3 | RPMII (x) - Line Break Alarm |
| 4-8 | UNUSED |
| 9-24 | RPMII (x) - Compromised Alarm: Device 1-16 |
| 25 | UNUSED |
| 26 | RPMII (x) - RPM II |
| 27-32 | UNUSED |
| 33-48 | RPMII (x) - Communication Failure Alarm: Device 1-16 |
PM II
| Input Range | Mapping |
|---|---|
| 1-128 | PMII (x) - Cable A: Segment 1-128 |
| 129-256 | PMII (x) - Cable A: Segment 129-256 |
| 257-288 | PMII (x) - Cable B: Segment 1-32 |
| 289-432 | PMII (x) - Cable B: Segment 73-216 |
| 433-436 | PMII (x) - Auxiliary Input 1-4 |
| 437-440 | UNUSED |
| 441 | PMII (x) - Cable A Fault |
| 442 | PMII (x) - Cable B Fault |
| 443 | PMII (x) - Enclosure Tamper |
| 444-448 | UNUSED |
| 449 | PMII (x) - Universal Installation Service Tool II Active |
(Note: PM II cable segment mappings continue past 256 on Cable A and past 216 on Cable B. Full mappings available in the SDK documentation.)
ROMII16
| Input Range | Mapping |
|---|---|
| 1-8 | ROMII16 (x) - Relay Status 9-16 |
| 9-16 | ROMII16 (x) - Relay Status 1-8 |
| 17 | ROMII16 (x) - Tamper Status |
ROMII8
| Input Range | Mapping |
|---|---|
| 1-8 | ROMII8 (x) - Relay Status 1-8 |
| 9 | ROMII8 (x) - Tamper Status |
AIMII
| Input Range | Mapping |
|---|---|
| 1-8 | AIMII (x) - Alarm Input 1-8 |
| 9-16 | AIMII (x) - Supervised Alarm on Input 1-8 |
| 17 | AIMII (x) - Tamper Switch |
MTPII
| Input Range | Mapping |
|---|---|
| 1-144 | MTPII (x) - Cable A: Segment 1-144 |
| 145-288 | MTPII (x) - Cable B: Segment 1-144 |
| 289 | MTPII (x) - Cable A Fault |
| 290 | MTPII (x) - Cable B Fault |
| 291 | MTPII (x) - Enclosure Tamper |
| 292-296 | UNUSED |
| 297 | MTPII (x) - Universal Installation Service Tool II Active |
MOD330
| Input Range | Mapping |
|---|---|
| 1 | MOD330 (x) - Microwave Alarm |
| 2 | MOD330 (x) - Tamper Alarm |
| 3 | MOD330 (x) - Align/Path Alarm |
| 4 | MOD330 (x) - Auxiliary Alarm |
| 5 | MOD330 (x) - Service Alarm |
| 6 | MOD330 (x) - Low Voltage Alarm |
For complete and detailed input mappings, consult the Intrepid SDK documentation.
Verification
- Confirm the Intrepid controller IP, port, username, and password are correct.
- Verify the Online Input (if configured) is not in alarm, indicating a healthy TCP connection.
- Trigger a test alarm on an Intrepid fence segment and verify the corresponding virtual module input in Integriti changes state.
- Use the auto-rename feature to confirm input names match expected Intrepid alarm descriptions.
- Check the Integriti event log for alarm and restore events from the Intrepid modules.
Troubleshooting
| Symptom | Possible Cause | Resolution |
|---|---|---|
| Online input in alarm | TCP connection lost | Verify IP address, port, and network connectivity to Intrepid controller |
| Authentication failure | Incorrect username/password | Verify credentials with the Intrepid system administrator |
| No fence alarms reporting | Fence Module ID or Type incorrect | Double-check Intrepid module addresses and types |
| Virtual module inputs not matching alarms | Input mapping bank misaligned | Verify which bank of 32 inputs maps to which virtual module |
| Auto-rename not working | Virtual modules not yet mapped | Map virtual modules first, then right-click and select auto-rename |
| Missing module type in Integriti | Older firmware | Update to the latest controller firmware |
Related Pages
- Integriti Comms Tasks Automation
- Integriti Communication Handlers
- Integriti Virtual Modules
- Integriti Automation Points