Running a Simulation
Everything that happens after the equipment is set up: writing the list of commands a run executes, playing it, watching it, and reading what it did.
The Execution page at /execution is where all of it happens — it is also where the application
opens.
Ordered as a run goes: build the list, play it, watch it, read it, and diagnose it.
Pages
- Building a Mission — The command list a run executes, and the checkbox on each command that decides whether it runs
- Playing a Program — The two commands that put NC code into a run, and which to use when
- The Other Commands — The settings, optimizer and output kinds, and the script command: what each is for and where in the list it belongs
- Starting and Stepping — The transport controls, the F5–F8 keys, and why one line is not one step
- Watching the Run — The canvas, and the three charts that show the whole mission at once
- Inspecting a Step — The Step Info column: the sentence, the step, the engagement and the per-revolution charts
- The Program Branch — The files a run read, the passes it made over each and what every line produced
- When Something Goes Wrong — Which of the four message lists answers which question, why a row is not an occurrence, and three things that look like faults and are not