Platform Devices Sectors Forecasting FAQ Blog Products
References About Contact
Sign In

Integrations

Every Device, One Platform

From Modbus to M-Bus, from MQTT to BACnet — Argus EMS speaks every industrial protocol used in the field.

Industrial Protocols

Supported Communication Protocols

Modbus TCP

Active

The most widely used industrial protocol. The vast majority of energy analyzers, UPS units, generators and inverters support it. Poll interval 15 minutes (configurable).

TCP port 502 · Slave ID 1–247 · Function Code 03/04 · Register map documentation

Modbus RTU

Active

Runs over an RS-485 serial line. Common for legacy meters and control panels. Integration via a USB-RS485 converter or an RS485-Ethernet gateway.

RS-485 · Baud: 9600/19200 · Parity: None/Even · Gateway-based connection

M-Bus TCP

Active

The standard protocol for water, heat and natural gas meters. Used in meters integrated with infrastructures such as İSKİ, İGDAŞ and similar utilities.

TCP port 10001 · Address-based reading · Manufacturer ID matching

MQTT / TLS

Active

The transport layer between the field agent and the central platform. Secure delivery with QoS 1, persistent session and TLS 1.3 encryption.

Port 8883 (TLS) · QoS 1 · clean_session=False · Retain=True config push

BACnet/IP

Coming Soon

A protocol widely used in building automation systems (BAS). Air handling units, chillers, VAV systems and DALI lighting controllers.

UDP port 47808 · COV subscription · BBMD broadcast management

OPC-UA

Coming Soon

For high-level integration with SCADA and MES systems. A bridge to machine manufacturer OEM data and ERP systems.

TCP port 4840 · Namespace browser · Security: Basic256Sha256
✓ ISO 50001 Compliant Reporting ✓ TLS 1.3 Encrypted MQTT ✓ 200+ Certified Devices ✓ Zero Data Loss Architecture

ERP & Software

Upstream System Integrations

Combine your energy data with your enterprise systems. Automate cost centers, maintenance work orders and budget flows.

SAP PM/PM

 Fault notifications and maintenance work orders — SAP RFC or REST bridge

Logo Tiger / Go

 Türkiye-based ERP. Energy cost center and accounting integration

Microsoft Dynamics

 Power BI data flow and Azure IoT Hub connection

Generic REST

 JSON webhook for any system — configurable POST payload

FAQ

Integration Questions

Send us your device's technical documentation and register map. We can develop a driver and add it to the system within 2–4 weeks. First review the current devices page: 200+ supported models.
No. The Argus architecture is field agent based; device reading, queue management and offline buffering all run through the field agent. This structure guarantees zero data loss.
Yes. REST API and MQTT feed access are available with enterprise licenses. For OpenAPI documentation, write to info@nevacontrol.com.

Shall we add your device?

Share the register map and protocol document, and the driver will be ready within 2–4 weeks.

Request Integration →

See Argus at Your Facility

Explore the system with your own data in a demo session.

const obs = new IntersectionObserver(entries => entries.forEach(e => e.isIntersecting && e.target.classList.add('visible')), {threshold:.12}); document.querySelectorAll('.reveal').forEach(el => obs.observe(el));