When a machine with incremental feedback powers up, it counts position from wherever it happens to be, which means it has no idea where its axes actually sit in the world. Before it can run safely, each axis must find a known physical reference and set its position from it. That startup routine is called homing. This guide explains why incremental axes need to home, walks through the common homing methods from limit switches to index pulses to hard stops, and explains why absolute encoders let a machine skip the homing routine entirely.
Homing in one line: Homing is the startup procedure that establishes an absolute position reference on an axis whose feedback is incremental. Because an incremental encoder only counts changes in position and starts from zero at power-up, the axis does not know its true location until it moves to a known physical feature, such as a home switch, sensor, or hard stop, and sets its position from that reference. Once homed, the axis's position readings correspond to real machine coordinates and normal moves can begin.
An incremental encoder does not report an absolute position; it reports change. It emits pulses as the axis moves, and the controller counts those pulses up or down to track how far the axis has travelled from wherever it started. When power is removed, the count is lost, and when power returns the controller simply starts counting from zero at the axis's current, unknown location. So an incremental axis wakes up believing it is at zero no matter where it physically is, and any move commanded from that false belief could send it in the wrong direction or into a mechanical limit.
Homing solves this by tying the counted position to a real physical landmark on the machine. The axis is driven, carefully and usually slowly, until it reaches a known reference feature whose exact location in machine coordinates is defined. At that moment the controller overwrites its position count with the known coordinate of that feature, and from then on every subsequent count is anchored to real machine geometry. The axis now knows where it is, and the whole coordinate system of the machine is calibrated against that home reference.
This is why homing is almost always the first thing a machine does after power-up, before it will allow production moves. Until an axis is homed, its position is untrustworthy, and good controllers refuse to run normal programmed motion on an unhomed axis for safety. The homing sequence is deliberately conservative, moving slowly and watching for the reference and for limits, precisely because the machine does not yet know where anything is until the reference is found.
The simplest method uses a limit or home switch. The axis moves toward a switch mounted at a known position, and when the switch trips the controller takes that as the reference. This is easy and robust but only as accurate and repeatable as the switch itself, which can trip at slightly different points depending on approach speed and switch quality, so it suits applications where modest home repeatability is acceptable.
A far more precise and very common method combines a home sensor with the encoder's index pulse. The encoder emits one sharp index pulse per revolution at a fixed mechanical angle, which is highly repeatable. The axis first finds the coarse home switch to get into the right region, then creeps until it sees the next index pulse and takes that exact pulse as the reference. This two-stage approach gives both an unambiguous general location from the switch and a precise, repeatable final reference from the index, which is why it is a workhorse method for accurate machines.
A third approach dispenses with a switch and homes against a hard stop. The axis is driven gently into a fixed mechanical end of travel under a reduced torque limit, and when it can move no further and the torque saturates against the stop, the controller takes that position as the reference. This is attractive where adding a switch is awkward, but it relies on a well-defined, repeatable hard stop and on carefully limiting the torque so the axis does not damage itself pressing into the stop. Whichever method is used, the homing sequence usually specifies a direction, an approach speed, and a slow final creep so the reference is found consistently every time.
An absolute encoder changes the picture entirely because it reports the axis's actual position directly, not just changes from an unknown start. At power-up, an absolute encoder immediately tells the controller where the axis is, so there is no need to move anywhere to find a reference. A single-turn absolute encoder knows position within one revolution, and a multi-turn absolute encoder, which counts revolutions using a backup power source or a geared mechanism, knows the full position across the axis's whole travel even after power has been off. In both cases the homing routine is unnecessary; the axis simply knows where it is the instant it powers on.
This is a real operational advantage. A machine with absolute feedback is ready to run immediately, without the time, motion, and risk of a homing sequence, which matters when homing a large or heavily loaded axis is slow or when moving an unhomed axis could cause a collision. The trade is cost and, for multi-turn devices, dependence on a backup battery or a mechanical counting scheme that must be maintained. Many machines mix the two, using absolute feedback on axes where startup motion is undesirable and incremental with homing where cost is the priority.
For operations overseen through cloud SCADA, the homing status of a machine's axes is a small but meaningful piece of readiness information. A platform such as Merobix can surface whether equipment has completed its startup reference sequence and is ready to produce, or whether it is still unhomed after a power event, which is useful when the machine sits at a remote site with nobody standing beside it. A pattern of homing failures, or an axis that struggles to find its reference, can point to a failing home sensor or a mechanical problem worth investigating, and bringing that state into a central monitoring view helps a team confirm that distributed equipment has come back cleanly after an outage without a trip to the site.
Generally no. An absolute encoder reports the axis's true position at power-up, so the controller knows where the axis is without moving it to find a reference. A multi-turn absolute encoder also retains its count across power cycles, so even the full travel position is known immediately. The homing routine is really a requirement of incremental feedback, which only counts changes and starts from an unknown zero, and absolute feedback removes that requirement.
A home switch alone can trip at slightly different positions depending on speed, wear, and switch quality, which limits how repeatable the home reference is. The encoder's index pulse occurs at one fixed, highly repeatable mechanical angle per revolution. Homing to the switch first to get close, then to the next index pulse for the exact reference, combines a reliable general location with a precise final reference, giving far better home repeatability than the switch by itself.
Hard-stop homing drives the axis gently into a fixed mechanical end of travel under a reduced torque limit until it can move no further and the torque saturates, then takes that position as the reference. It avoids needing a dedicated home switch, which is handy on simple or compact axes, but it depends on a well-defined, repeatable stop and on limiting the force carefully so the axis does not damage itself or the mechanism while pressing into the stop.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.