How to Configure Conveyor Counter Outputs for Egg Lines

An egg counter can be counting correctly while the farm management system records the wrong production figure. The usual cause is not the sensor head. It is the way the counter output has been connected, scaled or interpreted downstream. To configure conveyor counter outputs properly, treat the counter, cable run, PLC or logger, and reporting software as one measurement chain. Every part must agree on what a pulse represents and how it will be captured.

For egg collection belts, the preferred arrangement is normally one clean electrical pulse for each egg counted. That simple principle avoids conversion errors and gives the receiving system a direct record of line flow. The configuration work is then focused on matching the counter's output specification to the input hardware and ensuring that no pulse is missed, duplicated or filtered out.

Start with the required production signal

Before setting terminals or software parameters, define what the receiving equipment needs to measure. A PLC may need an individual count input for each collection belt. A farm computer may total eggs by house, row or packer route. An alarm system may only need confirmation that eggs are moving. These are different requirements, even when they originate from the same counter.

A per-egg pulse output provides the greatest flexibility. Each detected egg creates one output event, allowing a PLC or data logger to calculate totals for any shift, flock section or reporting period. It also allows the control system to compare production between belts and identify a stopped or underperforming line quickly.

Do not configure a counter output around an assumed reporting unit such as dozens or trays unless the receiving system specifically requires it. Scaling a one-pulse-per-egg signal inside the PLC is usually clearer than relying on an undocumented conversion at the counter. The raw count remains available for checking when figures do not reconcile.

Check output and input compatibility first

The electrical output from the counter must suit the electrical input on the receiving device. This is a basic commissioning step, but it is where many unreliable installations begin. Confirm the output type in the counter documentation and compare it with the PLC, remote I/O module, production monitor or standalone totaliser input.

The key points are the supply voltage, output type, current capability, switching polarity and common reference. A digital input may expect a sourcing or sinking signal, while the counter may provide a relay contact, transistor output or another defined interface. A relay contact is often straightforward for a simple external totaliser, but an electronic output may be better suited to fast PLC counting. The correct choice depends on the input card and the required count rate.

Also check whether the input requires an external pull-up or pull-down resistor, whether its common terminal is correctly connected, and whether the cable screen must be bonded at one end. Do not rely on wire colour alone when connecting equipment from different suppliers. Use the terminal designations and wiring diagrams for the specific units installed.

Where a counter is being added to an existing control cabinet, verify that the available power supply is suitable and stable. Shared supplies carrying motors, solenoids or worn contactors can introduce electrical noise. A counter may continue to display a correct local total while interference causes false transitions at a sensitive PLC input.

Use the right PLC input type

A standard digital input can be adequate where belt speed and egg flow are moderate, the pulse duration is comfortably longer than the PLC scan cycle, and the input is not heavily filtered. At higher line rates, a high-speed counter input is often the safer option. It records pulse edges independently of normal programme scan time and reduces the chance of lost counts during busy periods.

This choice depends on the output pulse width and the maximum possible eggs per minute, not the average daily production. Commission for the highest expected belt loading. A system that works during routine flow may fail when a backlog releases onto the conveyor after a stoppage.

Configure pulse handling, not just totalisation

The receiving device must recognise each legitimate pulse once. Set the input filter or debounce time only as high as needed to reject electrical noise and contact bounce. Excessive filtering can merge valid pulses when eggs are close together. Too little filtering can allow a noisy cable or switching contact to add false counts.

If the PLC software uses a rising edge to increment a total, keep that logic consistent across all belts. Avoid incrementing on both rising and falling edges unless the output arrangement has been specifically designed for it. One physical pulse has two edges, and treating both as eggs will double the recorded production.

Use a retained counter value if the PLC or monitoring system can lose power. The count should survive a controlled restart, or the system should record a clear reset event. A hidden reset at midnight, after a power interruption or during a programme download creates a production gap that may later be mistaken for a counting fault.

For farms that need shift totals, retain the lifetime or daily raw count separately from calculated shift figures. The reporting layer can reset a shift total without resetting the actual accumulated count from the conveyor counter. This makes fault finding much easier: operators can compare the physical counter display, the PLC raw value and the production report.

Keep cable routing practical

Counter output wiring is low-energy signal wiring and should be treated accordingly. Route it away from motor feeders, variable-speed drive cables, electric fencing circuits and high-current switching conductors. If routes must cross, cross at right angles rather than running in parallel for a long distance.

Use suitable screened cable where required by the installation conditions and follow the equipment guidance for screen termination. A screen connected incorrectly at both ends can create an earth loop in some installations; a screen left floating may provide little protection. The correct arrangement depends on the counter design, panel earthing and cable length.

Cable joints deserve the same attention as the counter itself. Damp junction boxes, loose terminals and poorly crimped conductors are common sources of intermittent pulse loss. Label each cable by house, belt or line position at both ends. When a production figure is queried weeks later, clear identification can save hours of tracing through a cabinet.

Test with a controlled count

Commissioning should include more than confirming that the PLC total changes. Run a controlled verification using a known quantity of eggs or a carefully observed section of belt. Compare the counter display with the value received by the PLC, monitor and any farm reporting platform.

Test at normal operating speed, then repeat at higher flow if possible. Observe the input diagnostics while the belt runs. The counter output indicator, PLC input status and software total should all advance in step. If the local display is correct but the PLC count is low, investigate pulse width, input filtering, scan time and cable interference. If the PLC count is high, look for noise, bounce or duplicate edge logic.

A useful acceptance check includes four operating conditions:

• normal egg flow at routine belt speed;

• closely spaced eggs or maximum expected throughput;

• belt start and stop events;

• a controlled power cycle of the counter and receiving system.

Record the wiring terminal numbers, input address, pulse interpretation and any scaling factors in the panel documentation. A settings sheet fixed inside the control cabinet is more valuable than a parameter remembered by one installer.

Build alarms around useful exceptions

Once the per-egg count is reaching the control system reliably, use it to identify operational exceptions rather than create unnecessary alarms. A line with no pulses during an expected collection period may indicate a stopped belt, a disconnected counter or simply an empty section of house. The alarm logic should account for scheduled collection times and known operating states.

Likewise, a sudden count rate outside the normal range can be useful, but it should not be treated as proof of a fault without context. Egg distribution changes with flock age, feeding pattern, belt timing and house management. Trend data is more useful when each conveyor is recorded separately before totals are combined.

Agro System counters are designed around a precise per-egg pulse, which gives integrators a clear starting point for this type of configuration. The final performance still depends on correct sizing for the conveyor, sound installation and an input system able to capture every event.

A well-configured output does more than produce a number on a screen. It gives the production team a count they can trace from the egg collection belt to the report, check when conditions change, and use with confidence when making day-to-day decisions.