Project objective
The objective was to make CNC camshaft motion data easier to inspect, understand, and communicate. Instead of reviewing raw point-by-point machine data directly, the tool turns motion output into visual plots that reveal cam lobe geometry, grinding paths, and differences between views or operations.
Design requirements
- Parse CNC camshaft motion data into structured information that can be plotted and inspected.
- Visualise cam lobe geometry and grinding paths in a browser-friendly format.
- Support front/rear views, point or revolution counters, and comparison-style inspection views.
- Keep the tool static and shareable without requiring a database, login system, or hosted backend.
- Make dense machine-path data easier to communicate to engineers and workshop users.
- Allow future screenshots or anonymised datasets to be added without changing the project structure.
System overview
The tool uses Python where preprocessing or data transformation is useful, then presents the resulting geometry in a static browser interface. This keeps the workflow simple: parse the data, transform it into structured points, render the plots, and review the result without needing a database or server.
- Input
- CNC camshaft grinding or motion output
- Preprocessing
- Python parsing, cleanup, and data transformation
- Visualisation
- HTML, CSS, JavaScript plotting and inspection views
- Views
- Lobe geometry, grinding paths, front/rear views, counters, comparisons
- Deployment
- Static browser output without backend complexity
- Use case
- Inspection, communication, anomaly spotting, and engineering review
My technical contribution
- Developed the project direction around translating CNC motion output into readable engineering plots.
- Worked on parsing and transforming camshaft motion data into a format suitable for plotting and inspection.
- Built or planned browser-based visualisation views for cam lobe geometry, grinding paths, counters, and comparisons.
- Kept the tool practical for manufacturing review by favouring static output, simple deployment, and clear visual communication.
Technical detail
The engineering value is in translation: machine-path data becomes inspectable geometry. A useful visualiser needs to preserve the important relationships in the data while making shape, motion, and comparison easier to see. This means handling file parsing, coordinate transformation, plotting scale, view modes, counters, and clear labelling.
The static approach is deliberate. For a workshop or engineering review tool, a simple file-based output can be easier to share, archive, and deploy than a heavier web application with login or database infrastructure.
Results and evaluation
The project produced a prototype tooling workflow for converting CNC camshaft data into browser-based engineering visuals. It met the initial objective by making machine-path and lobe-geometry information easier to inspect and communicate. Further evaluation should compare plotted output against known reference geometry, anonymised machine data, and expected grinding-path behaviour.
Visual gallery
Future improvements
- Add anonymised screenshots of the visualiser and example plots that can be shared publicly.
- Document the parsing pipeline with an input-to-output diagram.
- Add validation examples comparing plotted geometry against known reference data.
- Improve comparison views for different lobes, operations, or program revisions.
- Add exportable reports or static HTML bundles for easier sharing with engineering and workshop users.