Central controller
DefendX M32
128-Channel TCP/IP Fire Alarm Mimic and Event Recording Panel
A central network-based monitoring system designed to receive real-time status from up to 32 DefendX Nodes, operate 128 physical LED outputs, control 16 programmable relays, support multiple browser clients and retain at least 45 days of recorded status.
Specifications
Main Specifications
| Feature | Specification |
|---|---|
| Monitored fire panels | Up to 32 |
| LED digital outputs | 128 |
| Relay outputs | 16 changeover relays |
| Ethernet | 10/100 Mbps RJ45 |
| Communication | TCP/IP |
| Device protocol | MQTT or structured TCP |
| Web clients | Minimum 25 simultaneous clients |
| Event retention | Minimum 45 days |
| Storage design | Minimum 60-day capacity margin |
| Dashboard update | Real-time |
| Heartbeat supervision | Supported |
| Offline detection | Typically within 15 seconds |
| User roles | Viewer, Operator and Administrator |
| Time synchronization | RTC and NTP |
| Reporting | CSV and PDF |
| Operation | Local network, no compulsory cloud |
| Duty | Continuous 24×7 |
128 LED outputs
- 128 individually programmable outputs
- Four outputs per fire alarm panel
- Recommended mapping: Panel Power, Fire, Fault, Supervisory
- Configurable steady or flashing operation
- Lamp test
- Acknowledged and unacknowledged behaviour
- Flexible channel reassignment
- Modular output cards
Concept Product Visualization
16 programmable relay outputs
All 16 relays can be configured for:
- Common Fire
- Common Fault
- Common Supervisory
- Panel power failure
- Communication failure
- Individual panel status
- Building group status
- BMS integration
- CCTV triggering
- External hooter or strobe
- Custom cause-and-effect rules
Contact and timing options
- NO, NC and COM contacts
- Latched or non-latched operation
- Activation delay
- Restoration delay
- Pulse or continuous operation
- Normally energized fail-safe mode
Multi-client monitoring
One Controller. Many Synchronized Displays.
All clients view the same synchronized live status through a standard browser on the local network.
Main control room
Browser client
Security office
Browser client
Maintenance department
Browser client
Facility manager
Browser client
Tablet
Browser client
Large wall display
Browser client
45-day recording
The system records:
- Fire activation and restoration
- Fault activation and restoration
- Supervisory activation and restoration
- Panel power failure and restoration
- Node online and offline status
- Ethernet disconnection and restoration
- LED output changes
- Relay output changes
- Alarm acknowledgment
- Buzzer silence
- Controller restart
- User login
- Configuration changes
Two recording methods
- 1. Immediate change-based event recording.
- 2. Configurable periodic complete status snapshots.
- 14:32:10FIRE ACTIVEP07 — Production Block
NORMAL → ACTIVE · acknowledged by Control Room Operator
- 14:32:11RELAY ACTIVATEDR01 — Common Fire Relay
OFF → ON · acknowledged by System
- 14:32:15FIRE ACKNOWLEDGEDP07 — Production Block
UNACKNOWLEDGED → ACKNOWLEDGED · acknowledged by Control Room Operator
- 14:35:42COMMUNICATION LOSTP18 — Utility Building
ONLINE → OFFLINE · unacknowledged
Cause-and-effect programming
IF any panel reports Fire THEN activate Common Fire Relay.
IF Panel 01 to Panel 08 reports Fire THEN activate Building Group 1 Relay.
IF a Node remains offline for 15 seconds THEN activate Communication Fault Relay.
IF panel power is absent for 10 seconds THEN activate Panel Power Failure Relay.
Fail-safe behaviour
- Offline status is never treated as Normal
- Last valid data is marked as stale
- Communication-fault relay can activate
- Associated healthy indication turns off
- Last received timestamp remains visible
- Automatic reconnection
- Full status resynchronization after reconnection
Historical playback
Reconstruct Any Moment in the Last 45 Days
Interactive simulation using demonstration data.
Reconstructed state at 14:32:10 — P07 Production Block: FIRE ACTIVE
Front panel
Local Indications and Controls
Indications
Controls
Front-panel controls operate the annunciation, buzzer and indication logic of the DefendX M32 only.
DefendX is intended as a supplementary monitoring, annunciation, event-recording and auxiliary output-control system. It does not replace the primary approved fire alarm control and indicating equipment. Final installation, interfacing and use must comply with applicable fire-safety regulations, project requirements and approvals.
Enquiry
Request an M32 Proposal
See DefendX M32 Working
Open the simulated dashboard or arrange a technical walkthrough with the DefendX engineering team.