CNC G-Code Sender Software: Kcam4, Mach3, Alternatives Compared

Overview: The G-Code Sender's Role in a Small CNC Shop

A G-code sender (often called a motion controller, CNC driver, or machine interface) is the application that converts a text-based G-code program into real-time step and direction pulses, spindle commands, coolant outputs, and limit-switch monitoring for a CNC mill, router, lathe, or plasma cutter. In a one-person basement shop, a job shop with a single knee mill, or a prototyping lab, the sender is the piece of software that determines whether a CAM-posted program actually runs on the machine.

Small operators routinely evaluate G-code senders against three constraints:

• Strict compatibility with the G-code dialect produced by their CAM tool or hand-written offline.
• Native support for tool-length compensation and cutter-diameter compensation (cutter comp).
• Hardware support for the existing motion controller (parallel port breakout board, USB motion controller, or industrial CNC like Fanuc).

This reference compares the senders most often considered by small-shop operators—Kcam4, Mach3/Mach4, and commercial CAM/controller packages such as GibbsCAM—and frames a selection path for the case where free software is no longer adequate.

Common Failure Modes with Kcam4 and Legacy Senders

Kcam4 is a long-running Windows CNC controller that became popular for hobby and light-commercial routers and mills driven off the PC's parallel (printer) port. Operators who migrate from Kcam4 frequently report the following symptoms when consuming G-code generated on a modern CAM system:

• Trailing whitespace, line numbers, or BOM characters that were tolerated by older senders cause Kcam4 to misinterpret or skip blocks.
• Modal commands (G90/G91, G20/G21, G54–G59 work offsets) left in default state behave differently than the CAM post assumes.
• Tool-change codes (M6, T1, T2) and coolant codes (M7/M8/M9) that the CAM post emits as a matter of course are ignored or trigger a controller stop.
• File transfer through removable media can introduce CRLF/LF mismatches or rename the file to a short DOS 8.3 form that breaks manual re-loads.

Tool Compensation (Cutter Comp) Implementation

Tool compensation is the single most-requested feature when an operator moves from hand-tuned conversational programming to CAM-driven work. Two distinct features are commonly conflated:

Both Kcam4 and Mach3 implement G41/G42/G40 and G43/G49 when configured with an active tool table. The difference is in workflow: Kcam4 exposes the tool table through a single dialog, while Mach3 separates tool-table entries (Tools → Tool Table) from fixture offsets (Config → Fixtures). GibbsCAM handles compensation internally during toolpath simulation rather than relying on the controller's G41/G42 implementation, which can mask controller bugs but limits post-processor portability.

Software Comparison Matrix

Mach3/Mach4 Setup Considerations

Mach3 is the most common destination for operators leaving Kcam4 because it accepts the same parallel-port breakout boards and shares the same step/direction signalling. The setup pain reported by users new to Mach3 is concentrated in five areas:

1. Driver installation order. The Mach3 parallel-port driver must be installed before any Windows update overwrites the LPT1 resource. On 64-bit Windows, the legacy driver requires the "Mach3 Driver Signing" step documented on MachSupport.
2. Kernel frequency. Mach3's pulse engine runs at a configurable kernel rate (typically 25 kHz, 45 kHz, or 100 kHz). A kernel rate that exceeds the stepper driver's maximum pulse rate produces missed steps. Start at 25 kHz and only increase after validating stepper performance with a dial indicator.
3. Pins and ports mapping. Each output (Step Pin#, Dir Pin#, Active Low) must be entered for every axis and every input (limits, home, probe). Mis-wired enable pins are the single most common cause of "the motor just sits there" complaints.
4. Motor tuning. Velocity (steps/sec) and acceleration (steps/sec²) are derived from the leadscrew pitch, microstepping, and desired rapids. A useful field formula: steps_per_mm = motor_steps_per_rev × microsteps / leadscrew_pitch_mm. Velocity in mm/min equals steps_per_mm × steps_per_sec × 60.
5. Tool table population. Tool length must be measured with a probe or paper-shim method and entered into the tool table, not hard-coded as a G43 H## value in the program, otherwise every tool change requires a program edit.

Parallel Port Controller Hardware Notes

The parallel port (IEEE 1284) became the de-facto hobby CNC interface because it provides 8 data, 4 control, and 5 status lines driven directly from the PC, with sub-microsecond latency on legacy hardware. Modern UEFI-class desktops and laptops no longer expose parallel ports, so most parallel-port retrofits in 2025 use:

• PCI or PCIe parallel-port add-in cards (recognized in Mach3 as LPT1–LPT4).
• External USB-to-parallel adapters based on the MosChip MCS7715 chipset (recognized inconsistently).
• External motion controllers that emulate the parallel-port protocol over USB or Ethernet (SmoothStepper, ESS, PoKeys57CNC).

If a parallel-port retrofit must be replaced because no LPT is available, a Mesa Ethernet card or an Ethernet SmoothStepper preserves the existing breakout board while moving pulse generation off the PC, eliminating the kernel-frequency jitter that limits Mach3 step rates.

Fanuc Controller Integration

Operators who own an industrial machine with a native Fanuc 0i-MF, 30i-B, or 31i-MB controller can skip the PC-sender problem entirely: the Fanuc controller reads ISO/RS-274 G-code natively with built-in cutter compensation. Three integration points matter when CAM-posted code is sent to a Fanuc:

• Post processor. Fanuc controllers expect specific address formats: T01 M06 for tool call, G43 H01 Z0.1 for tool-length offset call, and M08/M09 for coolant. A post that emits T1 M6 (no leading zero) will trigger Fanuc alarm PS0011 on some controls.
• Conversational front-ends. Fanuc MANUAL GUIDE i and MANUAL GUIDE 0i are OEM options that provide a conversational programming environment on the same HMI—useful for one-off parts without leaving the controller.
• DNC mode. For programs exceeding Fanuc's memory (typically 1 MB on 0i-MF), DNC mode streams G-code from a connected PC over RS-232 or Ethernet (FOCAS). Buffer-handshake is Xon/Xoff or DC1–DC4 by default; configure the post and the controller to match.

Selection Criteria and Cost Analysis

For a single-operator small business, the decision typically reduces to four numbers: software license cost, machine downtime during migration, CAM-to-controller post processor availability, and whether tool-table data can be carried forward. A structured selection matrix:

The cost inflection point for a basement shop moving from Kcam4 to commercial CAM is usually around USD 175 (Mach3 license) when CAM is already in place (Fusion 360 personal use, FreeCAD, EstlCAM, or similar). If the CAM side also needs upgrading—because the post processor cannot be configured to a specific controller without a paid post library—GibbsCAM's value comes from bundling CAM + post + simulation rather than from any single feature.

Migration Path from Kcam4

1. Inventory programs. Catalog the Kcam4 program directory; flag any that use Kcam-specific extensions (proprietary subroutines, M-codes beyond M30, conversational-only operations).
2. Identify the motion controller hardware. Record the breakout-board model (Xylotex, HobbyCNC, TB6560, Gecko G540, etc.) and verify it is supported by the target sender's plugin/driver list.
3. Re-post the CAM programs. Export the CAD part to a modern CAM tool and post to the new sender's dialect (Mach3 .tap, LinuxCNC .ngc, Fanuc standard).
4. Set up the new sender in dry-run mode. Disable spindle and coolant outputs and run each migrated program at 5 % rapid override while monitoring position with a DRO.
5. Calibrate tool table. Touch off each tool, enter length and diameter offsets, and verify G43/G49 with a known reference part.
6. Cut air and cut wax. Run the first three jobs in soft material before scheduling a production run.

Verification Checklist

• G-code file passes an ASCII/CRLF audit in a hex editor.
• Work offset (G54) is set and verified with an edge finder before running the first part.
• Tool-length offset applied via G43 H##, not hard-coded Z values.
• Cutter-diameter compensation engages and disengages outside the part on a lead-in/lead-out move (never inside a corner).
• Coolant, spindle CW/CCW, and tool-change codes match the post processor documentation for the target controller.
• Emergency-stop and limit-switch wiring verified before powering stepper drivers.
• First cut dimensionally inspected with calipers or a CMM before releasing the program to production.

Frequently Asked Questions