The line runs on your network
Units, their programs and the links between them live on the box in your shop. The cloud is for design, configuration release and updates.
The line runs on your network
- Units on the box in your shopThe box (Ryzen 7 PRO, real-time OS) hosts virtual real-time controllers. It runs the unit programs (IEC 61131-3, SFC, PackML), the message bus and the simulator for commissioning; units talk to each other locally.
- No inbound portsThe box connects to the cloud only through an outbound secure connection. No public IP or port forwarding is needed.
- Signals straight from the boxAn engineer on the same network sees line signals straight from the box, without the cloud. Access requires a signed token issued after sign-in; an outsider on the plant network gets nothing.
- Cloud: design and releaseDigital twin, programs, unit debugging in the browser, configuration release and updates.
One copy of the unit — from screen to servo drive
Twin
The simulator is built from it and the controller configuration is printed from it.
Programs
Logic in IEC 61131-3, cutting and motion programs.
Simulator
Product, conveyor, sensors — through the same input as on site.
Screen
Run in the browser; next to the real line, its shadow in the simulator.
The whole vertical
- One copy, not twoThe model for verification and the controller configuration come from one twin.
- Browser → twin → controller → servoThe whole path of the program — in one platform.
- Open standardsIEC 61131-3, ISA-88/PackML, AutomationML, EtherCAT, CiA 402.
- Cloud or your perimeterThe platform also runs on your servers.
What works and what is worked out in the implementation
| Capability | Status |
|---|---|
| Unit test run in the browser | works |
| Simulator next to the controller, sensors through the same input | subject of the implementation |
| Line shadow on real drives | subject of the implementation |
| Virtual units started by a neighbour's sensor | subject of the implementation |
Site, cloud and browser
| Place | What runs | What follows from it |
|---|---|---|
| Site | The box is a computer next to the equipment: isolated virtual machines with a real-time loop and their own EtherCAT port; drives, I/O, machine-side panel | Real time is computed next to the hardware; the machine is controlled even without an external network. Box facts — “Box and requirements” |
| Cloud | Program development, compiler, runs on virtual axes, remote tests on a test bench with drives | Programs are written and checked without a trip to site |
| Browser | Twin, program labs, drive commissioning, unit test run | A window both ways: to the site and to the cloud |
What crosses the cloud boundary is intent — the program and the “run” and “stop” commands. Jog and raw drive commands stay at the equipment.
The twin is the single source of truth
The configuration is generated
Axes and limits, drives, tooling, tools, zeros — in the twin. The control configuration is not written by hand: change a field and the next start goes to the test bench with it.
An edit on the test bench is a second truth
A file edited by hand on the test bench itself disappears at the next start. That is why edits are made in the twin, where everyone sees them.
A number has an origin
Datasheet and measured numbers are stored with their source. The platform does not pass a datasheet value off as a measurement: “from the datasheet, not verified by touch” is a normal field state.
Mechanism and instance
A mechanism is a reference body model: links, joints, limits. An instance is your machine: its axes are bound to profiles, it carries tooling, it has a place.
Two modes of one twin
Virtual axes — drives stand still, blocks pass. Drives — commands go over the bus. The mode is chosen explicitly; the platform never switches to “drives” silently.
A green run is not proof
An axis with no assigned drive moves in simulation just like a real one. The screen states this on a separate line.
What the platform is built from
Equipment twin
Machines, robots and line units in 3D, programs and their runs.
Line automation
Units with channel roles, a line project, links on the “Graph”.
PLC programs
SFC and ST under IEC 61131-3, lab, PackML states.
Drives and commissioning
EtherCAT bus, CiA 402 profiles, oscilloscope, panel at the machine.
CNC machines
Cutting programs from the part, material removal simulation, checks before start.
Robots and tooling
Motion verbs across cell places, refusal instead of a guess.
Process physics
Friction, mass, inertia, beam sensors.
Virtual commissioning
The program is verified before the equipment arrives.
Line shadow
The line runs in parallel in the simulator: same commands, differences visible at once.
Discuss an implementation
Describe the unit or line — we will tell you what we will verify and in what time. Target indicators are fixed in the implementation specification.
Request access