A missing component found after placement does not identify where the component was lost. The pocket may have been empty, pickup may have failed, the part may have dropped in transit, or it may have remained on the nozzle. Each possibility points toward different evidence and corrective work.

Identify what the machine actually observes

ASMPT describes a component sensor that checks nozzle-associated component presence at multiple stages of placement. Those stages illustrate a useful diagnostic model. Establish which checks exist and are enabled on the actual machine rather than assuming a feature from another platform is available.

Document the configured package, nozzle, feeder, and detection recipe. Record the meaning of each event code from the equipment documentation. A vacuum threshold, optical height observation, and camera recognition result are different signals. Avoid translating all of them into a single generic pickup-failed category in the production export.

Preserve the event sequence

Observation point Question to investigate
Before pickup Was the expected pocket and nozzle state available?
After pickup Was a component detected in the intended position?
Before placement Did the component remain present during transport?
After release Does the nozzle still carry material, and what board inspection follows?

A retry must remain connected to its original event. If the machine picks another component successfully, the retry resolves immediate placement demand but may not explain what happened to the first part. Follow the machine’s recovery procedure and determine whether loose material or an affected board requires inspection.

Choose the next check from the pattern

For example, repeated empty-pocket events on one reel suggest a different investigation from failures that follow one nozzle across unrelated components. Combine the carrier-orientation review with feeder observations for the first pattern. Use nozzle condition evidence for the second.

Evaluate any detection-setting change with representative acceptable and unacceptable conditions approved for setup verification. Lowering sensitivity until alarms stop can remove useful coverage. Report both nuisance calls and demonstrated detection of the intended fault. Preserve machine-program revision and the component sample used for each verification. The released program should state which placement failures it can identify and which still depend on subsequent board inspection.

Move from reading to a build-ready project

Use the fabrication and assembly checklists to prepare drawings, production files and test requirements.

Open the DFM checklist