GFM G-Code Force Mapper · Spatial Data Mapping Utility

Machining Analysis Utility

Find the exact G-code line
behind a tool failure or part scrap.

Upload your ISO G-code and dynamometer CSV. The tool aligns your force, torque or any user defined data to the toolpath geometry and returns the specific G-code block, XYZ coordinate, and a confidence score, without manual time-offset guesswork.

Launch Web Utility

Input and output

Input
  • ISO G-code file
  • Dynamometer CSV — Fx, Fy, Fz, Mz columns
  • Optional user-defined channel: Any time-series signal including Power, Vibration, Temperature, Acoustics etc.
Output
  • Peak-force G-code line number
  • XYZ location on the toolpath
  • 2D and 3D force heatmap
  • Confidence score with diagnostic breakdown
  • Exportable mapped CSV
Compatibility
  • 3-axis machining
  • 3+2 indexed operations with ISO output
Access
  • Browser-based — no installation
  • Files processed in session memory only
  • No data stored after session ends
  • Works on any device including tablets

Accuracy objectives

01 Late-start and early-finish recording is handled. Forces map correctly even if data logging begins after the cut starts or stops before machining ends. No manual trimming needed.
02 Force data is never stretched to fit the G-code. Stretching the data requires explicit user acceptance and is flagged in the export as reduced-accuracy.
03 Rapid moves are excluded from cutting peaks. G0 traverse blocks are identified and removed. A data spike during a rapid will not be reported as the failure location.
04 Every result includes a confidence score. The score reflects the quality of signal alignment. Low-confidence results are flagged.

Scope boundaries

No simultaneous 5-axis Continuous A/B/C motion is not supported. 3+2 indexed operations with ISO output are supported.
ISO format required Heidenhain Klartext, Mazatrol, and other conversational formats are not supported.
No subprogram expansion Subroutine calls (M98, G65) are not expanded.
No canned cycle expansion Drilling and boring cycles are not expanded into toolpath geometry.
Feed per revolution (G95) not supported Feed is assumed to be G94 (per minute).
No multi-tool segmentation Tool changes are not separated; the full recording is treated as a single pass.
No machine dynamics modelling Look-ahead and corner deceleration are not modelled.
Rapids must be explicitly defined Ambiguous blocks may not be excluded from cutting analysis.

Typical use cases

Tool breakage on a high-value part Cutting data looks correct, but the tool still broke. Upload the post-run dynamometer CSV and G-code to find which toolpath block caused the overload. Applies to 3-axis and 3+2 indexed ISO operations.
Identifying a specific toolpath geometry issue A part scrapped and the question is whether a corner, thin wall, or sudden change in radial engagement caused it. The output is a G-code line number that can be searched directly in your CAM software.
Comparing cutting conditions across multiple runs Same G-code, different tools or parameters. Upload a different CSV each time to compare where peak forces occur and at what magnitude. The custom channel supports user defined input alongside Fx, Fy, Fz, Mz.
First use with no signal processing background CSV column detection is automatic. Defaults produce a usable first result. The summary panel — max force, XYZ location, G-code line — is readable without specialist knowledge and can be exported or screenshotted directly.

Disclaimer and privacy

Technical use

This is a free research and engineering utility. Output is provided for guidance only and does not replace professional engineering judgment, verified CAM simulation, or tooling supplier cutting data. This software is provided "as is" without warranty of any kind. No liability is accepted for machine damage, tool breakage, part scrap, or financial loss arising from use of this tool.

Data processing

Hosted on Streamlit Community Cloud. Uploaded G-code and CSV files are processed in session memory only. No file contents are stored, saved, or transmitted beyond what is required to render results within the session. Data is not retained after the session ends.

Analytics

Anonymous usage metadata — page views, export timestamps, confidence scores, and mapping mode — is collected via Google Analytics (GA4) for product improvement. No personal data or file contents are logged. Opt out using the Google Analytics opt-out browser add-on.