From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 27 05:16:10 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49543106564A; Mon, 27 Aug 2012 05:16:10 +0000 (UTC) (envelope-from prvs=57989d424=Brett.Wright@cooperindustries.com) Received: from cooperlighting-sw.cooperlighting.com (cooperlighting-sw.cooperlighting.com [216.130.131.68]) by mx1.freebsd.org (Postfix) with ESMTP id E21608FC08; Mon, 27 Aug 2012 05:16:09 +0000 (UTC) Authentication-Results: cooperlighting-sw.cooperlighting.com; dkim=neutral (message not signed) header.i=none X-IronPort-AV: E=Sophos;i="4.80,318,1344225600"; d="scan'208";a="66681003" Received: from cipt0175.nam.ci.root ([10.132.108.175]) by cooperlighting-sw.cooperlighting.com with ESMTP; 27 Aug 2012 01:16:03 -0400 Received: from APEVS1.AP.CI.ROOT ([10.180.2.22]) by cipt0175.NAM.CI.ROOT with Microsoft SMTPSVC(6.0.3790.4675); Mon, 27 Aug 2012 01:16:03 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 27 Aug 2012 13:14:37 +0800 Message-ID: <475A4E02EFF4724A9E58F55A56AC131606692EA4@APEVS1.ap.ci.root> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Atheros DFS radar detection Thread-Index: Ac2CISqsTQn/49MoRlKEHsg1PqQ+SwB7055g References: <475A4E02EFF4724A9E58F55A56AC13160641D618@APEVS1.ap.ci.root><475A4E02EFF4724A9E58F55A56AC13160661E6AC@APEVS1.ap.ci.root><475A4E02EFF4724A9E58F55A56AC13160661F137@APEVS1.ap.ci.root><475A4E02EFF4724A9E58F55A56AC131606667F85@APEVS1.ap.ci.root> From: "Wright, Brett" To: "Adrian Chadd" X-OriginalArrivalTime: 27 Aug 2012 05:16:03.0311 (UTC) FILETIME=[0DB95FF0:01CD8413] Cc: freebsd-wireless@freebsd.org, Kim Culhan Subject: RE: Atheros DFS radar detection X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Aug 2012 05:16:10 -0000 Hi Adrian, > -----Original Message----- > From: adrian.chadd@gmail.com [mailto:adrian.chadd@gmail.com] On Behalf > Of Adrian Chadd > Sent: Saturday, 25 August 2012 3:52 AM >=20 > I haven't yet sat down and done actual radar pulse train detection > with the AR5212 and I know it's just going to plain suck at doing > chirps in a busy environment (as they just look like long pulses; > there's no FFT data to assist the software in decoding what's going > on) but it should be enough to get you started. >=20 That might be half my problem, the radar patterns I have to setup to get compliant detection increase the chance of false radar train detection (in combination with the false pulse detection). Reducing this false pulse detection has been the biggest help. If I tinker too much with the radar patterns I can't get compliant detection. > Have you tried these NICs on different hardware? I wonder if you're > seeing some kind of spur or board noise that's contributing to both > the false detections and the high noise floor calibration value. I > don't have an SR-5 here to test against I'm afraid.. >=20 I haven't tried other hardware because I'm working on an existing hardware platform where I have to use SR5 (mainly for the high Tx power etc). But makes sense that the SR5 is making this whole process more difficult... Thanks for all the help. Brett