Fan CNC Machining: What the Controller Does to Your Part

• 1
  Key takeaways
• 2
  How fan CNC machining executes a toolpath
• 3
  Work offsets and tool offsets in fan CNC machining
• 4
  When macro variables save real money
• 5
  Why 5-axis fan CNC machining needs kinematic data
• 6
  Alarms, overtravel, and the limits of the control
• 7
  Which setup fits your part

Every fan CNC machining cycle starts the same way. The CAM system posts a text file of G-code blocks. The control reads ahead, fills its buffer, and converts each block into servo commands for X, Y, Z, and any rotary axis. What matters to your part is not the language itself but how fast the control can process blocks and how far ahead it looks. A control that only sees two blocks ahead will slow down in a corner even if the programmed feed rate says otherwise.

This is why the same toolpath can run at different speeds on different machines. Look-ahead, sometimes called block processing time, is quoted in milliseconds per block. A control that processes 1,000 blocks per second can hold feed through a dense 3D surface where an older control stutters. The visible result is not just cycle time. It is also surface finish on curved walls, because a stuttering control leaves dwell marks that no amount of polishing fully removes.

For the engineer sending a model out for quote, the practical question is whether the geometry needs that continuous processing. A part made of flat faces, drilled holes, and a few pockets will run well on almost any current control. A part with organic curves, thin ribs, or a blended fillet that runs into a wall is where look-ahead and servo tuning start to matter.

One number worth asking about is the smallest programmable increment. On our 5-axis centers the rotary table is Ø400 mm, and tolerance holds at ±0.005 mm. Those two facts together mean the control must resolve very small angular moves to keep a cutter on a curved wall. If the increment is coarse, the machine will round off corners that the model shows as sharp.

• 1
  Look-aheadMeasured in blocks per second. Higher means smoother feed through dense toolpaths.
• 2
  Servo tuningMatches the drive to the load. Poor tuning shows up as chatter on corners.
• 3
  Program incrementThe smallest move the control can command. Coarse increments round off sharp transitions.

A machine does not know where your part is. It knows where its axes are. Work offsets bridge that gap. When a setup technician touches off a vise or a fixture, the control stores the distance from machine zero to part zero. Every programmed coordinate is then measured from that stored point. Get it wrong by 0.1 mm and every feature on the part shifts by 0.1 mm, even though the toolpath is perfect.

Tool offsets work the same way in the other direction. Each cutter has a length and a radius that differ from the nominal value. The control adds those differences to the programmed path. On a 5-axis job the radius offset becomes more involved, because the cutter is no longer always perpendicular to the surface. The control has to apply the offset in the tool axis frame, not the machine frame.

This is where most scrap on complex parts comes from. Not from a bad model, but from a stale offset. A tool change that was not re-measured, a fixture that moved after clamping, a thermal shift after four hours of cutting. The control will follow the numbers you gave it, right into the fixture.

We handle this with in-process probing and a first-article check before the run continues. Raw material is verified on receipt, dimensions are monitored during the cut, and every part gets a final inspection before shipment. Reports are available on request. That sequence catches offset drift before it becomes a batch of scrap.

• 1
  Work offsetMachine zero to part zero. Set once per setup, verified with a probe.
• 2
  Tool length offsetRe-measured after every tool change on tight-tolerance jobs.
• 3
  Cutter radius offsetApplied in the tool axis frame on 5-axis work, not the machine frame.

Macro programming lets a program calculate instead of just execute. Instead of hard-coding a hole pattern at fixed coordinates, the program reads a variable for hole count and spacing, then loops. Change the variable and the same program cuts a different part. For a family of brackets that differ only in length and hole count, this removes a whole class of programming errors.

The gain is not only engineering time. A macro-driven program is easier to verify, because the logic is in one place. If the pattern is wrong, it is wrong the same way on every part, and the first article shows it. A hand-edited program for each variant hides errors in the places nobody re-reads.

Macros are also used for probing routines, tool breakage checks, and pallet scheduling. These are housekeeping tasks that do not change the part geometry, but they change how confidently a shop can run unattended. A probe that checks a datum after clamping and updates the work offset can absorb small fixture variation without an operator standing at the door.

Not every job needs this. A one-off prototype with five holes gains nothing from a macro. The break-even comes when a part repeats, or when a family of similar parts shares a fixture. Below that threshold, plain G-code is faster to write and easier to debug.

On a 3-axis machine, the relationship between the tool tip and the part is simple. Move X and the tool moves in X. On a 5-axis machine with a trunnion and a rotary table, the tool tip position depends on the angles of both rotary axes. To place the tip correctly, the control needs to know where the rotary centers sit relative to the spindle, and how far the pivot points are from each other.

Those numbers are the kinematic model. They are measured when the machine is installed and after any crash or major service. If they drift, the tool tip follows a path that is offset from the one in the CAM file. The error is not constant. It grows as the rotary axes tilt further from zero, which is why a part can be perfect on top and out of tolerance on a steep wall.

This is the difference between indexed 5-axis work and simultaneous work. Indexed work positions the part at an angle, locks the rotaries, and cuts with three axes. Kinematic error barely matters because the rotaries are not moving during the cut. Simultaneous work keeps all five axes in motion, and the kinematic model is used on every block.

For the buyer, the useful distinction is this. If your part has features on five faces but each face is machined flat, indexed work will usually hold tolerance with less setup risk. If your part has a curved surface that wraps around the part, or a port that must be blended into a contoured wall, simultaneous work is the only way to cut it in one pass.

• 1
  Indexed 5-axisRotaries lock during the cut. Simpler, lower risk, more setups per part.
• 2
  Simultaneous 5-axisAll axes move together. One setup, better blends, stronger kinematic dependency.

Most alarms that stop a run are not mysteries. Overtravel means an axis reached its soft limit, usually because a work offset is wrong or a fixture is taller than expected. A servo alarm often points to a load spike, which can be a dull tool, a chip pack, or a feed rate that is too aggressive for the material. A spindle alarm may be a temperature threshold or a drive fault.

The control reports what it sees. It does not know why. That is the job of the setup sheet and the operator. A shop that records the alarm number, the block it occurred on, and the offset values at the time will solve the next occurrence in minutes instead of hours.

There are also hard limits the control cannot work around. Maximum processing size on our machines is 4,000 mm, with travel of 4,000 × 400 × 150 mm on the largest platform. Rotary work is limited by the Ø400 mm table. A part that needs more swing than the table allows has to be repositioned, which adds a setup and a re-datum.

Tool access is the other boundary. A deep pocket with a small corner radius may be geometrically possible but practically unreachable, because the holder shank contacts the wall before the cutter reaches the floor. This is a tooling constraint, not a controller constraint, but it shows up in the same place: the part does not match the model.