Controls and signals

What signals are needed between a cap feeder and capper?

The control interface should show when the capper needs caps, when the feeder should pause, when the chute is full or empty, and how faults are cleared without flooding or starving the capping head.

Request cap feeder advice Call 01494 623015

Build the answer around the real closure and line.

Send representative caps, bottles, photos, available space, capper details and target output so Lancing can test the practical route instead of guessing from a generic feeder description.

Send project details

Direct answer

The control interface should protect the queue between feeder and capper.

A cap feeder control interface normally needs signals that describe demand, supply, faults and safe restart. The exact I/O depends on the capper and control platform, but the engineering purpose is consistent: keep a useful cap queue available without overfilling the chute, starving the capper, restarting into a jam or hiding a recoverable fault from the operator.

Controls should be agreed before build because mechanical design and sensor positions depend on the chosen line behaviour. A late controls discussion can create avoidable wiring, guarding and commissioning changes.

Signal groups

Define signal purpose before naming the exact I/O.

The naming should match the live capper PLC or control panel, but these groups help frame the integration discussion.

Signal group	What it tells the line	Typical design question
Cap demand	The downstream machine is ready for more caps or can accept feed to the chute.	Should the feeder run continuously, intermittently or only on capper demand?
Cap queue / cap-in-chute	The transfer route contains a suitable number of correctly presented caps.	Where is the sensor placed so it reflects the capper's real need?
Low level	The hopper, bowl or track is approaching a point where operator refill is needed.	Is the warning only advisory, or should it stop the line before starvation?
Jam or misfeed	A blockage, timeout, reject overload or repeated failed presentation requires intervention.	Should the feeder stop alone, or should the capper and conveyor also pause?
Guard or access state	A guard, door or access point is not in the expected production condition.	What is the controlled restart sequence after the area is made safe?
Reset and mode	The operator or engineer confirms manual, automatic, clean-down or setup condition.	Which settings are operator-controlled and which need engineering authority?

Integration sequence

Use a simple sequence before writing the final logic.

Define normal run

Agree how the feeder starts, keeps the queue supplied and stops when the capper pauses.

Define shortage

State what happens when hopper, bowl, chute or outlet level falls below the useful threshold.

Define blockage

Agree jam timeout, alarm wording, isolation boundary and how caps are cleared safely.

Define restart

Check that the restart sequence does not release unexpected caps or hide a repeated fault.

Buyer questions

Control questions to answer before installation.

Can controls be added to an existing capper?

Often they can, but the available signals, panel space, wiring access and safety architecture need checking. A retrofit may need a local control panel, agreed handshakes and clear operator messages rather than a direct change to the original capper program.

Should cap feeder signals be hardwired or networked?

The answer depends on the site standard, existing PLC, safety requirements and diagnostic expectations. Hardwired signals are simple and robust for basic demand and fault states, while networked integration may help where richer alarms or line data are needed.

What information should be sent for a controls review?

Send photos of the capper panel and handover area, the current machine make and model, available drawings, supply voltage, required alarms, line stop behaviour and the production team’s preferred fault messages.

How should controls be accepted?

Acceptance should test normal run, low caps, full chute, blocked chute, capper stop, capper restart, guard opening if applicable, power cycle and operator reset. The exact tests should be agreed before installation.

Discuss controls View integration guide

Related controls routes

Connect signal planning to the capper handover.

Feeder-to-capper handoverDefine the mechanical outlet and release point.Line stop controlPlan behaviour when the capper pauses or faults.Cap-in-chute sensorsControl the queue between feeder and capper.