MiravoMiravo

Protocols

Project one running Miravo environment across MQTT, OPC UA, and Modbus TCP so clients can read the same runtime state through real adapters.

Miravo publishes the same environment across MQTT, OPC UA, and Modbus TCP. More protocols coming soon.

MQTT

Live topic tree from Miravo's built-in broker.

OPC UA

Typed address space.

Modbus TCP

Register-mapped live values.

Coming soon

Siemens S7

Siemens PLC workflows in their native automation surface.

EtherNet/IP

CIP-based clients and EtherNet/IP automation stacks.

Sparkplug B

Sparkplug namespace, birth/death certificates, edge-node payloads.

A running environment exposes every protocol at once — like the plant it models. Run several when downstream systems need different shapes of the same environment.

CLI ⭢ miravo start

Adapter flags, port flags, and --no-mqtt.

CLI ⭢ Environment variables

Default ports and bind hosts.

Core ⭢ Templates

Protocol scope in .miravo.yaml.

Was this page useful?

Last updated on

Diesel generator

Model a diesel backup generator with engine state, electrical load response, fuel depletion, runtime health, and faults for power scenarios.

MQTT

Subscribe to Miravo topics from any MQTT client, using live JSON payloads and a plant-structured topic tree from the active environment.

On this page

Coming soon
Related pages