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 is a configured controller response to a travel-boundary signal during an active operation. An enabled limit or endstop sensor is hit; the controller recognizes that event and interrupts the operation in its configured way.^[1]^[2] The two documented responses here differ: LinuxCNC shuts down a motor amplifier when a limit switch is encountered during normal operation, while Marlin can abort an SD print after an enabled endstop hit under its M540 configuration.^[1]^[2]

The abstraction describes the event-to-interruption transition, not a guarantee of an immediate physical stop. LinuxCNC explicitly allows distance for an unpowered motor to coast after the amplifier is shut down.^[1] Marlin documents aborting the SD-print job; that statement alone does not establish that every motor stops instantly or that a collision is prevented.^[2]

Structural Signature¶

Active operation. A machine operation is in progress and can be interrupted. LinuxCNC's example concerns normal axis operation; Marlin's concerns an SD print.^[1]^[2]
Enabled travel-boundary detector. The controller must have an operative limit or endstop signal. A switch that exists physically but is disabled or unconnected does not perform this role. LinuxCNC locates the limit switch before the hard stop; Marlin requires enabled endstop checking for its M540 behavior.^[1]^[2]
Recognized hit. The sensor's transition must be detected during that operation. Merely having a sensor configured without a hit is a possible guard, not an instance of interruption.^[1]^[2]
Configured interruption. The controller must act on the recognized event. The LinuxCNC example removes motor-amplifier drive; the Marlin example aborts the SD-print job.^[1]^[2] Detection alone, with no enabled response, does not complete this pattern.

The after state is an interrupted controller operation. Its physical consequences depend on the machine and configuration; the definition neither presumes zero coast nor guarantees avoidance of harm.^[1]^[2]

What It Is Not¶

Not reference-seeking machine homing. A homing sequence searches for a physical reference and assigns a machine coordinate. A normal-operation limit hit can interrupt travel without assigning any coordinate. LinuxCNC permits a switch to serve both roles in some configurations; the shared component does not merge the operations.^[1]
Not a software soft limit. A controller can reject a commanded position at a software travel limit before a physical endstop is hit.^[1] That may prevent motion, but it lacks this pattern's sensor event.
Not a general emergency stop. An operator-activated emergency-stop system may have different triggers and safety architecture. Neither reviewed configuration establishes that broader identity.
Not a certified fail-safe outcome. The configured response can be protective, but the two sources do not show that it always reaches the least harmful state or prevents every collision.^[1]^[2]

Scope of Application¶

This entry is grounded in two first-party descriptions of controller configurations, not observations of named machines in the field. LinuxCNC Stepconf explains that a limit switch can be placed before an axis's hard stop and that hitting it during normal operation shuts down the motor amplifier.^[1] Marlin documents M540 as an option to abort an SD print on an endstop hit, provided the firmware includes SDSUPPORT and SD_ABORT_ON_ENDSTOP_HIT, the abort setting is active, and endstop checking is enabled.^[2]

Another controller fits only if an enabled travel-boundary event during an operation actually triggers a configured interruption. Similar vocabulary in a manual is not enough: the event and response must both be documented or observed. These two sources do not establish universal practice across CNC machines, printers, or industrial robots.

Clarity¶

Keep sensor, event, controller response, and physical outcome distinct. A switch is hardware; a hit is a detected event; amplifier shutdown or job abort is the response; eventual motion and damage are separate outcomes. LinuxCNC's explicit coast allowance shows why the response cannot be equated with instant physical rest.^[1]

The Marlin case is narrower than “any endstop stops a printer.” Its documented behavior is tied to the SD-print abort option and the feature and endstop conditions stated above.^[2] A different endstop use, including homing, must be classified by what the controller does after the trigger rather than by the same sensor name.

Manages Complexity¶

Controller manuals expose many hardware and firmware settings. This abstraction reduces the classification to four questions: What operation was active? Was the travel-boundary detector enabled? Did the controller recognize a hit? What interruption was configured?^[1]^[2] Those questions compare a CNC axis and a printer job without pretending that amplifier power and a print-job state are the same layer.

The reduction is deliberately bounded. Sensor placement, deceleration and coast, firmware build options, and the active response setting matter in real equipment.^[1]^[2] The pattern identifies a control transition; it does not replace those configuration checks.

Abstract Reasoning¶

If a running operation reaches an enabled travel boundary, the recognized sensor event can switch the controller from continuing that operation to interrupting it. The transition is conditional: with no recognized event, or with the response disabled, the case is outside this identity. With an event but no interruption, the structural signature is incomplete.

This ordering also blocks two inferences in the frozen Home position source. A limit hit by itself does not prove that the controller lost its position or identify a particular failure cause. Neither documented response proves that every crash or catastrophic loss will be prevented. The LinuxCNC coast allowance supplies a concrete reason to keep response and outcome separate.^[1]

Knowledge Transfer¶

The role map transfers between the documented CNC and printer configurations: active operation → enabled boundary detector → recognized hit → configured interruption. The implementation does not transfer wholesale. LinuxCNC interrupts the axis power stage; Marlin's M540 feature aborts an SD print.^[1]^[2]

The map can guide examination of another controller manual, but no third deployment is established here. General phrases such as “a guard stops a process” are analogies unless there is an enabled travel-boundary sensor and a documented machine-operation response.

Examples¶

LinuxCNC axis limit during normal operation¶

Stepconf describes a limit switch located before the axis's hard stop.^[1] If that switch is encountered during normal operation, LinuxCNC shuts down the motor amplifier.^[1] Mapped back: active axis operation → configured physical limit switch → limit hit → amplifier shutdown. The manual requires enough remaining travel for the unpowered motor to coast, so the documented response is not an instantaneous mechanical halt.^[1]

Marlin SD print with M540 endstop abort¶

In a build with the documented SD-support and abort-on-endstop features, M540 can enable aborting an SD print when an endstop is hit, if endstop checking is enabled.^[2] Mapped back: active SD print → enabled printer endstop → endstop hit → SD-print abort. The documentation supports the job-abort transition, not an assertion that all printer motion stops instantly or damage is impossible.^[2]

Structural Tensions¶

The two manuals specify different interruption layers but do not establish a shared, measured tradeoff between speed, nuisance trips, and safety. This entry therefore does not infer such a tradeoff from the mere existence of a limit switch. A later engineering comparison would need controller-specific evidence about response timing and machine behavior before asserting one.

Structural–Framed Character¶

Evaluative weight. The identity is descriptive: it asks whether a configured boundary event interrupts an active machine operation. Avoiding damage may motivate that design, but neither reviewed manual certifies a least-harmful state or universal protection.^[1]^[2]

Human-practice dependence. People place and enable sensors, select controller responses, and decide which operation is interruptible. The relation is therefore recognized in configured practice, not obtained from a switch's physical presence alone. LinuxCNC and Marlin expose materially different response settings.^[1]^[2]

Institutional origin. The evidence comes from first-party controller and firmware documentation. It establishes documented configurations, not a measured population of installations or an independent safety standard.^[1]^[2]

Vocabulary travel. The ordered event-response roles travel literally between these motion-control settings. The words endstop, axis, motor amplifier, and SD print do not transfer intact to arbitrary exception handling; using them there would be analogy.

Import versus recognition. A designer can import the procedure by configuring a detector and response. An analyst can recognize it after the fact only if an enabled travel-boundary hit and actual configured interruption are evidenced. The article does not infer the procedure from shared hardware or a safety-themed name.

Its character: a framed, domain-specific controller procedure with a reusable conditional skeleton, whose literal instances require motion-control hardware and configuration and whose protective outcome remains bounded by the documented response.

Structural Core vs. Domain Accent¶

The core is an active operation interrupted because an enabled travel-boundary event is recognized. Remove the operation, the event, or the configured response and this particular transition is absent. The accent is how a controller realizes interruption: LinuxCNC's amplifier shutdown and Marlin's SD-print abort are different implementations.^[1]^[2]

The domain boundary is load bearing. A general exception handler or an operator's stop button may interrupt work, but it is not an endstop-triggered machine interruption without the travel-boundary sensor and its controller response. The portable event-to-interruption skeleton is a future-Prime question, not an established cross-domain owner: none has passed the required full-signature review here. This named entry remains domain-specific even if later work admits a broader Prime.

This entry includes Coupling.

Coupling is an approved strict internal composition/part_of parent. In each documented configuration, a distinguishable boundary-sensor event directionally changes a controller operation: LinuxCNC shuts down amplifier drive, and configured Marlin aborts an SD print.^[1]^[2] The parent relation is local to that sensor-to-response channel; this entry adds the enabled travel-boundary detector, active motion-control operation and particular interruption. It does not claim measured latency or universal physical safety. Fail-Safe is a nearby but declined parent because its full signature requires an engineered least-harmful post-failure state, which these two sources do not establish. Circuit Breaker, Threshold-Triggered Rule Activation and Feedback also fail the full necessary-parent test for the documented cases.

Relationships to Other Abstractions¶

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 (99^th 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¶

Reference-seeking machine homing: recognizes a physical reference and assigns a coordinate for later positioning; a normal-operation limit interruption need not do so.
Soft travel limit: blocks or rejects a command without a physical endstop hit.^[1]
Emergency stop: a broader stop function with different possible triggers and requirements.
Physical collision avoidance: an outcome that cannot be inferred from a controller's documented interruption alone.

References¶

[1] LinuxCNC Project, Stepper Configuration Wizard, §11 “Axis Travel and Home,” accessed 2026-10-22. First-party controller documentation; cited for limit-switch placement, normal-operation amplifier shutdown, coast distance, and optional home-switch reuse. This is a described configuration, not an observed deployment. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s ↩t ↩u ↩v ↩w ↩x ↩y ↩z

[2] Marlin firmware project, M540 - Endstops Abort SD, “Description,” “Notes,” and “Usage,” accessed 2026-10-22. First-party firmware documentation; cited for the SD-print abort option, build features and enabled-endstop condition. This is a described configuration, not an observed printer run. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s ↩t ↩u