From: Gui Iribarren <gui@altermundi.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Realtime plot of Spectral Scan in ath9k
Date: Fri, 26 Jul 2013 15:26:52 -0300 [thread overview]
Message-ID: <51F2BF6C.4020003@altermundi.net> (raw)
In-Reply-To: <51F2A14A.2020809@altermundi.net>
On 07/26/2013 01:18 PM, Gui Iribarren wrote:
> On 07/25/2013 04:54 PM, Adrian Chadd wrote:
>> Cool!
>>
>
> Gabriel Tolon has various measurement equipment, so i hope with this
> visualization he'll be able to better calibrate or find
> misintepretations of the source data :D
Ahh, already enjoying this! Baby steps so far, but already answering my
own questions about why the data plots the way it is... :)
While trying to visualize a transfer on channel 1, i can see perfectly
the "ladder" on neighbouring channels, but an unexplainable low sampling
on the actual channel 1.
Turns out, the FFT is done only when the radio is idle; that is, not
receiving or sending packets;
Felix told me about that back in April,
and Adrian clearly states in
https://wiki.freebsd.org/dev/ath_hal%284%29/SpectralScan
"either spectral scan FFT reporting can run, OR packet
transmission/reception"
(+1 Insightful)
but seeing it live, is a whole another thing :D
http://tinypic.com/r/16bld2r/5
now it's pretty clear that when radio is tuned to (say) channel 2, it
can't decode the packets and only sees a very intense "noise" (i.e part
of the neighbouring transmission).
but when it's on channel 1, it can fully decode the packets (even though
they're destinated for someone else) and during that time no FFTs are made.
So, what are the few samples you can see on channel 1?
Well, either A) silent instants along the transfer, or B) partial
transmissions, but in terms of time; i.e. the radio tuned into 2412 in
the middle of an ongoing packet, and since it lost half of it, can't
decode it and samples the "tail" of the packet as a mildly intense "noise".
Cheers!
next prev parent reply other threads:[~2013-07-26 18:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 15:50 [ath9k-devel] Spectral Scan in ath9k Saulo Queiroz
2012-03-24 22:53 ` Adrian Chadd
2012-05-30 10:25 ` Alex Hacker
2012-05-31 10:58 ` Saulo Queiroz
2012-05-31 13:27 ` Alex Hacker
2012-05-31 14:48 ` abhinav narain
2012-05-31 19:19 ` Adrian Chadd
2012-06-01 3:01 ` Peizhao Hu
2012-06-01 14:10 ` Adrian Chadd
2012-06-01 8:57 ` Alex Hacker
2013-05-08 16:15 ` Claudio
2013-05-08 17:50 ` Oleksij Rempel
2013-06-10 15:15 ` Gui Iribarren
2013-07-25 13:43 ` [ath9k-devel] Realtime plot of " Gui Iribarren
2013-07-25 19:54 ` Adrian Chadd
2013-07-26 16:18 ` Gui Iribarren
2013-07-26 18:26 ` Gui Iribarren [this message]
2013-07-26 21:18 ` Adrian Chadd
2013-07-28 7:29 ` Gui Iribarren
2013-07-28 17:52 ` Adrian Chadd
2013-07-30 12:12 ` Michal Kazior
2013-07-25 20:24 ` [ath9k-devel] Measurements with " Gabriel Tolón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F2BF6C.4020003@altermundi.net \
--to=gui@altermundi.net \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.