How it works

What it simulates

A ten-machine CNC job shop in four cells, read by one Litmus Edge over each controller's own protocol: Sinumerik over S7comm, FANUC over FOCAS2 and Heidenhain over LSV2, on five DeviceHub drivers with no gateway in between. 300 tags.

Tool wear is computed on the Edge, not in the machine. The Edge carries each machine's tool table and handbook cutting data, works out the cutting speed, feed per tooth and the load a sharp edge would draw, and from the gap to the measured load, the wear, the life left and a verdict.

• an isometric shop floor by cell, with each controller's data path into the Edge
• every register on a machine, side by side with what the Edge read back

What it configures on Litmus Edge

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

• 10 DeviceHub devices across five drivers
• 6 Digital Twin models, one per controller type, with 10 instances
• 6 Analytics groups: unattended stop, feed override cost, cutting data, axis load trend, spindle utilisation, and the live values the page reads back

Scenarios you can inject

• A lights-out stop nobody sees until the morning shift, priced at the machine's hour rate
• The feed turned down instead of a tool change, with the dollars an hour lost and nothing alarming
• A broken end mill cutting air while the program runs on
• Way lube starvation read off the Y drive load before the controller alarms
• Tool life thrown away on a counter by a program proven slow years ago