Verify How Your Assembly Operates
Topline Circuit powers assembled boards and checks their response to specified inputs and loads. We follow the approved procedure to verify startup, communication and other functions defined for your build.
Send your assembly revision, build quantity and required functions with your PCB assembly quote. We review the test setup, fixtures and acceptance criteria with you.
Functional Checks and Acceptance Criteria
| Check | What to define | What to verify |
|---|---|---|
| Power-up and startup | Supply voltage, current limit, startup sequence and firmware revision. | Expected boot indication, maximum startup time and acceptable current draw during startup or steady operation, as applicable. |
| Interface communication | Connector pinout, interface settings, test commands and response timeout. | Expected reply, data or status within the specified time. |
| Inputs and outputs | Input levels, timing and operating mode. | Output level, state or timing within the agreed limits. |
| Operation under load | Load type and value, supply conditions, test duration and when to take measurements. | Specified output and current while the load is applied. |
Prepare the Fixture, Script and Firmware
For a customer-supplied setup, provide the fixture drawing or wiring diagram, adapters, script version, required software and firmware. Identify the board revision and variant supported by the setup.
If a fixture or script still needs to be prepared, share your interface requirements and agree on who will supply each item. An approved reference unit can help check the setup before the first production run.
Approve the Procedure Before Production
For each step, specify the input, expected response, acceptance limits and any time allowed for the response. Include the startup, reset and shutdown sequence where it affects the result.
Identify which checks apply to every unit or to a sample. Agree on who approves the first production run and how to review changes to the assembly, firmware or test script.
Record Results and Retests by Serial Number
Specify whether results are tracked by serial number or lot. Agree on which records to deliver, such as board and firmware revisions, test step, measured value, units, acceptance limit and pass/fail result.
If a unit fails, record the original result and apply the agreed hold, rework and retest rules. Link any retest to the original unit record.
Files for a Functional Test Quote
- Assembly revision, BOM, schematic and connector pinout
- Required functions, test sequence, inputs, loads and pass/fail limits
- Firmware and script revisions, programming instructions and fixture or cable details
- Build quantity, per-unit or sampling requirements, and report format
PCBA Functional Testing FAQs
Yes. Send the schematic, connector pinout and the functions you need verified. Include known supply settings and expected outputs. We identify the missing steps, limits and setup details for your approval before production.
Send the wiring diagram, required software, script and firmware revisions, and the assembly revision the setup supports. We review compatibility and agree on a trial run with the reference board before using the setup for production.
FCT verifies responses such as startup under load or a reply to an interface command. ICT checks selected accessible connections and component values. Send the operating functions you need verified so they can be included in the test procedure.
Your team approves the limits before production testing. Send the allowable range or expected state for each check, with units, load and timing where applicable. If a limit is still open, flag that step so we can review it with you.
We record the failed step, operating conditions and measured result against the board identifier. The agreed procedure defines when we can repeat the check and when the unit must be held for review. We keep the original result and log any authorized retest under the same board identifier.
Specify serial-number reporting when you request a quote. Provide the serial number format and required report fields, such as firmware and test procedure revisions, step results, measured values with units, acceptance limits and initial and retest outcomes.
Discuss Your Functional Test Requirements
Send the functions to verify, operating conditions, acceptance limits and reporting requirements. Include your current firmware, fixture or test script details so we can review the setup for your quote.
