Control, measurement and learning.
Every machine project starts with a practical question: what should it measure, how should it respond, and what do you need to learn? See how our control, measurement and software work addresses each part.
- 01
Measure
Capture suitable sensor signals and test context. MODAL focuses on structural tests; industrial acquisition serves local equipment applications.
Explore - 02
Control
Industrial sequences run locally. Motion coordination uses a private EtherCAT domain; motor loops stay at the drives.
Explore - 03
Connect
Software defines applications and exchanges selected state and history through a separate service path.
Explore - 04
Learn
Research datasets and models outside deterministic loops. Validate any proposed advisory output for the actual machine.
Explore
Product relationships shown for explanation. Each hardware/software connection needs its own integration and validation.
How it could work in practice
Illustration only. This is not a live connection or the production application.
Define
Use the UI to connect control functions and describe equipment signals.
Validate & package
The backend checks and packages an application artifact for a supported target.
Deploy & run
The local MCR runtime owns the control loop; the service process handles communication.
Observe & recover
Review state and selected history. Retain and recover telemetry within the documented test boundary.
Control and learning have different responsibilities
Deterministic control executes defined rules on time. Signal processing transforms measurements; statistical detection compares them with a baseline. A learned model derives parameters from training data; inference applies those parameters to new data. Training may use a workstation or server. Any local inference needs its own resource and timing validation and must remain outside motor loops and independent machine protection.