[{"data":1,"prerenderedAt":397},["ShallowReactive",2],{"blog-lock-emc-fcc-compliance-en":3,"header-nav-en":69},{"title":4,"description":5,"date":6,"category":7,"image":8,"readingTime":9,"wordCount":10,"timeRequired":11,"htmlContent":12,"tags":13,"slug":19,"jsonld":20},"Smart Lock PCB Before EMC: Where the Board Gets Exposed","A release-focused read on smart lock boards: actuation noise, return continuity, antenna placement, enclosure interaction, and ESD entry paths decide whether pre-compliance starts cleanly.","2026-04-20","technology","/blog-cover/lock-emc-fcc-compliance.svg?title=Smart+Lock+PCB+Before+EMC%3A+Where+the+Board+Gets+Exposed&category=technology",13,2533,"PT13M","\u003Cul>\n\u003Cli>A smart lock PCB gets exposed at the boundaries first: actuation power, low-voltage logic, touch inputs, cable entries, and the antenna region all compete inside a tight enclosure.\u003C/li>\n\u003Cli>The first EMC problem is usually coupling, not the radio by itself.\u003C/li>\n\u003Cli>Pre-compliance should be treated as release discipline, not as a promise about the first lab run.\u003C/li>\n\u003Cli>A pre-approved module may simplify certification scope, but it does not remove antenna, enclosure, labeling, or host-integration review.\u003C/li>\n\u003Cli>The common failure is an ownership gap between board, wiring, motor path, and enclosure metal.\u003C/li>\n\u003C/ul>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Quick Answer\u003C/strong>\u003Cbr>Review a smart lock PCB before EMC by mapping where noise, ESD, and antenna sensitivity enter the enclosure. If the actuation path, return continuity, metal around the antenna, and ownership of host integration are still vague, pre-compliance usually fails for predictable reasons.\u003C/p>\n\u003C/blockquote>\n\u003Cp>For the broader release-readiness workflow that ties manufacturability, test planning, board-level pre-compliance review, and evidence layering together, see the \u003Ca href=\"/en/blog/pcb-design-for-manufacturing-dfm-guide\">PCB Design for Manufacturing Guide\u003C/a>.\u003C/p>\n\u003Ch3 id=\"public-parameter-anchors\" data-anchor-en=\"public-parameter-anchors\">Public parameter anchors\u003C/h3>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Source / method\u003C/th>\n\u003Cth>Example parameters\u003C/th>\n\u003Cth>Scenario\u003C/th>\n\u003Cth>Boundary\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>FCC Part 15 board-review context\u003C/td>\n\u003Ctd>\u003Ccode>Part 15\u003C/code>, \u003Ccode>Subpart B\u003C/code>, modular-transmitter route under \u003Ccode>15.212\u003C/code>\u003C/td>\n\u003Ctd>US wireless host-product preparation\u003C/td>\n\u003Ctd>standards and process identity, not pass proof\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>FCC / pre-compliance staging\u003C/td>\n\u003Ctd>\u003Ccode>conducted\u003C/code> review, \u003Ccode>radiated\u003C/code> review, host-product authorization path\u003C/td>\n\u003Ctd>pre-compliance planning before formal lab work\u003C/td>\n\u003Ctd>stage vocabulary only; not a limit table for every product\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>TI return-path guidance\u003C/td>\n\u003Ctd>continuous reference, avoid splits, keep return current close to the signal path\u003C/td>\n\u003Ctd>mixed-signal and noisy-actuator layout review\u003C/td>\n\u003Ctd>routing method guidance, not FCC proof\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Silicon Labs antenna note\u003C/td>\n\u003Ctd>\u003Ccode>2.4 GHz\u003C/code> PCB antenna integration and nearby-metal sensitivity\u003C/td>\n\u003Ctd>module or PCB antenna region review in compact smart-lock enclosures\u003C/td>\n\u003Ctd>module-specific antenna guidance must still be followed\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>APT testing / validation pages\u003C/td>\n\u003Ctd>staged board debug, inspection, and handoff evidence\u003C/td>\n\u003Ctd>release package before lab scheduling\u003C/td>\n\u003Ctd>manufacturing evidence is separate from authorization outcome\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>If the article publishes a parameter, keep it attached to the test stage, the regulatory route, and the integration boundary that produced it.\u003C/p>\n\u003Cdiv data-component=\"BlogQuickQuoteInline\">\u003C/div>\n\n\u003Ch2 id=\"table-of-contents\" data-anchor-en=\"table-of-contents\">Table of Contents\u003C/h2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"#first-review\">What should engineers review first?\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"#preparation-not-claim\">Why is this an EMC and FCC preparation problem rather than a certification claim?\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"#first-failure-risk\">Which board-level issues usually create the first failure risk?\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"#validation-staged\">How should pre-compliance and release validation be staged?\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"#freeze-before-release\">What should be frozen before release?\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"#next-steps\">Next steps with APTPCB\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"#faq\">FAQ\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"#references\">Public references\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"#author\">Author and review information\u003C/a>\u003C/li>\n\u003C/ul>\n\u003Ca id=\"first-review\">\u003C/a>\n\u003Ch2 id=\"what-should-engineers-review-first\" data-anchor-en=\"what-should-engineers-review-first\">What should engineers review first?\u003C/h2>\n\u003Cp>Start with \u003Cstrong>actuation path, control region, antenna region, external entry points, and enclosure interaction\u003C/strong>.\u003C/p>\n\u003Cp>That order matters because smart-lock articles are often written as if \u003Ccode>EMC\u003C/code>, \u003Ccode>FCC\u003C/code>, \u003Ccode>wireless range\u003C/code>, and \u003Ccode>access control compliance\u003C/code> were all one subject. They are not. At board level, the most useful review is narrower: where does switching noise originate, where does it return, where can ESD enter, and what parts of the enclosure or hardware stack can destabilize the radio path?\u003C/p>\n\u003Cp>The first review questions should be:\u003C/p>\n\u003Col>\n\u003Cli>Does the board clearly separate the actuator or relay path from the logic and RF regions?\u003C/li>\n\u003Cli>Is the return path continuous under the routes that matter, or are plane breaks and local detours quietly creating larger loop areas?\u003C/li>\n\u003Cli>Which user-touch, cable, battery, charging, or reader interfaces can inject ESD or conducted noise into the board?\u003C/li>\n\u003Cli>Is the antenna region still being treated as protected RF real estate, or has it become leftover layout space near metal hardware?\u003C/li>\n\u003Cli>Does the release package explain what belongs to board debug, pre-compliance review, and later formal lab work?\u003C/li>\n\u003C/ol>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Review axis\u003C/th>\n\u003Cth>What to ask\u003C/th>\n\u003Cth>Why it matters\u003C/th>\n\u003Cth>What usually goes wrong\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Actuation path\u003C/td>\n\u003Ctd>Where do motor, relay, strike, or driver currents flow?\u003C/td>\n\u003Ctd>The noisiest path usually shapes the board's EMC posture first\u003C/td>\n\u003Ctd>A lock or latch path is routed too close to logic or RF areas\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Return path\u003C/td>\n\u003Ctd>Does the signal still have a clean reference path through transitions?\u003C/td>\n\u003Ctd>Plane discontinuities enlarge loop area and make noise harder to predict\u003C/td>\n\u003Ctd>The signal route looks tidy, but the return path is broken underneath\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>External entry points\u003C/td>\n\u003Ctd>Which lines are exposed to touch, cable insertion, or off-board wiring?\u003C/td>\n\u003Ctd>ESD and fast transients often arrive from the edge, not the center of the board\u003C/td>\n\u003Ctd>Protection is added late, after connectors and openings are fixed\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Antenna and enclosure\u003C/td>\n\u003Ctd>Is nearby metal, battery, or bracket placement changing the RF region?\u003C/td>\n\u003Ctd>Antenna behavior depends on its physical environment, not just its schematic symbol\u003C/td>\n\u003Ctd>The antenna is placed correctly in 2D but trapped by metal in assembly\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Validation ownership\u003C/td>\n\u003Ctd>What does the board review actually prove before lab testing?\u003C/td>\n\u003Ctd>Pre-compliance discipline is different from final authorization outcome\u003C/td>\n\u003Ctd>Teams use one generic \u003Ccode>tested\u003C/code> label for every stage\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cdiv style=\"background:#ffffff;border:1px solid #e2e8f0;border-radius:24px;padding:34px 28px;margin:28px 0 22px;box-shadow:0 18px 42px rgba(15,23,42,0.06);\">\n  \u003Cdiv style=\"text-align:center;margin-bottom:28px;\">\n    \u003Ch3 style=\"margin:0 0 10px 0;color:#0f172a;font-size:1.55em;font-weight:800;\" id=\"four-zones-that-usually-decide-a-smart-lock-emc-review\" data-anchor-en=\"why-is-this-an-emc-and-fcc-preparation-problem-rather-than-a-certification-claim\">Four Zones That Usually Decide a Smart-Lock EMC Review\u003C/h3>\n    \u003Cp style=\"margin:0;color:#475569;font-size:1.02em;line-height:1.7;\">The board becomes easier to release when noise source, return path, external-entry protection, and antenna region are reviewed as separate ownership zones.\u003C/p>\n  \u003C/div>\n  \u003Cdiv style=\"display:grid;grid-template-columns:repeat(auto-fit,minmax(220px,1fr));gap:16px;\">\n    \u003Cdiv style=\"background:#f8fafc;border:1px solid #dbe4ee;border-radius:18px;padding:24px 20px;border-top:5px solid #0f766e;\">\n      \u003Cdiv style=\"font-size:2.1em;font-weight:900;color:#cbd5e1;margin-bottom:10px;line-height:1;\">01\u003C/div>\n      \u003Cstrong style=\"color:#0f766e;font-size:1.15em;display:block;margin-bottom:10px;\">Noise Source Zone\u003C/strong>\n      \u003Cp style=\"color:#475569;font-size:0.95em;line-height:1.7;margin:0;\">Motor, strike, relay, or switching-driver energy should be contained before it reaches control and RF areas.\u003C/p>\n    \u003C/div>\n    \u003Cdiv style=\"background:#f8fafc;border:1px solid #dbe4ee;border-radius:18px;padding:24px 20px;border-top:5px solid #1d4ed8;\">\n      \u003Cdiv style=\"font-size:2.1em;font-weight:900;color:#cbd5e1;margin-bottom:10px;line-height:1;\">02\u003C/div>\n      \u003Cstrong style=\"color:#1d4ed8;font-size:1.15em;display:block;margin-bottom:10px;\">Return-Path Zone\u003C/strong>\n      \u003Cp style=\"color:#475569;font-size:0.95em;line-height:1.7;margin:0;\">A visually short route can still be noisy if its reference path is split or forced into a detour.\u003C/p>\n    \u003C/div>\n    \u003Cdiv style=\"background:#f8fafc;border:1px solid #dbe4ee;border-radius:18px;padding:24px 20px;border-top:5px solid #7c3aed;\">\n      \u003Cdiv style=\"font-size:2.1em;font-weight:900;color:#d8ccf7;margin-bottom:10px;line-height:1;\">03\u003C/div>\n      \u003Cstrong style=\"color:#7c3aed;font-size:1.15em;display:block;margin-bottom:10px;\">Entry-Protection Zone\u003C/strong>\n      \u003Cp style=\"color:#475569;font-size:0.95em;line-height:1.7;margin:0;\">Touch surfaces, charging ports, battery contacts, and reader cables should be reviewed as entry paths, not just connectors.\u003C/p>\n    \u003C/div>\n    \u003Cdiv style=\"background:#fffaf0;border:1px solid #f3dfb7;border-radius:18px;padding:24px 20px;border-top:5px solid #b45309;\">\n      \u003Cdiv style=\"font-size:2.1em;font-weight:900;color:#e5d7b8;margin-bottom:10px;line-height:1;\">04\u003C/div>\n      \u003Cstrong style=\"color:#b45309;font-size:1.15em;display:block;margin-bottom:10px;\">Antenna Region\u003C/strong>\n      \u003Cp style=\"color:#475569;font-size:0.95em;line-height:1.7;margin:0;\">The RF area should follow module or antenna guidance and stay protected from nearby metal and enclosure drift.\u003C/p>\n    \u003C/div>\n  \u003C/div>\n\u003C/div>\n\n\u003Ca id=\"preparation-not-claim\">\u003C/a>\n\u003Ch2 id=\"why-is-this-an-emc-and-fcc-preparation-problem-rather-than-a-certification-claim\" data-anchor-en=\"which-board-level-issues-usually-create-the-first-failure-risk\">Why is this an EMC and FCC preparation problem rather than a certification claim?\u003C/h2>\n\u003Cp>Conclusion: \u003Cstrong>Because the board team can prepare the design and the release package, but it cannot honestly collapse that work into a blanket authorization outcome.\u003C/strong>\u003C/p>\n\u003Cp>This boundary is where many low-quality compliance blogs fail. They present FCC language as if it were simply a layout checklist, then promise pass results that depend on the full host device, enclosure, wiring, antenna implementation, and lab configuration.\u003C/p>\n\u003Cp>The safer engineering posture is:\u003C/p>\n\u003Cul>\n\u003Cli>treat \u003Ccode>FCC\u003C/code> as the regulatory path the finished product may enter\u003C/li>\n\u003Cli>treat \u003Ccode>EMC review\u003C/code> as the board-level discipline that reduces avoidable failure modes\u003C/li>\n\u003Cli>treat \u003Ccode>smart lock\u003C/code> or \u003Ccode>access-control board\u003C/code> as the application context\u003C/li>\n\u003Cli>keep \u003Ccode>UL 294\u003C/code> and related standards as system-context vocabulary rather than turning them into PCB-level proof\u003C/li>\n\u003C/ul>\n\u003Cp>If the design uses a modular radio, the path may be narrower than a fully discrete transmitter design. But the module does not make the host product invisible. The integration still needs to respect the approved antenna path, final physical configuration, and labeling or instruction requirements attached to the module route. That is why smart-lock EMC writing should focus on host-board review and integration clarity rather than certification slogans.\u003C/p>\n\u003Ca id=\"first-failure-risk\">\u003C/a>\n\u003Ch2 id=\"which-board-level-issues-usually-create-the-first-failure-risk\" data-anchor-en=\"how-should-pre-compliance-and-release-validation-be-staged\">Which board-level issues usually create the first failure risk?\u003C/h2>\n\u003Cp>Conclusion: \u003Cstrong>The first failure risk usually sits at the intersection of actuation noise, return-path breaks, edge-entry protection, and antenna or enclosure drift.\u003C/strong>\u003C/p>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Risk area\u003C/th>\n\u003Cth>What should be reviewed\u003C/th>\n\u003Cth>Why it matters\u003C/th>\n\u003Cth>Typical release failure\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Actuator or relay region\u003C/td>\n\u003Ctd>Driver placement, current loop containment, and separation from control logic\u003C/td>\n\u003Ctd>The noise source can dominate emissions and reset behavior\u003C/td>\n\u003Ctd>A compact lock board places the switching path beside the wireless or MCU region\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Return-path continuity\u003C/td>\n\u003Ctd>Reference-plane continuity and layer-transition discipline\u003C/td>\n\u003Ctd>Higher-frequency current follows the lowest-impedance return path\u003C/td>\n\u003Ctd>A neat signal route crosses a split or disrupted reference area\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Edge-entry interfaces\u003C/td>\n\u003Ctd>Keypad, reader cable, battery, charging, and service connector entry paths\u003C/td>\n\u003Ctd>These locations often inject ESD or conducted transients first\u003C/td>\n\u003Ctd>Protection is added late, after the mechanical openings are frozen\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Antenna region\u003C/td>\n\u003Ctd>Antenna keep-out discipline and nearby metal or battery interaction\u003C/td>\n\u003Ctd>RF behavior changes when the physical environment changes\u003C/td>\n\u003Ctd>The board layout is reviewed in isolation from the assembled lock body\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Release evidence\u003C/td>\n\u003Ctd>Revision identity, pre-compliance scope, and unresolved integration notes\u003C/td>\n\u003Ctd>Teams need to know what is already proven and what remains open\u003C/td>\n\u003Ctd>A board is sent to test with no clean handoff between layout review and system setup\u003C/td>\n\u003C/tr>\n\u003C/tbody>\u003C/table>\n\u003Cp>A typical engineering hold looks harmless at first. The board package is complete, the radio module is already chosen, and the enclosure model seems nearly finished. But the release still leaves one unresolved question: does the antenna sit beside a plastic window, a battery cavity, or a metal bracket after final assembly? That single ambiguity can overturn the layout assumptions that looked acceptable on the bench.\u003C/p>\n\u003Cp>Another common failure chain starts in the actuation path. The layout review focuses on the microcontroller and wireless section because they are easy to discuss, while the motor or strike path is treated as ordinary power routing. Later, the board shows unstable behavior during lock or unlock events, and the root cause turns out to be local return-current disturbance and coupling near the control region rather than a mysterious firmware problem.\u003C/p>\n\u003Cp>The same pattern appears with touch interfaces and cable entry points. ESD exposure is not only a component-selection topic. It is also a path-design topic. If the board edge, connector choice, grounding path, and enclosure opening are decided separately, the protection strategy often arrives too late to be structurally clean.\u003C/p>\n\u003Ca id=\"validation-staged\">\u003C/a>\n\u003Ch2 id=\"how-should-pre-compliance-and-release-validation-be-staged\" data-anchor-en=\"what-should-be-frozen-before-release\">How should pre-compliance and release validation be staged?\u003C/h2>\n\u003Cp>Conclusion: \u003Cstrong>Validation should move in layers: board review first, pre-compliance debug second, then formal product-level testing.\u003C/strong>\u003C/p>\n\u003Cp>The board team should keep those layers separate:\u003C/p>\n\u003Col>\n\u003Cli>\u003Cstrong>Release review\u003C/strong> for partitioning, return-path continuity, entry-point protection posture, antenna-region discipline, and unresolved enclosure interactions.\u003C/li>\n\u003Cli>\u003Cstrong>Build and bench debug\u003C/strong> for confirming that the assembled board behaves as expected under switching, charging, communication, and actuation conditions.\u003C/li>\n\u003Cli>\u003Cstrong>Pre-compliance checks\u003C/strong> for identifying obvious board and integration issues before a formal lab cycle.\u003C/li>\n\u003Cli>\u003Cstrong>Formal product testing and authorization path\u003C/strong> for the complete host device, where enclosure, wiring, module integration, and final configuration are evaluated together.\u003C/li>\n\u003C/ol>\n\u003Cp>That separation also makes the handoff package more useful. Instead of a vague \u003Ccode>ready for FCC\u003C/code> statement, the release should carry revision identity, interface notes, unresolved enclosure dependencies, antenna assumptions, and the validation scope already completed. A compact smart-lock board often fails not because no one worked hard enough, but because the board and system teams were looking at different assumptions about the finished product.\u003C/p>\n\u003Ca id=\"freeze-before-release\">\u003C/a>\n\u003Ch2 id=\"what-should-be-frozen-before-release\" data-anchor-en=\"next-steps-with-aptpcb\">What should be frozen before release?\u003C/h2>\n\u003Cp>Conclusion: \u003Cstrong>Freeze the decisions that can destabilize the noise path, the RF region, or the product handoff before the board enters a serious test cycle.\u003C/strong>\u003C/p>\n\u003Cp>Before release, freeze:\u003C/p>\n\u003Col>\n\u003Cli>the boundary between noisy actuation hardware and the logic or RF region\u003C/li>\n\u003Cli>the intended reference-plane and layer-transition posture for the routes that matter\u003C/li>\n\u003Cli>the external-entry map for keypad, battery, charging, reader, and service interfaces\u003C/li>\n\u003Cli>the antenna placement assumption, including the nearby enclosure and metal context\u003C/li>\n\u003Cli>the validation ladder, including what the board review proves and what still belongs to later lab work\u003C/li>\n\u003C/ol>\n\u003Cp>If those items are still drifting, the design may still be a valid prototype, but it is not yet a clean EMC or FCC-preparation release package.\u003C/p>\n\u003Ca id=\"next-steps\">\u003C/a>\n\u003Ch2 id=\"next-steps-with-aptpcb\" data-anchor-en=\"faq\">Next steps with APTPCB\u003C/h2>\n\u003Cp>If your smart-lock project is being slowed by actuator-noise coupling, return-path uncertainty, antenna placement inside a crowded enclosure, or unclear pre-compliance ownership, send the Gerbers, stackup intent, enclosure notes, RF-module details, and validation questions to \u003Ca href=\"mailto:sales@aptpcb.com\">sales@aptpcb.com\u003C/a> or upload them through the \u003Ca href=\"/en/quote\">quote page\u003C/a>. APTPCB's engineering team can return DFM feedback within 24 hours and help identify whether the real risk sits in the switching path, board-edge entry protection, antenna region, or host-device integration assumptions.\u003C/p>\n\u003Cp>If you are still shaping the release package, use \u003Ca href=\"/en/pcb/antenna-pcb\">antenna PCB\u003C/a> for antenna-region context, \u003Ca href=\"/en/industries/security-equipment-pcb\">security equipment PCB\u003C/a> for application framing, and \u003Ca href=\"/en/pcba/testing-quality\">PCB testing and quality\u003C/a> when the board needs a clearer validation handoff before lab scheduling.\u003C/p>\n\u003Cdiv data-component=\"BlogQuickQuoteInline\">\u003C/div>\n\n\u003Ca id=\"faq\">\u003C/a>\n\u003Ch2 id=\"faq\" data-anchor-en=\"does-using-a-wireless-module-mean-the-smart-lock-pcb-no-longer-needs-fcc-related-review\">FAQ\u003C/h2>\n\u003C!-- faq:start -->\n\n\u003Ch3 id=\"does-using-a-wireless-module-mean-the-smart-lock-pcb-no-longer-needs-fcc-related-review\" data-anchor-en=\"is-this-article-proving-a-smart-lock-pcb-is-fcc-compliant\">Does using a wireless module mean the smart-lock PCB no longer needs FCC-related review?\u003C/h3>\n\u003Cp>No. A module can narrow the radio portion of the path, but the host board still needs careful review for antenna use, physical integration, and the assumptions carried into final product testing.\u003C/p>\n\u003Ch3 id=\"is-this-article-proving-a-smart-lock-pcb-is-fcc-compliant\" data-anchor-en=\"should-emc-review-focus-only-on-the-wireless-section\">Is this article proving a smart-lock PCB is FCC compliant?\u003C/h3>\n\u003Cp>No. This article is about preparing the board and release package before EMC and FCC testing. Formal authorization depends on the finished product path and the applicable test program.\u003C/p>\n\u003Ch3 id=\"should-emc-review-focus-only-on-the-wireless-section\" data-anchor-en=\"are-keypad-battery-and-charging-interfaces-really-emc-issues\">Should EMC review focus only on the wireless section?\u003C/h3>\n\u003Cp>No. On a smart-lock board, the first issue often comes from the actuator or switching path, its return path, and how that energy couples into the logic or RF region.\u003C/p>\n\u003Ch3 id=\"are-keypad-battery-and-charging-interfaces-really-emc-issues\" data-anchor-en=\"what-is-the-most-common-release-mistake-on-this-topic\">Are keypad, battery, and charging interfaces really EMC issues?\u003C/h3>\n\u003Cp>Yes. They are common external-entry paths for ESD and conducted disturbance, so they need to be reviewed as part of the board boundary rather than as late accessory details.\u003C/p>\n\u003Ch3 id=\"what-is-the-most-common-release-mistake-on-this-topic\" data-anchor-en=\"public-references\">What is the most common release mistake on this topic?\u003C/h3>\n\u003Cp>The board layout and the final assembled product are reviewed as if they were the same thing. The missing link is usually enclosure, antenna, or edge-interface ownership rather than one dramatic schematic error.\u003C/p>\n\u003C!-- faq:end -->\n\n\u003Ca id=\"references\">\u003C/a>\n\u003Ch2 id=\"public-references\" data-anchor-en=\"author-and-review-information\">Public references\u003C/h2>\n\u003Col>\n\u003Cli>\u003Cp>\u003Ca href=\"https://www.fcc.gov/engineering-technology/laboratory-division/general/equipment-authorization\">FCC equipment authorization page\u003C/a>\u003Cbr>Supports cautious wording that the finished wireless product enters an FCC authorization path, without turning that regulator entry page into pass-status proof.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Ca href=\"https://ecfr.io/Title-47/Section-15.212\">47 CFR § 15.212 Modular transmitters\u003C/a>\u003Cbr>Supports the article's guarded language that a modular radio route still carries host-device responsibilities around integration, labeling context, and final configuration.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Ca href=\"https://www.ti.com/lit/an/scaa082a/scaa082a.pdf\">TI high-speed layout guidelines\u003C/a>\u003Cbr>Supports the article's return-path language about continuous reference structures, avoiding plane discontinuities, and maintaining continuity through routing transitions.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Ca href=\"https://www.silabs.com/documents/public/application-notes/an1088-designing-with-pcb-antenna.pdf\">Silicon Labs AN1088 designing with a PCB antenna\u003C/a>\u003Cbr>Supports the article's careful antenna-region language that nearby copper, metal, and physical placement decisions can affect the RF section and should follow module or antenna guidance.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Ca href=\"/en/pcb/antenna-pcb\">APTPCB antenna PCB page\u003C/a>\u003Cbr>Supports the article's board-manufacturing context for antenna-region planning, RF layout attention, and related fabrication support.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Ca href=\"/en/industries/security-equipment-pcb\">APTPCB security equipment PCB page\u003C/a>\u003Cbr>Supports the application framing that smart-lock and access-control boards sit inside a wider civilian security-equipment hardware family.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Ca href=\"/en/pcba/testing-quality\">APTPCB testing and quality page\u003C/a>\u003Cbr>Supports staged validation and release-handoff wording for board debug, inspection, and test preparation.\u003C/p>\n\u003C/li>\n\u003C/ol>\n\u003Ca id=\"author\">\u003C/a>\n\u003Ch2 id=\"author-and-review-information\">Author and review information\u003C/h2>\n\u003Cul>\n\u003Cli>Author: APTPCB security-hardware and board-process content team\u003C/li>\n\u003Cli>Technical review: mixed-signal layout, RF-integration, and validation-planning engineering team\u003C/li>\n\u003Cli>Last updated: 2026-04-20\u003C/li>\n\u003C/ul>\n\n\u003Csection class=\"related-links\" aria-label=\"Related\">\u003Ch3>Related links\u003C/h3>\u003Cul>\u003Cli>\u003Ca href=\"/en/blog/pcb-design-for-manufacturing-dfm-guide\">PCB Design for Manufacturing Guide\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/quote\">quote page\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/pcb/antenna-pcb\">antenna PCB\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/industries/security-equipment-pcb\">security equipment PCB\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"/en/pcba/testing-quality\">PCB testing and quality\u003C/a>\u003C/li>\u003C/ul>\u003C/section>",[14,15,16,17,18],"smart lock PCB","EMC PCB review","FCC Part 15","access control board","antenna PCB","lock-emc-fcc-compliance",{"blog":21,"breadcrumb":30,"faq":44},{"@context":22,"@type":23,"headline":4,"description":5,"image":8,"url":24,"datePublished":6,"dateModified":6,"timeRequired":11,"keywords":25,"articleSection":7,"author":26,"publisher":29},"https://schema.org","BlogPosting","https://aptpcb.com/en/blog/lock-emc-fcc-compliance","smart lock PCB, EMC PCB review, FCC Part 15, access control board, antenna PCB",{"@type":27,"name":28},"Organization","APTPCB",{"@type":27,"name":28},{"@context":22,"@type":31,"itemListElement":32},"BreadcrumbList",[33,38,42],{"@type":34,"position":35,"name":36,"item":37},"ListItem",1,"Home","https://aptpcb.com/",{"@type":34,"position":39,"name":40,"item":41},2,"Blog","https://aptpcb.com/en/blog",{"@type":34,"position":43,"name":19,"item":24},3,{"@context":22,"@type":45,"mainEntity":46},"FAQPage",[47,53,57,61,65],{"@type":48,"name":49,"acceptedAnswer":50},"Question","Does using a wireless module mean the smart-lock PCB no longer needs FCC-related review?",{"@type":51,"text":52},"Answer","No. A module can narrow the radio portion of the path, but the host board still needs careful review for antenna use, physical integration, and the assumptions carried into final product testing.",{"@type":48,"name":54,"acceptedAnswer":55},"Is this article proving a smart-lock PCB is FCC compliant?",{"@type":51,"text":56},"No. This article is about preparing the board and release package before EMC and FCC testing. Formal authorization depends on the finished product path and the applicable test program.",{"@type":48,"name":58,"acceptedAnswer":59},"Should EMC review focus only on the wireless section?",{"@type":51,"text":60},"No. On a smart-lock board, the first issue often comes from the actuator or switching path, its return path, and how that energy couples into the logic or RF region.",{"@type":48,"name":62,"acceptedAnswer":63},"Are keypad, battery, and charging interfaces really EMC issues?",{"@type":51,"text":64},"Yes. They are common external-entry paths for ESD and conducted disturbance, so they need to be reviewed as part of the board boundary rather than as late accessory details.",{"@type":48,"name":66,"acceptedAnswer":67},"What is the most common release mistake on this topic?",{"@type":51,"text":68},"The board layout and the final assembled product are reviewed as if they were the same thing. The missing link is usually enclosure, antenna, or edge-interface ownership rather than one dramatic schematic error.",{"pcbManufacturingColumns":70,"capabilityColumns":195,"resourceColumns":226,"pcbaColumns":266},[71,119,148,177],{"heading":72,"links":73},"PCB Product Families",[74,77,80,83,86,89,92,95,98,101,104,107,110,113,116],{"label":75,"path":76},"FR-4 PCB","/pcb/fr4-pcb",{"label":78,"path":79},"High-Speed PCB","/pcb/high-speed-pcb",{"label":81,"path":82},"Multilayer PCB","/pcb/multilayer-pcb",{"label":84,"path":85},"HDI PCB","/pcb/hdi-pcb",{"label":87,"path":88},"Flexible PCB","/pcb/flex-pcb",{"label":90,"path":91},"Rigid Flex PCB","/pcb/rigid-flex-pcb",{"label":93,"path":94},"Ceramic PCB","/pcb/ceramic-pcb",{"label":96,"path":97},"Heavy Copper PCB","/pcb/heavy-copper-pcb",{"label":99,"path":100},"High Thermal PCB","/pcb/high-thermal-pcb",{"label":102,"path":103},"Antenna PCB","/pcb/antenna-pcb",{"label":105,"path":106},"High Frequency PCB","/pcb/high-frequency-pcb",{"label":108,"path":109},"Microwave PCB","/pcb/microwave-pcb",{"label":111,"path":112},"Metal Core PCB","/pcb/metal-core-pcb",{"label":114,"path":115},"High-Tg PCB","/pcb/high-tg-pcb",{"label":117,"path":118},"Backplane PCB","/pcb/backplane-pcb",{"sections":120},[121],{"heading":122,"links":123},"RF & Materials",[124,127,130,133,136,139,142,145],{"label":125,"path":126},"Rogers PCB","/materials/rf-rogers",{"label":128,"path":129},"Taconic PCB","/materials/taconic-pcb",{"label":131,"path":132},"Teflon PCB","/materials/teflon-pcb",{"label":134,"path":135},"Arlon PCB","/materials/arlon-pcb",{"label":137,"path":138},"Megtron PCB","/materials/megtron-pcb",{"label":140,"path":141},"ISOLA PCB","/materials/isola-pcb",{"label":143,"path":144},"Spread Glass FR-4","/materials/spread-glass-fr4",{"label":146,"path":147},"Impedance Control","/pcb/pcb-impedance-control",{"sections":149},[150],{"heading":151,"links":152},"Manufacturing / Stackups",[153,156,159,162,165,168,171,174],{"label":154,"path":155},"Quickturn Prototypes","/pcb/quick-turn-pcb",{"label":157,"path":158},"NPI & Small Batch (PCB)","/pcb/npi-small-batch-pcb-manufacturing",{"label":160,"path":161},"High-Volume Production","/pcb/mass-production-pcb-manufacturing",{"label":163,"path":164},"High Layer Count PCB","/pcb/high-layer-count-pcb",{"label":166,"path":167},"PCB Fabrication Process","/pcb/pcb-fabrication-process",{"label":169,"path":170},"Advanced PCB Manufacturing","/pcb/advanced-pcb-manufacturing",{"label":172,"path":173},"Special PCB Manufacturing","/pcb/special-pcb-manufacturing",{"label":175,"path":176},"Multi-Layer Laminated Structure","/pcb/multi-layer-laminated-structure",{"heading":178,"links":179},"Specialties & Resources",[180,183,186,189,192],{"label":181,"path":182},"PCB Surface Finishes (ENIG / ENEPIG / HASL / OSP / Immersion)","/pcb/pcb-surface-finishes",{"label":184,"path":185},"Drilling & Vias (Blind / Buried / Via-in-Pad / Backdrill / Half Hole)","/pcb/pcb-drilling",{"label":187,"path":188},"PCB Stackup (Standard / High-Layer / Flex / Rigid-Flex / Aluminum)","/pcb/pcb-stack-up",{"label":190,"path":191},"Profiles (Milling / V-Scoring / Depaneling)","/pcb/pcb-profiling",{"label":193,"path":194},"Quality & Inspection (AOI + X-Ray / Flying Probe / PCB DFM Check)","/pcb/pcb-quality",[196,201,206,211,216,221],{"links":197},[198],{"label":199,"path":200},"Rigid PCB Capability","/capabilities/rigid-pcb",{"links":202},[203],{"label":204,"path":205},"Rigid-Flex Capability","/capabilities/rigid-flex-pcb",{"links":207},[208],{"label":209,"path":210},"Flex PCB Capability","/capabilities/flex-pcb",{"links":212},[213],{"label":214,"path":215},"HDI PCB Capability","/capabilities/hdi-pcb",{"links":217},[218],{"label":219,"path":220},"Metal PCB Capability","/capabilities/metal-pcb",{"links":222},[223],{"label":224,"path":225},"Ceramic PCB Capability","/capabilities/ceramic-pcb",[227,237,258],{"heading":228,"links":229},"Downloads",[230,233,236],{"label":231,"path":232},"Materials Datasheet / Processing Notes","/resources/downloads-materials",{"label":234,"path":235},"PCB DFM Guidelines","/resources/dfm-guidelines",{"label":175,"path":176},{"heading":238,"links":239},"Tools",[240,243,246,249,252,255],{"label":241,"path":242},"Gerber Viewer","/tools/gerber-viewer",{"label":244,"path":245},"PCB Viewer","/tools/pcb-viewer",{"label":247,"path":248},"BOM Viewer","/tools/bom-viewer",{"label":250,"path":251},"3D Viewer","/tools/3d-viewer",{"label":253,"path":254},"Circuit Simulator","/tools/circuit-simulator",{"label":256,"path":257},"Impedance Calculator","/tools/impedance-calculator",{"heading":259,"links":260},"FAQ & Blog",[261,264],{"label":262,"path":263},"FAQ","/resources/faq",{"label":40,"path":265},"/blog",[267,297,327,360],{"heading":268,"links":269},"Core Services",[270,273,276,279,282,285,288,291,294],{"label":271,"path":272},"Turnkey PCB Assembly","/pcba/turnkey-assembly",{"label":274,"path":275},"NPI & Small Batch PCB Assembly","/pcba/npi-assembly",{"label":277,"path":278},"Mass Production PCB Assembly","/pcba/mass-production",{"label":280,"path":281},"Flex & Rigid-Flex PCB Assembly","/pcba/flex-rigid-flex",{"label":283,"path":284},"SMT & Through-Hole Assembly","/pcba/smt-tht",{"label":286,"path":287},"BGA PCB Assembly","/pcba/bga-qfn-fine-pitch",{"label":289,"path":290},"Components & BOM Management","/pcba/components-bom",{"label":292,"path":293},"Box Build Assembly","/pcba/box-build-assembly",{"label":295,"path":296},"PCB Assembly Testing & Quality","/pcba/testing-quality",{"heading":298,"links":299},"Supporting Services",[300,303,306,309,312,315,318,321,324],{"label":301,"path":302},"Every Support Touchpoint","/pcba/support-services",{"label":304,"path":305},"Stencil Lab","/pcba/pcb-stencil",{"label":307,"path":308},"Components Sourcing","/pcba/component-sourcing",{"label":310,"path":311},"IC Programming","/pcba/ic-programming",{"label":313,"path":314},"Conformal Coating","/pcba/pcb-conformal-coating",{"label":316,"path":317},"Selective Soldering","/pcba/pcb-selective-soldering",{"label":319,"path":320},"BGA Reballing","/pcba/bga-reballing",{"label":322,"path":323},"Cable Assembly","/pcba/cable-assembly",{"label":325,"path":326},"Wire Harness","/pcba/harness-assembly",{"heading":328,"links":329},"Quality & Testing",[330,333,336,339,342,345,348,351,354,357],{"label":331,"path":332},"Quality Inspection","/pcba/quality-system",{"label":334,"path":335},"First Article Inspection (FAI)","/pcba/first-article-inspection",{"label":337,"path":338},"Solder Paste Inspection (SPI)","/pcba/spi-inspection",{"label":340,"path":341},"AOI Optical Inspection","/pcba/aoi-inspection",{"label":343,"path":344},"X-Ray / CT Inspection","/pcba/xray-inspection",{"label":346,"path":347},"ICT In-Circuit Testing","/pcba/ict-test",{"label":349,"path":350},"Flying Probe Testing","/pcba/flying-probe-testing",{"label":352,"path":353},"FCT / Functional Testing","/pcba/fct-test",{"label":355,"path":356},"Final Inspection & Packing","/pcba/final-quality-inspection",{"label":358,"path":359},"Incoming Quality Control","/pcba/incoming-quality-control",{"heading":361,"linkClass":362,"links":363},"Industry Applications (Entry)","text-nowrap",[364,367,370,373,376,379,382,385,388,391,394],{"label":365,"path":366},"Server / Data Center","/industries/server-data-center-pcb",{"label":368,"path":369},"Automotive / EV","/industries/automotive-electronics-pcb",{"label":371,"path":372},"Medical","/industries/medical-pcb",{"label":374,"path":375},"Telecom / 5G","/industries/communication-equipment-pcb",{"label":377,"path":378},"Aerospace & Defense","/industries/aerospace-defense-pcb",{"label":380,"path":381},"Drone / UAV","/industries/drone-uav-pcb",{"label":383,"path":384},"Industrial Control & Automation","/industries/industrial-control-pcb",{"label":386,"path":387},"Power & New Energy","/industries/power-energy-pcb",{"label":389,"path":390},"Robotics & Automation","/industries/robotics-pcb",{"label":392,"path":393},"Security / Security Equipment","/industries/security-equipment-pcb",{"label":395,"path":396},"PCB Industry Overview →","/pcb-industry-solutions",1780457711470]