Sysmac Studio · NJ/NX · the laptop dress-rehearsal
Simulation & Digital Twin
A controller does one stubborn thing, forever: read its inputs → solve its logic → write its outputs, a few thousand times a second. Simulation rips that loop out of the steel cabinet and runs it on your laptop. A digital twin hands it a virtual machine to push around. What's below isn't a diagram — it's a working filling line. Run it, wind it to 20×, and jam the valve on purpose.
🧠 the brain, on a PC🏭 a virtual machine⏩ faster than real life
🎭
01 · The living line
One machine, watched three ways at once
Here's the whole point of simulation in one picture. The same running program drives three windows in lockstep: the machine moving, the I/O signals flickering true/false, and the logic deciding what to do next. Hit play and watch a bottle roll in, the photo-eye catch it, the valve pour, and the line index on. Nothing here is wired to anything real.
👀 Watch the link: when BottleAtFill flips to TRUE, rung R2 lights, FillValve goes green, and only then does liquid pour. Machine, signals, and logic are never out of step — because they're all the same program. That is what "running in simulation" actually feels like.
02 · The cheap mistake
You just broke a machine and it cost nothing
Hit ⚡ Jam the valve above and watch what happens: LevelFull goes TRUE, R3 tries to shut the valve — but it's stuck open. The bottle overflows, the spill counter climbs, the line locks up. Now imagine that on the real plant floor: sticky syrup over a €90k machine, a stopped line, and a very bad afternoon. Here it's a number you reset with a button.
🐛
A bug caught here is basically free
The same defect costs minutes on your laptop and can mean wrecked product, downtime, and a callout on the real line. The overflow you triggered above? That's the whole pitch in one click.
€0
🔁
It is the real scan cycle, not a cartoon
The controller you watched read inputs, solved the rungs, and wrote outputs — exactly the loop the physical NJ/NX runs. Logic proven in simulation behaves the same when the hardware shows up.
read→solve→write
⏩
You can bend time
At 20× you tested minutes of production in seconds — and you could just as easily slow down to inspect a single scan. Try forcing a jam at 20× and at 1×; same bug, two ways of seeing it.
20×
🧯
Rehearse the disasters safely
Jams, sensor failures, e-stops mid-pour — every nightmare you'd never dare provoke on real steel, you can fire at will here. Nobody gets hurt and nothing actually breaks.
no risk
03 · The real vocabulary
"Simulation" and "twin" aren't the same word
Engineers don't say "running without hardware" — they say where the real bits sit. It's a ladder called X-in-the-loop: as you climb it, more of the setup becomes real and the test gets more trustworthy. Tap each rung.
The thread through all three: a model of the machine feeding inputs back to the controller automatically. Plain simulation needs you to fake those inputs by hand — a twin generates them itself. That feedback loop is the whole difference.
04 · Check yourself
One that separates the two
Your virtual line filled a bottle, the photo-eye tripped on its own, and the valve opened — all with no clicking from you. Which setup were you running?