RESOURCES / INTEGRATIONS

Protocol-level, not vendor-level.

We don't sell you a logo wall. We integrate at the protocol level: any device exposing a documented Modbus TCP map can be added, and we scope the effort for your hardware before you commit — because a claim you can check beats a grid of brands you can't.

VALIDATED IN PRODUCTION

Running on our plants today.

Huawei SmartLogger 3000 and SUN2000 — per-inverter and per-string registers, both logical and communication addressing modes, across two plant generations. Multi-EMI weather stations. Every claim in this block is checkable in a demo on live telemetry.

M

Modbus TCP

30-second polling of loggers and inverters — per-inverter and per-string registers, logical and communication addressing modes, multi-EMI weather stations.

MQ

MQTT

Lightweight pub/sub for sensor and fan nodes — autonomous local control loops with last-will-and-testament presence, streaming to the edge broker.

API

REST API

Pull telemetry, alerts, and work orders into your ERP, CMMS, or data warehouse from the platform API — full reference and guides at developers.dynvolt.com.

Building against the platform? The complete API reference, authentication guide and examples live at developers.dynvolt.com.

IMPLEMENTED, AWAITING HARDWARE

One BESS family at register level.

ESMU and PCS register maps with alarm decode — implemented and awaiting hardware for validation as our 20.64 MWh commissioning completes. Additional BMS and PCS families are an integration cycle each; we will scope the effort before you commit.

HOW NEW HARDWARE GETS ADDED

Two engineering days, last time we did it.

We integrate at the protocol level, not the vendor level. Any device exposing a documented Modbus TCP map can be added. Our most recent variant — including weather-station and addressing quirks — took two engineering days. We will scope yours before you commit.

1

Send us the map

The device's Modbus register documentation — or access to one unit we can interrogate.

2

We scope it

A written effort estimate for your exact hardware, including quirks, before any commitment.

3

Validated on site

The integration ships when it reads correctly from your device — not when the register map compiles.

TELECONTROL

IEC 60870-5-104 — built to your operator's specification.

Direct telecontrol interfacing to a transmission or distribution system operator is delivered as a project build within the DYNVOLT platform, not as a shipped module. Every operator has its own point list and telecontrol specification, so we implement to yours, publish a Protocol Implementation Conformance Statement, and include security extensions per IEC 62351. Scope, timeline and acceptance testing are agreed before the engagement starts.

Today, without a 104 link, the platform enforces the export limit configured at the point of connection from the edge and applies curtailment on instruction received through your existing operator channel.

PROTOCOL ROADMAP

Next on the protocol build path.

Build order follows customer demand — if one of these is a hard requirement for your site, tell us and it moves up. And true to form: each ships to this page as "in production" only after it runs at a real site, not before.

O

OPC-UA

On the build path for BESS EMS and PPC interfaces where the site vendor stack requires it.

61850

IEC 61850

On the build path for substation automation and HV-side observability.

DNP

DNP3

On the build path for sites where operator endpoints require it.

Huawei, SmartLogger and SUN2000 are trademarks of their respective owners. Naming them here describes tested compatibility, not partnership or endorsement.

Send us your register map.

We'll scope the integration for your exact hardware — effort, quirks, and timeline in writing — before you commit to anything.

Request an integration scopeSee the architecture →
FAQ

Integrations — frequently asked

Can't find what you're looking for? Talk to our team →

How long does an integration take?
For a device with a documented Modbus TCP map, our most recent variant — including weather-station and addressing quirks — took two engineering days. We scope your exact hardware in writing before you commit.
Do I need to install firmware on inverters?
No. We read the manufacturer Modbus map natively. Where a BESS vendor requires an OEM control license for write access, that sits between you and the OEM — we tell you upfront if your hardware needs one.
Can DYNVOLT push data to my data lake?
Telemetry, alerts and work orders are available over the REST API and webhooks in JSON and CSV. If you need a specific warehouse pipeline, we scope it as integration work rather than promising a connector list.
Is there an API?
Yes — a full REST + Webhook API for everything in the UI, rate-limited per tenancy with full audit logs. The complete reference, authentication guide and examples are published at developers.dynvolt.com.