Currently supports the Fanuc dialect (including the common command sets of Fanuc-compatible controls from Mitsubishi, Brother, Haas and others). Need another controller? Tell us →
You can also use a built-in sample. Each one was either written by us or generated from the rule stated in its header — none of them is customer code:
These are configuration templates —
every number in them is inferred from a machine class. None of it is measured
from any real machine.
Load your own file and the result starts reflecting your machine:
build one on the machine file page, or
download a blank template.
Machine files are not uploaded either.
Where the parameters come from →
The report will show this machine's name and calibration level.
If you fill in an existing estimate, the report shows a line-by-line difference rather than just comparing totals. It can come from anywhere — your CAM's built-in estimate, another simulator, or a machinist's judgement.
Paste your CAM or current figure into the existing-estimate field above and the difference shows up here.
Click any segment of the 3D path.
This is an estimate, not a guarantee. Accuracy depends on where the machine parameters came from, and every report states the source level used. Do not make it your only basis for a quote, a schedule, or acceptance. Full disclaimer and data policy.
The scope is motion behaviour and cycle time, the Fanuc dialect is supported for now, and this page caps at 100 MB. How the engine computes, the parameter source levels and a note on accuracy are on About.
If the estimate is far from your measured cycle time, that data point is the most valuable thing you can send us — send one and it is four fields, no NC program needed. For anything else use Contact (anonymous is fine) or contact@nccyclesense.com.