← All projects
ManufacturingsimulationPrototype

CNC Machine Program Simulator

An offline browser simulator for a documented subset of Siemens-style multi-axis NC commands and machine visualization.

MY FOCUSDeveloped parsing, state updates, animated toolpaths, configurable machine axes, and diagnostic logging.
HTMLJavaScriptCNC programming3D visualization

ENGINEERING VALUE

Demonstrates manufacturing-domain software design with explicit safety boundaries.

PROJECT SCOPE

CNC visualization and interpretation prototype

Explore the project checks ↗
ENGINEERING STUDY / CNCJS—02

Engineering concept illustration.

01 / THE PROBLEM

The engineering challenge.

NC programs need an accessible way to inspect axis motion and coordinate-transform intent before machine use.

02 / CONSTRAINTS

What the solution must consider.

  • The simulator is not collision-certified, not a complete interpreter, and does not model OEM dynamics or controls.

03 / ENGINEERING APPROACH

Reasoning before geometry.

01

Engineering method

Parse only documented commands, make unsupported behavior explicit, and separate the machine configuration from program state.

02

Workflow features

Subset parser; Multi-axis state; AROT and transform handling; Animated toolpath; Machine configuration; JSONL diagnostics.

04 / DESIGN & IMPLEMENTATION

Connecting intent to execution.

The prototype progressed through the v11 development lineage with an interactive machine and toolpath interface.

  • Subset parser
  • Multi-axis state
  • AROT and transform handling
  • Animated toolpath
  • Machine configuration
  • JSONL diagnostics

05 / VALIDATION

The checks behind the design.

Prototype

The tool supports software exploration of machining sequences. It requires interpreter and motion checks for the selected NC dialect and provides no collision-certified machine verification.

06 / OUTCOME

The value of the work.

Demonstrates manufacturing-domain software design with explicit safety boundaries.

THE ENGINEERING PRINCIPLE

Make the process assumptions visible.

A plan or calculator is easier to trust when its units, quantity basis, setup assumptions and handoff documents are explicit. A numerical answer should be traceable to the inputs and method.

A question for a technical conversation

Which input changes the result most, and how would you compare the estimate with shop-floor observations?

Explore the engineering tools ↗

LET’S BUILD SOMETHING THAT WORKS

Good design belongs
on the shop floor.

Considering a role in mechanical design, manufacturing methods,
fixture design, or estimation? Let’s connect.