Reject Loop Timing for FMCG High-Speed Lines Guide

By James Smith on November 2, 2026

reject-loop-timing-for-fmcg-high-speed-lines-guide

Reject loop timing is the interval between a detector flagging a unit and the reject device removing exactly that unit. It is the sum of detection and control delay, actuator response and the time the unit needs to travel from the inspection point to the reject point. On a fast FMCG line, a timing error of a fraction of a second means the divert hits the wrong pack, and the flagged unit carries on to the customer. Operations teams can measure the latency stack on their own line in a short session.

FMCG High-Speed Lines · Reject Timing

Make Sure the Unit You Flag Is the Unit You Remove

iFactory AI, an on-premise industrial AI platform, helps engineers measure the full detect-to-divert delay and prove it across the whole line speed range.

Detect
Travel: about 0.5 to 2 m
Reject
Bin
0 m1 m2 m

What Is Reject Loop Timing and How Is It Calculated?

The reject device must fire when the flagged unit reaches it. Program the delay from the measured distance and the actual belt speed, not the nominal figure (2M Technology, 2026).

Fire delay
equals
Distance divided by speed
minus
Actuator response
10–100 ms
typical physical actuator response (iFactory engineering guide, 2026)
0.5–2 m
usual distance from inspection to reject station (2M Technology, 2026)
600
encoder pulses over 60 inches at 10 per inch, at any speed (US patent 11373488)

What Adds Up in the Latency Stack?

Each stage adds time. Add them from measurements, not from data sheets. Teams can send a latency worksheet request to get a template.

StageWhere the Delay Comes FromHow to Measure It
Detection and processingCamera exposure, image analysis, detector signalTime stamp at trigger and decision
Network and PLCScan time and message transferLog decision to output change
Actuator responseValve, solenoid or arm movement, 10–100 msHigh-speed recording of the device
Product travelDistance and speed consistencyEncoder count between points
Actuator response depends on mechanism type, air pressure and mechanical wear, so a value measured last year may not hold today.

Why Does Belt Speed Shrink the Tolerance Window?

The window is the gap between packs, in time. As speed rises, the same gap shrinks. The figures below are an illustrative example with a 0.8 m reject distance and 0.3 m between packs.

Slow: 0.5 m per second
Travel time1.6 s
Window between packs0.6 s

Fast: 1.0 m per second
Travel time0.8 s
Window between packs0.3 s

Counting encoder pulses keeps position correct when speed changes, because the pulse count to the reject point stays the same (US patent 11373488).

Find Out How Much Margin Your Reject Really Has

Share your line speeds, pack pitch and reject distance. iFactory AI's team will show the delay budget and how tight the window is at top speed.

Which Reject Method Fits Which Pack?

Pack weight and shape decide the device. Published limits from one metal detector range show the pattern (Mettler-Toledo SL1500 data sheet).

MethodTypical PackWatch For
Air blastLight packs, under 2 kgAir pressure and valve wear
PusherHeavier packs, up to 10 kg or 30 kg by modelFull travel and return time
Overhead sweepPacks that need gentle contactSweep timing against pack gap
Stop on detectSlow or manual-clear linesOperator response and lockout
Record the measured values, not just a pass. A trend from 40 to 80 milliseconds shows wear long before a missed reject does.

How Do You Confirm the Reject Actually Landed?

A reject that is never confirmed is only a hope. Retailer-grade systems add six safeguards (Thermo Fisher Scientific compliance backgrounder).

Reject confirmation
A sensor proves the unit entered the bin.
Bin full
A full bin stops the belt.
Locked bin
Door monitoring prevents removal.
Air pressure
Low pressure raises an alarm.
Enclosed path
Full cover from detector to bin.
Failsafe
If the reject fails, alarm and stop.

How Do You Validate Timing Across the Whole Speed Range?

Run test units at the slowest and fastest observed speeds, not only the nominal one, and test back-to-back rejects (iFactory engineering guide, 2026).

1
Record speed range from start-up to peak
2
Test at slowest speed
3
Test at fastest speed
4
Fire consecutive rejects
5
Record results and limits

Should the Line Stop on Detect or Keep Running?

Both are valid, and the choice follows pack value, speed and risk. Teams can compare both options for their own line in a short session.

Stop on detect
No divert timing to get wrong
Operator clears the unit by hand
Costs line time at every reject
Automatic divert
Line keeps running at speed
Needs measured, validated timing
Needs confirmation and bin controls

Which Reject Faults Fail Silently?

Misfiring ejector
The detector signals while flagged product continues down the line (Oxmaint, 2026).
Worn actuator
Response creeps from tens to hundreds of milliseconds without an alarm.
Speed drift
A drive change shifts travel time, and the fixed delay is wrong.
Overflowing bin
Rejects re-enter the stream downstream of the detector.

Where Does iFactory AI Fit in Reject Timing?

iFactory's integration engineers measure the latency stack across camera, network and PLC and confirm reject placement against the real line speed range before go-live.

Latency Measurement

Detect-to-divert delay is measured on your line, stage by stage.

Speed-Range Validation

Timing is proven from slowest to fastest speed.

Reject Confirmation Log

Every flagged unit is matched to a confirmed divert.

Drift Alerts

Rising actuator response or speed change raises a work order.

Treat a timing change like a product change. After any new drive, belt, valve or recipe speed, re-measure the delay and re-run the reject test before the line is released for production.
Engineer (illustrative): did every flagged unit on line 6 reach the reject bin last shift?
iFactory AI: 41 of 41 confirmed. Actuator response is trending longer, so a work order is open for the air valve.

What Belongs in a Reject Test Record?

Line, product and belt speed at test
Test unit type and how it was introduced
Detection result and time stamp
Reject confirmed in the bin
Back-to-back reject result
Air pressure and bin alarm status
Measured actuator response
Person who signed off the test

Expert Review: Judging a Reject Loop

Expert reviewReject timing on high-speed FMCG lines
What holds up
Measuring each delay, tracking position with an encoder, and confirming every reject with a sensor.
What to verify
Timing at the slowest and fastest speeds, back-to-back rejects, and bin-full and low-air alarms.
What to avoid
Fixed delays copied from a data sheet, untested rejects, and rejects with no confirmation.
Bottom line: measure the delay, prove it at every speed, and confirm each divert.
Written from established packaging line engineering practice. Equipment limits come from your reject device supplier.

Frequently Asked Questions

How do you calculate reject delay on a conveyor?

Divide the measured distance to the reject point by the actual belt speed, then subtract the actuator response time. Use measured speeds, not nominal ones. Work through the sums on your line with our team.

Why do rejects miss at high speed?

At higher speed the gap between packs shrinks in time, so the same timing error now hits the wrong unit. Actuator wear and speed drift add to it. Ask support how to check the window on your fastest recipe.

How long does a reject actuator take to respond?

Physical response is typically 10 to 100 milliseconds, depending on mechanism, air pressure and wear (iFactory engineering guide, 2026). Measure your own device rather than assuming a value. See actuator timing measured in a short demo.

How do you prove a rejected unit reached the bin?

Fit a reject confirmation sensor and a bin-full sensor, and make the line alarm and stop if the reject does not enter the bin (Thermo Fisher Scientific). Log every confirmation. Review a confirmation log built for your line.

Does iFactory AI change the reject hardware?

No. Your air blast, pusher or diverter stays. iFactory AI measures the delay, validates it across speeds and logs each confirmed reject. Plan the integration with our engineers.

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How do you calculate reject delay on a conveyor?","acceptedAnswer":{"@type":"Answer","text":"Divide the measured distance to the reject point by the actual belt speed, then subtract the actuator response time. Use measured speeds, not nominal ones."}},{"@type":"Question","name":"Why do rejects miss at high speed?","acceptedAnswer":{"@type":"Answer","text":"At higher speed the gap between packs shrinks in time, so the same timing error now hits the wrong unit. Actuator wear and speed drift add to it."}},{"@type":"Question","name":"How long does a reject actuator take to respond?","acceptedAnswer":{"@type":"Answer","text":"Physical response is typically 10 to 100 milliseconds, depending on mechanism, air pressure and wear (iFactory engineering guide, 2026). Measure your own device rather than assuming a value."}},{"@type":"Question","name":"How do you prove a rejected unit reached the bin?","acceptedAnswer":{"@type":"Answer","text":"Fit a reject confirmation sensor and a bin-full sensor, and make the line alarm and stop if the reject does not enter the bin (Thermo Fisher Scientific). Log every confirmation."}},{"@type":"Question","name":"Does iFactory AI change the reject hardware?","acceptedAnswer":{"@type":"Answer","text":"No. Your air blast, pusher or diverter stays. iFactory AI measures the delay, validates it across speeds and logs each confirmed reject."}}]}

Prove Every Flagged Unit Leaves the Line

See iFactory AI measure your detect-to-divert delay and confirm every reject. Book a walkthrough using your own line speeds and reject layout.


Share This Story, Choose Your Platform!