Communication Protocols
Mervis SCADA supports a wide range of communication protocols, allowing integration with native Mervis controllers, third-party PLCs, IoT devices, and utility meters.
1. Direct Connectivity
These protocols allow devices to communicate directly with the Mervis SCADA cloud or server without the need for an intermediate gateway or PLC.
- SSCP (Native): The primary protocol for connecting Mervis Controllers (PLCs) and Mervis Runtime (RT). Secure, optimized for low bandwidth.
- MQTT: Supported for generic IoT devices and specific integrations.
- BMR Network Analysers: Direct encrypted integration (TLS) for PLA34, PLA44, and PLA404 series.
- IoT Sensors: Support for generic MQTT payloads (JSON/Structure).
- Modbus TCP: Direct connection to Modbus TCP servers (check license availability).
2. Supported via Mervis RT (Controllers)
The following protocols are supported at the controller level (Mervis IDE/RT). Data from these devices is aggregated by the controller and sent to Mervis SCADA via SSCP.
| Protocol | Usage | Notes |
|---|---|---|
| IEC 60870-5-104 | Telecontrol & Power | Used for substations and smart grid communication. |
| BACnet | Building Automation | Standard for HVAC interoperability. |
| Modbus RTU/TCP | General Automation | Widely used for inverters, sensors, and third-party PLCs. |
| M-Bus | Metering | Support for heat and water meters (wired). |
| IEC 62056-21 | Metering | Optical/Wired readout for electricity meters. |
| Wago CC100 | Native Support | Full integration of Wago Compact Controller 100 inputs/outputs. |
3. Database & API
Mervis SCADA also allows external systems to access stored data:
- Mervis API: JSON-based REST API for reading/writing values and history.
- Export: CSV, XML options for reporting.