Your machine — a kind in the line twin
The mechanism, channels and example program of your machine are described once. The buyer puts it into their line on screen and runs a test in the browser.
A machine is described by data, not code
- One mechanism for all instancesEditing the mechanism changes all machines of the kind; the numbers of a specific machine are on the instance.
- Channel datasheetAxes with roles, inputs and outputs with clear labels on the operator screen.
- Example programIts motion values are taken from the mechanism limits, not invented.
- PackML unit interfaceWith it the machine joins a line project on a par with its neighbours.
- A parametric typeDimensions, travel, drives and tooling are set as numbers — the configuration is assembled from the twin.
The machine in their line — before it arrives
Test run
Product, conveyor, sensors — in the browser, without a test bench.
Links to neighbours
Unit tags are connected on the project graph.
The logic is open
IEC 61131-3: the buyer’s commissioning engineer reads and edits it.
Four parts of the description
- MechanismLinks, joints, limits, sensor points — from your STEP assembly or an open mechanism description.
- Channel datasheetAxes with roles and drive mode, inputs and outputs with roles: what a port does, what a sensor knows.
- Example programA cycle in SFC or ST; its motion values are taken from the mechanism limits.
- Unit interfacePackML states and tags, phases with parameters — the machine joins a line project on a par with its neighbours.
Numbers are marked
A datasheet number and a number measured on the machine are stored with their source; a typical template number carries a “typ.” badge.
Variant — by settings
One machine comes in different variants: jaw drive, tool change method. The variant is chosen in the card, and the signals follow from it.
Geometry and licence
The library shows only kinds with their own geometry or under an open licence; terms for showing your geometry are agreed separately.
Manufacturer questions
Can the buyer try the machine before buying?
Yes: the unit test run starts in the browser — product, conveyor, reset, sensors — without a test bench and without installing software.
What happens to the buyer’s changes when the kind is updated?
Each channel remembers its source: what the kind brought and what the engineer added by hand. Additions are not lost on update.
How does the machine connect to the buyer’s line?
Through the PackML unit interface: states, Command and Status tags, phases. The line project connects it to its neighbours with wires on the “Graph”.
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