DFS Client Declaration-X540BMW r2

FCC ID: ZNFX540HM

Cover Letter(s)

Download: PDF
FCCID_4452257

DFS Client Declaration Letter Date: 2019/09/19 We have declared below featured for device, FCC ID: ZNFX540HM (1) DFS Device Master Client with Radar detection capability Client without radar detection capability (2) Active / Passive Scanning, ad hoc mode access point capability Frequency Scanning Plan Ad Hoc Mode Access point WiFi Direct WiFi Direct Band (MHz) Capability Capability Group Owner Group Client 2412 - 2462 Active Yes Yes Yes Yes 5180 – 5240 Active Yes Yes Yes Yes 5260 – 5320 Passive No No No No 5500 – 5580 Passive No No No No 5660 – 5700 Passive No No No No 5745 - 5825 Active Yes Yes Yes Yes (3) Country code selection capability to end user- Yes, No If yes, please explain how it was implemented: (please also help to provide detail of options for each country selection) (4) Transmission in 5600 MHz to 5650 MHz is notched - Yes, No (5) Meet Part 15.202 requirement - Yes, No A master device is defined as a device operating in a mode in which it has the capability to transmit without receiving an enabling signal. In this mode it is able to select a channel and initiate a network by sending enabling signals to other devices. A client device is defined as a device operating in a mode in which the transmissions of the device are under control of the master. A device in client mode is not able to initiate a network. (6) For client devices that have software configuration control to operate in different modes (active scanning in some and passive scanning in others) in different bands (devices with multiple equipment classes or those that operate on non-DFS frequencies) or modular devices which configure the modes of operations through software, the application must provide software and operations description on how the software and / or hardware is implemented to ensure that proper operations modes cannot be modified by end user or an installer. Apply, Not Apply, (If apply, please help to provide explanation on it was implement, and how V1.0

software was controlled). Signature ____________________________ Printed Name: Position: Company: V1.0


Document Created: 2019-09-20 17:43:14
Document Modified: 2019-09-20 17:43:14
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC