How it works

What it simulates

An automotive body shop framing line: seven stations welding and fastening one body at a time, 181 tags, over Modbus TCP with a tightening tool controller on Atlas Copco Open Protocol.

Two protocols on purpose. The tool controller's own field names are the domain model, so torque and angle arrive as the controller reports them rather than as numbers somebody mapped by hand.

• station cycle times against a 55 second takt
• weld counts, currents and electrode wear per gun
• torque, angle and result per fastening, tied to the body's VIN

What it configures on Litmus Edge

On startup, and it removes exactly what it created when you are finished:

• 7 DeviceHub devices on the Modbus TCP and Open Protocol drivers, 181 tags
• 5 Digital Twin models covering 7 instances
• 6 multi-input Analytics groups: weld quality, torque window, dimensional, throughput, station downtime, traceability

Scenarios you can inject

• A nutrunner drifting out of its torque window raises the question of which bodies are affected, and the genealogy answers it by VIN rather than by shift
• Electrode wear producing cold welds passes the weld controller's own counters, because those report the schedule that ran and not the joint it made
• A fixture shift or a robot fault moves the constraint on the line, and every station's cycle against takt says which one to work on