EDA60K-0_Client declaration letter rev2

FCC ID: HD5-EDA60K0

Cover Letter(s)

Download: PDF
FCCID_3731738

Honeywell International Inc Honeywell Sensing & Productivity Solutions 9680 Old Bailes Rd. Fort Mill, SC 29707 United States Client Declaration Letter Date: Jan 21, 2018 FCC ID: HD5—EDAGOKO We have declared below featured for device identified as (1) DFS Device —— O Master, C Client with Radar detection capability , & Client without radar detection capability, O N/A (2) Active / Passive Scanning , ad hoc mode access point capability Frequency Client Ad Hoc Mode Access point WiFi Direct WiFi Direct Band (MHz) Mode capability Capability Group Owner Group Client 2412 — 2462 Yes No No No No 5180 — 5240 Yes No No No No 5260 — 5320 Yes No No No No 5500 — 5720 Yes No No No No 5745 — 5825 Yes No No No No (3) Country code selection capability to end user— J Yes , &¥ No If yes, pis explain how it was implemented: (pls also help to provide detail of options for each country selection) (4) Meet Part 15.202 requirement — M Yes , O No . * 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 can‘t be modified by end user or an installer. O Apply M No Apply (If apply, pis help to provide explanation on it was implement, and how software was controlled). Name: Michael Robinson Position: Product Compliance Honeywell International Inc Honeywell Sensing & Productivity Solutions


Document Created: 2018-01-26 13:18:04
Document Modified: 2018-01-26 13:18:04
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC