Elecrow PCBA AOI Inspection Guide for SMT Assemblies
Elecrow PCBA AOI guide: pre and post-reflow defect detection, SPI pairing, design for inspection, first-article tuning, and SMT yield improvement tips.
Automated optical inspection (AOI) is the primary gate between SMT placement and reflow verification on most Elecrow PCBA lines. It catches missing components, wrong orientation, shifted placements, marginal solder joints, and bridge conditions faster than manual review alone. Yet AOI is only as effective as the data, lighting, and acceptance criteria behind it. A board designed without inspection in mind can pass electrical test while hiding defects AOI was never configured to find.
This guide explains how AOI fits into SMT assembly, what defects it detects reliably, where it has blind spots, and how design and documentation choices improve first-pass yield. Whether you are preparing a prototype run or scaling to production, understanding Elecrow PCBA AOI expectations helps you reduce rework, shorten debug cycles, and build inspection data into continuous process improvement.
Where AOI sits in the SMT flow
Typical SMT sequence includes solder paste print, paste inspection (SPI), component placement, pre-reflow AOI or post-reflow AOI, and additional checks such as X-ray or ICT depending on the BOM. Pre-reflow AOI verifies that the correct components are present, oriented correctly, and placed within tolerance before heat is applied. Post-reflow AOI evaluates solder joint shape, fillet height, bridging, and tombstoning on visible joints.
Some lines use both stages; others rely on SPI plus post-reflow AOI for cost and cycle-time reasons. Elecrow PCBA workflows emphasize catching placement errors early because rework after reflow is slower, more expensive, and more likely to damage sensitive packages. Provide accurate centroid files, assembly drawings, and polarity marks so AOI programs can be generated without guesswork.
Relationship to SPI and downstream test
Solder paste inspection measures deposit volume, alignment, and bridging before components are placed. AOI does not replace SPI; the two systems cover different failure modes. SPI finds insufficient paste and misregistered deposits; AOI finds missing parts and bad joints after placement and reflow. Functional test and in-circuit test validate electrical behavior but may not localize a marginal joint on a fine-pitch connector.
Think of inspection as layered defense. SPI protects paste quality, AOI protects component and joint quality, X-ray protects hidden joints under BGAs and QFNs, and ICT or flying-probe test protects net connectivity. The SMT inspection methods overview compares these tools and when each is worth specifying on a build.
Defects AOI detects well
Modern AOI systems excel at consistent, repeatable checks on visible SMT joints and component bodies. When lighting, CAD alignment, and thresholds are tuned to a stable process, AOI catches defects that human inspectors miss during long shifts or on repetitive panel arrays.
- Missing components on visible placements.
- Wrong component value or package when body markings or shape models differ.
- 180-degree or 90-degree rotation errors on polarized parts.
- Insufficient or excessive solder on gull-wing and chip-component joints.
- Solder bridges between adjacent leads on QFPs, connectors, and fine-pitch passives.
- Tombstoning and billboarding on two-terminal chips.
- Lifted leads or coplanarity issues on larger ICs when fillet geometry changes.
AOI also supports trend analysis. Recurring bridge locations may indicate a stencil aperture issue, placement offset, or reflow profile problem rather than random defects. Feed AOI results back to design and process owners instead of treating failed boards as one-off events.
Where AOI has limitations
AOI inspects what the cameras can see. Joints under BGAs, CSPs, QFN bodies, and shield cans are not fully visible from the top. Head-in-pillow defects on BGA balls, voiding under thermal pads, and partial co-planarity failures often require X-ray review. Through-hole joints, press-fit connectors, and hand-soldered rework areas may fall outside standard AOI programs unless separately configured.
Highly reflective or dark component bodies, mirrored ENIG surfaces, and unusual package colors can challenge edge detection algorithms. Tombstoned 0201 passives may appear present but stand at an angle AOI interprets ambiguously. For these cases, combine AOI with targeted X-ray sampling and clear Elecrow PCBA first article inspection criteria on early builds.
False calls and program maturity
A new AOI program often produces false failures until golden boards and process limits are established. Shaded solder fillets on NSMD pads, acceptable resin bleed on small components, and intentional solder mask encroachment can trigger alarms if acceptance windows are too tight. Plan time on first article to tune thresholds rather than disabling checks entirely.
Document accepted cosmetic exceptions in the assembly drawing. If certain test points or debug pads intentionally receive minimal solder, AOI should exclude them or use relaxed rules. Uncontrolled exceptions force operators to override alarms, which erodes trust in the system over time.
Design boards for better AOI coverage
Design choices made months before assembly determine AOI effectiveness. Footprint pad geometry, silkscreen polarity marks, component orientation consistency, and fiducial placement all influence how reliably the machine aligns to each board.
Fiducials and panel consistency
Global fiducials should be clear of mask defects, copper pour edge effects, and silkscreen clutter. Use at least two global fiducials for basic alignment; add local fiducials near fine-pitch BGAs when placement and inspection accuracy require them. Panelized arrays need consistent fiducial availability on each unit or on the panel frame per the assembler’s standard.
Silkscreen, polarity, and centroid accuracy
Polarity marks must match the centroid and BOM orientation. A cathode stripe on silk that disagrees with the placement file causes AOI to flag correct placements as errors—or worse, trains operators to ignore real reversals. Keep reference designators readable but away from pad edges where they interfere with joint imaging.
Centroid files should use the same origin and rotation convention as the pick-and-place machine. Mixed metric units, bottom-side mirroring errors, and outdated revisions are frequent root causes of AOI misalignment that looks like widespread placement failure.
Set up AOI programs for Elecrow PCBA builds
AOI programming starts from CAD data: paste layer, copper, silkscreen, BOM, and XY placement file. The programmer assigns component libraries, joint inspection models, and tolerance windows for each footprint. Incomplete or nonstandard libraries slow first-article approval and increase false calls.
Provide the approved package list with manufacturer part numbers, not just generic footprint names. Two inductors sharing a 0805 land pattern may have different body heights and inspection profiles. Call out bottom-side assembly, lead-free versus leaded process, and any no-populated positions clearly so the program skips unplaced designators.
First article and golden board strategy
First article inspection validates that AOI thresholds match real process capability. Build a small quantity, review flagged defects with process and design engineers, and adjust programs before full production. Save approved golden images and limit files so future builds of the same revision start from a known baseline.
For engineering changes that alter pad size, mask definition, or component height, treat the next build as a partial re-qualification. Small footprint edits can shift fillet geometry enough to invalidate prior AOI limits. The Elecrow SMT reflow profile optimization guide helps when joint shape changes trace back to thermal process rather than placement.
Use AOI data for continuous improvement
Export AOI defect Pareto charts by location, component type, and failure mode. Clusters on one IC footprint suggest stencil or profile issues; scattered rotation errors suggest reel orientation or feeder setup problems. Share summaries with your design team when the same land pattern fails across multiple builds.
Link AOI outcomes to BOM readiness and documentation quality. Builds with late BOM changes, substitute parts, and incomplete assembly notes spend more time in AOI reprogramming and manual review. The Elecrow PCBA BOM readiness checklist reduces those delays by standardizing inputs before upload.
When to request enhanced inspection
Standard AOI covers most consumer and industrial prototypes with visible SMT joints. Specify additional inspection when the product risk justifies it: medical devices, automotive electronics, high-reliability industrial controllers, and designs with large BGA or QFN counts. X-ray sampling, increased first-article depth, or custom reporting may be appropriate even when base AOI is included.
Discuss inspection scope when submitting nonstandard materials, heavy boards with long thermal mass, or assemblies with both SMT and through-hole on the same side. Early conversation prevents assuming coverage that the default program does not provide.
Prepare your submission
Before ordering Elecrow PCBA assembly, confirm that inspection-related deliverables are complete and revision-controlled.
- Centroid file matches BOM revision and board side definitions.
- Assembly drawing specifies polarity, no-pop, and special handling.
- Fiducials meet assembler placement and AOI alignment requirements.
- Footprint pad and mask definitions are stable across the ordered PCB revision.
- First-article expectations and acceptance criteria are documented for new designs.
Upload files through the Elecrow shop and contact Elecrow support for questions about AOI scope, X-ray add-ons, or first-run qualification on complex assemblies. AOI is most valuable when treated as a partnership between design data, process setup, and measurable feedback—not as a black box at the end of the line. Explore more PCBA guidance on the Elecrow blog to keep inspection, design, and test aligned across every revision.