MiravoMiravo

Protocols

Read one running Miravo factory over MQTT, OPC UA and Modbus TCP, with the same runtime values behind each protocol.

OPC UA, Modbus TCP and MQTT today, with more to come.

MQTT

A live topic tree from the built-in broker.

OPC UA

A typed address space.

Modbus TCP

Live values in a register map.

A running factory serves the same live values over every enabled protocol at once. Enable several when downstream systems need different views of the same factory. A template can narrow what each protocol serves with protocol_scope.

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. Live JSON payloads arrive on a topic tree that follows the plant hierarchy.

On this page

Related pages