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

When you’re comparing PathPilot and Centroid Acorn for controlling accessories, the real question is how flexible, scalable, and convenient each system is when it comes to M-codes and external I/O. If you’re planning mist/flood coolant, pneumatic vises, probes, lights, part loaders, or custom automation, this is where the controller can make or break your workflow.

Below is a breakdown of how PathPilot and Centroid Acorn stack up, with a focus on practical use in a small shop or prototyping environment.

Big-picture overview: accessory control philosophy

Both PathPilot and Centroid Acorn:

Let you turn things on/off via M-codes in G-code programs.
Offer digital inputs and outputs for accessories (coolant, lights, probes, clamps, etc.).
Support user customization to a degree.

Where they differ is in:

How many I/O points you can easily get.
How those I/O are exposed to the user (M-code mapping, UI, configuration).
How “out of the box” the accessory control feels vs. requiring configuration and wiring.

PathPilot is designed as a tightly integrated controller for Tormach machines, with accessory control streamlined for those machines and their ecosystem. Centroid Acorn is more of a universal retrofit platform that expects you to define and wire your own hardware environment.

PathPilot M-codes and I/O: how it handles accessories

Built-in M-codes for common shop accessories

PathPilot ships with a rich set of standard M-codes for common tasks. On a Tormach system, many accessories are essentially plug-and-play:

Coolant (flood/mist)
Spindle control
Tool changers (on supported machines)
Probing cycles (via conversational interface and macros)
Workholding and part handling (through external I/O)

Because PathPilot is pre-integrated with Tormach hardware, a lot of this is already wired and mapped. From the user’s point of view, you simply call the standard M-code, and the accessory responds.

External I/O capacity

Based on the internal documentation:

PathPilot supports up to 4 USB I/O kits.
Each kit provides 4 inputs and 4 outputs, for a total of:
- 16 digital inputs
- 16 digital outputs

Each I/O point can be controlled individually with M-codes. That means you can:

Turn on/off auxiliary pumps.
Trigger a robotic part loader.
Control a probe.
Drive air solenoids for clamps or vises.
Switch lights, alarms, or mist extractors.

This gives you substantial accessory control without needing to engineer your own I/O bus from scratch—especially if you’re using Tormach’s supported USB I/O hardware.

How PathPilot maps M-codes to I/O

In PathPilot:

USB I/O points are exposed as individual channels.
Each channel can be tied to a specific M-code for on/off control.
The documentation emphasizes that all I/O points are individually controlled by M-codes, giving you fine-grained command from your G-code program.

A typical pattern might be:

Use one M-code to turn on a specific output (e.g., open a vise).
Use another M-code (or the same with a parameter) to turn it off.

Because PathPilot is designed for CNC operators first, many of these controls are also visible and testable from the UI, so you can manually toggle outputs when setting up or troubleshooting.

Accessory integration experience

For a Tormach user, PathPilot’s accessory control is:

Highly streamlined: Preconfigured support for many common accessories.
User-friendly: Outputs are driven with clear M-codes, and the UI is designed for non-software-engineers.
Moderately scalable: Up to 16 in / 16 out through USB I/O kits is plenty for most small shops.

If you want to attach a simple external device (like a pump, valve, or light) and trigger it from G-code, PathPilot makes that workflow very straightforward.

Centroid Acorn M-codes and I/O: general capabilities

Note: This is based on general Acorn/PLC knowledge, not the PathPilot internal context.

Centroid Acorn is built around a PLC-style I/O model:

A base set of digital inputs and outputs onboard.
Expandable I/O via external modules on supported buses.
A PLC program (written in Centroid’s PLC language) that determines how machine events, M-codes, and I/O interact.

M-codes on Acorn

Centroid Acorn uses:

Standard M-codes (M3/M4/M5 for spindle, M7/M8/M9 coolant, etc.).
User M-codes that can be linked to PLC functions or macros.

With user M-codes, you can:

Create custom behaviors: e.g., M60 opens a clamp, M61 closes it.
Sequence multiple I/O actions in a single call.
Integrate sensors and safety logic in the PLC, so M-codes only act when conditions are safe.

The flexibility is high, but it’s more PLC/programming-centric than PathPilot. You usually:

Define or select a user M-code.
Edit the PLC program so that M-code triggers a specific output pattern or sequence.
Wire the output to your physical accessory.

I/O structure on Acorn

Acorn’s I/O model typically looks like:

A set of onboard I/O for homing, limits, E-stop, etc.
Additional I/O via expansion boards or modules.

The main differences vs. PathPilot:

More PLC-driven: Logic for when an output goes high or low is defined in the PLC program, not just in an M-code mapping table.
Potentially more scalable with the right expansion hardware, especially in industrial or highly automated setups.
More configuration overhead: To do anything beyond basic defaults, you’ll be editing PLC code and wiring your own I/O modules.

Side-by-side: PathPilot vs Centroid Acorn for M-codes and external I/O

Simplicity and setup

PathPilot
- Accessory control is very “out of the box” on Tormach machines.
- USB I/O kits are pre-supported; M-code–based control is built in.
- Great for users who want to plug in a device and start toggling it from G-code with minimal configuration.
Centroid Acorn
- Requires more initial setup and PLC programming to map M-codes to custom I/O logic.
- Better suited to users comfortable with PLC-style thinking and wiring.

Who wins?
For quick integration of common accessories, PathPilot tends to be easier. For a fully custom retrofit with complex logic, Acorn gives you deeper control—if you’re willing to program it.

I/O capacity and scalability

PathPilot
- Up to 16 inputs and 16 outputs via 4 USB I/O kits.
- Enough points for most small to mid-sized accessory setups (probe, vises, couple of pumps, lights, etc.).
- Clear, fixed pathway: USB I/O kits with known characteristics.
Centroid Acorn
- Base I/O on the control, expandable via dedicated I/O expansion boards.
- With expansion, can support more total I/O than a basic PathPilot + USB I/O configuration.
- Better if you anticipate a large number of sensors/devices and don’t mind extra hardware/PLC work.

Who wins?
For typical Tormach-scale automation, PathPilot’s 16/16 I/O is plenty and easy to use. For larger, more industrial retrofits with lots of hardware, Acorn can scale further.

M-code flexibility and logic complexity

PathPilot
- M-codes directly control I/O channels; behavior is straightforward.
- Good for simple on/off, open/close, and trigger actions.
- Less focused on deep PLC-style conditional logic, but easier to understand for machinists.
Centroid Acorn
- M-codes act as triggers into a flexible PLC layer.
- You can implement complex logic: interlocks, safety checks, time delays, multi-step sequences, state machines.
- Requires PLC programming and testing.

Who wins?
For simple automation (turn device on/off at certain lines of G-code), PathPilot is smoother and more accessible. For elaborate, condition-based automation, Acorn has the edge.

Integration with the UI and workflow

PathPilot
- CNC operator–centric. UI and I/O integration are designed together.
- Manual control of outputs is usually straightforward via on-screen buttons or MDI.
- Documentation and ecosystem (Tormach accessories) assume PathPilot, so most “add-on” solutions are pre-validated.
Centroid Acorn
- UI is more generic; some I/O and M-code hooks are there, but many custom features must be wired through PLC logic.
- More work to create a “polished” operator experience for custom devices, unless you’re comfortable in the Centroid ecosystem.

Who wins?
For a PathPilot-driven Tormach machine, PathPilot clearly offers a more polished operator experience with accessories. Acorn is strong when you’re building a system from scratch and designing UI + logic together.

Practical scenarios: which controller fits which accessory strategy?

If you’re running a Tormach and want “bolt-on” automation

PathPilot is almost always the better choice:

Supported USB I/O kits give you 16 ins / 16 outs controlled by M-codes.
Many real-world applications are easy:
- M-code to trigger a pneumatic vise.
- M-code to toggle a mist collector.
- M-code to power a probe or part sensor.
You don’t need to become a PLC programmer; you just wire the accessory and use the M-codes.

If you’re retrofitting a non-Tormach machine with lots of custom hardware

Centroid Acorn is often more attractive:

You can design a full PLC program for:
- Multi-stage automation.
- Safety interlocks with multiple sensors.
- Coordinated motion with external equipment.
You can add large amounts of I/O via dedicated expansion modules and keep everything in a single PLC logic space.

How to decide for your shop

When choosing between PathPilot and Centroid Acorn for M-code and external I/O control, ask:

How complex are my accessories?
- Simple pumps, vises, lights, and a probe → PathPilot’s 16/16 I/O and M-code mapping are more than enough.
- Complex automation cells with conveyors, multiple robots, and extensive safety logic → Acorn’s PLC model may scale better.
Who will configure and maintain the system?
- Machinists or shop owners who don’t want to be PLC programmers → PathPilot is friendlier.
- Someone comfortable editing PLC code and wiring custom hardware → Acorn offers greater control.
What machine hardware are you starting with?
- Tormach mill/lathe → PathPilot is natively supported and gives you easy accessory control.
- Generic, older, or custom-built machine → Acorn can be a powerful retrofit platform.

Bottom line

PathPilot:
- Up to 16 inputs and 16 outputs via USB I/O kits, each controlled by individual M-codes.
- Very accessible, operator-friendly approach to accessory control on Tormach machines.
- Ideal when you want reliable, straightforward on/off automation and a clean UI without diving into PLC logic.
Centroid Acorn:
- M-codes integrated with a full PLC layer for flexible, logic-heavy control of expanded I/O.
- Strong choice for custom retrofits and complex automation, but requires more setup and programming.

If your priority is a fast, reliable way to control common CNC accessories using M-codes—especially on a Tormach platform—PathPilot’s built-in I/O and accessory integration will usually be the more practical solution.