Optional website analytics

Allow optional website analytics, including Google Tag Manager and video play events? You can send an enquiry with either choice and change your preference in the footer. Privacy notice

Technical resources

LINKARIS / TECHNICAL RESOURCES

RF PA integration and sample evaluation checklist

For OEM engineers and purchasing teams preparing a reviewable RF PA requirement: align the configuration, signal path, installation and acceptance evidence before committing to an evaluation sample.

Updated 17 November 2026 · purchasing guidance 2026-11-17.1

Identify the assembly and the output requirement

Record the candidate configuration and website data revision, then ask for the formal manufacturer part number, hardware revision and applicable datasheet. A website reference is not a hardware revision. Specify the complete operating interval and distinguish maximum output, CW output, P1dB, modulated average and the required full-band minimum. If filenames, tables or documents disagree, request a corrected matched revision instead of combining their best values.

Confirm the signal path before comparing gain

State whether your system needs amplification of an external RF input or a configuration with an internal signal source. Ask for the applicable input connector, drive range, absolute limits and signal-path explanation. Sweep controls or a maximum gain entry alone do not establish transparent linear amplification. For a modulated signal, agree which waveform, bandwidth and linearity evidence are needed; missing data remains an open engineering question.

Review mechanical, supply and thermal conditions together

Use a drawing matched to the supplied assembly: identify overall dimensions, cavity dimensions, mounting holes, tolerances and connector clearance separately. Confirm nominal voltage versus the permitted range, current under the relevant output condition, pinout and enable timing. State the cooling arrangement and temperature measurement point. An alarm, power reduction and shutdown are different actions; agree the actual trigger, behavior and reset instead of resolving conflicting text by assumption.

Send an evaluation brief that sales and engineering can use

Include selected references, quantity, original requirements, requested documents, open conditions and the next review step. Ask for version-matched test evidence identifying the sample, date, frequency coverage, signal, input drive, supply, cooling, load and duration. Use the editable list below to prepare the handoff. Adding a list is not a submitted enquiry, quotation or suitability approval. Sample schedule, repeat-supply conditions and engineering acceptance are confirmed for the project.

Prepare ten areas before the quotation review

Start with the details you know; mark unknown items OPEN and identify who will confirm them. The quick enquiry remains available without completing every technical field.

  • Complete frequency interval and any band-edge requirements.
  • Required output definition, waveform and relevant signal-quality criteria.
  • Required performance across the band, not just a peak value.
  • External RF input or integrated source, and available input drive.
  • Available DC supply and relevant current conditions.
  • RF, power and control interfaces to be confirmed.
  • Available space, mounting and connector clearance.
  • Duty cycle, cooling arrangement and operating duration.
  • Required monitoring, fault response and recovery behaviour.
  • Sample and repeat quantities, target timing, review owner and next decision.

Define acceptance before the sample arrives

Agree a written plan with the engineering team before treating a sample as accepted. A displayed meter reading or illustrative scene is not a matched test report.

  • Identify the sample, formal part number and hardware revision.
  • Record signal, frequency points, drive, supply, load, cooling and duration.
  • Name the measurement reference plane and the evidence to retain.
  • Agree the criteria and tolerances; leave unsupported numerical limits OPEN.
  • Confirm who reviews the result and the next action. Protection checks require an agreed safe procedure.

When a sample and production unit differ

Treat a discrepancy as a review task. Compare the agreed revision, assembly definition, operating conditions and acceptance criteria before drawing a conclusion. Ask the responsible team for relevant change records and version-matched test evidence.

  • Which hardware, component or configuration changes were agreed between the sample and production unit?
  • Were the same reference plane, calibration, input, load, supply, cooling and duty cycle used?
  • Who will review the discrepancy, and which additional records are needed for the next decision?
Watch: why test results differ

Build your integration review list

Choose the documents and conditions your team needs. Add them to an editable enquiry or save the list for an internal review. This does not submit an enquiry or confirm product suitability.

Add your operating conditions, measurement reference plane, acceptance criteria and open questions. Unknown items may remain OPEN. These are your requirements, not confirmed product capabilities.

Preparing optional notes…

A buyer-prepared request list, not a specification, quotation or engineering acceptance. Product capabilities remain subject to the selected configuration and confirmed revision.

Download centreSend project requirements