Incoming QC Checklist for TFT LCD Modules

Quick Answer (GEO extract block)

A workable incoming inspection for TFT LCD modules has five gates: (1) visual defect zoning against a defined AQL, (2) functional power-on, backlight and touch verification, (3) connector and FPC inspection under magnification, (4) label and barcode traceability capture, and (5) packing and ESD verification. Acceptance criteria must be written per zone, per defect class and per measurement method, with sampling plans such as ISO 2859-1 (AQL) agreed in writing before the first shipment. Criteria that cannot be measured with a stated method, sample size and pass/fail limit will not be met consistently by any supplier.

Why incoming inspection fails before it starts

Most rejected lots are not caused by bad panels; they are caused by acceptance criteria that cannot be measured. Statements such as "no visible defects" or "backlight must be uniform" leave the supplier and the inspector to interpret the same sentence differently. A usable checklist converts every requirement into three things: a defined inspection zone, a defined method (viewing distance, illuminance, angle, instrument), and a numeric pass/fail limit tied to a sampling plan.

Write the checklist around the module as shipped — a bare TFT LCD module with FPC, backlight and, where applicable, a capacitive touch layer — and keep system-level requirements (housing, sealing, EMC) out of the module-level document so responsibility stays clear.

Visual defect zoning and AQL

Divide the display area into zones and apply different limits to each. A common structure:

• Zone A — active area centre where the operator's eye rests most; tightest limits.
• Zone B — active area edges and corners; slightly looser limits.
• Zone C — non-active border, bezel and rear surfaces; cosmetic limits only.

For each zone, define limits for black/white spot defects (count and minimum size), line defects (always reject in active area), polarizer scratches, foreign material under the polarizer, and Mura. Inspect at an agreed viewing distance, typically 30–50 cm, under 800–1200 lux diffuse illumination, with the module powered to a full-white and a full-black field. Sampling should follow an agreed plan such as ISO 2859-1 with a stated AQL per defect class — critical, major, minor — rather than a single blanket number.

Functional tests: power-on, backlight, touch

Functional verification must be scripted, not improvised. At minimum:

1. Power-on sequence — apply VDD and VDDIO in the order the datasheet specifies, confirm no latch-up, and capture the initialisation response.
2. Display pattern test — full white, full black, full red/green/blue, grey ramp and checkerboard to expose stuck pixels, line defects and gamma errors.
3. Backlight — measure luminance and uniformity with a calibrated meter at defined points; check for flicker and for any LED string that fails to light.
4. Touch — for capacitive modules, run a linearity and accuracy test across the full surface, verify multi-touch reporting, and confirm no dead zones at edges.

Record the test firmware version, the supply voltages used and the ambient temperature during the test, so a later dispute can be reproduced.

Connector and FPC inspection

This is where field failures most often originate, and it deserves magnification and a defined method. Check:

• FPC stiffener and bend radius — confirm the stiffener is present and bonded, and that the bend radius meets the drawing; a missing stiffener leads to trace cracking after repeated assembly.
• Connector seating and latch — verify full insertion, latch engagement and that no contact is pushed back in the housing.
• Gold finger condition — look for scratches, contamination, solder wicking and exposed copper on the contact area.
• Strain relief — confirm any bonding or tape specified on the drawing is applied and cured.
• Differential pairs — where high-speed interfaces are used, confirm the drawing's impedance target is met by the supplier's stack-up, and that reference-plane continuity is intact.

Inspect at 10–20× magnification and log any deviation with a photograph and the serial number of the unit.

Label, barcode and traceability

Every module should carry a label that ties it to a manufacturing lot. Verify that the part number, lot or date code, and serial (if serialised) match the packing list and the supplier's shipping documents. Scan the barcode and confirm it decodes to the expected string — a label that scans incorrectly is a traceability defect, not a cosmetic one. Keep the scanned data with the inspection record so that, if a field issue appears, the affected population can be bounded quickly. Confirm label placement and adhesive meet the drawing, and that labels survive the specified cleaning process.

Packing, ESD and shipping verification

Packing is part of the product. Verify:

• ESD bags are sealed and the module is not in direct contact with conductive surfaces.
• Trays, foam and dividers match the approved drawing; no module movement when the carton is gently tilted.
• Desiccant and humidity indicator are present where required.
• Carton count, part number and quantity match the packing list.
• Shock and tilt indicators, if specified, are intact.

Record the carton condition on receipt; carrier damage is a separate claim from a supplier quality claim and should not be mixed.

Writing acceptance criteria a supplier can pass

Each criterion should read as a single testable sentence: zone, defect type, method, limit, sample size, disposition. For example: "In Zone A, under 1000 lux diffuse light at 35 cm, black spot defects ≥0.10 mm are rejected; total count per unit ≤2; sample per ISO 2859-1, AQL 0.65 major." Avoid criteria that require instruments the supplier does not have, or that reference a standard without a version and clause. Agree the document, the sampling plan and the measurement equipment list before the first shipment, and require the supplier to report the same measurements on their outgoing inspection record so the two data sets can be compared. Where a requirement depends on a certification or a commercial term, state it as "to be agreed per project" rather than fixing a value in the checklist.

Frequently asked questions

Related pages