Sorter carrier tracking is the invisible thread that links induction decisions to discharge events. On a high-speed parcel sorter, every carrier is both a physical asset and a logical record; the controls system must know where a carrier is, which parcel it carries, and exactly when to trigger an action. Tracking is not a single sensor reading but a continuous model assembled from encoder counts, registration events, and carrier identity. This article explains the operating principles of that model, the hub boundaries where tracking responsibility changes hands, and the practical evidence that helps sortation teams distinguish a genuine tracking fault from a mechanical or procedural issue.
What Carrier Tracking Actually Does #
Tracking solves a simple but brutal problem: a sorter moving at speed gives each carrier only a short window to read, hold, and release a parcel. The control system needs a stable representation of carrier position that survives vibration, wheel slip, thermal expansion, and the constant flow of parcels. That representation is a virtual map held in the programmable logic controller (PLC), with each carrier stored as a record containing its identity, current position, assigned parcel data, destination, and discharge state.
The tracking function performs three tasks simultaneously. It confirms that a parcel has been successfully transferred onto a carrier at induction. It computes the precise position at which the carrier must trigger discharge or diversion. It also verifies that an action actually occurred, so that a missed discharge can be detected and the parcel recirculated rather than silently lost. In a courier hub, these tasks directly determine destination accuracy, recirculation load, and the number of parcels that must be manually re-handled downstream.
Components That Build the Tracking Picture #
The tracking model depends on a small group of interacting components: the encoder that measures motion, one or more registration sensors that anchor the count to physical reality, carrier markers or flags that identify individual carriers, and the PLC software that maintains the carrier map. No component is authoritative on its own; each contributes a layer of evidence that the system continuously reconciles.
Encoders and Registration #
An incremental encoder mounted on a drive shaft or drive wheel produces a pulse train as the sorter moves. The PLC counts these pulses to estimate distance travelled and to compute when a carrier has reached a discharge position. Because encoders measure rotation rather than actual belt or chain travel, they are vulnerable to wheel slip, coupling wear, and mechanical backlash. A registration sensor, typically a photo-eye or proximity detector, looks for a physical marker on the sorter structure and resets the counting scheme at a known reference point. Without registration, small per-revolution errors accumulate until the virtual carrier position drifts one or more carriers away from the physical reality.
Carrier Identity and the Carrier Map #
Each carrier is usually identified by a mechanical flag or coded target that the registration system reads as the carrier passes. The PLC stores a carrier record in a ring buffer or indexed array, so the position of a record in the map corresponds to the physical carrier’s place in the train. As the sorter moves, the PLC advances the index. When a parcel is inducted, the system writes the parcel data into the carrier record. When the carrier reaches the programmed discharge point, the system reads the record and initiates the tip, tilt, or cross-belt action. The map is only as trustworthy as the counts and registration events that keep it aligned; if the map loses alignment, the system may act on the wrong carrier, discharge to the wrong spur, or hold parcels that should have been released.
Tracking Boundaries Inside the Hub #
Tracking responsibility is not uniform across the sorter. It is useful to think in terms of boundaries where one system’s authority ends and another begins. These boundaries are the induction handoff, the discharge event, and the recirculation loop. Each boundary has distinct failure modes and distinct evidence trails.
Induction Boundary #
The induction boundary is where the parcel leaves the induction conveyor and enters the carrier’s ownership. The tracking system must confirm that the parcel physically crossed the handoff sensor and that the carrier record was written correctly. If the handoff confirmation is missed, the system can create a “ghost parcel” that remains in the carrier record long after the parcel has fallen or completed its cycle. Induction timing windows are deliberately tight; at high speed, the parcel must be placed within a narrow envelope of carrier position. A tracking offset at this boundary becomes visible as spurious recirculation, parcels that are never assigned, or parcels that are discharged from the wrong carrier.
Discharge Boundary #
The discharge boundary is the most safety-critical tracking point on the sorter. The system uses the carrier position, the parcel destination, and the spur sensor state to decide when to trigger discharge. It must also respect downstream conditions such as a full chute or a blocked slide, because a parcel discharged into an occupied spur can cause a jam or a damaging impact. After discharge, a confirmation sensor or bump-check verifies that the parcel left the carrier. This confirmation is essential: without it, the system cannot distinguish between a successful discharge and a parcel that rode past the spur, and recirculation decisions become unreliable.
Recirculation Boundary #
Parcels that miss their spur, are scanned late, or are rejected for data quality issues continue around the loop and return to the induction area. The recirculation boundary is a logical boundary rather than a physical handoff. The carrier record must remain valid for the full circumference of the sorter, which means the tracking model must survive the mechanical shock of the loop, the transition from one drive segment to another, and any splice or joint in the chain or belt. If the model loses a carrier at the loop transition, the system may overwrite a valid parcel with a new induction, causing misroutes and unexplained losses.
Observable Symptoms of Tracking Degradation #
Tracking faults rarely announce themselves as a single catastrophic event. They degrade incrementally, and the early symptoms are often attributed to mechanical issues or operator error. Common observable signs include:
- Parcels consistently discharging one spur early or one spur late, especially at higher sorter speeds.
- Frequent “empty carrier” discharges, where the PLC initiates discharge for a carrier whose parcel was already released or never loaded.
- Parcels recirculating repeatedly even though the spur was not full and the destination address was valid.
- Intermittent induction jams that correlate with speed changes or surge conditions.
- Recirculation volume rising steadily while the induction rate and parcel mix remain constant.
- Discharge confirmation counters showing more discharge initiation events than confirmed parcel exits.
These symptoms tend to be periodic because they repeat with the sorter’s physical loop. A tracking drift of one carrier, for example, will produce errors that appear at every spur but only under certain load patterns. Understanding that periodicity is essential for diagnosis.
Evidence Collection and Interpretation #
When a tracking fault is suspected, the control system’s time-stamped logs are the primary evidence source. The table below summarises practical diagnostic guidance for common symptom patterns.
| Observed Symptom | Likely Tracking Area | Data to Collect | First Checks |
|---|---|---|---|
| Parcels discharge one spur early or late | Encoder count offset or registration reference drift | Spur sensor time stamps, carrier index at discharge, discharge confirm sensor log | Verify registration sensor pulse, inspect encoder coupling for slip or backlash, compare PLC carrier count to physical carrier markers |
| Repeated “empty carrier” discharges | Carrier map desync or missing induction handoff | Carrier record history, induction sensor time stamps, discharge initiation log | Check carrier map wrap-around, confirm induction handoff sensor is clean and aligned, review zeroing routine at shift start |
| Jams at induction only at high speed | Tracking latency or encoder drift | Drive motor speed signal, encoder pulse count, induction photo-eye timing | Measure drive wheel slip, inspect encoder mounting, verify registration marker position after a maintenance intervention |
| Recirculation rises for the same parcel mix | Missed discharge confirmation or chute occupancy conflict | Discharge confirmation counter, full-chute status, recirculation entry sensor log | Test discharge confirmation sensor, review chute-full logic, check for a blocked spur that prevents confirm signals |
Collecting evidence should always follow site-specific procedures. The intent is to establish whether the error is constant, periodic, or random. A constant offset usually points to registration or mechanical reference issues. A periodic error that repeats every loop points to a single damaged marker or a localised mechanical anomaly. Random errors are more often related to sensor noise, intermittent handoff failures, or communication issues between the induction and sorter controllers.
Common Interpretation Errors #
Experienced maintenance teams can still misinterpret tracking evidence. The most common errors include:
- Assuming the encoder is an absolute position source. An encoder is a relative device; it only tells the system how much motion has occurred since the last reference. Any drift or slip is invisible until a registration sensor detects it.
- Confusing carrier index with physical position. The PLC’s carrier record index is a logical construct. When the map is shifted, the index may be internally consistent while physically wrong.
- Attributing discharge problems to the discharge mechanism itself. A tipped tray that does not fail mechanically may still discharge at the wrong location because the trigger point was computed from a drifted tracking model.
- Changing tracking constants, such as discharge lead times, without first logging the actual carrier position against the sensor evidence. This often masks the underlying drift and creates a secondary error at other sorter speeds.
- Ignoring operator shift logs that record registration zeroing or manual carrier resets. These events are valuable evidence of long-term drift patterns.
Maintenance Implications and Decision Boundaries #
Tracking accuracy is a maintenance and controls issue at the same time. Routine checks should include verifying encoder coupling integrity, cleaning and aligning registration sensors, confirming the presence and integrity of carrier markers, and testing discharge confirmation sensors. A scheduled zeroing routine, performed with the sorter empty and at low speed, allows the control system to re-establish the carrier map and provides a baseline for detecting drift. Changes to the mechanical drive chain, tensioning, or carrier replacement must be followed by a tracking verification, because even a small change in chain pitch can invalidate the existing map.
There are clear decision boundaries. If a tracking error is intermittent and cannot be reproduced on demand, stopping the sorter may be justified to inspect sensors and mechanical references. If the error is constant, the first response should be a full registration and zeroing cycle, not an adjustment of discharge constants. If the error persists after cleaning, alignment, zeroing, and encoder checks, the issue may lie in the controls application logic or in an undocumented mechanical modification. At that point, escalation should follow the OEM technical support path or the site’s internal engineering review process. This article does not override any of those authorities.
Safety is the non-negotiable boundary. All diagnostic work, sensor inspection, and mechanical adjustment must be performed in accordance with site procedures, including lockout and tagout requirements. Where OEM documentation, site engineering judgment, or safety regulations conflict with general guidance, the site authority takes priority. Do not attempt to modify the tracking system or its safety interlocks to compensate for an unexplained fault; masking a functional problem with forced discharges or bypassed confirmation sensors is dangerous and never acceptable.
Key Takeaways #
- Carrier tracking is a model of the sorter, not a direct reading of reality; it depends on encoder counts, registration events, and the PLC carrier map working together.
- The three critical tracking boundaries are induction handoff, discharge confirmation, and recirculation, and each has its own failure signatures.
- Symptoms such as early or late discharges, empty carrier actions, and rising recirculation often indicate tracking drift before any mechanical fault is visible.
- Evidence must come from time-stamped logs, discharge confirmation counters, and registration events, and the error pattern should be classified as constant, periodic, or random.
- Encoder drift and registration misalignment are more common causes of dispatch errors than mechanical failure of the discharge mechanism itself.
- Changing discharge constants without first re-establishing the carrier map masks the root cause and introduces new errors.
- Routine zeroing, sensor cleaning, and coupling inspection are essential maintenance tasks for sustained destination accuracy in high-speed courier hubs.
- Always apply site procedures, lockout requirements, and OEM guidance, and escalate to competent engineering judgment when the fault persists beyond standard corrective actions.
