Your line on screen and programs
Machine, robot or line — in 3D, right in the browser: the process engineer and commissioning engineer develop and verify programs remotely on a virtual model and on real equipment; control runs on your site.
The error is seen on screen, not on the machine
Visible before purchase
Your machine and its working area in 3D: axis strokes, part and tool position, cycle bottlenecks — before buying equipment.
The program describes the part
Coordinates are set from the part, not the machine. Changing the machine changes how the path is executed, while the program text stays the same.
Control — from the model
Control settings are taken from the description of your machine on screen, not rewritten by hand on the side. One value — in one place.
First module: from the task to a verified program
Next, the program goes to line automation and to your drives — the other modules in the diagram are clickable.
What exactly the engineer gets
Your machine in the browser
- What is modelled
- A machine, robot, line unit or the whole line: axes, their strokes and speeds, the working tool, the part.
- Where it opens
- In the browser, with no software installed on the workstation.
- Equipment types
- Milling, 5-axis and turning, welding, machine tending, palletizing.
- Platform scale
- 11 machine and robot types are described on the platform synctwin.ru, September 2026
Two kinds of programs
- Machining
- Part program: the tool path and orientation are set from the part.
- Motion
- Path of a robot or mechanism, logic of unit steps.
- Portability
- 1 program text — on a 3-axis, 5-axis machine and a robot synctwin.ru
- Zero and setup
- The part zero and position are set in the setup, not in the text: shifting the blank does not change the program.
Commissioning before the equipment arrives
- Promise
- The program is verified on the model of your machine before the site visit.
- How it works
- Machine model → program run: line and path on screen → the same twin sets the control settings.
- What you get
- A program is rejected only when it is physically impossible — with the reason: axis stroke, unreachable pose.
- After start-up
- The same screen shows the actual position from the drives.
- Next
- Virtual commissioning and line shadow →
Stage “Model and cell layout”
- Timeline
- In the implementation contract
- Result
- The line’s cells in the twin with browser access — the first act of the implementation.
- Price
- Per line cell, minimum 3 cells — in the “Implementation” block below on this page.
Compatibility — by open specifications
| Standard | What we follow | Where it is verified |
|---|---|---|
| EtherCAT | bus for drives and couplers; the master brings slaves up to OP | works on the test bench |
| CiA 402 | drive profile: states, CSP and CSV modes; servo drives from different manufacturers on the test bench | works on the test bench |
| IEC 61131-3: ST and SFC | unit logic; compiler check; execution on the test bench | works on the test bench |
| PLCopen Motion | axis motion blocks in the unit program | works |
| ISA-88 | unit model: a unit of modules, a module of channels | works |
| PackML | unit states and Command/Status tags | works |
| AutomationML | line project export; import in external systems is a subject of the implementation | export available |
| CANopen | drive on the test bench: travel measured | verified on the test bench |
For an integrator this means: the logic, bus and drives of your line can be read, verified and maintained by open specifications.
Key points for this module
- Verification before start-up— the program and the line run on the digital twin of your machine; control is configured from the twin, not by hand.
- Machines, robots and the line in one window— milling, 5-axis and turning, welding, machine tending, palletizing.
Discuss an implementation
Your line or machine: what you need to see before purchase.
Model on screen and program runs within an R&D stage.
Indicators from the R&D report — published with your consent.
Questions about the module
Can we take only this module?
The implementation is priced by line cells, minimum 3; the first act is the model and cell layout on screen. The next stage follows the result of the act.
What do you need from us for the model?
Line composition or machine datasheet, working area, a part or a sample program. The exact list of input data is fixed in the implementation specification.
Is the model a picture or a working system?
A working one: the program runs on the model of your machine, and when started on the equipment the same screen shows the actual position from the drives.
Where does it run?
Inside the enterprise perimeter — on your servers; the model opens in the browser inside your network.
Implementation under an R&D contract
Line virtual commissioning implementation: price per line cell, minimum 3 cells; payment in stages by acts.
- Model and cell layoutYour line’s cells in the twin: mechanisms from the library or from your STEP, layout on the site.
- SFC logic and cycle timeThe cells’ SFC program is run on virtual axes; the line cycle time comes from the run.
- Report and run videoA report on conflicts and reachability and a video of the line run.
A cell is a line unit (an ISA-88 unit). Scope — mechanisms from our library or the customer’s STEP, no modelling from scratch.
Implementation price and terms →We will show your machine on screen
Tell us which machine, robot or line — we will reply with the price and timeline of the stage.
Request access