Muvia IndustrialFleet and cloud
You know right away which node stopped answering.
Each node reports that it is alive at an interval you choose. Muvia shows the state of its drivers and alerts you when a node no longer answers.
- Line 2, press12 s ago · Siemens S7 connected
- Furnace40 s ago · Modbus TCP waiting
- Spare parts storeUnreachable · alert open
Illustrative example
The fleet, node by node.
Node heartbeat
Each node reports that it is alive, at an interval from 5 to 300 seconds.
State of every driver
Connected, waiting for a connection or in error: driver by driver.
Offline alert
A node that stops answering raises an alert.
Where the data stops
For each driver, the chain driver, node, platform and database shows where the data stops.
From the warning to the fault
- 01
Watch the fleet
See which nodes answer and when they last did.
- 02
Open a driver
State, latest values and the trend of what was read and written.
- 03
Act
If the node is offline the alert arrives; the local console stays reachable from the node.
In detail
- Heartbeat
- Interval of your choice, 5 to 300 seconds
- Driver state
- Connected, waiting for a connection, in error
- Alert
- When a node stops answering
- Per driver
- Latest values and trend of read and written
- Window
- You choose the period to look at
Also in Fleet and cloud
Frequently asked questions
A node that stops answering raises an alert.
Yes: each driver shows as connected, waiting for a connection or in error.
No. Updates are explicit: you decide which node and when.
Tell us which machines you run. We'll tell you how to read them.
PLC brand, protocol, how the floor is connected: with those three answers, in a demo with one of our engineers, we show you how Muvia Industrial puts line data next to the rest of the business.