ELAUSYS / AJAX-MBTCP
Ajax Modbus TCP Gateway
The AJAX-MBTCP connects a compatible Ajax alarm hub to a Modbus TCP building management system. Monitor group states, power faults, and up to 96 zone statuses while armed over the local network. Optional arm, night-mode, and disarm commands require an Ajax cloud connection and internet access.
The product
Designed for your installation.
Connect your Ajax alarm system to Modbus TCP
The Elausys AJAX-MBTCP makes supported alarm-system information available to a Modbus TCP client through its server interface. View alarm states alongside other building information and use them in configured automation.
Status information arrives from the hub over the local network. Optional control commands use an Ajax cloud connection and require internet access.
Monitor zones and alarm-system states
Monitor four groups, with six statuses per group: disarmed, armed, night mode, fire alarm, panic alarm, and intrusion alarm. Up to 96 zone statuses are available as Modbus coils while the system is armed. Hub AC-failure and battery-failure data is also available.
Zone reporting is limited to events while the system is armed. Group states and power faults remain available.
Use alarm information in building automation
Display alarm information alongside other building data in a compatible BMS, PLC, or visualisation. For example, use a confirmed armed state to request an energy-saving building mode. Configure responses in the connected controller using the documented Modbus data.
A compatible Modbus TCP client can issue arm, night-mode, and disarm commands for up to four groups. The gateway sends these commands through an optional Ajax cloud connection, which requires internet access. Status monitoring uses the hub’s local monitoring-station feed.
The alarm panel continues to manage its own security functions. The gateway adds integration with the building automation system.
Compatibility and installation
Supported systems: Compatible Ethernet-connected Ajax hubs in the Superior, Fibra, and Baseline lines.
Configure the hub to send its monitoring-station status feed to the gateway on the local network. Set the gateway’s network and Modbus parameters through its web interface, then map the documented data and commands in your Modbus client. Configure the optional Ajax account connection if commands are required.
Installation requires a compatible Modbus TCP client and Ethernet connectivity, plus an external 12–30 VDC power supply. Configure the gateway in a web browser; ETS is not required.
Check the documentation for the required panel settings, supported functions, and installation details.
Specifications
- Reference
- AJAX-MBTCP
- Manufacturer
- ELAUSYS
| Parameter | Specification |
|---|---|
| Product reference | AJAX-MBTCP |
| Supported alarm systems | Compatible Ethernet-connected Ajax hubs in the Superior, Fibra, and Baseline lines |
| Required panel interface | Compatible Ajax hub; optional Ajax account connection for commands |
| Alarm connection | Ethernet, RJ45; local monitoring-station status feed |
| Building automation interface | Modbus TCP server over Ethernet |
| Communication direction | Local status monitoring; optional cloud commands |
| Zone monitoring | Up to 96 zone-status coils, reported while armed |
| Areas / sections / groups | 4 groups |
| Status information | 6 statuses per group, exposed through the Modbus map |
| Control commands | Arm, night mode, and disarm via optional Ajax cloud connection |
| Outputs and virtual inputs | Group, zone, and power-fault data via Modbus; see register map |
| Scene integration | Not applicable; automation is configured in the connected Modbus client |
| Expansion | Up to 96 zones per gateway |
| Alarm and fault monitoring | Hub AC-failure and battery-failure status |
| Internet dependency | Status monitoring: local network, no internet required; commands: optional Ajax cloud connection, internet required |
| External power supply | 12–30 VDC external, screw terminal |
| KNX bus current | Not applicable; Modbus TCP gateway |
| Housing / dimensions | 2-module DIN-rail housing |
| Mounting | 35 mm DIN rail |
| Operating temperature | +5 to +45 °C |
| Configuration | Gateway web interface; register mapping in the Modbus client |
Key features
- Connect compatible Ajax alarm systems to Modbus TCP
- Monitor up to 96 zone statuses while armed
- Monitor 4 groups with 6 statuses per group, exposed through the Modbus map
- Send arm, night-mode, and disarm commands via the optional Ajax cloud connection
- Receive group states and power faults over the local network
- Integrate through the documented Modbus register map
- Configure through the gateway’s web interface
Documents & support
PDFModbus TCP Gateway for AJAX alarm systems DatasheetProduct document · Opens in a new tabPDFQuick-Start-GuideProduct document · Opens in a new tabPDFSafety-and-Regulatory-Notice-ENProduct document · Opens in a new tabBrowse product supportFAQ
Frequently Asked Questions
Which Ajax alarm systems are compatible?
Compatible Ethernet-connected Ajax hubs in the Superior, Fibra, and Baseline lines. Check the documentation for the exact panel and interface configuration.
Can I arm or disarm the system from Modbus TCP?
A compatible Modbus TCP client can issue arm, night-mode, and disarm commands for up to four groups. The gateway sends these commands through an optional Ajax cloud connection, which requires internet access. Status monitoring uses the hub’s local monitoring-station feed.
Can I see detector activity when the alarm is disarmed?
No. Zone events are reported while the system is armed. Group states and power faults remain available. Use the documented Modbus map to distinguish status data from command functions.
Does it need an internet connection?
Status monitoring uses the local network and does not require internet access. Arm, night-mode, and disarm commands require the optional Ajax cloud connection and internet access. If internet access is lost, local status monitoring can continue, but cloud commands are unavailable.
What do I need to install it?
Compatible Ajax hub; optional Ajax account connection for commands. You also need Ethernet connectivity, a compatible Modbus TCP client, an external 12–30 VDC supply, and a web browser for gateway configuration.
Where can I find the Modbus register map?
The register map is available in the linked product documentation. Use it to configure the supported status reads and command writes in your Modbus TCP client.