Body shop framing line

An automotive body shop framing line running at 55 second takt, one body at a time, with per-VIN genealogy: three respot cells, a torque station, a gauge station and end of line. Seven devices and 181 tags.

This is the only solution here that speaks two industrial protocols at once, and that is the point rather than a complication.

Both ports must be reachable from the Edge. Publishing only the Modbus port leaves the torque station unreachable behind a solution that otherwise looks healthy.

Seven DeviceHub devices covering the three respot cells, the torque station, the gauge station, end of line and the underbody supply, with 181 tags. A Digital Twin model and instance per station. Analytics groups behind the containment, weld quality and takt figures.

Download automotive-body-shop-demo-0.6.1-amd64.tar.gz from the solution's page on portal.litmus.io. The archive is the container image, not a source bundle, and needs no registry access.

docker load prints the image it added, which is the one the files below name:

Save this as docker-compose.yml:

Or, without Docker Compose, run the same image with the same .env:

Flags given with -e take precedence over .env, so change APPLY_ON_START or EDGE_VERIFY_TLS on the command line rather than in the file.

Open http://localhost:4014.

The page stays on its waiting panel until the Edge carries this solution's devices. That is deliberate: the simulation does not tick and no value is shown until Litmus Edge is verified to hold the devices and poll them, so nothing on screen can be mistaken for data that never made the trip. With APPLY_ON_START at its default of 1 the solution configures the Edge itself on startup, which takes 30 to 60 seconds. If you set it to 0, or the apply failed, press Apply to Edge in the page header.

This solution can also publish its 7 Digital Twins into Litmus Unify, one message per asset under litmus/assembly-plant-01/.... It stays off until two things are true: the UNIFY_ values above are set, and the Litmus Edge has a Litmus UNS connector, which the Solutions provisioner can pair in one click. The next apply then publishes the twins, the page header shows how many are arriving, and removing the solution from the Edge removes its branch from Unify as well. Leave the values empty to keep Unify out of it.

The six stations across the top with their live tags, cycle time against takt, and job per hour. Below them, bodies moving down the line with their VINs, and the buffers between stations.

Each body carries its own genealogy, so a fault introduced at one station can be followed to the vehicles that passed through it while the fault was present.

Faults include electrode wear running away in cell 2, the spindle drifting out of the torque-angle window, a robot fault that holds the line, a shifted framing fixture, and the underbody supply starving cell 1.

Use Clean up in the Solutions provisioner to remove what it created on the Edge.

[email protected]