RFID, IoT & LoRa PCB Manufacturing

Separate HF RFID, UHF RFID and LoRa requirements

HF RFID and NFC commonly use 13.56 MHz interfaces; UHF RFID belongs to a different frequency family and uses different antenna and chip arrangements. NXP distinguishes these technology families in its RFID and NFC portfolio. Do not transfer a coil layout or matching assumption from one family to the other.

For RFID, also identify reader versus tag and active versus passive architecture. A passive tag needs an appropriate chip-powering and response analysis. The one-way receiver link calculator on this page is not a passive-tag read-range model and does not calculate the backscatter return path.

Distinguish LoRa modulation from LoRaWAN networking

Semtech identifies LoRa as the physical radio modulation and LoRaWAN as a networking protocol in its LoRa and LoRaWAN guide. A board with a LoRa-capable transceiver does not by itself define network behavior. Record the intended protocol, firmware configuration and counterpart device or gateway.

Treat labels such as 868 MHz and 915 MHz as incomplete product specifications. Identify the target market and have the responsible team establish permitted frequencies, power, channel behavior and conformity requirements. This page provides no worldwide license-free claim. Semiconductor tuning range and a regional reference design are not operating authorization.

Start from a reference that matches the selected radio

Choose the correct radio part, band and RF output configuration before using a reference layout. Semtech publishes separate SX1262 reference designs and application documents on its device resource page. Preserve the identity of the selected reference with the schematic and explain deliberate departures from it.

Highlight changed component packages, RF routing, ground geometry and antenna connection on a comparison drawing. Review each difference before fabrication. Retaining component values while rearranging them does not establish RF equivalence. Record tuning changes in the final BOM.

Reserve antenna geometry before the mechanical design closes

An antenna uses space that other product teams may also want: an edge, a ground region or separation from a battery and mounting hardware. Include that space in the mechanical drawing early. Define which copper layers, components and enclosure parts may occupy each region, using the chosen antenna supplier’s requirements.

TI’s antenna impedance and matching report illustrates detuning from a plastic case and nearby loading. Its examples support measuring the intended assembly rather than copying their numerical matching values. Keep the enclosure revision and measurement setup with the antenna results so a later mechanical change can be evaluated against the same baseline.

Choose the laminate for the actual feed and board size

A compact sensor node is not automatically improved by using an RF laminate throughout its entire stackup. Identify the relevant trace lengths, impedance requirements, dimensional sensitivity and fabrication constraints first. Discuss a standard or RF construction using the material selection guide, with the actual operating band and layout available.

The impedance calculator can help organize a preliminary feed geometry. Confirm that geometry against the proposed construction before release. An antenna clearance is not the same as a transmission-line reference: document where ground is required and where the chosen antenna design calls for a keepout.

Read the link-budget outputs without hiding assumptions

The calculator uses received power = transmit power + transmit antenna gain + receive antenna gain − total path loss − miscellaneous losses. Net margin = received power − receiver sensitivity − reserved fade margin. Power is entered in dBm, gains in dBi and losses or margins in dB.

Enter conducted transmit power, not an EIRP value that already includes antenna gain. Keep propagation loss separate from cable, connector and implementation losses, and avoid counting any loss twice. Use receiver sensitivity for the selected operating mode. The calculation subtracts your supplied values; it does not derive path loss from distance or predict the installation environment.

Test a conservative scenario as well as the nominal one

A positive margin says that the entered received power exceeds the entered threshold after your reserve. It does not show how frequently the path will experience a worse condition. Create scenarios for the antenna orientation, mounting position and obstruction conditions relevant to the product, using justified inputs instead of choosing values to reach a desired result.

An additional 3 dB of miscellaneous loss reduces calculated net margin by 3 dB. This helps compare a cable or matching change, but cannot establish packet delivery under interference or changing conditions. Preserve the assumptions beside any reported margin.

Separate antenna matching, filtering and production checks

Matching and unwanted-emission control answer different questions. Review the complete RF path, including any switch or filter, with the filter and duplexer PCB guide. A well-matched antenna does not by itself demonstrate an acceptable transmitted spectrum or receiver behavior.

For production planning, identify an accessible test point and specify the board state, firmware settings and fixture connection. Decide which measurements belong to assembly screening and which require a more complete product test. Include reference-plane information when cables or connectors are part of the result. Do not label a continuity-tested bare board as a verified radio.

Release the RF variant and its evidence together

A repeat order should identify the antenna geometry, board revision, matching BOM and intended regional variant. A late change to the enclosure, battery holder or feed connector should trigger review of the affected evidence. The RF PCB DFM checklist helps collect the manufacturing portion of that package.

Compare prototype and production scope using the RF PCB cost calculator. Include tuning samples and test fixture work. Send controlled files and open questions through the quote form for review.

Prepare a reviewable engineering request

Check only the requirements you have actually documented. This list records readiness; it does not inspect your files or certify a design. Missing information is useful: identify it explicitly so the engineering review can resolve it before a production release.

Select the information you have prepared.

Project notes and open questions

These inputs are processed in your browser and are not submitted by this tool. The downloaded summary is a plain-text planning record. Use the secure quote form to send files; request an NDA first if your project requires one.

Manufacturing context

RFPCB and PCBSync share the manufacturing facility shown below. These process photographs illustrate the production environment; they are not evidence that a particular board, material grade or RF performance has been qualified. Request the documentation and inspection scope applicable to your project.

RFID, IoT and LoRa PCB FAQs