Use this guide to decide whether Machinery Twin fits the engineering question in front of you. It shows the workflows it supports today, alongside the boundaries that need a different model or deployment.
A good fit
Connect supported PLC data to a configured machine model and inspect how axes, mechanisms, cams, and state respond to the running program. The connection carries values from the PLC into the twin.
Read the hardware-in-the-loop guideA good fit
Run the same machine model with simulated variables and state machines to explore a sequence before connecting a PLC.
Read about standalone simulationA good fit
Use a kinematic model to make a machine cycle, mechanism, or motion concept visible in a presentation or discussion.
Read about presentation modeNot a current fit
Machinery Twin does not write simulated sensor values back to the PLC. Full closed-loop sensor-feedback testing is outside the current connection workflow.
Use a different model scope
Machinery Twin models geometry, positions, and motion. Use a physics, contact, or process model when forces, loads, material behavior, or process physics determine the result.
Planned
Pro requires sign-in and online entitlement validation. Offline, machine-locked licensing is planned for deployments that cannot connect to the internet.
Discuss offline requirementsYour controller runtime, PLC simulation software, and network setup remain separate from Machinery Twin. Current live connections support Siemens S7, TwinCAT ADS, and OPC UA; PLCSIM Advanced connects directly, while PLCSIM Basic requires a bridge such as NetToPLCSim.
Explore a machine model in the browser, or tell us about your PLC, machine, and the behavior you want to investigate.