Scripting

How a HiNC session is driven from C#: the command surface a script is written against, the step objects a run produces, and the message stream it reports through. The same commands run from the app's script panels, from inside an NC comment, and from a hosted session, so this section describes the surface rather than the screen.

Ordered the way a script meets them — the language and its global scope first, then what a run produces and how it reports, then the one input that is not G-code.

Writing a Script

• Script Command — The C# syntax, the session lifecycle a command runs inside, ;@ commands embedded in NC, and the [NcName] output template
• SessionShell — The global scope every command resolves against, mapped family by family onto the work each family does

What a Run Produces

• Step — The computation unit, one spindle revolution by default: its custom variables, and how a script reads and exports it
• Step Field Reference — What each group of per-step output covers, and the two values that are most often misread
• ShellProgress — The four message severities, tag filtering, and exporting a session log

Playing Something Other Than G-code

• Cutter-Location (CL) Playback — Replaying a CAM cutter-location file before it is post-processed, and what the chain choice decides

See Also

• Milling Physics — what the per-step values a script exports are measuring
• NC Optimization — the optimizer that the Opt* settings on this surface drive