Litmus Edge

Miravo maps a running factory into Litmus Edge. It creates devices, tags, Digital Twins models and Digital Twins instances, and links them.

Doing this by hand means creating and linking each resource yourself. Miravo applies the template in one operation, and you can update or remove the same set later.

Digital Factory DemoCopy Anchor Link

This demo runs two CNC plants, Detroit and Toronto, with wear and faults. Litmus Edge connects to both over OPC UA, Modbus TCP, and MQTT, maps the tags into Digital Twins, and sends OEE and equipment health to Grafana.

Fail the Detroit compressor from the Miravo console. Air pressure drops, that site's assembly line stops, and the dashboards show it. Toronto keeps running. One command starts the stack.

Run the demoCopy Anchor Link

Requirements: Docker Engine 24 or later, Docker Compose v2, and about 6 GB of RAM.

git clone https://github.com/amine-amaach/miravo.git && \
  cd miravo/examples/miravo-litmus-edge-dfd && \
  docker compose up

Startup takes up to 2 minutes. Litmus Edge configures itself, and Grafana opens with live panels.

Map your own templateCopy Anchor Link

Map your own template from the Console or the CLI. Save the target with miravo le target add, then preview or apply the mapping with miravo le apply.

From the ConsoleCopy Anchor Link

Open /integrations in the Miravo Console and register the target. Then open Factory, go to the Integrations tab, and click Apply on the row of a template or standalone asset. A dry-run preview shows the plan before anything is written. Review past runs in the activity log on Integrations.

From the CLICopy Anchor Link

The CLI uses miravo le target add, miravo le apply and miravo le cleanup. Without --protocol, apply maps every asset on its scoped protocol (opcua when an asset lists several). --protocol takes opcua, modbus or mqtt and limits the run to that protocol, with a warning for any skipped assets.

The token never goes on the command line. Pipe it to --api-token-stdin, answer the hidden prompt on a terminal, or set LITMUS_EDGE_API_TOKEN.

printf %s "$LE_TOKEN" | miravo le target add --label Demo --hostname 10.0.1.100 \
  --source-hostname 10.0.1.50 --api-token-stdin

miravo le apply --target Demo -t smart-factory --dry-run

miravo le apply --target Demo -t smart-factory

Offline templatesCopy Anchor Link

If your machine cannot reach Litmus Edge, generate an importable bundle locally with miravo le export template.

miravo le export template -t smart-factory

This writes smart-factory.le-template.json and smart-factory-tags.csv, covering every asset, and prints the asset count per protocol. Import the JSON in Litmus Edge under Template Store, Import.

What gets created in Litmus EdgeCopy Anchor Link

• Devices: one per asset, for the protocol you apply.
• Tags: every published member, with engineering units and access levels. MQTT tags are strings holding the whole Miravo JSON message, because the Litmus Edge MQTT Client driver cannot extract a field from the payload. Use OPC UA or Modbus for numeric tag values.
• Digital Twins models: one per Miravo asset model.
• Digital Twins instances: one per running asset, bound to its device and tags.

NextCopy Anchor Link