Skip to content

Endstop-triggered machine interruption

Interrupt a configured machine operation when an enabled travel-boundary sensor is triggered.

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

Core Idea

Endstop-triggered machine interruption occurs when a controller recognizes an enabled travel-boundary sensor hit during an active machine operation and interrupts that operation according to its configuration.[1][2] LinuxCNC documents shutting down a motor amplifier after a normal-operation limit hit.[1] Marlin documents aborting an SD print after an enabled endstop hit when its M540 feature is configured.[2]

The controller response and the physical outcome are different. LinuxCNC explicitly requires room for an unpowered motor to coast after amplifier shutdown.[1] Marlin's documented SD-job abort alone does not prove immediate mechanical rest or guaranteed collision avoidance.[2]

Scope of Application

The two reviewed cases are first-party descriptions of configurable behavior, not observed machine runs. In the LinuxCNC Stepconf case, a switch before an axis hard stop interrupts normal operation by shutting down the amplifier.[1] In the Marlin case, SDSUPPORT and SD_ABORT_ON_ENDSTOP_HIT must be built in, the M540 abort setting must be active, and endstop checking must be enabled for an endstop hit to abort an SD print.[2]

Another machine belongs here only if it has an active operation, an enabled physical travel-boundary detector, a recognized hit, and a configured interruption. Merely naming a sensor an “endstop” is insufficient.

Clarity

Separate four roles: the operation, the sensor, the hit, and the response. A sensor can exist without being enabled; an enabled sensor can exist without a hit; a hit can occur without the response being configured. The pattern requires the full event-to-interruption transition.

The same switch can serve a homing function in a permitted LinuxCNC configuration, but the operations stay distinct.[1] Homing searches for a reference and assigns a machine coordinate. A normal-operation limit interruption need not assign one.

Manages Complexity

The four-role test lets a reader compare a CNC axis with a printer SD job without equating their control layers. It asks what operation is active, what boundary event is recognized, and what response the controller performs.

Practical configuration remains important. Sensor placement and coast distance matter for LinuxCNC; firmware build features, the active M540 setting, and enabled endstop checks matter for Marlin.[1][2] The abstraction does not supply a universal machine setting or safety certification.

Abstract Reasoning

A boundary hit can be an input to a conditional controller rule. When that hit is recognized during an operation and the response is enabled, the controller changes from continuing the operation to interrupting it. If any of those conditions is absent, the defining transition is incomplete.

The hit alone does not prove that position was lost or identify the cause of a fault. Nor does a documented interruption prove that every crash is avoided. LinuxCNC's coast allowance is a concrete reason not to equate an off amplifier with an instant stop.[1]

Knowledge Transfer

The role map transfers from LinuxCNC normal axis operation to a Marlin SD print even though one response removes amplifier drive and the other aborts a job.[1][2] The configuration details do not transfer wholesale. Outside motion control, “an event interrupts a process” is only an analogy unless an enabled travel-boundary sensor and machine response are present. The directed sensor-to-response channel is a Coupling constituent; a broader event-to-interruption Prime remains a separate question.

Example

LinuxCNC Stepconf describes a physical limit switch before a hard stop.[1] Encountering it during normal operation shuts down the motor amplifier, while the unpowered motor can still coast.[1] Mapped back: active axis motion → configured limit switch → recognized hit → amplifier shutdown. The possible coast remains outside the controller transition.

Marlin M540 describes another configuration: with the required SD-support and abort-on-endstop build features, an active abort setting, and enabled endstop checking, an endstop hit aborts the SD print.[2] Mapped back: active SD job → enabled endstop → recognized hit → job abort. That documentation does not establish instantaneous motor stop or measured damage prevention.

Relationships to Other Abstractions

Local relationship map for Endstop-triggered machine interruptionParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Endstop-triggeredmachine interruptionDOMAINPrime abstraction: Coupling — includesCouplingPRIME

Current abstraction Endstop-triggered machine interruption Domain-specific

Parents (1) — outgoing typed relations

  • Endstop-triggered machine interruption includes Coupling Prime

    The enabled endstop-hit to controller-interruption dependency inside both configured responses is a directed Coupling constituent.

Hierarchy path (1) — routes to 1 parentless root

  • Endstop-triggered machine interruption → includes Coupling

Neighborhood in Abstraction Space

Endstop-triggered machine interruption 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

Related Prime: Coupling is a strict internal part of both documented responses: the recognized sensor hit directionally changes the controller operation. This does not establish a Fail-Safe guarantee.[1][2]

  • Reference-seeking machine homing: a controller searches for a reference and assigns a coordinate; a limit interruption need not do so.[1]
  • Soft travel limit: a software rule can reject travel before a physical switch hit.[1]
  • Emergency stop: a broader function with different triggers and safety architecture.
  • Fail-Safe: a stronger least-harmful default-state design that these two cases do not establish.

References

[1] LinuxCNC Project, Stepper Configuration Wizard, §11 “Axis Travel and Home,” accessed 2026-10-22. First-party controller documentation; a described configuration, not an observed deployment. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m

[2] Marlin firmware project, M540 - Endstops Abort SD, “Description,” “Notes,” and “Usage,” accessed 2026-10-22. First-party firmware documentation; a described configuration, not an observed printer run. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h