Parcel gapping control is the unglamorous link between singulation and reliable sortation. It governs the physical spacing of parcels as they approach induction metering, and that spacing determines whether downstream scanners, merges, and destination chutes operate cleanly or suffer from recurring misreads and jams. This article explains the operating context of gapping control, the components that influence it, the signs that indicate drift or failure, and the boundaries within which maintenance and controls teams should act.
The Role of Gapping in Induction and Singulation #
In a courier hub, the induction point is where individually singulated parcels are released onto a high-speed mainline that carries them through scanner tunnels and toward destination chutes. Gapping is the distance, measured in time or millimetres, between the trailing edge of one parcel and the leading edge of the next. That distance must be large enough for the controls system to separate, track, and assign each parcel, but small enough to preserve throughput during peak dispatch windows.
Too little gap leads to two parcels being read as one, overlong parcel windows, or same-address parcels travelling so closely that downstream divert actions collide. Too much gap wastes mainline capacity, reduces the number of parcels scanned per hour, and forces the hub to extend induction windows. Gapping control is therefore not a single device but a behaviour produced by the interaction of sensors, conveyors, stops, drives, and the PLC logic that coordinates them.
Component Interaction From Infeed to Dispatch #
The gapping chain begins well before the metering belt. Parcels arrive from receiving, are de-palletised, and pass through buffer conveyors and merges. Each merge decision, each belt speed change, and each singulator centring action alters the arrival pattern at the induction metering point. The relevant component chain is usually:
- Infeed belts and merge sections that combine multiple parcel streams.
- Singulation devices, including side belts, centring rollers, and spacing wheels, that separate side-by-side or overlapping parcels.
- Metering belts with variable-speed drives that set the release speed into the mainline.
- A release stop, typically a pneumatic or servo-driven gate, that holds the parcel until the PLC releases it at the correct moment.
- Photoeyes and encoders that measure parcel length, belt speed, and the actual inter-parcel gap.
- The scanner tunnel entry point where the mainline accepts the released parcel and confirms its identity.
When any of these components drifts, the effect often appears downstream at the scanner tunnel rather than at the component that caused it. That is why early warning signs must be traced back along the chain rather than treated where they first appear.
Key Inspection Points #
Effective gapping inspection focuses on a small number of physical locations. These are the points where spacing is created, measured, or lost.
Infeed and merge zones. Inspect the merge logic and its blocking sensors. If two incoming lines converge, the controls must hold one parcel while the other passes. Check that the merge photoeyes are clean, correctly aligned, and not reacting to reflections from shiny tape or packaging film. A delayed blocking signal at a merge will create a paired parcel that travels all the way to induction as one double.
Singulator and separation section. Check side-belt pressure and centring rollers for wear. A singulator that no longer centres parcels reliably will present parcels to the metering belt at an angle, causing the gap photoeye to misread parcel length and release the next parcel too early. Inspect spacing fingers or wheels for missing segments, as these directly control physical separation.
Metering belt and release stop. Verify that the variable-speed drive is running at its commanded speed under load. Check encoder wheel traction on the belt surface, since a slipping encoder will make the controller believe the belt is faster than it is, leading to late releases and oversized gaps. Inspect the release stop for worn cushioning or sticky pneumatic action. A stop that does not fully retract will scrape the parcel and slow its launch into the mainline.
Scanner tunnel entry. The photoeye just before the scanner is the point where gapping is effectively measured for sorting purposes. Confirm that this sensor is positioned at the manufacturer-recommended distance from the scanner trigger. A sensor mounted too far upstream will generate a gap measurement that does not reflect the actual spacing at the scan field.
Observable Symptoms and Early Warning Signs #
Gapping faults rarely announce themselves as a single alarm. They appear as patterns in operational data and as subtle physical clues. Early signs include:
- Repeated double scans or multiple parcels assigned the same tracking identity at induction.
- Intermittent jams at downstream merge points or chute entry points, particularly during peak rate.
- An increasing number of parcels flagged as untracked or lost between scanner tunnel and chute.
- Gap readings on the HMI that are consistently near the minimum threshold, even when throughput is average.
- High gap variability, meaning the interval between parcels swings widely, rather than being uniformly short or long.
- Motor current traces on the metering belt that show repeated overload peaks, suggesting the belt is accelerating parcels that were not fully released.
- Phantom parcels, where the controls believe a parcel is present but no physical parcel passes the sensor, often caused by a sensor reading a reflective surface or a lingering voltage spike.
Any single symptom can be dismissed as a one-off event. The warning becomes significant when two or more symptoms occur within the same operating shift, or when the pattern repeats on successive days at the same time of day.
Evidence Collection and the Diagnostic Table #
Before changing any tuning parameter, collect evidence that separates a controls problem from a mechanical problem. Useful evidence includes time-stamped gap logs, photoeye event counts, VFD current traces, encoder speed comparisons, and a record of recent maintenance work on the relevant section. The table below summarises common gapping fault patterns and the evidence needed to identify their cause.
| Observed Condition | Likely Contributors | Evidence to Gather |
|---|---|---|
| Consistently short gaps at release | Incorrect release timing in PLC logic, encoder overspeed, worn release stop membrane | Time-stamped gap logs, VFD speed trace, encoder wheel condition report |
| Random short gaps only after a merge | Merge blocking sensor delayed, merge belt speed mismatch, parcels arriving overlapped | Photoeye event timestamps at merge, belt speed setpoints, video review of merge section |
| Large gaps after singulator | Worn spacing fingers, side-belt pressure too high, singulator drive slip | Singulator torque readings, visual inspection of spacing devices, belt surface condition |
| Gap grows during peak rate | Infeed cannot supply parcels fast enough, metering belt accelerating poorly, stop releasing late under load | Infeed photoeye counts, VFD current trace at high rate, stop position sensor signal |
| Intermittent double parcels at scanner entry | Photoeye not detecting gap due to reflection, parcel tilt, sensor height misadjusted | Sensor sensitivity setting, parcel height range in that shift, ambient lighting condition |
Common Interpretation Errors #
Diagnosing gapping faults is prone to a few recurring mistakes. The most common is confusing parcel length with gap data. If the encoder measuring belt travel is slipping, the controller will calculate a parcel as longer or shorter than it really is, and the gap calculation will be wrong even though the sensor signals are correct. Always verify belt speed with an independent measurement before interpreting length-based logs.
A second error is tuning for the minimum gap at the metering belt without confirming the actual physical gap at the scanner entry. Parcels can be slowed by friction, tilted by worn rollers, or accelerated by a downstream belt running faster than the metering belt. The gap that matters is the one at the scan field, not the one in the PLC register.
A further error is assuming that a sensor fault is a controls fault. A photoeye with a scratched lens, loose bracket, or accumulated dust may produce intermittent signals that look like erratic PLC logic. Conversely, a mechanical fault such as a stiff pneumatic stop can be misread as a tuning problem because the gap pattern appears consistent. Mechanical inspection and controls analysis must proceed in parallel, not sequentially.
Maintenance Implications and Tuning Boundaries #
Gapping control depends heavily on routine mechanical care. Belt tension, drive roller condition, sensor cleanliness, and encoder wheel traction are the primary physical influences on gap accuracy. Lubrication of pneumatic stops and hinge points should follow the hub maintenance schedule, and any work that affects belt speed or sensor position must be recorded so that controls engineers do not chase faults caused by a changed baseline.
Tuning boundaries are defined by the OEM commissioning settings and by the physical capability of the conveyor system. Do not reduce the minimum parcel gap below the value stated in the OEM documentation, and do not attempt to compensate for mechanical wear by adjusting release timing. If the gap is consistently short or long, the underlying cause is usually mechanical or sensor-related, not a tuning deficiency.
Safety and operational procedures take priority over any advice in this article. Site procedures, lockout requirements, OEM documentation, and competent engineering judgment must always be followed before inspecting moving machinery, adjusting drives, or modifying control parameters.
Decision Boundaries: Stop, Observe, Escalate #
Not every gapping discrepancy requires an immediate stop. A slight increase in gap variability during peak hours may be acceptable if downstream missort rates remain unchanged. However, certain conditions justify stopping the affected induction line and escalating to a competent engineer:
- Consecutive double parcels reaching the scanner tunnel, indicating a loss of parcel identity tracking.
- Repeated jams at chute entry points that are clearly linked to tight gaps on the mainline.
- Evidence that a sensor is providing false presence signals, which can cause the system to release parcels into an occupied zone.
- Any condition that causes parcels to contact each other at high speed, risking damage or an unsafe divert action.
When escalation is required, hand over the collected evidence, the exact timeline of the fault, and any recent maintenance records. A calm, evidence-based handover allows the responsible engineer to distinguish between a one-off sensor glitch and a systemic gapping failure before making permanent changes.
Key Takeaways #
- Gapping is a system behaviour, not a single device; failures at merges, singulators, and stops all appear at the scanner entry.
- Inspect the four key zones: infeed and merges, singulation, metering and release, and scanner entry.
- Look for patterns, such as repeated double scans, phantom parcels, or gap variability, rather than single isolated alarms.
- Collect time-stamped logs, VFD traces, and photoeye counts before changing any control parameter.
- Verify belt speed and sensor alignment independently before interpreting length-based gap data.
- Treat mechanical maintenance and controls tuning as parallel workstreams; neither alone explains all gapping faults.
- Never reduce minimum gap settings below OEM recommendations, and always follow site lockout and safety procedures.
- Escalate when parcel identity tracking is lost, when chute jams become recurring, or when sensor signals appear unreliable.
