Skip to content

Reference-seeking machine homing

Find a physical reference for an untrusted motion axis and assign it a machine coordinate for later positioning.

Version
v1 · 2026-10-25 · History
Domain-specific #
14433
Origin domain
Engineering
Subdomain
Motion Control → Engineering

Core Idea

Reference-seeking machine homing is a way for a controller to establish a machine coordinate when it does not yet know where a motion axis is.[1][2] The controller moves the axis until a configured physical reference is detected, assigns a coordinate to that point, and then uses the resulting machine frame for later positioning.[1][2]

The detected point need not be numerical zero or the position where the axis finally stops.[1][2] LinuxCNC documents separate settings for the detected point's coordinate and the later home destination; Marlin also sets a configured coordinate after its reference triggers.[1][2]

This entry covers only physical reference seeking. LinuxCNC also calls immediate coordinate initialization and some absolute-encoder procedures “homing” even though they do not seek a physical reference.[1]

Scope of Application

The pattern appears in documented CNC-joint and 3D-printer-axis configurations.[1][2] A LinuxCNC joint can search for a switch and latch an encoder index before assigning the detected point a coordinate.[1] A Marlin printer axis can run G28 toward an endstop and set its configured home coordinate when the endstop triggers.[2] These are controller documentation cases, not observations or accuracy measurements from particular machines.

Another machine qualifies only if its controller actually moves an untrusted axis to a physical reference and assigns that event a machine coordinate. Merely having a switch, encoder, or place named “home” is insufficient.

Clarity

Ask three separate questions: Where did the sensor trigger? What coordinate was assigned there? Where did the axis finish?

LinuxCNC distinguishes a switch or index event, the assigned home offset, and the final HOME position.[1] Treating these as one location can hide a configuration error.

The name also separates the reference-seeking branch from other controller operations called homing. An absolute encoder can provide a coordinate without the search that defines this subkind.[1]

Manages Complexity

Controller manuals contain many settings: search direction and speed, latch speed, sensor choice, assigned offset, and final destination.[1][2] The abstraction reduces them to five roles: an untrusted coordinate, a physical reference, a search and event capture, coordinate assignment, and a trusted state for later positioning.[1][2]

The details still matter for an actual machine. A wrong search direction or failed reference can cause a bad home or unsafe motion; the concept does not supply a universal speed, precision, or safety guarantee.[1][2]

Abstract Reasoning

If the controller does not trust the axis coordinate, issuing a position command cannot by itself establish the physical position.[1][2] In this subkind, a detected reference event must be bound to a numerical coordinate.[1][2] If the event is missed, or if the controller detects it but assigns no coordinate, the defining transition is incomplete.[1][2]

This gives a diagnostic order: check the initial trust state, the configured sensor, the search and capture, the assigned coordinate, and only then the later commanded position.[1][2] It also prevents mistaking a limit switch used only to stop travel for completed homing.[1]

Knowledge Transfer

The same role questions work for a CNC joint and a printer axis, although their commands, sensors, and parameters differ. LinuxCNC's switch-plus-index configuration and Marlin's endstop-triggered G28 both seek a physical reference and assign a coordinate.[1][2]

The idea does not transfer literally to every activity described as “finding a baseline.” It requires a motion controller, an axis, a detected physical event, and machine-coordinate assignment. Current graph review found no existing Prime whose full identity is a necessary parent, so this entry is provisionally unparented.

Example

In one documented LinuxCNC configuration, a joint searches for a home switch, captures an encoder index, assigns that detected point a configured machine coordinate, and may then move to a separately configured HOME destination.[1] Mapped back: the initially untrusted joint is the axis; switch and index provide the physical reference; search and latch capture it; the home offset assigns a coordinate; later positioning uses the established frame.[1]

Marlin documents a second form: after startup, a printer axis can move under G28 to an endstop, optionally back off and approach again more slowly, then set the configured home coordinate.[2] Mapped back: the axis begins without a trusted coordinate; the endstop is the reference; G28 captures the trigger; the firmware assigns a home coordinate; later motion can use that position.[2] This does not claim measured performance on a particular printer.

Neighborhood in Abstraction Space

Reference-seeking machine homing sits in a sparse region of the domain-specific corpus (99th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2769 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25

Not to Be Confused With

  • Home position: a reference or final location, rather than the procedure that finds a physical reference and assigns its coordinate.

  • Immediate or absolute-encoder homing: controller modes that may establish a coordinate without physically searching for a reference.[1]

  • Limit or emergency stop: a trip that halts motion without assigning a machine coordinate.[1]

  • Calibration in general: measuring deviation from a standard and adjusting an output; this is not required for every reference-seeking homing sequence.

References

[1] LinuxCNC project, Homing Configuration, LinuxCNC 2.8 documentation, §§4–6.13, accessed 2026-10-22. First-party controller configuration; cited for documented operations, not an observed milling deployment. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s ↩t ↩u ↩v

[2] Marlin (firmware project), Homing, especially “When homing happens,” “What G28 does,” “The home position,” and “Sensorless homing,” accessed 2026-10-22. First-party current firmware documentation; cited for documented printer operation, not a measured printer deployment. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p