MT7927 QA-Tool User Guideline

1 System overview

1.1 General Description

The MT7927 chip is a highly integrated single chip featuring a 2x2 dual-band wireless LAN and Bluetooth combo radio. It can be configured in test-mode for performance validation, production testing, and regulatory certification. Two software tools, QA-Tool and Combo-Tool, are responsible for evaluating Wi-Fi and Bluetooth signal and performance testing. This document introduces how to install and use the QA-Tool.

Input rating: 3.3Vdc, Operating Temperature: -10~70°C

2 QA-Tool

Users must install three major software components before using QA-Tool:

• WinPcap
• Windows 7 X64 security package
• QA-Tool Windows driver

MediaTek strongly recommends installing QA-Tool on a Windows 7-64bit operating system.

2.1 How to install QA-tool

Please follow the procedure listed below to install QA-Tool:

1. Install WinPcap
2. Update Windows 7 security package to register x64 signature mechanism
3. Install QA-Tool Windows driver.

2.1.1 Install WinPcap

If users are operating this tool for the first time, they should install WinPcap first. Please follow the link and steps below to install this software.

Link: https://www.winpcap.org/install/

WinPcap version: 4.1.3 or later.

Description of WinPcap installer screenshots: The screenshots show the WinPcap 4.1.3 Setup Wizard, including the welcome screen, license agreement, installation options (e.g., 'Automatically start the WinPcap driver at boot time'), and the completion screen.

2.1.2 Windows 10 install note

If users cannot install the driver in Windows 10 due to driver integrity check, try to disable the integrity check to allow installation.

Disable Driver Integrity Check

1. Open cmd as Administrator.
2. Execute 'bcdedit /set nointegritychecks on'
3. Reboot
4. Then install again. If still fails, try disabling 'Secure Boot' below.

NOTE: Re-enable the driver integrity check by executing 'bcdedit /set nointegritychecks off' and then rebooting.

Disable Secure Boot

Please refer to: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/disabling-secure-boot

2.1.3 QA-Tool Windows driver

MT7927 supports USB, SDIO, and PCIE interfaces. According to the interface type of MT7927 on the user's device, please refer to the steps shown below to install the QA-Tool Windows driver:

USB interface:

1. Connect DUT to PC/NB and check Windows Device Manager.
2. Windows Device Manager will discover the DUT, showing "Generic Bluetooth Adapter" (BT device) and "WiFi_If" (WiFi device).

Description of Device Manager screenshot: A screenshot of Windows Device Manager showing various hardware categories, including 'Generic Bluetooth Adapter' and 'Network adapters' which would contain the WiFi device.

3. Right-click the “Generic Bluetooth Adapter" BT device and select 'Disable' as shown.

Description of disabling Bluetooth adapter: A dialog box asking for confirmation to disable the 'Generic Bluetooth Adapter' device.

4. Right-click on the "WiFi_If" Wifi device and select 'Update Driver Software'.

Description of updating WiFi driver: A screenshot of Windows Device Manager showing the 'Network adapters' section, with the 'WiFi_If' device highlighted, and the context menu showing 'Update Driver Software'.

5. According to the user's Windows OS, select and install the test tool driver.

Description of driver installation steps: Multiple screenshots illustrating the Windows driver installation process, including selecting how to search for drivers (automatic vs. manual), browsing for driver software, selecting the driver from a list, and handling driver signature warnings (e.g., 'Windows cannot verify the publisher of this driver software').

2.2 How to use QA-tool

2.2.1 Launch QA-Tool

Double-click the QA-Tool icon "QATool_Dbg.exe"; the Device Select window will pop up.

Description of QA-Tool launch: A small window showing 'QATool_Dbg' and 'QATest MFC Application 0.0.1.38'.

Select the interface type and click the "OK" button to launch QA-Tool.

Description of Device Select window: A window with radio buttons for interface types like CTP, USB, PCIe, SDIO, CAPSOC, CUART, META, with an OK and Cancel button.

After the QA-Tool UI appears, users can check the RF Type, which should be shown as MT7927: 2T 2R, to ensure the QA-Tool is working normally. There are two modes: BIN-file mode and E-fuse mode, supported by QA-tool. Sections 2.2.2 & 2.2.3 provide details about each respective mode.

Description of QA-Tool UI: A screenshot of the QA-Tool interface showing various settings for Wi-Fi testing, including sections for TX/RX Band, EEPROM, MAC, BBP, RF Page, etc. Key elements like 'RF Type: MT6639 :: 2 T2R', 'Test Mode', 'Channel', 'Rate', 'TX frame setting', 'Payload', 'Start TX', 'Stop TX', 'Reset counter', etc. are visible.

2.2.2 Start QA-Tool in BIN-file Mode

To start in BIN-file mode, the user can use "eeprom.bin" while launching the QA tool. If "QATool_Dbg.exe" is in the same folder as "eeprom.bin", QA-tool will start in BIN-file mode. After QA-tool is launched, users can check the "EEPROM" sheet and verify "EEPROM Type: eeprom" to confirm the mode of QA-Tool in operation.

Description of EEPROM sheet (BIN-file mode): A screenshot of the QA-Tool's EEPROM sheet showing 'EEPROM Type: eeprom' and options for 'Single Read/Write Mode' with 'READ' and 'WRITE' radio buttons, 'Offset', 'Value', and 'Length' fields.

2.2.3 Start QA-Tool in E-fuse Mode

If the "eeprom.bin" file is not in the same folder as "QATool_Dbg.exe", QA-tool will start in E-fuse mode. Users can also check EEPROM Type: E-fuse in the "EEPROM" sheet.

Description of QA-Tool launch error (E-fuse mode): A dialog box stating "Buffer mode file not found! Read from eFuse..." with an OK button.

Description of EEPROM sheet (E-fuse mode): A screenshot of the QA-Tool's EEPROM sheet showing 'EEPROM Type: E-fuse' and similar 'Single Read/Write Mode' options as in BIN-file mode.

2.3 How to Use the QA-Tool

2.3.1 WIFI Packets Transmitting -1 stream

On the TX/RX page:

1. Select the TX sub-page and "Test Mode" as shown in the figure.
2. Select "Band0" for G band & "Band1" for A band.
3. Set Channel/Mode/Rate. Options include: 802.11b CCK, 802.11g OFDM, 802.11n HT Mix Mode, 802.11ac VHT, 802.11ax HESU, 802.11ax RU HETB (requires step g and RU Page setup), 802.11be EHTSU, 802.11be RU EHTTB (requires step g and RU Page setup).
4. Set BW. (Generally, System BW = Pre-Packet BW).
5. Select TX0 or TX1 only.
6. Select "Nss=1" and choose “TX/RXO” for transmitting.
7. Set LFT+GI index. (Generally, setting index 3) (This step is for HESU, HETB(RU), EHTSU, EHTTB(RU)).
8. Click the "Start TX" button to begin packet transmitting and click the "Stop TX" button to stop.
9. Set the packet number. (0 means infinite packets).
10. The transmitted packets number is shown in the "Transmitted:" area.
11. Users can click the "Reset counter" button to reset the "Transmitted:" area.
12. Users can click the [Up Arrow] button to modify the power level of the transmitting signal.
13. Users can click the [Right Arrow] button to modify the frequency offset of the transmitting signal.
14. If users want to adjust packets duty cycle:
    • Click "HWTX".
    • Adjust packets lengths (L) to modify packets duty cycle (example: 512).

Note: Please re-trigger "HWTX" if users change Channel/Mode/Rate/BW. Re-triggering involves clicking "Stop TX", un-clicking "HWTX", clicking "HWTX" again, and then clicking "Start TX".

Description of QA-Tool TX settings (1 stream): A detailed screenshot of the QA-Tool's TX settings interface, highlighting various parameters like 'RF Type', 'Test Mode', 'Channel', 'Rate', 'Nss', 'TX frame setting', 'Payload', 'MPDU Tx Length', 'Packet Tx Time', 'Start TX', 'Stop TX', 'Reset counter', etc.

2.3.2 WIFI Packets Transmitting -2 stream

On the TX/RX page:

1. Select the TX sub-page and "Test Mode" as shown in the figure.
2. Select "Band0" for G band & "Band1" for A band.
3. Set Channel/Mode/Rate. Options include: 802.11b CCK, 802.11g OFDM, 802.11n HT Mix Mode, 802.11ac VHT, 802.11ax HESU, 802.11ax RU HETB (requires step g and RU Page setup), 802.11be EHTSU, 802.11be RU EHTTB (requires step g and RU Page setup).
4. Set BW. (Generally, System BW = Pre-Packet BW).
5. Both TX0 and TX1.
6. Select "Nss=2" and choose both TX0 and TX1 for transmitting.
7. Set LFT+GI index. (Generally, setting index 3) (This step is for HESU, HETB(RU), EHTSU, EHTTB(RU)).
8. Click the "Start TX" button to begin packet transmitting and click "Stop TX" button to stop.
9. Set the packet number. (0 means infinite packets).
10. The transmitted packets number is shown in the "Transmitted:" area.
11. Users can click the "Reset counter" button to reset the "Transmitted:" area.
12. Users can click the [Up Arrow] button to modify the power level of the transmitting signal.
13. Users can click the [Right Arrow] button to modify the frequency offset of the transmitting signal.
14. If users want to adjust packets duty cycle:
    • Click "HWTX".
    • Adjust packets lengths (L) to modify packets duty cycle (example: 512).

Note: Please re-trigger "HWTX" if users change Channel/Mode/Rate/BW. Re-triggering involves clicking "Stop TX", un-clicking "HWTX", clicking "HWTX" again, and then clicking "Start TX".

Description of QA-Tool TX settings (2 stream): A screenshot similar to the 1-stream example, but showing 'Nss=2' selected and options for transmitting on both TX0 and TX1.

2.3.3 WIFI Packets 11ax RU TX (HE TB (trigger based)) Transmitting setting

On the RU page:

1. Select the RU sub-page.
2. Select band (0:G-band, 1:A-band).
3. Set Category.

Set RU index (wanted TB RU location). Refer to the RU Index from below.

Description of RU Index diagram: A visual representation showing different RU sizes mapped to indices across various bandwidths (BW20, BW40, BW80, BW160), with segments indicated.

Set data rate.

Set MU NSS/LDPC/stream index/length:

• "MU Nss=1" for Antenna number.
• Set LDPC or non-LDPC for transmitting.
• Set "Nss=1" for transmitting.
• Set "stream index=1".

Refer to the "Length" from the table below. (For example, set to 128 at RU26/MCS0...)

Click the "ADD" button to add a test case.

Click the "SET" button to set the test case.

If a user wants to test another case, they can select the original test case and click the "Remove" button to remove the old case and then reset another case.

Description of RU setting interface: A screenshot of the QA-Tool's RU setting interface, showing fields for 'Select Band', 'Category', 'Allocation (binary)', 'Sta ID', 'RU Index', 'MCS', 'MU Nss', 'LDPC', 'Stream Idx', 'Length', and buttons like 'ADD', 'Remove', 'SET', 'Save to File', 'Load from File', 'Clear All'.

2.3.4 VSA Setting

Open the Litepoint MW Web page and select VSA.

Setting RU info:

1. litepoint GI LTF Type should align with QAtool LTF+GI.
2. litepoint LDPC sym. (1=Orange light; 0=Gray light) should align with QAtool LDPC Extra Sym.
3. litepoint PE Disamb. (1=Orange light; 0=Gray light) should align with QAtool Tx PE.
4. A Factor:
   • If QAtool A Factor is set to 0, set litepont A Factor to 4.
   • If QAtool A Factor is set to 1, set litepont A Factor to 1.
   • If QAtool A Factor is set to 2, set litepont A Factor to 2.
   • If QAtool A Factor is set to 3, set litepont A Factor to 3.
5. Litepoint Stream setting (1 or 2) should align with QAtool RU-page stream setting.
6. Litepoint MCS rate setting should align with QAtool RU-page MCS setting.
7. Litepoint RU idx setting should align with QAtool RU-page RU index setting.
8. If QAtool RU-page LDPC is checked, set litepoint Coding to LDPC; otherwise, set litepoint Coding to BCC.

Description of iQxel VSA interface: A screenshot of the iQxel software interface, showing various RF measurement parameters like 'Packet Detection', 'Signal Power', 'EVM', 'Frequency Error', 'LTF+GI', 'LDPC Sym', 'PE Disamb', 'A Factor', 'Coding', etc., with specific settings highlighted.

2.3.5 WIFI Packets Receiving –1 stream

On the TX/RX page:

1. Select "Band0" for G band & "Band1" for A band.
2. Select the RX sub-page and "Test Mode" as shown in the figure.
3. Set Channel frequency.
4. Set BW. (Generally, System BW = Pre-Packet BW).
5. Choose "TXO/RXO" or TX1/RX1 for receiving.
6. Select HE_MU and EHT mode and Set RU Station ID (wanted RU location station ID) (this step is for HETB(RU), EHTTB(RU) and the default sat ID is "888").
7. Click the "Start RX" button to receive WIFI packets.
8. Enable the WIFI signal generator to transmit packets. Click the "Stop RX" button to stop receiving.
9. Successful received packets number will be shown in the "RX OK” area and RSSI shown in the "inst RSSI IB 0" area.
10. Users can click the "Reset counter" button to reset the counter value.

Description of QA-Tool RX settings (1 stream): A screenshot of the QA-Tool's RX settings interface, showing fields for 'Channel', 'BW', 'TX/RXO' selection, 'RU Station ID', 'Start RX', 'Stop RX', 'RX OK' count, 'inst RSSI IB 0', and 'Reset counter'.

2.3.6 WIFI Packets Receiving –2 stream

On the TX/RX page:

1. Select "Band0" for G band & "Band1" for A band.
2. Select the RX sub-page and "Test Mode" as shown in the figure.
3. Set Channel frequency.
4. Set BW. (Generally, System BW = Pre-Packet BW).
5. Choose "TXO/RXO" and TX1/RX1 for receiving.
6. Select HE_MU mode and Set RU Station ID (wanted RU location station ID) (this step is for HETB(RU), EHTTB(RU) and the default sat ID is "888").
7. Click the "Start RX" button to receive WIFI packets.
8. Enable the WIFI signal generator to transmit packets. Click the "Stop RX" button to stop receiving.
9. Successful received packets number will be shown in the "RX OK” area and RSSI shown in the "inst RSSI IB 0" area.
10. Users can click the "Reset counter" button to reset the counter value.

Description of QA-Tool RX settings (2 stream): A screenshot similar to the 1-stream RX example, indicating options for receiving on both TX0/RX0 and TX1/RX1.

2.4 Read, Write E-fuse Table

2.4.1 Read a Value from E-fuse

Users can use QA-Tool to read a value from an address offset of E-fuse.

On the EEPROM page:

1. In E-fuse Mode, EEPROM Type is "E-fuse".
2. Select Single Read/Write as "READ".
3. Set the address offset in the "Offset" text box, then click the "R/W" button. The value of the assigned address offset will be shown in the "Value" text box.

Description of E-fuse read operation: A screenshot of the QA-Tool's EEPROM page in E-fuse mode, showing 'EEPROM Type: E-fuse', 'Single Read/Write Mode: READ', 'Offset' and 'Value' fields, and the 'R/W' button. Below this, a hex dump of the E-fuse data is displayed.

2.4.2 Write a Value to E-fuse

Users can use QA-Tool to write a value to an address offset of E-fuse.

On the EEPROM page:

1. In E-fuse Mode, EEPROM Type is "E-fuse".
2. Select Single Read/Write mode as "WRITE".
3. Set the address offset and new value in the "Offset" and "Value" text boxes, then click the "R/W" button.
4. Click the "Read ALL" button to update the e-fuse value in the e-fuse table and check it.

Description of E-fuse write operation: A screenshot similar to the read operation, but with 'Single Read/Write Mode' set to 'WRITE', and example values entered in 'Offset' and 'Value' fields. The 'Read ALL' button is also visible.

2.5 Homologation suggest setting

1. Normal Test item: We suggest Packet lengths use 512 Byte.

Description of Normal Test item settings: A screenshot showing QA-Tool TX settings with 'MPDU Tx Length' and 'Packet Tx Time' set to 512.

2. SAR test item: We suggest using HWTX, and adjust packet lengths so that the duty cycle meets test conditions (duty 85%).

Description of SAR test item settings: A screenshot showing QA-Tool TX settings with 'HWTX' checked and 'MPDU Tx Length' and 'Packet Tx Time' set to 512.

2.6 RU Setting example

RU index setting under QA Tool.

Description of RU Index diagram: A visual representation showing different RU sizes mapped to indices across various bandwidths (BW20, BW40, BW80, BW160), with segments indicated.

Ex: RU Index 61 Can be found at RU242 1st ROW.

Description of RU setting interface example: A screenshot showing the QA-Tool's RU setting interface populated with example data for RU242, including 'Select Band', 'Category', 'Allocation (binary)', 'Sta ID', 'RU Index' (set to 61), 'MCS', 'Nss', 'LDPC', 'Stream Idx', and 'Length'.

3 General Information & Integration Instructions

3.1 General Description of MT7927

Channel counts for 5GHz and 6GHz bands, and TX power levels for different bands and modes are detailed in the following text:

U-NII-1: 802.11a, 802.11n (HT20), 802.11ac (VHT20), 802.11ax (HE20), 802.11be (EHT20): 4 channels; 802.11n (HT40), 802.11ac (VHT40), 802.11ax (HE40), 802.11be (EHT40): 2 channels; 802.11ac (VHT80), 802.11ax (HE80), 802.11be (EHT80): 1 channel.

U-NII-2A: 802.11a, 802.11n (HT20), 802.11ac (VHT20), 802.11ax (HE20): 4 channels; 802.11n (HT40), 802.11ac (VHT40), 802.11ax (HE40): 2 channels; 802.11ac (VHT80), 802.11ax (HE80): 1 channel; 802.11ac (VHT160), 802.11ax (HE160): 1 channel.

U-NII-2C: 802.11a, 802.11n (HT20), 802.11ac (VHT20), 802.11ax (HE20): 12 channels; 802.11n (HT40), 802.11ac (VHT40), 802.11ax (HE40): 6 channels; 802.11ac (VHT80), 802.11ax (HE80): 3 channels; 802.11ac (VHT160), 802.11ax (HE160): 1 channel.

U-NII-3: 802.11a, 802.11n (HT20), 802.11ac (VHT20), 802.11ax (HE20), 802.11be (EHT20): 5 channels; 802.11n (HT40), 802.11ac (VHT40), 802.11ax (HE40), 802.11be (EHT40): 2 channels; 802.11ac (VHT80), 802.11ax (HE80), 802.11be (EHT80): 1 channel.

For 1TX:

5.955~6.425GHz: 65.163 mW (EIRP: 22.9 dBm / 194.984 mW)

6.425~6.525GHz: 33.806 mW (EIRP: 19.58 dBm / 90.782 mW)

6.525~6.855GHz: 68.077 mW (EIRP: 22.94 dBm / 196.789 mW)

6.875~7.115GHz: 69.663 mW (EIRP: 22.52 dBm / 178.649 mW)

For 2TX:

5.955~6.425GHz: 65.66 mW (EIRP: 22.93 dBm / 196.336 mW)

6.425~6.525GHz: 35.177 mW (EIRP: 20.22 dBm / 105.196 mW)

6.525~6.855GHz: 68.169 mW (EIRP: 22.95 dBm / 197.242 mW)

6.875~7.115GHz: 69.78 mW (EIRP: 22.53 dBm / 179.061 mW)

3.2 Antenna information

The antennas mentioned below are covered in the certification scope and the HOST can only be used with the following antennas:

Note1: Use of other antenna types or the same type of antenna with higher gain than listed above must be performed additional testing and appropriate permissive change approval.

Note2: In the 5.955-7.115GHz band, use of other similar type antennas and the antenna gain not higher/lower than listed above may only require a C1PC without any additional testing/submission.

Note3: Additional testing/submission (C2PC) will be required if the device does not meet the antenna and RF exposure requirements.

Note4: Contact MediaTek for additional guidance if choosing to use different antenna types or higher/lower gain antennas in the end system.

IMPORTANT: The final host product must have an integral antenna that is not removable by the end-user.

Note4: Antenna Set No 2 and 3 were certified with this device for UNII 5 – 8 operation.

Contact info for above certified antennas:

Company/Dept.: Walsin Technology Corp./ Antenna Business Dept.

Contact window: Andrew Lin

Tel: +886-3-475-8711 # 8172

Cell phone: +886-938-286-596

Email address: andrewlin@passivecomponent.com

URL link: http://www.passivecomponent.com/zh-hant/products/antenna/

3.3 Host Integration instructions

The product is designed to be used with the “NGFF (Next Generation Form Factor) M.2 2230” PCIE Bus. Please install the module into an M.2 2230 PCIE slot.

Description of module installation: An image showing an M.2 2230 module being inserted into an M.2 slot on a motherboard, with an orange arrow indicating the insertion direction.

3.4 Host product testing guidance

The HOST must follow the specific restrictions listed in the “3.5 Regulatory notes” section below and section 3 of KDB996369 D04 V02 Module Integration Guide v01, to verify that the host product meets all applicable rules.

3.5 FCC regulation requirements / installation restrictions

RF Software restrictions (Implement by MTK)

1. Contention-Based Protocol, as demonstrated in the FCC test report, is permanently embedded in the module and is not host-dependent; it cannot be changed by anyone.
2. This Modular device will only associate and connect with a low-power indoor access point or subordinate device and will never directly connect to other client devices. This feature is included in its firmware and cannot be changed by anyone.
3. This Modular device will always initiate transmission under the control of a low-power indoor AP or subordinate, except for brief transmissions before joining a network. These short messages will only occur if the client has detected an indoor AP or subordinate operating on a channel. These brief messages will have a time-out mechanism such that if it does not receive a response from an AP, it will not continually repeat the request.
4. Transmissions will be lower than or equal to the power advertised by the indoor low-power access point or subordinate and never above the maximum output power allowed by the FCC grant for equipment class 6XD.

This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.

This device meets all other requirements specified in Part 15E, Section 15.407 of the FCC Rules.

Radiation Exposure Statement:

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with a minimum distance of 20cm between the radiator and your body.

Installation restrictions

When using and installing this modular device, it is prohibited for control of or communications with unmanned aircraft systems, including drones.

Federal Communication Commission Interference Statement

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.

FCC Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment.

FCC Part 15 Subpart B disclaimer

This transmitter module is tested as a subsystem and its certification does not cover the FCC Part 15 Subpart B (unintentional radiator) rule requirement applicable to the final host. The final host will still need to be reassessed for compliance with this portion of rule requirements if applicable.

As long as all conditions above are met, further transmitter test will not be required. However, the OEM integrator is still responsible for testing their end-product for any additional compliance requirements required with this module installed.

IMPORTANT NOTE: In the event that these conditions cannot be met (for example, certain laptop configurations or co-location with another transmitter), then the FCC authorization is no longer considered valid, and the FCC ID cannot be used on the final product. In these circumstances, the OEM integrator will be responsible for re-evaluating the end product (including the transmitter) and obtaining a separate FCC authorization.

Manual Information To the End User

The OEM integrator must be aware not to provide information to the end user regarding how to install or remove this RF module in the user's manual of the end product which integrates this module.

The end user manual shall include all required regulatory information/warning as shown in this manual.

OEM/Host manufacturer responsibilities

OEM/Host manufacturers are ultimately responsible for the compliance of the Host and Module. The final product must be reassessed against all the essential requirements of the FCC rule, such as FCC Part 15 Subpart B, before it can be placed on the US market. This includes reassessing the transmitter module for compliance with the Radio and EMF essential requirements of the FCC rules. This module must not be incorporated into any other device or system without retesting for compliance as multi-radio and combined equipment.

Modules: extended to host manufacturers by integration instructions.