PD9BE200NGIntel BE200

Intel(R) WiFi Adapter Information Guide index.htm[5/23/2023 2:49:19 PM] Intel® WiFi Adapter Information Guide This version of Intel® PROSet/Wireless WiFi Software is compatible with the adapters listed below. Note that newer features provided in this software are generally not supported on older generations of wireless adapters. The following adapters are supported in Windows* 10: Intel® Wi-Fi 7 BE200 Intel® Wi-Fi 6E AX411 Intel® Wi-Fi 6E AX211 Intel® Wi-Fi 6E AX210 Intel® Wi-Fi 6 AX203 Intel® Wi-Fi 6 AX201 Intel® Wi-Fi 6 AX200 Intel® Wi-Fi 6 AX101 Intel® Wireless-AC 9560 Intel® Wireless-AC 9462 Intel® Wireless-AC 9461 Intel® Wireless-AC 9260 Intel® Dual Band Wireless-AC 8265 Intel® Dual Band Wireless-AC 8260 Intel® Dual Band Wireless-AC 3168 Intel® Dual Band Wireless-AC 7265 Intel® Dual Band Wireless-N 7265 Intel® Wireless-N 7265 Intel® Dual Band Wireless-AC 3165 With your WiFi network card, you can access WiFi networks, share files or printers, or even share your Internet connection. All these features can be explored using a WiFi network in your home or office. This WiFi network solution is designed for both home and business use. Additional users and features can be added as your networking needs grow and change. This guide contains basic information about Intel adapters. Intel® wireless adapters enable fast connectivity without wires for desktop and notebook PCs. Adapter Settings Regulatory and Safety Information Specifications Support Warranty Depending on the model of your Intel WiFi adapter, your adapter is compatible with 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac and 802.11ax wireless standards. Operating at 5GHz or 2.4GHz frequency, you can now connect your computer to existing high-speed networks that use multiple access points within large or small environments. Your WiFi adapter maintains automatic data rate control according to the access point location and signal strength to achieve the fastest possible connection. Information in this document is subject to change without notice. Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein. IMPORTANT NOTICE FOR ALL USERS OR DISTRIBUTORS: Intel wireless LAN adapters are engineered, manufactured, tested, and quality checked to ensure that they meet all necessary local and governmental regulatory agency requirements for the regions that they are designated and/or marked to ship into. Because wireless LANs are generally unlicensed devices that share spectrum with radars, satellites, and other licensed and unlicensed devices, it is sometimes necessary to dynamically detect, avoid, and limit usage to avoid interference with these devices. In many instances Intel is required to provide test data to prove Intel(R) WiFi Adapter Information Guide index.htm[5/23/2023 2:49:19 PM] regional and local compliance to regional and governmental regulations before certification or approval to use the product is granted. Intel's wireless LAN's EEPROM, firmware, and software driver are designed to carefully control parameters that affect radio operation and to ensure electromagnetic compliance (EMC). These parameters include, without limitation, RF power, spectrum usage, channel scanning, and human exposure. For these reasons Intel cannot permit any manipulation by third parties of the software provided in binary format with the wireless LAN adapters (e.g., the EEPROM and firmware). Furthermore, if you use any patches, utilities, or code with the Intel wireless LAN adapters that have been manipulated by an unauthorized party (i.e., patches, utilities, or code (including open source code modifications) which have not been validated by Intel), (i) you will be solely responsible for ensuring the regulatory compliance of the products, (ii) Intel will bear no liability, under any theory of liability for any issues associated with the modified products, including without limitation, claims under the warranty and/or issues arising from regulatory non-compliance, and (iii) Intel will not provide or be required to assist in providing support to any third parties for such modified products. Note: Many regulatory agencies consider Wireless LAN adapters to be "modules", and accordingly, condition system- level regulatory approval upon receipt and review of test data documenting that the antennas and system configuration do not cause the EMC and radio operation to be non-compliant. Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries. *Other names and brands may be claimed as the property of others. © Intel Corporation. April 2023 Adapter Settings Back to Contents Adapter Settings The Advanced tab displays the device properties for the WiFi adapter installed on your computer. How to Access Double-click on the Intel WiFi adapter in the Network adapters section of the Device Manager and select the Advanced tab. A description of the WiFi adapter settings on the Advanced tab can be found here: https://www.intel.com/content/www/us/en/support/articles/000005585/network-and-i-o/wireless-networking.html Back to Top Back to Contents Trademarks and Disclaimers adaptusr.htm[5/23/2023 2:49:20 PM] Regulatory Information regs.htm[5/23/2023 2:49:23 PM] Back to Contents Regulatory Information This section provides regulatory information for the following wireless adapters: Intel® Centrino® Wireless-N 100 Intel® Centrino® Wireless-N 105 Intel® Centrino® Wireless-N 130 Intel® Centrino® Wireless-N 135 Intel® Centrino® Wireless-N 1000 Intel® Centrino® Wireless-N 1030 Intel® Centrino® Wireless-N 2200 Intel® Centrino® Wireless-N 2230 Intel® Centrino® Wireless-N + WiMAX 6150 Intel® Centrino® Advanced-N 6200 Intel® Centrino® Advanced-N 6205 Intel® Centrino® Advanced-N 6230 Intel® Centrino® Advanced-N 6235 Intel® Centrino® Advanced-N + WiMAX 6250 Intel® Centrino® Ultimate-N 6300 Intel® Dual Band Wireless-AC 7260 Intel® Dual Band Wirele…

Text truncated - open the document above for the full version.

021423-17 rev 4 Certification Application Attestation Statements Date: July 24, 2023 American Certification Body, Inc. 313 Park Avenue Suite 300 Falls Church, VA 22046 To Whom It May Concern: Statement for 47 CFR section 2.911(d)(5)(i) Intel Corporation certifies that as of the date of the application the equipment for which authorization is sought is not “covered” equipment 1 prohibited from receiving an equipment authorization pursuant to section 2.903 of the FCC rules. If the equipment for which the applicant seeks authorization is produced by any of the entities identified on the current Covered List, including affiliates or subsidiaries of the named companies, the applicant must include an explanation on why the equipment is not “covered” equipment. Additional Explanation: <N/A> Statement for 47 CFR section 2.911(d)(5)(ii) Intel Corporation (“the applicant”) certifies that, as of the date of the filing of this application, the applicant ☐ - is / ☒ - is not identified on the Covered List as an entity producing “covered” equipment. Thank you, By: (S ignature 2 ) Benjamin Lavenant (Print name) Title: Regulatory Engineer Company: Intel Corporation Telephone: 0493001400 1 - The Commission’s Covered List is published by the Public Safety and Homeland Security Bureau and posted on the Commission’s website. This Covered List, which is periodically updated, identifies particular equipment, produced by particular entities, that constitutes “covered” equipment. https://www.fcc.gov/supplychain/coveredlist . 2 - Letters should be placed on appropriate letterhead.

U.S. Agent Designation for Service of Process (Applicant and U.S. Agent are Separate Parties) TO: Federal Communications Commission 7435 Oakland Mills Road Columbia MD 21046 intel. ATTENTION: FCC Certification - Section 2.911 (d)(7) Information Desjgnated U.S Agent Company Name: Intel Corporation Contact Name: Robert W Paxman Street Address: 2111 NE 25th Avenue City/Province/Zip: Hillsboro, OR 97124 Telephone No: (503) 712- 8077 Email: [email protected] FRN #: 0023093867 This letter is to confirm that we ("the Designated U.S. Agent) have accepted the responsibility to act as the Designated U.S. Agent for Service of Process as required by section 47 CFR 2.911 (d)(7) o ?� e Applicant noted below. U.S. Agent Signature: /�� 4--- Date: 7/24/2023 Signed by: Robert W. Paxman/ Wireless Product Regulations Engineer The Applicant acknowledges that they must maintain an agent for no less than one year after terminating all marketing and importation OR the conclusion of any Commission­ related proceeding involving the equipment. The applicant further acknowledges their responsibility to inform the FCC whenever the Designated U.S. Agent information above changes. Applicant Company name: Intel Corporation Grantee Code: PD9 Contact Name: Benjamin Lavenan t Street Address: 425 rue de Goa City/Province/Zip: 06600 Telephone No: 0493001400 Email: [email protected] Applicant Signature: Date:7/24/2023 Signed by: Benjamin Lavenant / Wireless Regulatory Engineer 022423-17 Rev 6

Intel Corporation S.A.S. 425 Rue de Goa – Le Cargo B6 – 06600 Antibes – France Tel. +33 (0)4 93 00 14 00 - Fax +33 (0)4 93 00 14 01 SAS au capital de 5 208 026,16 E uros – RCS Nanterre 302 456 199 – Siret 302 456 199 00256 - TVA F R54302456199 July 31, 2023 Federal Communications Commission 7435 Oakland Mills Road Columbia, Maryland 21046 USA S ubject: Model BE200D2W Wireless LAN Adapter Card FCC ID: PD9BE200NG IC: 1000M-BE200NG Gentlemen: Please be advised that the Model BE200NGW 802.11a/b/g/n/ac/be + BT Wireless LAN mini-PCIe card is manufactured for the global market but when mark eted in the U.S. under FCC ID: PD9BE200NG and in Canada under IC: 1000M-BE200NG. The non-volatile memory (NVM) will be programmed at the factory to only actively scan and operate on these specific channels during normal WLAN operation. During Wi-Fi Direct mode the device may act as a group owner (GO) to establish a peer-to-peer (P2P) net work including conditions when no master device is present on these specific channels. Channels 1-13,2412-2472MHz 802.11b mode Channels 1-13, 2412-2472MHz 802.11g mode Channels 1-13, 2412-2472MHz 802.11n mode (20MHz channel) Channels 3-11, 2422-2462MHz 802.11n mode (40MHz channel) The device operates as a client without radar detection capability and will be programmed at the factory to passively scan on the following dynamic frequency selection (DFS) channels and will only listen for a master device and cannot send a probe request to initiate communication on these DFS channels. Accordingly passive scanning provides protection for TDWR operations and preventing transmission in the 5600MHz – 5650MHz frequency band. Client software and drivers will never enable the device to act as a master or GO for operation in DFS frequency bands and therefore ad- hoc mode is always disabled on these passive scan DFS channels. Channels 52-64, 5260-5320MHz 802.11a mode Channels 52-64, 5260-5320MHz 802.11n mode (20 MHz channel) Channels 52-64, 5260-5320MHz 802.11ac mode (20 MHz channel) Channels 54-62, 5270-5310MHz 802.11n mode (40MHz channel) Channels 54-62, 5270-5310MHz 802.11ac mode (40MHz channel) Channel 58, 5290MHz 802.11ac mode (80MHz channel) Channel 50, 5250MHz 802.11ac mode (160MHz channel) Channels 100-140, 5500-5700MHz 802.11a mode Channels 100-140, 5500-5700MHz 802.11n mode (20 MHz channel) Channels 100-144, 5500-5720MHz 802.11ac mode (20 MHz channel) Channels 102-134, 5510-5670MHz 802.11n mode (40MHz channel) Channels 102-142, 5510-5710MHz 802.11ac mode (40MHz channel) Channels 106 &138, 5540 & 5690MHz 802.11ac mode (80MHz channel) Channel 114, 5570MHz 802.11ac mode (160MHz channel) Intel Corporation S.A .S . 425 Rue de Goa – Le Cargo B6 – 06600 Antibes – France Tel. +33 (0)4 93 00 14 00 - Fax +33 (0)4 93 00 14 01 SAS au capital de 5 208 026,16 Euros – RCS Nanterre 302 456 199 – Siret 302 456 199 00256 - TVA FR54302456199 This device meets the requirements of FCC Part 15.202 and accordingly will be programmed at the factory to active scan on the following non-DFS channels to initiate communication during normal WLAN operation. When operating in Wi-Fi Direct mode on these non-DFS channels, it may operate as a P2P client device or GO to establish a P2P network if, and only if, a master device is present and network communication is maintained between a master device and the GO. Channels 36-48, 5180-5240MHz 802.11a mode Channels 36-48, 5180-5240MHz 802.11n mode (20 MHz channel) Channels 36-48, 5180-5240MHz 802.11ac mode (20 MHz channel) Channels 38-46, 5190-5230MHz 802.11n mode (40MHz channel) Channels 38-46, 5190-5230MHz 802.11ac mode (40MHz channel) Channel 42, 5210MHz 802.11ac mode (80MHz channel) Channels 149-165, 5745-5825MHz 802.11a mode Channels 149-165, 5745-5825MHz 802.11n mode (20 MHz channel) Channels 149-165, 5745-5825MHz 802.11ac mode (20 MHz channel) Channels151-159, 5755-5795MHz 802.11n mode (40MHz channel) Channels151-159, 5755-5795MHz 802.11ac mode (40MHz channel) Channel 155, 5775MHz 802.11ac mode (80MHz channel) This device meets the requirements of FCC Part 15.202 and 15.407 as a 5.9GHz band Indoor client module (UNII) and accordingly will be programmed at the factory to passive scan on the following channels. On these channels, a) the client device will not directly connect to another client device, b) will only associate and connect with an indoor Access Point (AP) or indoor subordinate, and c) the Client device (EUT) will always be under the control of an indoor AP. However. there may exist situations where the client may transmit brief messages, prior to being under the control of an AP, to join an AP network. But these brief messages will only occur if the client has detected a signal confirming that an AP is operating on a particular channel. These brief messages will have a time-out mechanism if it does not receive a response from an AP. Channels 169-177, 5845-5885MHz 802.11a mode Channels 169-177, 5845-5885MHz 802.11n mode (20 MHz channel) Channels 169-177, 5845-5885MHz 802.11ac mode (20 MHz channel) Channels 167-175, 5835-5875MHz 802.11n mode (40MHz channel) Channels 167-175, 5835-5875MHz 802.11ac mode (40MHz channel) Channel 171, 5855MHz 802.11ac mode (80MHz channel) Channel 163, 5815MHz 802.11ac mode (160MHz channel) Intel Corporation S.A .S . 425 Rue de Goa – Le Cargo B6 – 06600 Antibes – France Tel. +33 (0)4 93 00 14 00 - Fax +33 (0)4 93 00 14 01 SAS au capital de 5 208 026,16 Euros – RCS Nanterre 302 456 199 – Siret 302 456 199 00256 - TVA FR54302456199 This device meets the requirements of FCC Part 15.202 and 15.407 as a 6GHz Dual Client (6CD) and accordingly will be programmed at the factory to passive scan (listen before talk) on the following channels. This client may initiate a brief message to associate with a low power indoor access point or subordinate or Standard Power Access Point and establish a connection only after receiving a confirmation signal confirming that an AP is present and operating on a particular channel. After being assoc…

Text truncated - open the document above for the full version.

Intel Corporation S.A.S. 425 Rue de Goa – Le Cargo B6 – 06600 Antibes – France Tel. +33 (0)4 93 00 14 00 - Fax +33 (0)4 93 00 14 01 SAS au capital de 5 208 026,16 Euros – RCS Nanterre 302 456 199 – Siret 302 456 199 00256 - TVA FR54302456199 July 31, 2023 Declaration Let ter related to Channel puncturing feature. We, Intel Corporation, attest that this device under FCC ID PD9BE200D2 and I C 1000M – BE200D2 has the channel puncturing not activated. The firmware is programmed at the factory and cannot be modified by third parties. Yours Sincerely, B enjamin Lavenant Wireless regulatory Engineer Intel Corporation

July 27, 2023 The information provided in this document applies to the following Intel Wireless Adapter Modules FCC ID: PD9BE200NG IC: 1000M – BE200NG Software Security Description – KDB 594280 D02v01r03 Section II – RSS 248 (section 11 a, b, & c) General Description 1. Describe how any software/firmware update will be obtained, downloaded, and installed. Software that is accessed through manufacturer’s website or device’s management system, must describe the different levels of security as appropriate. There is no downloadable software provided by the manufacturer that can modify critical radio transmitter parameters. All critical parameters are programmed in OTP memory at the factory and cannot be modified or overridden by third parties. 2. Describe the rf parameters that are modified by any software/firmware without any hardware changes. Are these parameters in some way limited, such that, it will not exceed the authorized RF characteristics? There are no rf parameters that can be modified. All rf parameters are programmed in OTP memory at the factory and cannot be modified or overridden by third parties. 3. Describe in detail the authentication protocols that are in place to ensure that the source of the RF related software/firmware is legitimate. Describe in detail how the software is protected against modification. The firmware is programmed at the factory and cannot be modified by third parties. 4. Describe in detail any encryption methods used to support the use of legitimate RF relatedsoftware/firmware. The firmware is programmed at the factory and cannot be modified by third parties therefore no encryption is necessary. 5. For a device that can be configured as a master and client (with active or passive scanning), explain how the device ensures compliance for each mode? In particular if the device acts as master in some band of operation and client in another; how is compliance ensured in each band of operation? This is a client module only. Third‐Party Access Control 1. Explain if any third parties have the capability to operate a US sold device on any other regulatory domain, frequencies, or in violation of the device’s authorization if activated in the U.S.. violation of the device’s authorization if activated in the U.S..violation of the device’s authorization if activated in the U.S..violation of the device’s authorization if activated in the U.S.. violation of the device’s authorization if activated in the U.S..any manner that is in Third parties do not the capability to operate in any manner that is violation of the certification in the U.S. 2.Describe, if the device permits third‐party software or firmware installation, what mechanisms are provided by the manufacturer to permit integration of such functions while ensuring that the RF parameters of the device cannot be operated outside its authorization for operation in the U.S. In the description include what controls and/or agreements are in place with providers of third‐party functionality to ensure the devices’ underlying RF parameters are unchanged and how the manufacturer verifies the functionality. factory and cannot be reprogrammed or re-flashed by third parties. 3. For Certified Transmitter modular devices, describe how the module grantee ensures that hosts manufactures fully comply with these software security requirements for U‐NII devices. If the module is controlled through driver software loaded in the host, describe how the drivers are controlled and managed such that the modular transmitter parameters are not modified outside the grant of authorization. There are no rf parameters that can be modified. All rf parameters are programmed in OTP memory at the factory and cannot be modified or overridden by third parties. The module is not controlled by driver software on the host and cannot override critical rf parameters stored in module OTP memory. SOFTWARE CONFIGURATION DESCRIPTION – KDB 594280 D02v01r02 Section III USER CONFIGURATION GUIDE 1. Describe the user configurations permitted through the UI. If different levels of access are permitted for professional installers, system integrators or end‐users, describe the differences. No UI provided. a) What parameters are viewable and configurable by different parties? None b) What parameters are accessible or modifiable to the professional installer or system integrator? None i) Are the parameters in some way limited, so that the installers will not enter parameters that exceed those authorized? The module micro-code reads the parameters from the module OTP memory. These parameters cannot be modified or overridden by sw drivers. ii) What controls exist that the user cannot operate the device outside its authorization in the U.S.? Default mode is always FCC compliant. Other country modes cannot be activated without receiving three independent country codes from different APs, otherwise remains in FCC default mode (always FCC compliant) c) What parameters are accessible or modifiable by the end‐user? None i) Are the parameters in some way limited, so that The module micro-code reads the parameters from the the installers will not enter parameters that exceed those authorized? module OTP memory. These parameters cannot be modified or overridden by sw drivers. ii) What controls exist that the user cannot operate the device outside its authorization in the U.S.? Default mode is always FCC compliant. Other country modes cannot be activated without receiving three independent country codes from different APs, otherwise remains in FCC default mode (always FCC compliant) d) Is the country code factory set? Can it be changed in the UI? Default country code is set in the factory and no UI is provided for modification. i) If it can be changed, what controls exist to ensure that the device can only operate within its authorization in the U.S.? Programmed for default mode which is always FCC compliant. Always set for default for all start-ups, resets, timeouts or other ho…

Text truncated - open the document above for the full version.

July 20, 2023 Attestation Letter for Dual Client (6CD) Module Approval We, Intel Corporation, attest that this device under FCC ID PD9BE200NG complies with device protocol requirements and operational restrictions for Dual Client 6CD. a)This device only support 6 CD category and the maximum power does not exceed authorized values. b)This device will only associate and connect with a Low Power Indoor Access Point, Subordinate Device, or Standard Power Access Point and never directly link to any other client devices. c)This device will always initiate transmission under the control of a Low Power Indoor Access Point, Subordinate Device, or Standard Power Access Point except for brief communications before joining a network. These brief messages will only occur if the client has detected a Low Power Indoor Access Point, Subordinate Device, or Standard Power Access Point operating on a channel. These messages will have a timeout mechanism such that if this device does not receive a response from an AP, it will not continually repeat the request. d)This device, when associated and connected with a Low Power Indoor Access Point, Subordinate Device or Standard Power Access Point device, will operate at or below power levels advertised by the Low Power Indoor Access Point, Subordinate Device, or Standard Power Access Point: i. Lower than or equal to the power advertised by the Low Power Indoor Access Point or Subordinate Device; and never above the maximum output power allowed by the FCC grant for clients associated with Low Power Indoor Access Points or Subordinate Devices. ii. 6 dB lower than the Standard Power Access Point’s authorized power level; and never above the maximum output power allowed by the FCC grant for clients associated with Standard Power Access Points. e)Contention-based protocol as demonstrated in the test report is permanently embedded in the module and is not host-dependent based protocol demonstrated in the test report. f)We acknowledge this device is subject to restrictions listed below. i. Prohibited for control of or communications with unmanned aircraft systems, including drones. This device is prohibited for control of or communications with unmanned aircraft systems, including drones. Best Regards, Benjamin LAVENANT Regulatory Engineer Intel Corporation [email protected]

July 20, 2023 Subject: Confidentiality Request for FCC ID: PD9BE200NG P ursuant to FCC 47 CRF 0.457(d) and 0.459 the applicant requests that a part of the subject FCC application be held confidential. Type of Confidentiality Requested Exhibit Short Term User's Manual Permanent Operation Description Short Term Test Setup Photos Intel Corporation has spent substantial effort in developing this product and it is one of the first of its kind in industry. Having the subject information easily available to "competition" would negate the advantage they have achieved by developing this product. Not protecting the details of the design will result in financial hardship. Permanent Confidentiality: The applicant requests the exhibits listed above as permanently confidential be permanently withheld from public review due to materials that contain trade secrets and proprietary information not customarily released to the public. Short-Term Confidentiality: The applicant requests the exhibits selected above as short term confidential be withheld from public view for a period of 180 days from the date of the Grant of Equipment Authorization and prior to marketing. This is to avoid premature release of sensitive information prior to marketing or release of the product to the public. Applicant is also aware that they are responsible to notify ACB in the event information regarding the product or the product is made available to the public. ACB will then release the documents listed above for public disclosure pursuant to FCC Public Notice DA 04-1705. Sincerely, Benjamin LAVENANT Regulatory Engineer Intel Corporation [email protected]

053019-02a Request for Modular/Limited Modular Approval ☐- Limited Split Modular Approval ☒- Modular Approval☐- Split Modular Approval Confidentiality Request for: ______PD9BE200NG_____ 8 Basic Requirements – FCC Part 15.212(a)(1) For Items Marked “NO(*)”, the Limited Module Description Must be Filled Out on the Following Pages Modular Approval Requirement Requirement Met 1. The modular transmitter must have its own RF shielding. This is intended to ensure that the module does not have to rely upon the shielding provided by the device into which it is installed in order for all modular transmitter emissions to comply with FCC limits. It is also intended to prevent coupling between the RF circuitry of the module and any wires or circuits in the device into which the module is installed. Such coupling may result in non-compliant operation. The physical crystal and tuning capacitors may be located external to the shielded radio elements. 15.212(a)(1)(i) ☒ - YES ☐ - NO(*) Details: – The module contains a metal shield which cover s all RF components and circuitry. The shield is located on the top of the board next to antenna connector. See photo provided with this filing. 2. The modular transmitter must have buffered modulation/data inputs (if such inputs are provided) to ensure that the module will comply with FCC requirements under conditions of excessive data rates or over-modulation. 15.212(a)(1)(ii) ☒ - YES ☐ - NO(*) Details: – Data to the modulation circuit is buffered as described in the operational description provided with the application> 3. The modular transmitter must have its own power supply regulation on the module. This is intended to ensure that the module will comply with FCC requirements regardless of the design of the power supplying circuitry in the device into which the module is installed. 15.212(a)(1)(iii) ☒ - YES ☐- NO(*) Details: – The module contains its own power supply regulation. Please refer to operational description filed with this application 4. The modular transmitter must comply with the antenna and transmission system requirements of §§ 15.203, 15.204(b), 15.204(c), 15.212(a), and 2.929(b). The antenna must either be permanently attached or employ a ‘‘unique’’ antenna coupler (at all connections between the module and the antenna, including the cable). The ‘‘professional installation’’ provision of § 15.203 is not applicable to modules but can apply to limited modular approvals under paragraph 15.212(b). 15.212(a)(1)(iv) ☒ - YES ☐ - NO(*) Details: – The module connects to its antenna using an UFL connec tor which is considered a non-standard connector. The antenna and connector specification are provided with this filing. 5. The modular transmitter must be tested in a stand-alone configuration, i.e., the module must not be July 20, 2023 Subject: Manufacturer’s Declaration for inside another device during testing. This is intended to demonstrate that the mo dule is capable of complying with Part 15 emission limits regardless of the device into which it is eventually installed. Unless the transmitter module will be b attery powered, it must comply with the AC line conducted requirements found in Section 15.207. AC or DC power lines and data input/output lines connected to ☐ X - YES the module must not contain ferrites, unless they will be marketed with the m odule (see Section 15.27(a)). The length of these lines shall be length typical of actual use or, if that length is unknown, at least 10 centimeters to insure that there is no coupling between th e case of th e module and supporting equipment. Any accessories, peripherals, or support equipment connected to the module during testing shall be unmodified or commercially available (see Section 15.31(i)). 15.212(a)(1)(v) Details: – The module was tested in stand-alone mode as described in this filing. - NO(*) ☐- Limited Modular Approval 053019-02a Modular Approval Requirement Requirement Met 6. The modular transmitter must be labeled with its own FCC ID number, or use an electron display (see KDB Publication 784748). If using a permanently affixed label with its own FCC ID number, if the FCC ID is not visible when the module is installed inside another device, then the outside of the device into which the module is installed must also display a label r…

Text truncated - open the document above for the full version.