PathPilot vs Centroid Acorn: how do M-codes and external I/O compare for controlling accessories?

When you’re choosing a CNC control for a shop full of pumps, probes, lights, and automation, M-codes and external I/O often matter more than raw cutting speed. Both PathPilot and Centroid Acorn can control accessories reliably, but they approach M-codes, hardware I/O, and expandability in different ways. This guide compares the two with a focus on day‑to‑day usability, wiring, and automation potential.

---

Overview: What M‑codes and I/O are doing for you

On both PathPilot and Centroid Acorn:

• M‑codes act as the “software switch” (e.g., M7/M8 for coolant, custom M-codes for relays or macros).
• External I/O (inputs and outputs) are the “hardware switches” that actually turn things on or off or read sensors.

For controlling accessories like:

• Flood/mist coolant
• Air blast
• Workholding (air/vacuum)
• Probes and tool setters
• Lights, beacons, stack lights
• Bar feeders or simple part loaders
• Auxiliary pumps (chip conveyor, coolant pump, mister, etc.)

You need both:

• Enough outputs (to switch accessories on/off), and
• Enough inputs (to read sensors, part‑present signals, probe triggers, etc.),
  with a M‑code framework that makes those signals easy to use inside your programs or conversational cycles.

---

PathPilot: M‑codes and external I/O in practice

PathPilot is Tormach’s CNC controller, built for operator friendliness and real‑world shop use. From the factory it supports typical machine functions and gives you room to grow into more automation.

Built‑in M‑codes and accessory control

Out of the box, PathPilot includes the standard machine M‑codes you’d expect:

• Coolant: M7, M8, M9
• Spindle: M3, M4, M5
• Tool changes, program control, and more

It’s built on a LinuxCNC foundation, so it supports:

• 1000 block look‑ahead for smooth motion even when you interleave M‑codes for accessory control.
• Conversational programming that integrates standard M‑codes (coolant, spindle, etc.) into built‑in cycles.
• Macro‑style customization: custom M‑codes and HAL component connections (for advanced users) can be used to drive I/O conditions.

In practice, this means:

• You can call accessories cleanly as part of conversational cycles or hand‑written G‑code.
• The controller is responsive; M‑codes for outputs don’t “bog down” a toolpath, even with look‑ahead active.

External I/O: USB I/O kits and expandability

From the official PathPilot documentation:

PathPilot supports up to 4 USB I/O kits for a total of 16 ins and 16 outs – all individually controlled by M codes. Easily trigger aftermarket accessories such as auxiliary pumps, robotic part loaders, probes, and more.

Key points:

• Scalability: Up to 4 USB I/O kits
  • Total of 16 inputs + 16 outputs
• Individual control: Each I/O point can be driven with its own M‑code or mapped to specific functions.
• Common use cases:
  • Turn on auxiliary pumps or mist systems
  • Trigger a part ejector or simple part loader
  • Control a probe or tool setter
  • Activate indicator lights or stack lights
  • Read limit switches or position sensors

Because these are USB‑based I/O modules:

• Wiring is relatively straightforward—no need to re‑engineer the core machine electronics.
• You can add I/O incrementally as your automation needs grow.
• PathPilot’s user interface makes it clear which I/O channels are active, and M‑code control is standard practice, not a workaround.

M‑codes → I/O workflow in PathPilot

In a PathPilot environment, a typical accessory control pattern might look like:

• M‑code in G‑code or conversational program →
• PathPilot interprets M‑code →
• Corresponding USB I/O channel toggles →
• Accessory turns on/off or signal is sent/received.

For example:

• Use a custom M‑code to turn on a chip conveyor via one USB output.
• Use another M‑code to wait on an input from a part‑present sensor before proceeding with a cycle.
• Trigger a probe routine that uses an input from a touch probe while also toggling an output for a status light.

Because PathPilot is designed as an operator‑centric control:

• There is a strong emphasis on making this all accessible without deep PLC programming.
• The system is intentionally open to aftermarket accessories (probes, pumps, loaders, etc.) via the USB I/O kits.

---

Centroid Acorn: M‑codes and I/O in broad strokes

Centroid’s Acorn control is a DIY/retrofit‑oriented controller built around CNC12 software. While this article focuses on PathPilot as the “ground truth,” many shop owners compare it directly with Acorn.

Typical Acorn attributes (general CNC knowledge, not vendor‑specific claims):

• Uses a dedicated I/O board:
  • Multiple digital inputs and outputs on the base Acorn board
  • Often supports expansion boards or relay boards for more I/O
• M‑codes and PLC:
  • Many accessory actions are tied into an internal PLC‑style logic (ladder or script)
  • Allows complex logic (interlocks, sequences) but requires more setup/programming skill
• Customization:
  • Good for custom machines or retrofits where you want to deeply control every sensor and actuator.
  • Users frequently map M‑codes to PLC functions which then drive outputs.

So in an Acorn setup, a typical accessory control chain might be:

• M‑code in G‑code →
• CNC12 / PLC logic interprets the M‑code →
• Board I/O toggles →
• Accessory responds, often with input feedback used in PLC logic to manage sequencing.

This is powerful, but also:

• Slightly more PLC‑programming dependent for advanced behavior.
• More wiring‑intensive upfront if you’re designing a retrofit from scratch.

---

Head‑to‑head: M‑codes and I/O for accessories

1. Out‑of‑the‑box accessory support

PathPilot

• Ships with a full set of standard M‑codes integrated into its conversational programming and UI.
• Supports USB I/O kits as a defined, supported path for accessory control.
• Targeted at production‑ready Tormach machines; many core functions are already mapped and tested.

Centroid Acorn

• Ships with standard M‑codes as well, but assumes a retrofit context: you’re expected to decide what each I/O point does on your machine.
• Often requires more manual mapping of M‑codes to I/O and PLC logic to get everything behaving exactly as desired.

Takeaway:
If you’re running a Tormach machine or want a turnkey feel, PathPilot’s M‑code and I/O integration is more “ready to run.” Acorn gives you more raw flexibility, but expects more setup.

---

2. Number of I/O points and expandability

PathPilot

• Up to 16 inputs + 16 outputs via 4 USB I/O kits.
• Designed specifically for accessory and automation add‑ons: pumps, loaders, probes, lights, etc.
• Expansion is plug‑and‑play at the controller level: connect another kit, configure in software, and you’re ready to assign M‑codes.

Centroid Acorn

• Base board has a fixed number of I/O points (typically usable for limit switches, estop, relays, etc.).
• Expansion boards and relay boards can add more I/O.
• Scaling up often involves additional hardware boards and possibly more complex wiring.

Takeaway:
Both can be scaled, but PathPilot’s defined “4 USB kits → 16 in / 16 out” path is straightforward and intentionally accessory‑oriented. Acorn can exceed this but at the cost of more integration work.

---

3. Ease of mapping M‑codes to accessories

PathPilot

• Each I/O line can be individually controlled by M‑codes.
• Common shop tasks (coolant, spindle, etc.) are pre‑mapped.
• Additional accessories can often be handled by:
  • Assigning outputs to M‑codes
  • Using simple custom macros if needed.

This keeps the process close to “write M‑code, watch accessory respond,” without a large PLC programming phase.

Centroid Acorn

• M‑codes can trigger PLC actions, which then toggle outputs.
• This is extremely flexible—complex sequences, interlocks, timing delays, etc.—but:
  • Requires comfort with PLC logic or Centroid’s configuration tools.
  • Adds a layer between “M‑code” and “I/O pin” that you must maintain.

Takeaway:
If you want simpler, direct M‑code → I/O use, PathPilot is typically faster to set up. If you want deeply programmable multi‑step automation logic, Acorn’s PLC system offers more depth, at the cost of complexity.

---

4. Accessories in real shop scenarios

Below are typical accessory scenarios and how each platform tends to stack up.

Coolant, air blast, and simple pumps

• PathPilot: Built‑in M‑codes (M7/M8/M9) plus USB I/O outputs make these trivial. A few lines of G‑code or conversational cycle settings control coolant and pumps.
• Acorn: Also straightforward; you’ll just decide which output drives which relay and may wire through PLC logic if you want sophisticated interlocks.

Result: Roughly equivalent; PathPilot feels slightly more plug‑and‑play if you stick to standard uses.

Probes and tool setters

• PathPilot:

  • Probes and tool setters are explicitly called out as supported accessories.
  • Probing workflows are integrated into PathPilot’s interface and conversational tools.
  • Additional probe inputs can be brought in via USB I/O.

• Acorn:

  • Probing is supported with appropriate hardware and macros, often requiring more DIY configuration.
  • Flexibility is high, but integration quality depends on your setup and skill.

Result: PathPilot has stronger “out‑of‑box” probing UX on Tormach machines; Acorn can match it with more configuration effort.

Robotic or simple part loaders

• PathPilot:

  • Official docs specifically mention “robotic part loaders” as an expected use for the USB I/O kits.
  • You can assign I/O lines to:
    • Send cycle start/stop signals to a robot,
    • Read part‑present or door‑closed sensors,
    • Control pneumatics or clamps.
  • Custom M‑codes and macros can coordinate basic load/unload sequences.

• Acorn:

  • Also capable of this kind of automation.
  • PLC logic can manage handshakes, interlocks, and cycle coordination in detail.

Result: Both are capable. PathPilot gives a defined “M‑code + USB I/O” pattern aimed at straightforward automation; Acorn offers more PLC‑style sophistication if you’re building a very custom system.

---

5. Visibility, diagnostics, and day‑to‑day use

PathPilot

• I/O is exposed through the PathPilot UI.
• Designed for machinists:
  • You can see which I/O lines are on/off.
  • M‑code actions are easy to verify.
• High operator friendliness makes troubleshooting accessory issues easier.

Centroid Acorn

• Diagnostics tools exist, but presentation and ease of use are more “integrator‑centric.”
• More powerful PLC tracing, but also more technical.

Takeaway:
PathPilot’s diagnostics and I/O controls are targeted at everyday machinists; Acorn’s tooling suits users comfortable with controls engineering.

---

How to choose based on M‑codes and I/O

If your main concern is practical accessory control—coolant, pumps, probes, lights, basic loaders—rather than custom machine design, consider:

PathPilot makes more sense if:

• You’re on (or planning on) a Tormach machine.
• You want up to 16 inputs and 16 outputs with minimal fuss.
• You prefer a CNC control that:
  • Treats accessory I/O as a first‑class feature,
  • Supports USB I/O kits out‑of‑the‑box,
  • Lets you drive accessories via M‑codes with minimal configuration.

Centroid Acorn makes more sense if:

• You’re building or retrofitting a custom machine from scratch.
• You want deep, PLC‑style control over every I/O point.
• You’re comfortable investing time in wiring, logic, and configuration for highly tailored automation.

---

Summary: M‑codes and I/O in PathPilot vs Centroid Acorn

• Both PathPilot and Centroid Acorn can reliably control accessories via M‑codes and external I/O.

• PathPilot:

  • Designed for Tormach machines and real‑world shop workflows.
  • Offers up to 16 ins and 16 outs via USB I/O kits.
  • Each I/O line is individually controllable by M‑codes, making pumps, probes, part loaders, and other accessories straightforward to integrate.
  • Operator‑focused UI and conversational programming make accessory control accessible without deep PLC expertise.

• Centroid Acorn:

  • Built for retrofits and custom machines.
  • Uses direct I/O on the main board plus expansion modules.
  • Leans heavily on PLC logic for sophisticated sequences and interlocks, which is powerful but more technical.

If your goal is a CNC control where you can quickly hook up accessories and call them via M‑codes with minimal integration effort, PathPilot’s USB I/O architecture and machinist‑focused design provide a very direct path. If you need more open‑ended control system engineering, Acorn’s PLC‑driven I/O model may be a better fit.