About CNC Path Analyzer and contact
Why CNC Path Analyzer was made, how paths are calculated and verified, data handling principles, operator information, and how to ask questions or report errors.
Why it was made
NC programs consist only of numbers and letters, so even experienced people find it hard to review long programs by eye. Dedicated CAM or simulation software is expensive and needs installation, which is a burden for a quick check on a shop-floor PC or a smartphone.
CNC Path Analyzer was built as a lightweight tool where "you paste a program and immediately see the path". All it needs is a browser, and there is also an Android app that uses the same engine.
Main features and what the tool cannot check
- It does: interpret supported G-codes and cycles, draw the path, link it to source lines, flag lines that need checking and calculate a reference machining time.
- It does not: send programs to machines, judge collisions or approve machining. It also does not guess and draw unconfirmed controller behavior.
How it is verified
We do not collect or publish production NC programs from users or customers. When a feature is added, its expected coordinates, number of moves and error classification are first fixed in tests using independently written synthetic programs, and the same tests are run again every time the engine changes. The path drawings in the Learning Center are also recalculated with the same engine every time the pages are built, so the articles and the tool never disagree.
Web and Android app
The web tool and the Android app share the same interpretation engine. When an interpretation rule is changed on one side, the same regression tests are run on both to confirm the results match before release. The web version is handy because it needs no installation; the app makes it easy to open NC files stored on your smartphone.
Data handling
NC text and path calculation are processed inside your browser and are not uploaded to our servers. Your work and settings may remain in the same browser's storage and are deleted when you clear the browser data. Details, including advertising and cookies, are in the privacy policy.
Operator
The operator is Hyeon, an independent developer. Unverified career history, qualifications or customer cases are not shown.
The Learning Center articles are written by the operator, and every example program in them is reinterpreted with the same engine as the tool before publication to automatically confirm that the numbers in the text and the drawings agree. Where controller manuals differ, we do not make claims about a specific manufacturer but state the scope, such as "many controllers" or "the FANUC family", and point out where readers should check their own machine manual.
Questions and error reports
Email: cjh8838a@naver.com. This is a service run by an individual, so replies may take a few days; messages are handled in the order received. We welcome questions about using the tool, technical errors in Learning Center articles, cases where the path is drawn differently from the machine's behavior, and suggestions for controllers and cycles you would like supported.
| Information to include in an error report | Example |
|---|---|
| Web version and browser/device | Version shown at the top of the screen, Chrome / Android |
| Machine settings | Lathe, FANUC, display coordinate system X-Z |
| Expected behavior and what was shown | The last G72 pass should go down to Z-14 but stops |
| Minimal synthetic NC | 10–20 lines that reproduce the problem, with coordinates you made up |
| Warning text | The wording of the cause line and the cycle call line |
How inquiries are handled
Inquiries are used only to reply and solve the problem, and are deleted within one year after the reply. Fixes resulting from reports are recorded in the changelog without personal information. Retention exceptions and how to exercise your rights follow the privacy policy.