FCC Part 15 for Wireless Robots: Module, Antenna and Change Evidence

FCC Part 15 robotics compliance requires a review of the robot as the final radio host, not just its purchased module. A certified module can reduce filing work when its grant and integration conditions are met, but the host manufacturer remains responsible for applicable requirements outside that grant and for the final product's compliance. Keep module identity, antenna, RF exposure, simultaneous transmitters, digital circuitry and operating configuration connected to evidence. A module approval alone does not approve the whole robot. (FCC KDB 996369 D04, sections 1.0 and 2.0)

This guide is for US-facing robotics hardware, regulatory and manufacturing owners preparing a product release or radio-related change. Its output is a module-to-host evidence register. The buyer's question is which existing authorisation can be used for this robot configuration and which host or change work is still needed.

What does FCC Part 15 modular approval cover?

Section 15.212 provides requirements for modular transmitters. Its conditions include matters such as shielding, buffering, power regulation, antennas, stand-alone testing, labelling, applicable operating requirements and RF exposure. Limited modular approval is a separate case with its own controls. The actual grant and integration instructions are therefore essential inputs, not administrative attachments. (47 CFR 15.212(a) and (b))

FCC's KDB 996369 page identifies D04 Module Integration Guide v02 as guidance for host product manufacturers. The current KDB record should be used to identify the applicable guidance documents and versions. D04 explains the host's responsibilities when relying on a certified transmitter module. (FCC KDB 996369, attachment descriptions)

The guide's introduction says host manufacturers are responsible for following integration guidance and limited transmitter verification work, and for additional equipment authorisation and testing not covered by the module grant. It gives Part 15 Subpart B unintentional-radiator requirements and other non-modular transmitters as examples. The final host review must account for those functions. (D04, section 1.0)

A mobile robot may also contain cellular or other radios governed by separate rule parts. Identify all included radio functions and their applicable authorisation basis. “Part 15 complete” should not conceal a transmitter outside the declared scope. D04's general guidance explicitly asks hosts to account for all applicable FCC requirements. (D04, section 2.0(a) and note 1)

Which module documents does the robot manufacturer need?

Identify the exact module and FCC ID, grant conditions, integration instructions, relevant antenna information and any restrictions on host type or simultaneous operation. Record the module revision actually installed, the radio configuration available in the host and the organisation responsible for resolving unanswered integration questions.

For a limited module or unclear instructions, D04 directs the integrator to work with the module grantee. Its guidance also requires following the RF-exposure instructions and contacting the module manufacturer when those instructions are unclear. A purchasing data sheet is not a substitute for the approved integration basis. (D04, section 2.0(b) and (c))

Keep the documentation specific to the final product. A robot's enclosure, cable arrangement, motors, digital electronics and radio operating modes can be relevant to the host investigation. The evidence record should identify the manufactured configuration rather than an unnamed engineering bench assembly. D04's host testing guidance discusses effects from other transmitters, digital circuitry and the physical host properties. (D04, section 3.1(b))

Use the robot component supplier-change guide for supplier claim and configuration handover. This FCC register adds the actual grant, antenna and final-host authorisation boundaries.

How should the module-to-host evidence register work?

Use one row per grant condition, host requirement or consequential integration change. Retain the source, approved configuration, implementation, evidence and receiving decision. Label FCC rules, FCC guidance, grant conditions and internal engineering methods by their role.

The following fictional worksheet concerns a US robot manufacturer proposing a wireless inspection robot. No module grant, robot or laboratory result is real. The identifiers illustrate how the evidence would be organised and deliberately do not resemble actual FCC IDs.

The table is a proposed records method, not an FCC test procedure. Its useful output is a configuration-specific disposition and open-action list. Receiving a module certificate can close a document-delivery action while leaving RF-02 or RF-04 unresolved.

What changes to antennas and RF exposure need review?

D04 identifies limits on changing a module and the types of antenna usable in the final product. Its antenna-gain guidance discusses situations requiring involvement of the module grantee, change in FCC ID or new evidence. The appropriate route depends on the grant and the technical change. Do not decide it from a generic rule such as “same connector means equivalent antenna”. (D04, sections 1.0 and 3.5)

For RF exposure, D04 describes different integration conditions, including specified separation distances and specific host platforms authorised for closer operation. The distance and assessment depend on the actual instructions and grant. A generic 20 cm figure is not a universal robot separation rule, nor is it a machinery collision-safety distance. (D04, section 2.0(c))

Record the intended exposure scenario. A robot parked near an operator's workstation and a robot serviced close to a radiating structure may create different questions. The regulatory reviewer needs the actual antenna placement and operating conditions. If those conditions are not established, keep the exposure row open rather than importing another product's grant assumption.

An enclosure or antenna relocation can also affect the host evidence even if the module is unchanged. Trace the modification to the original investigation and applicable grant conditions, then retain the rationale for any evidence reused. A mechanical change is not automatically outside the radio compliance scope.

What final-host evidence remains after module approval?

D04 asks hosts to maintain documentation showing how the product complies, obtain applicable unintentional-radiator authorisation, label the product appropriately and investigate the final product with transmitters operating. Its section 3.1 explains the recommended composite investigation and the host's responsibility for emissions introduced by the combined arrangement. Separate certification applications are not automatically required for every such investigation. The specific route must follow the actual product and applicable rules. (D04, section 2.0(a), (d), (e), (f) and section 3.1)

Agree the relevant operational modes with the qualified test and authorisation reviewers. Keep radio software, enabled bands and channels, simultaneous transmission, digital activity and hardware configuration identifiable in the evidence. The article does not prescribe a universal frequency sweep or emission limit. Those criteria come from the applicable rule and test basis.

The robotics verification configuration guide describes how results retain their setup and limitations. Apply that discipline to host investigations so the manufacturing release can identify precisely which configuration the evidence addresses.

Also keep radio compliance separate from robot behaviour under communication failure. A host authorisation or emissions result does not demonstrate command continuity, fault response or a protective function. The robotics interface guide supports defining those separate engineering interfaces and response requirements.

Which antenna-change failure should hold release?

In the fictional inspection robot, procurement proposes a higher-gain antenna to improve reception. The module remains M-7, so the release checklist retains its earlier “approved module” status. No one has compared the new antenna against the grant conditions or the original host investigation.

The open issue is not whether M-7 once received approval. It is whether the proposed host can use the new antenna under the actual authorisation and what change evidence is required. RF-02 should remain unresolved, linked to the antenna change and the affected host configuration.

A proposed disposition would hold that radio configuration from release until the module grantee and qualified reviewers establish the route and required evidence. The final decision would also identify any affected exposure, composite-product, labelling or manufacturing records. No test or approval is reported in this example.

This workflow avoids overwriting historical evidence. The earlier result remains evidence for the earlier configuration. A new applicability review or further work must establish what supports the changed product.

How can Arc connect the FCC evidence handover?

Arc's connected programme model can hold configured grant-condition, host-requirement and supplier records with ownership and relationships. Its traceability can connect an antenna or enclosure change to affected conditions and evidence.

Verification records retain requirements, configurations, procedures, results and evidence. The team defines the schema and qualified review process. Arc organises the release record. It does not perform RF testing, select an authorisation route or issue FCC approval.

Sources and method

Prepared on 2 November 2026 using current 47 CFR 15.212, FCC's KDB 996369 record and its D04 Module Integration Guide v02, plus Arc's canonical capability-page source. Claims distinguish the regulation, guidance and product-specific grant conditions. The worksheet and inspection-robot example are fictional editorial methods with no actual grant or executed evidence. No universal antenna substitution, exposure distance, emission limit or filing route is asserted. Arc sells requirements management and systems engineering software.

Frequently asked questions