4.4 Programming & Tuning
Inspection programming involves translating raw component and solder data into actionable pass or fail criteria. The primary operational goal of tuning an inspection system is balancing a minimized false alarm rate against the goal of zero escapes (false negatives). This requires a structured approach that relies on Golden Boards, organized library management, and continuous iterations driven by the Pareto analysis of actual false calls. Remember, inspection programs are not a substitute for process control; they function as a sensitive process monitor that flags upstream drift in your printing or placement operations.
The Inspection System Programming Loop
Section titled “The Inspection System Programming Loop”Programming and tuning transform static design data into a robust, repeatable inspection judgment that stays consistent across different shifts and operators.
- Data Import: CAD or Gerber data (centroid location, rotation, polarity, generic component shape) is imported and mapped to the machine’s internal package library.
- Teaching and Calibration: The machine is taught by scanning the Golden Board. This establishes the optimal lighting profiles for AOI and the specific slice planes for AXI Laminography.
- Tuning: Thresholds and inspection criteria are iteratively adjusted to balance detection capability against the operational cost of manual verification.
Pro-Tip: The success of an inspection program is measured not only by the defects it catches, but equally by the low number of false calls it generates. An effective program catches anomalies without causing excessive line stoppages.
Library and Data Standardization
Section titled “Library and Data Standardization”A standardized central library is helpful for smooth NPI changeovers and steady throughput across multiple products.
- One Package, One Library: A single, central library item should be created for each unique component package (e.g., standard 0402, 0.5 mm QFN). This central item defines the Presence Window, Polarity Region, and Solder Pad ROI (Region of Interest) for inspection across all products.
- Reusability: Reusing library items globally across all product programs ensures consistency and minimizes programming time for new products.
- AXI Specifics: For AXI, the library item should define structural parameters such as ball pitch, component height, and slice plane locations, along with clear voiding rules (e.g., voiding per individual ball vs. total combined area).
- Golden Set: Build the baseline program using data derived exclusively from the Golden Board (the known-good assembly built during First Article). When possible, supplement this with Near-Limit Boards (assemblies with barely acceptable features) to help train the system on acceptable boundaries.
Risk Classification and Limit Setting
Section titled “Risk Classification and Limit Setting”Not all defects carry the same risk. Outline your inspection limits according to the actual risk level to prevent cosmetic issues from unnecessarily blocking production flow.
| Risk Class | Defect Type | Limit Strategy | Action upon Failure |
|---|---|---|---|
| Class A (Critical) | Missing Component, Polarity Reversal, BGA Bridge. | Defined Limits. Typically triggers a stop or rejection to the rework station. | Should be addressed and cleared before the next panel begins. |
| Class B (Major Quality) | Tombstoning, Insufficient Fillet, Minor component skew. | Moderate Limits. Requires human verification and potential rework; data is logged for SPC tracking (Chapter 4.5). | Serves as a leading indicator to monitor upstream process drift. |
| Class C (Informational) | Smudges, Silk Screen Nicks, minor Flux Residue. | Tracking Only. Generally does not block WIP. Used to gather data for periodic housekeeping checks. | Data is captured in the background but may not trigger a line alarm. |
Tuning and the False Call Reduction Loop
Section titled “Tuning and the False Call Reduction Loop”Tuning is the continuous engineering process of adjusting parameters to reduce false calls while maintaining strong defect detection. This process should be driven by data.
- Pareto Analysis: Run a sample lot (50–200 boards) and generate a Pareto chart of all false calls, classified precisely by component reference designator (RefDes) and the specific failure reason (e.g., “U10 fillet too reflective”).
- Iterative Fixes: Address the top 3 false-call sources with the smallest applicable programmatic change—for instance, adjusting a single lighting angle or subtly widening one component’s acceptable X/Y window. Try to avoid global threshold relaxation unless necessary.
- Verification: Re-run a small mini-lot (10 boards) to confirm that the false call rate drops, while verifying that the detection of true defects remains intact.
- Process vs. Program: If tuning cannot resolve a consistent false call, such as recurring insufficient solder calls on a specific component, the issue is likely process drift (e.g., low SPI volume, poor paste release). Shift focus from camera tuning to the physical stencil or printer recipe.
Change Control and Program Maintenance
Section titled “Change Control and Program Maintenance”Because inspection programs guide what ships to the customer, they benefit from the same change control rigor as PnP placement programs.
- Version Control: Ensure the AOI/AXI program revision updates with any change to the libraries, limits, or algorithm settings. Tie the program version to the product’s Golden Recipe.
- Documentation: Include a brief explanation for every program change in a changelog (e.g., “v2.1: Reduced false bridge calls on C47-C49 by softening the side-lighting angle”).
- Machine Learning (ML): If the inspection system uses ML/AI for defect classification, utilize a diverse training set. Reserve a holdout set of images for regular, independent verification of the model’s accuracy to ensure it continues to identify defects correctly.
Final Checklist: Inspection Program Health
Section titled “Final Checklist: Inspection Program Health”| Action | Control Point | Responsibility |
|---|---|---|
| Library Management | Component library items are centrally reused, standardized, and version-controlled. | AOI/AXI Programmer |
| False Call Control | Monitor the false call rate regularly to ensure it falls below the target threshold. | Quality Engineer (QE) |
| Process Feedback | Utilize the false call Pareto to flag process drift instead of treating it only as a tuning opportunity. | Process Engineer (PE) |
| Recipe Integrity | Safely store the program revision, lighting/slice settings, and limits sheet within the product’s Golden Recipe bundle. | Manufacturing Engineering |