PCB E-Test: Electrical Testing Before Assembly

Send the PCB manufacturing package and an independently exported design netlist from the same approved revision. Comparing a CAM-derived connectivity model with the source design helps identify data discrepancies before test programming. Resolve intentional net ties, isolated pads, panel features and any embedded components explicitly.

Testing only against a model reconstructed from the same incorrect manufacturing data can reproduce the mistake. Identify who approves the reference and how discrepancies are handled. KiCad and other CAD systems can export IPC-D-356 data, but file availability alone does not prove that the correct revision and connectivity were supplied.

The test plan must define which conductive paths and net relationships are evaluated, with applicable resistance criteria, measurement conditions and exceptions. Do not copy a generic voltage or resistance threshold from a web article into a production order without reviewing the product requirements and test method.

Agree the relevant contractual standard and revision, along with customer requirements. The public IPC-9252B scope describes testing of unpopulated boards and its limitations; it is not a substitute for the current agreed document or a universal recipe. Boards with embedded components or unusual construction need additional engineering review.

Flying probes avoid a dedicated contact fixture for many designs, while fixture-based routes can reduce repeated contact movement for suitable repeat work. The commercial decision depends on accessibility, board stability, quantity, program effort and the required measurement sequence. Neither route has a universal crossover quantity.

Use the station-time tool with reviewed cycle and handling data to plan one sequential test station. Additional executions are entered assumptions, not a predicted failure rate. Ask the quotation to separate initial data preparation or tooling, recurring test work, exceptional diagnosis and the reporting deliverable.

A useful result identifies the board or panel, product revision, approved test program, scope and disposition. Define how a failed contact is distinguished from an actual board defect, how retests are authorized and how the original result is retained. Do not erase the history by reporting only the final passing attempt.

Confirm whether the ordered scope covers each shipped board and which tests occur after final processing. Request the report format, exception handling and release authority in writing. PCBSync can review your files and proposed criteria so the quotation describes the quality evidence your receiving team actually needs.