Wireless sensor PCBA: antenna keepouts and assembly constraints

A wireless sensor PCBA can report a plausible measurement and still fail to communicate reliably after installation. The manufacturing release therefore needs to describe two products together: the populated circuit board and the mechanical arrangement around its antenna. A correct BOM alone does not tell an assembler where a battery lead may run, which module variant is approved, or how to distinguish a radio fault from a sensor fault.

This guide focuses on the handoff from a module-based sensor design to assembly and enclosure integration. Use the broader IoT assembly requirements to define firmware, provisioning and interface responsibilities alongside the RF constraints.

Freeze the antenna configuration before quoting the build

Start with the complete radio module ordering code. A family name is insufficient when one variant has an integrated PCB antenna and another has an external connector. Put the approved antenna, cable and connector parts in the system BOM where applicable. Record whether alternate parts require engineering approval, and identify who owns any matching adjustments.

For an integrated antenna, release a drawing showing the module orientation, board edge and antenna clearance. For a connector-based solution, add the cable route, attachment point and assembly sequence. A purchasing substitution that fits the same footprint may still require a different mechanical arrangement or validation. Make that approval boundary visible in the quotation package.

Make keepouts specific to the selected module

Do not turn a familiar clearance number into a universal antenna rule. Espressif’s current ESP32 layout guidance recommends placing the module’s PCB antenna beyond the base-board edge. It also discusses board cutouts when that placement is impossible and recommends at least 15 mm of clearance around the antenna inside the housing. These instructions belong to that documented configuration; a different antenna or module must be checked against its own integration instructions. See the manufacturer’s ESP32 module placement guidance.

Translate the selected manufacturer’s drawing into an enforceable release note. Identify which layers and objects the exclusion applies to, its dimensional reference and the controlled drawing revision. Separate the antenna exclusion from the ground connection requirements under the rest of the module. A note saying only “keep clear” leaves too many decisions to interpretation.

Review the assembled model as well as the PCB layout. Include the battery, mounting screws, cable clips, labels and any conductive coating in that review. Ask the mechanical designer to approve a defined space around the antenna rather than relying on an unannotated STEP model. Record any deviation and its validation plan before fabrication.

Connect each constraint to a manufacturing record

Review soldering, cleaning and rework as separate decisions

The ESP32-C3-WROOM-02/02U datasheet, version 1.7, calls for a single reflow and provides module storage and reflow requirements. It also warns against ultrasonic vibration from equipment such as cleaners or welders. These are component-specific manufacturing constraints, not a generic recipe for every wireless sensor. Consult its Product Handling section for the complete conditions.

For a two-sided assembly, ask the process engineer to show how the selected module’s allowed exposure fits the proposed sequence. Do this before approving the panel and placement plan. Keep the approved thermal process with the build records, and resolve conflicts between module instructions, other components and the proposed soldering process.

Treat rework as a controlled exception. Define who can authorize module removal, what records are required and which checks must be repeated afterward. Likewise, specify whether the sensor’s exposed sensing surface needs protection during processing. The sensor manufacturer should supply any applicable cleaning restrictions; a radio module instruction does not establish compatibility for the rest of the BOM.

Approve a complete first unit, including the battery and lid

Consider a battery-powered temperature node with an antenna at one end of the board. The PCB drawing may be correct while the enclosure work instruction permits the battery cable to take several routes. The first-unit review should resolve one repeatable route, show it in a photograph or drawing and define how it is retained. This is a proposed review example, not a reported production result.

Agree the box build integration scope before ordering. State whether the supplier delivers tested boards, programmed subassemblies or closed products. Assign responsibility for battery installation, enclosure assembly and the final communication check. If those steps occur at different facilities, transfer the same revision-controlled instructions with the units.

Define tests that help locate the failure

Use separate acceptance entries for sensor measurement, radio operation and final product behavior. A failed upload should not automatically become an antenna diagnosis. The test record should establish whether the unit booted, loaded the intended configuration, acquired a sensor reading and exchanged the expected data.

For a repeatable communication screen, specify the peer device, software revision, channel or channel-selection procedure, power setting, distance, orientation and test environment. Define the transaction count and pass/fail criteria with the product engineer. Record retries and failures as well as successful connection. Avoid an invented universal RSSI threshold: a threshold must be justified for the selected setup and product requirements.

Keep engineering RF characterization separate from the shorter production screen. Agree what evidence the first approved assembly needs, what every unit must demonstrate and what changes trigger renewed evaluation. Retain a reference unit with its configuration, but do not use it as a substitute for calibrated equipment where the procedure requires measurement accuracy.

Use a controlled comparison when the enclosure changes performance

If a first unit communicates on an open bench but behaves differently after closure, preserve the original test conditions before troubleshooting. Identify the unit, firmware, supply arrangement and peer device, and record the sequence that produced the observation. An engineer can then compare configurations without mixing a mechanical change with a firmware update or a different access point. These comparisons are diagnostic proposals; they do not replace the product’s approved radio characterization.

Start with a repeatable baseline and change one assembly feature at a time. A useful investigation might compare the approved battery route with the suspect route, then compare the lid installed and removed while retaining the same wiring. Record the exact configuration for every run, including orientation. If changing the lid also moves the battery cable, the experiment cannot identify which change matters. Photograph the cable position before closing the unit so that the configuration can be reproduced by someone other than the original operator.

Do not promote the best result from that experiment directly into a production instruction. The design owner should review the evidence, choose the intended configuration and establish whether additional evaluation is required. Once approved, update the mechanical drawing, work instruction and inspection criterion together. A note in a troubleshooting spreadsheet is easy to miss when production follows a separate assembly drawing.

Keep provisioning records useful without exposing credentials

Define the information that connects a tested board to its finished product. A practical record may include the assembly serial number, module identifier, firmware release, configuration profile, programming station and test result. Distinguish identifiers that operators may view from secrets that must remain inside the approved provisioning process. The assembly traveler should confirm completion without copying private keys or shared network passwords into an ordinary spreadsheet.

Document the response to an interrupted programming operation. Specify how the station determines whether the unit is unprogrammed, partially programmed or ready for test, and who may authorize a retry. Where identifiers must be unique, include a check for duplicate assignments and a disposition for rejected hardware. Scrapping a physical board should not leave its identity available for accidental reuse unless the product’s own controlled process explicitly permits that.

Keep the acceptance test independent of an operator’s personal phone or account. The release package should identify the approved test peer and how its configuration is controlled. If a factory test configuration differs from the delivered configuration, document the transition and verify the final state. Otherwise, a successful factory connection can conceal a unit that was shipped with the wrong destination, pairing state or reporting interval.

Plan the handoff between board test and final assembly

Define a small set of checkpoints rather than treating every failure as a reason to repeat the entire build. For example, board test can establish that the intended firmware starts and the sensor interface responds; enclosure test can establish that the completed mechanical configuration supports the required transaction. Record both results against the same unit identifier. A missing final-assembly result must remain visible even when the earlier board result passed.

When a unit is reopened, state which earlier approvals are invalidated. Moving an antenna cable, replacing a battery holder or removing the radio module can affect different parts of the acceptance record. The work instruction should direct the operator to the relevant reinspection and retest, with the reason recorded. This makes repair history meaningful and prevents a repaired unit from inheriting a result measured before the repair.

For repeat orders, review changes to the enclosure, cable supplier, battery arrangement and programming package as well as the bare PCB revision. Request a written change summary from each responsible party. A repeat purchase order is not evidence that all those inputs stayed constant. Close the review with a named approver and the complete revision set that the assembler is authorized to use.

Release the build when responsibilities are clear

Before purchase approval, close these five items:

1. Confirm module, antenna and mechanical revisions against the BOM.
2. Approve the dimensional antenna exclusion and cable route.
3. Resolve soldering sequence, handling and rework restrictions.
4. Release firmware, identifiers and repeatable acceptance procedures.
5. Name the owner of first-unit approval and any later substitutions.

Use the production timeline planner only after identifying dependencies such as enclosure samples, approved antennas and test-fixture readiness. Its estimates are planning inputs, not a commitment. To request a project review, provide the board files, system BOM, antenna drawing and intended acceptance scope together, and identify any unresolved engineering decisions explicitly.