Muvia IndustrialFleet and cloud
A fleet of nodes, configured from one place.
In Node configuration you enrol the node with a token, add its drivers and tags and describe its processing. Nothing is left to set by hand on site.
- furnace_temperatureDB10.DBD4S7
- line_pressurens=2;s=PressureOPC UA
- compressor_energyregister 40001Modbus TCP
Illustrative example
Everything a node needs to know.
Enrol with a token
The node introduces itself with your company's token and appears in the fleet.
Drivers per node
Add the drivers each node needs and set their parameters.
Named tags
Variables, addresses and tag names, even declared before the machine is installed.
Processing
The node's program, with catalogue and Python functions, is composed and tried here.
From token to data
- 01
Enrol the node
Generate the token and the node uses it on first boot.
- 02
Add drivers and tags
Choose protocol, addresses and names.
- 03
The node updates
The configuration reaches the node; values start flowing.
In detail
- Enrolment
- With a company token
- Per node
- Drivers, tags and processing
- Declared signals
- Can be defined before the machine is installed
- A tag's values
- Latest values and trend from the tag's page
Also in Fleet and cloud
Frequently asked questions
No. The node enrols with the token and the rest is configured in Muvia.
Yes, signals can be declared in advance.
Whoever holds the permissions for it in your company, through Muvia's roles.
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.