Why Counters Double Count on Egg Belt Systems

An egg count that suddenly runs high is not a minor reporting error. On a commercial collection system, it can distort house performance figures, feed conversion calculations, flock comparisons and packing forecasts. Understanding why counters double count starts with one basic question: is the counter seeing an egg twice, or is a correctly generated count signal being recorded twice elsewhere?

Those are different faults. Treating them as the same problem often leads to unnecessary sensor changes while the real cause remains on the belt, in the mounting arrangement or in the farm's control wiring.

Why counters double count on egg belts

An egg counter is intended to register one event for each egg passing through its sensing area. Double counting occurs when the system receives two count events associated with what operators regard as one egg. The second event can be created mechanically, optically or electrically.

The first step is therefore to separate the count point from the reporting point. Check the counter's local indication or diagnostic output against the total received by the PLC, data logger or production-management system. If the local count is correct but the management total is high, the fault is downstream. If the local count itself is high, inspect the belt and the counter installation first.

This distinction saves time. It also prevents production staff from adjusting settings to compensate for a problem that changes with belt condition, line speed or electrical load.

The egg moves through the sensing area twice

The most common physical cause is repeat movement. An egg reaches the sensing zone, is counted, then rolls back or is carried back across part of the detection area before continuing forward. This can happen on transfer points, around poorly supported belt sections, or where a belt has a slight reverse motion during starts and stops.

A stop-start collection line deserves particular attention. When the drive stops abruptly, eggs can continue travelling on their own momentum. When the belt restarts, a loose egg may change position again. If the sensing point is close to a transfer, a guide or a section where the belt flexes, that movement can create a second valid detection.

Look for egg accumulation immediately before and after the counter. Eggs held against one another can separate as the belt moves, rotate around a side guide or change lanes. The issue may be intermittent, which is why a short visual inspection at low belt speed can miss it. Observe the line under normal loading, including the period when egg flow is heaviest.

Belt tracking also matters. A belt that walks from side to side may guide eggs through a different part of the sensing field on successive movements. Correct the belt tension, tracking and support before changing electronic settings. A count system cannot compensate for unstable egg presentation indefinitely.

Transfer points and belt condition

A damaged joint, raised belt splice, worn roller or unsupported section can introduce a small but repeatable bounce. The egg may not visibly travel backwards, yet it can lift, turn or shift enough to produce two separate detection events. This is especially likely where the counter is fitted too close to a roller, bend or transfer gap.

Inspect the belt surface for contamination, damaged slats, loose material and uneven joins. Check rollers for run-out and ensure the counter mounting frame is not moving with the conveyor. A sensor mounted on a vibrating guard or unsupported bracket is effectively moving relative to the eggs.

The best sensing position is usually a stable, straight section of conveyor where eggs are travelling in one direction with consistent spacing and support. It depends on the conveyor layout, but counting at a mechanically quiet point is generally more effective than attempting to filter out movement caused by a poor location.

Incorrect sensor position or alignment

Two-dimensional infra-red egg counters are designed around a defined sensing area. Their mounting height, alignment and position across the belt are part of the measurement system, not minor installation details. If the unit is tilted, mounted at the wrong clearance or offset from the egg path, its detection pattern may not match the belt conditions it is expected to monitor.

For narrow belts, it is easy to assume that a centrally mounted counter will cover every egg path. In practice, side guides, belt drift and egg flow patterns can move eggs away from the expected line. On wider conveyors, correct model selection and careful positioning become even more significant because eggs may travel in several lanes and may converge near a transfer.

A counter should be installed square to the conveyor and fixed rigidly. Check that the sensing faces are clean and that their position has not changed after maintenance. A bracket can be knocked during wash-down, belt work or guard removal without appearing obviously damaged.

Do not use a mounting position where adjacent equipment repeatedly obstructs the field. Deflectors, guide fingers, loose belt edges or parts of a transfer arrangement can create unwanted detections, particularly if their position changes with belt movement. The counter must see eggs, not moving conveyor hardware.

Match counter width to the conveyor

Using a sensing arrangement that does not suit the conveyor width can produce poor coverage or unpredictable egg paths at the edges. The solution is not always a wider unit. A wider sensing area fitted to a belt with uncontrolled egg flow can still experience repeat events if eggs circulate, bunch or cross through the count zone more than once.

The selected counter and its installation should reflect the actual belt width, guide arrangement and egg presentation. Agro System's Accucount Mark 5 and Accucount N series are intended for different conveyor widths, but correct sizing must be followed by correct mechanical installation. The counter width, belt stability and line geometry work together.

Electrical pulses can be counted twice downstream

A per-egg pulse from the counter may be correct while the receiving equipment records two increments. This is common where a counter has been connected to an existing PLC input, relay interface or third-party recording device without checking the required pulse characteristics.

The receiving input must be configured to accept one pulse as one egg. If its scan cycle, edge detection, debounce setting or input filter is unsuitable, it may react to a signal transition more than once. The problem can also arise when both rising and falling edges are being used as count events.

Check whether the reported total doubles exactly over a sustained period. A near-perfect doubling often points to signal handling rather than egg movement. A variable overcount that becomes worse during heavy flow is more likely to be mechanical or optical, although both faults can exist on the same line.

Wiring condition is equally relevant. Loose terminals, damaged cable insulation, poor screening and shared electrical noise can create false transitions at the receiving input. Route signal cable sensibly, keep power and signal connections secure, and verify the counter's supply against its specification. A supply problem may not stop the counter completely. It can instead produce intermittent behaviour that is difficult to identify from daily totals alone.

A practical fault-finding sequence

Avoid changing several things at once. Work from the egg movement to the recorded figure so each test provides a clear result.

1. Run a known quantity of eggs through the line and compare the local counter total with the PLC or management-system total.

2. Watch the sensing zone at normal operating speed and loading. Look for rollback, oscillation, bunching, egg rotation and repeat passage after a stop or transfer.

3. Inspect belt tracking, joins, rollers, support, guides and the rigidity of the counter bracket.

4. Confirm the counter is square, clean and mounted at the specified height and position for the belt.

5. If the counter total is correct but the displayed production total is not, inspect the pulse input configuration, wiring, grounding and signal interface.

Record the result after each change. A simple test log showing belt speed, line condition, local count and reported count will usually reveal whether the fault follows the mechanical line condition or the electrical reporting path.

Do not compensate for an overcount in software

It can be tempting to apply a correction factor once the overcount appears consistent. That approach may make a daily total look reasonable, but it conceals the fault and fails as soon as belt loading, egg size, speed or electrical conditions change. It also makes production data less useful when comparing houses or identifying collection losses.

A dependable count comes from stable egg presentation, correctly sized and aligned sensing equipment, and one clean pulse accepted once by the receiving system. When the line is set up this way, the count becomes a useful operating measurement rather than another figure that needs explaining at the end of the day.

If the cause is not immediately visible, begin with a controlled count test at the counter and follow the signal through the system. The point where the extra count first appears is the point that needs correction.