|
From: | Marcus Müller |
Subject: | Re: [Discuss-gnuradio] Continuously Write FFT Samples to a File |
Date: | Mon, 23 Jan 2017 19:14:12 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
Hi Mallesham, this is one of the cases where capitalization makes a difference: mbps=millibit per second is really not that much, and even 100 Mb/s would still be pretty tolerable, but that would only be a little more than 3 MS/s; what you're referring to is multiple 100 MegaBytes per second, so that doesn't even fit through gigabit ethernet anymore. I want to find the suitable duty cycle parameters for this particular setup with minimal error compared to actual spectrum data."actual spectral data" is the interesting phrase here. Because that isn't actually all that easy to define: Is having a higher rate at which you "revisit" one frequency better than covering a larger overall bandwidth? What is the actual dynamic range that you want to achieve? Are the transmitters you want to observe expected to be active for prolonged periods, or are they only active in short, temporally uncorrelated bursts? What's your metric for how "close" your observation is to the "actual spectral data"? I think you must define that first! Best regards, Marcus On 01/23/2017 06:44 PM, Mallesham
Dasari wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |