How to Calibrate Egg Pulse Output on a Conveyor

An egg counter can be counting correctly at the belt while the receiving system records the wrong total. The usual cause is not the sensor itself. It is the relationship between the counter’s per-egg pulse output and the PLC, data logger, display or farm-management input receiving that signal. Knowing how to calibrate egg pulse output means verifying the complete counting chain, from egg detection through to the recorded production figure.

For a commercial collection system, calibration is not a matter of adjusting production numbers to match a report. It is a controlled comparison between a known number of eggs and the number of pulses accepted by the connected equipment. If the counter produces one pulse per egg, the receiving device must also be configured to treat one valid pulse as one egg.

Start with the pulse specification

Before testing the line, confirm the output arrangement of the egg counter and the input requirements of the connected control system. A pulse is an electrical event, not automatically an egg count. The receiving input needs to recognise its voltage level, polarity, duration and repetition rate.

Check the installation information for the counter and record the output type in use. Depending on the equipment and installation, this may be a transistor output, relay contact or another switching arrangement. The PLC or logger input must be compatible with that output. A mismatch can create missed pulses, false counts or an input that remains permanently active.

The key settings to establish are the pulse width, the minimum input pulse accepted by the PLC, the input filter or debounce setting, and the scaling applied in software. A counter may generate a clean pulse for each egg, but a PLC input filter set too long can reject pulses when egg flow is high. Conversely, a filter set too short may allow electrical noise or contact bounce to be recorded as additional counts.

Do not assume that a system set to “high speed” is correct. The correct setting depends on the maximum egg rate on that specific belt and the pulse timing produced by the counter.

Isolate whether the error is in counting or recording

A practical calibration test begins by separating the egg counter from the receiving system. First establish whether the counter is detecting eggs correctly. Then confirm that every output pulse is received and scaled correctly.

Use a measured test quantity of eggs, preferably large enough to expose a small percentage error. A sample of 100 eggs can identify an obvious fault, but 500 or 1,000 eggs gives a more useful result on a high-output line. Run the sample under normal operating conditions. Belt speed, egg spacing and product presentation should be representative of production.

Record three figures: the manually verified egg quantity, the counter’s local or diagnostic count where available, and the total shown by the PLC, logger or management system. These figures identify the fault location.

If the manual total and counter total agree, but the receiving system differs, the issue is in the pulse connection, input configuration or software scaling. If the counter total also differs from the manual total, inspect sensor alignment, belt condition and egg presentation before changing any PLC values. Altering software scaling to conceal a detection issue will create unreliable results as operating conditions change.

How to calibrate egg pulse output at the PLC input

Once the egg counter is shown to detect the test batch correctly, calibrate the receiving input against the known quantity. Start with a one-to-one basis: one counter pulse should increase the recorded total by one egg.

View the input status in the PLC diagnostics while eggs pass the counter. The input should change state once for each egg. Where the controller supports a high-speed counter function, use it when belt speed and pulse frequency justify it. Standard scan-based inputs can miss short pulses if the scan time, filter setting or programme logic is unsuitable.

Check whether the programme counts a rising edge, a falling edge or both. One complete output pulse has two transitions. A programme configured to increment on both edges can double the recorded quantity. Similarly, a latching routine that does not reset correctly can fail to count subsequent eggs.

Confirm that the software multiplier is set to 1.00, or to one pulse per egg. Some production systems use scaling factors for batches, trays or reporting units. Those settings may be useful downstream, but the raw egg-count input should remain traceable. Keep the source count as individual eggs and apply reporting conversions separately where possible.

After adjusting settings, repeat the measured test. Compare the accepted pulse count with the test quantity, not only with a displayed production total that may include shift resets, previous counts or aggregation rules.

Set pulse timing for the actual belt speed

Pulse width must be long enough for the receiving equipment to recognise it consistently, yet short enough for individual eggs to produce distinct events at the highest expected throughput. This is where installation conditions matter.

At low belt speeds, an overly long pulse may appear to work without difficulty. At higher flow rates, the input may still be active when the next egg passes. The result can be undercounting. A pulse that is too short can be missed by a conventional PLC input or by a remote data-collection device.

Use the manufacturer’s stated pulse timing as the starting point. Do not alter the counter output merely to compensate for an unsuitable PLC configuration unless the equipment documentation specifically permits the adjustment. In most cases, it is better to configure the receiving input correctly than to move the counter away from its designed operating parameters.

Measure the fastest realistic egg flow, including periods when the collection belt is heavily loaded. Commissioning a system at a slow test speed can give a false result. The calibration must hold at normal flow and at peak collection conditions.

Inspect the installation before changing settings

An electrical adjustment cannot correct a mechanical installation problem. If test results vary between runs, inspect the physical system before changing pulse width, scaling or filters.

The sensor area must be clean and correctly positioned over the belt. Dust, feather debris, belt contamination and damaged guarding can interfere with infrared detection. Check that the conveyor is running true and that eggs pass through the intended sensing zone rather than travelling at an extreme side position or bunching against a guide.

Egg spacing also matters. A two-dimensional infrared counter is designed to distinguish eggs travelling on a collection belt, but poor transfer conditions can create touching eggs, rolling eggs or irregular presentation. Review transfer points, belt speed changes and guides if counts become less stable after an equipment change.

Inspect cable routing and terminations as well. Pulse cables run alongside motors, variable-speed drives and solenoids can pick up electrical interference if they are poorly routed or screened. Intermittent false counts often point to wiring, earthing or input noise rather than a calibration value.

Use a repeatable acceptance test

A calibration result should be documented so that maintenance teams can recognise a future change in performance. Record the date, counter location, belt identification, test quantity, belt operating condition, counter result, received pulse result and any PLC settings changed.

Run at least three test batches. A single successful batch may hide an intermittent connection or an egg-presentation issue. The result should be consistent across repetitions and should remain correct when the belt operates at its normal production rate.

For systems with several collection belts, test each channel independently. Do not transfer settings blindly from one line to another. Conveyor width, belt speed, cable length, PLC hardware and local electrical conditions may differ. This is particularly relevant where different counter sizes are installed across a site, such as an Accucount Mark 5 on a narrow belt and an Accucount N series unit on wider collection conveyors.

Common symptoms and their likely cause

A recorded total that is exactly double the expected figure usually indicates that both pulse edges are being counted, or that a duplicated input is being summed elsewhere in the programme. A total that is consistently half the expected figure can indicate an incorrect scaling factor or a count routine that only accepts every second event.

Intermittent undercounting, especially at high collection rates, usually points to pulse duration, PLC filtering, scan time or pulse overlap at the input. Intermittent overcounting is more often associated with electrical noise, poor earthing, unsuitable debounce settings or an unstable signal connection.

If the error changes with belt loading, look first at egg flow and sensor presentation. If it remains at a fixed ratio regardless of flow, look first at PLC logic and scaling.

A calibrated pulse output gives production staff a dependable raw count they can use for flock performance, collection monitoring and reconciliation. Treat the test as part of planned maintenance, particularly after PLC changes, counter replacement, belt alterations or electrical work. The useful outcome is not a number that looks right on one shift, but a count signal that stays correct as the conveyor works.