How to use and support scope

Import a file, confirm the machine and coordinates, then view the toolpath. Compare source blocks with the path; save edits and export an NC copy. Only supported lathe and milling syntax is interpreted. H and MPF display interpretable XYZ paths, not full five-axis machine motion, cutter compensation or collision safety. Verify with the controller and established procedures before operating machinery.

CNC Path Analyzer is an independently developed app for visualizing CNC program paths. Support refers to previewing verified program syntax; it does not guarantee machining or collision safety on a real machine.

The workbench and public guide are provided on the same site; advertising is not isolated on a separate origin. Advertising and external tracking scripts are currently inactive, and empty ad areas are hidden. NC text and path calculations stay in the browser and are not uploaded to the operating server.

1. Start with files and the demo

In Program, select Load file or drop a file onto the text area. The limit is 2MB per file. NC/TXT, extensionless text and H/MPF inputs are accepted; accepting a format does not mean every controller command is supported. Check the decoded characters and lines. Export existing work before replacing it.

O1000 is an independently created synthetic visualization demo with G71/G70, C-axis indexing, an XC contour and a spiral. Never run it on machinery. Previously saved browser work may be restored instead of the default demo.

2. Choose the machine and read the path

Select View toolpath and choose lathe or milling to match the program. Lathe X diameter commands are displayed as radial distances. Use XZ for turning profiles and XYZ for paths including Y. Inside G12.1/G13.1, C is a virtual linear coordinate, not an ordinary rotary C angle.

Fit the path with Show all, then use Play, Pause and block stepping. Turn preview off to reveal movements during playback. Double-click an execution row to seek to it. Start here in a tool layer seeks to that tool’s starting position.

3. Variables, subprograms and editing

Load external programs into slots 1–5. M98 matches the O number inside the program, not the filename or slot. Variables are shared across the supported main/subprogram execution flow. Undefined variables currently evaluate to zero; this is not evidence of the value stored in a real controller.

G10 blocks and standalone #700 assignments are silently skipped; G10 offsets are not applied. This does not discard coordinate/feed expressions referencing #700 or the entire #701–#799 range. Enable editing in the execution panel and Save to synchronize the Program tab. Keep a separate original.

4. Check estimated machining time

Open Machining time and review tool results, feed and spindle conditions. G97 uses specified RPM; G96 depends on cutting speed and diameter, with the G50 spindle limit affecting RPM. Feed per minute and feed per revolution must not be confused.

If — is shown, check feed mode, F/S values and unsupported sections. Feed distance is NC path length, not contact distance or removed volume. Rapid/dwell settings, actual acceleration, tool changes and machine-specific actions affect real duration. The result is an estimate, not a guaranteed cycle time.

5. Limits and troubleshooting

This tool does not control machinery or certify collision/machining safety. It does not reproduce every controller cycle, offset, reference return or macro. H/MPF input and rotary-axis views do not fully emulate actual five-axis TCP, pivots or tool length.

For unexpected paths, check machine type, coordinates, source, called O numbers and missing variables. Ignoring an error can omit movements. Restart the tutorial from Settings help and change language in the language menu. Send only short synthetic reproductions, never confidential production NC.

6. Current website, privacy and advertising

The workbench and public guide are provided on the same site; advertising is not isolated on a separate origin. Advertising and external tracking scripts are currently inactive, and empty ad areas are hidden. NC text and path calculations stay in the browser and are not uploaded to the operating server.

Work and settings may remain in the same browser. Clearing an editor does not clear all site data. Export needed files before deleting site data in browser settings. Cloudflare may process connection data for delivery/security. Support emails are deleted within one year after the final response, subject to legal retention exceptions described in the privacy policy.