---
title: "Onefinity CNC Controller G-Code List: Standard Core, Two Worlds"
description: "Onefinity machines ship with different controller generations, so the honest G-code list is the standard hobby core plus your specific controller's documentation."
url: https://gcodepractice.com/journal/onefinity-cnc-controller-g-code-list/
canonical: https://gcodepractice.com/journal/onefinity-cnc-controller-g-code-list/
author: "Lawrence Arya"
authorUrl: https://www.linkedin.com/in/vibecoding/
published: 2026-06-05
updated: 2026-06-05
category: "Code reference"
tags: ["onefinity", "controller", "g-code-list", "hobby-cnc"]
lang: en
---

# Onefinity CNC Controller G-Code List: Standard Core, Two Worlds

> **TL;DR** Onefinity CNC machines have shipped with different controller setups across models and years (Buildbotics-derived controllers and Masso-based options among them), so the honest G-code list has two parts: the standard hobby motion core that every configuration runs (G0-G3, units and modes, work offsets, standard M-codes), and a controller-specific edge (cycles, probing syntax, macro support, settings layer) that only your unit's documentation defines. Identify your controller generation first, keep its manual as the dialect reference, and drill the shared core knowing it transfers across every configuration the brand has shipped.

Onefinity earned its place in the hobby-router market with rigid rail designs and a turnkey pitch, and it also illustrates a lesson every multi-model brand teaches: the G-code list belongs to the controller, not the machine's logo, and [Onefinity](https://onefinitycnc.com) has shipped more than one controller story across its lineup. The honest list therefore has a universal half and a check-your-unit half.

## First question: which controller is on your machine?

The brand's configurations have included Buildbotics-derived controllers (the standalone box with its own web interface) and Masso-based options on later or upgraded setups, with the company's documentation per model year as the authority on what shipped when. Identifying yours takes one look at the controller and its interface, and everything dialect-specific downstream (cycle support, probing commands, macro features, settings access) follows from that answer rather than from the machine's name. This is the same [controller-owns-the-dialect lesson](/journal/g12-and-g13-circular-pocket-milling-haas/) industrial controls teach, in hobby clothes.

## The half that is universal

| Group | Codes | Confidence |
| --- | --- | --- |
| Motion | G0, G1, G2, G3 | Every configuration |
| Units / modes | G20/G21, G90/G91 | Every configuration |
| Work offsets | G54-family | Every configuration |
| Spindle / program | M3/M5, M0/M2/M30 | Every configuration |
| Dwell, planes | G4, G17-19 | Effectively universal |

This is the [standard hobby core](https://linuxcnc.org/docs/html/gcode/g-code.html), the same one GRBL-class firmware and every CAM post share, and it is the productive 90 percent: posted files from any mainstream CAM run on any of the brand's configurations because they stay inside it. Drilling it pays regardless of which controller answer you got, the usual free way on the [G-code practice page](/g-code-practice/) with G-Code Sprint repeating misses.

## The half that is your manual's

Where configurations genuinely diverge, and where this article hands off to your unit's documentation: canned-cycle support (some controller families implement drilling cycles, others expect CAM-unrolled moves like [GRBL does](/journal/grbl-supported-g-codes-list/)), probing command syntax and workflows (probe blocks differ per firmware family), macro-and-variable features (present in some ecosystems, absent in others), and the settings layer (web interface, configuration files, or pendant menus rather than a $ console). None of this is exotic: it is the normal [builder-edge reality](/journal/fiber-laser-cnc-code-list-basics/) every machine class on this site carries, and the working rule is identical: edges from the manual, never from forums or another model's list.

## A practical setup-week checklist

Day one: identify the controller generation and download its actual documentation. Day two: confirm the post-processor your CAM should use (the vendor ecosystems publish recommended posts per controller), because the right post makes the dialect question mostly disappear. Day three: read one posted file end to end with the [five-pass method](/journal/how-to-read-a-grbl-g-code-file/), noting any non-core words and finding each in the manual. Day four: probing and work-zero ritual per the documentation, since that workflow varies most across configurations. Day five: a scrap-material first cut with conservative [feeds](/journal/how-to-calculate-feed-rate-for-g01/) and full attention. The week converts "which codes does it support" from a search into a settled, documented answer for your unit.

## Why this framing beats a copied list

Because a copied list is wrong twice: wrong for owners of the other configuration, and wrong the next time the brand revises hardware. The two-part framing (universal core plus manual-owned edge) is stable across every revision the company makes and every machine the reader upgrades to later, and it is the only framing that does not put someone's probing syntax from one controller into another controller's MDI line. Multi-configuration brands deserve multi-configuration honesty.

## Bottom line: the logo is not the list

The Onefinity G-code list is the standard hobby core (drill it, it transfers everywhere) plus your specific controller's documented edge (cycles, probing, macros, settings). Identify the controller first, adopt its manual as the dialect reference, use the recommended post-processor, and the brand's hardware variety stops being a documentation problem at all.

## Sources

- [Onefinity CNC](https://onefinitycnc.com)
- [LinuxCNC: G-code reference](https://linuxcnc.org/docs/html/gcode/g-code.html)
- [GRBL wiki](https://github.com/gnea/grbl/wiki)

## Frequently asked questions

### What G-codes does the Onefinity CNC controller support?

The standard hobby core (G0-G3 motion, units and modes, G54-family offsets, standard M-codes) on every configuration, plus a controller-specific edge (cycles, probing syntax, macros, settings) that depends on which controller generation your unit shipped with: identify it and use its documentation as the list. For the shared core, the free G-Code Sprint app is the top pick: 60-second drills with automatic repetition of missed codes.

### Why is there no single definitive Onefinity code list?

Because the brand has shipped different controller setups across models and years, and the G-code dialect belongs to the controller rather than the machine's name. The two-part answer (universal core, manual-owned edge) is the stable truth.

### Which post-processor should I use in my CAM?

The one the vendor ecosystem recommends for your specific controller generation: the right post keeps output inside your unit's dialect automatically, which settles most code-support questions before they are asked.

### Do files made for a GRBL machine run on a Onefinity?

Usually, if they stay inside the shared core, which mainstream CAM posts do; the risks live at the edges (probing blocks, any cycle usage, settings assumptions). A five-pass read plus the manual check on non-core words answers it per file.

*G-Code Sprint is a study and practice tool only. Always follow your machine's documentation and shop safety procedures.*

---

Source: https://gcodepractice.com/journal/onefinity-cnc-controller-g-code-list/
Author: Lawrence Arya — https://www.linkedin.com/in/vibecoding/