吃瓜tv

A Wi-Fi module keepout review should end with checkable PCB constraints, not a note saying 鈥渓eave space around the antenna.鈥� Identify the exact antenna variant, translate its drawing into electrical and mechanical rules, inspect the exported fabrication data, and reserve a final-enclosure RF test. This workflow helps the layout engineer and manufacturer review the same geometry.

Start with the exact module, not a generic clearance number

Two modules with similar names can expose different antenna interfaces. One may carry a printed antenna; another may use a connector or RF pad for an external antenna. Their host-board requirements are not interchangeable. Record the complete ordering code, antenna option, hardware revision, document revision and recommended host-board construction before copying a footprint into the project.

Espressif鈥檚 ESP32 hardware guidance describes edge placement and a conditional clearance recommendation for its PCB-antenna arrangement. Silicon Labs AN1342 gives a different geometry for the RS9116 CC1. These are examples of device-specific instructions, not competing universal rules. Do not average their dimensions or apply the most convenient number to another module. Read the relevant drawing and its notes together.

Make a short constraint register with four columns: source drawing, requirement, CAD implementation, and verification evidence. Assign an owner to any ambiguity. If the drawing distinguishes a copper keepout from a physical cutout, preserve that distinction. A copper-free laminate region still contains dielectric material; removing copper does not create an opening in the board.

Translate the drawing into separate CAD objects

A component courtyard helps assembly clearances; it is not automatically an RF exclusion rule. A mechanical outline shows the module body but may not prevent a ground pour under the antenna. A graphic on a documentation layer can communicate intent while enforcing nothing. Use the CAD system鈥檚 appropriate copper, routing, via and component restriction objects, and verify that each rule applies to the intended layers.

Separate the permitted ground region beneath the module electronics from the antenna exclusion region. Removing ground indiscriminately from the entire module can damage the intended return path. Conversely, adding stitching vias 鈥渇or RF quality鈥� inside an excluded area can violate the antenna layout. Follow the module drawing at the boundary instead of applying generic ground-plane advice everywhere.

Record whether top and bottom components are restricted and whether mechanical metal is covered by the same outline. Include mounting hardware, test pads, shields and any conductive marking or coating. Where the drawing specifies an edge overhang, add a board-edge constraint so that a later mechanical resize cannot move laminate back under the antenna unnoticed.

Use coordinates to catch a plausible-looking footprint error

Consider a deliberately hypothetical drawing: an antenna exclusion extends from x = 0 to 12 mm and y = 0 to 6 mm in module-local coordinates. The module origin is placed at board coordinates (30, 20) mm with no rotation. The translated exclusion therefore spans x = 30 to 42 mm and y = 20 to 26 mm. This example teaches coordinate checking; those dimensions are not a recommendation for any real module.

Now rotate the module 90 degrees counterclockwise around that same origin. A local point (x, y) becomes the board point (30 鈭� y, 20 + x). Transform all four corners: the exclusion now spans x = 24 to 30 mm and y = 20 to 32 mm. A manually drawn box that did not rotate with the module would still look reasonable but protect the wrong area.

Check the library鈥檚 origin, rotation convention and bottom-side mirroring before accepting that arithmetic. CAD packages and manufacturing exports can represent orientation differently. Use an asymmetric feature, such as pin 1 and the antenna end, to establish the physical orientation. The goal is agreement between the drawing, placement data and board, rather than forcing one convention onto every software tool.

Inspect the exported board, including the 鈥渋nvisible鈥� layers

After the final copper refill, inspect the fabrication output in an independent viewer. Turn on one copper layer at a time, then inspect drill data and the board outline. Check for plane islands, thermal spokes, test points, via barrels and copper text that the visual footprint review could miss. Repeat after panelization if rails, tooling features or adjacent boards approach the antenna region.

Ask whether the delivered product is depanelized before RF operation. A temporary manufacturing rail and a permanent enclosure bracket are different conditions, but both need to be understood. If a test fixture operates the module while the rail remains attached, its RF results may not represent the shipped geometry. Record the tested configuration rather than labeling both conditions as 鈥渢he same board.鈥�

Save the actual export revision, not just a screenshot of the editable layout. A later copper refill or footprint update can invalidate a prior review. A useful release check pairs the module ordering code with the fabrication archive revision and the enclosure revision. Keep any exception explicit and supported by the module vendor or by a documented engineering validation plan.

Review the enclosure as part of the antenna system

The antenna does not experience the PCB in isolation. Inspect the lid, metalized finish, battery, display frame, connector shells, screws, cable shields and possible cable movement. Evaluate both sides of the board and the fully assembled product. A generous top-view gap can conceal a battery or bracket directly above the antenna.

Microchip鈥檚 RNWF02 documentation distinguishes host-board copper and antenna placement requirements and stresses product-level RF verification. For your design, turn those requirements into an assembly review: identify what can move, what is fixed, and what changes across product variants. Do not assume a plastic enclosure is electromagnetically irrelevant simply because it is nonconductive.

If the industrial designer cannot accommodate the selected antenna arrangement, raise that conflict before releasing the PCB. Options may include changing module placement, modifying the enclosure or evaluating a documented external-antenna variant. Each option changes the integration problem; none should be treated as a guaranteed correction without reviewing the chosen hardware and applicable approval conditions.

Protect power integrity and signal routing without confusing them with keepout

Antenna clearance is only one item in the module integration review. Check the supply path against the selected module鈥檚 peak current requirements, the recommended decoupling arrangement and the actual power-source behavior. Keep noisy switching nodes and high-speed interfaces away from sensitive RF regions where practical. These checks complement the keepout review; they do not replace it.

If an RF transmission line exists on the host board, its geometry depends on the actual stackup and reference plane. Do not copy a trace width from a development board with a different dielectric spacing. For a module with an integrated antenna and no host RF feed, an unrelated 鈥�50-ohm trace鈥� calculation does not validate the antenna. Identify which interconnect actually requires impedance control before adding a fabrication note.

For broader product integration, the IoT PCB planning page covers the host-board context. Use the RF material and design center when an actual RF feed, stackup or material decision needs analysis. The Wi-Fi module assembly overview addresses the wider manufacturing route; this review remains focused on turning antenna requirements into releasable constraints.

Define a final-product test that can distinguish causes

Test the assembled product with its intended enclosure, cable arrangement, firmware and power source. Agree on the application requirement first: a fixed sensor link and a high-throughput access point do not share the same acceptance target. Record channel, band, orientation, distance, access-point configuration, traffic direction and background interference so that the result can be repeated.

Compare open-board and enclosed operation as a diagnostic experiment, while keeping the other conditions fixed. A change can identify an enclosure sensitivity, but a single RSSI value cannot prove antenna efficiency or regulatory compliance. Include the operating cases that generate electrical noise, such as display updates, battery charging or processor activity, if those occur during normal wireless use.

Keep the module vendor鈥檚 evaluation board as a controlled reference where appropriate. It is a useful comparison, not a promise that a different host board will match it. If formal radiated performance or compliance measurements are required, specify the laboratory method and acceptance limits separately from a basic connectivity check.

What to include in the manufacturing review request

Send the exact module part number, the cited antenna drawing, fabrication files, layer stack, assembly drawing and the relevant enclosure views. Mark the protected region and state whether it is a copper exclusion, physical cutout, component restriction or combination. Include the board revision, quantity and any unresolved mechanical exception.

Ask for confirmation of the manufacturing interpretation, especially where panel rails, tooling, milling or component placement approach the protected region. RF performance remains a product-level engineering responsibility unless a specific test scope has been agreed. A clear review request separates a producible board from a validated wireless product and prevents an apparently simple layout note from becoming an assumption between teams.

Request a review of your module integration files and identify the exact question that needs resolution. Do not send only a generic request to 鈥渃heck Wi-Fi鈥�; attach the constraint register so that each answer can be tied to a drawing and revision.

Technical references: ; ; . Consult the revision applicable to your ordered module.