Thanks Marcus.
Following up on the rx_time format, I notice from the link that the
timestamp format is the same as uhd::time_spec_t . Therefore the timestamp
printed out on a tag is of the form: full_seconds and a fractional_seconds.
For e.g., I see: Offset: 667 Source: n/a Key: rx_time
Hi Avinash,
that's pretty much a basic OFDM question:
You take the DFT of the input signal. Hence, the bins of the DFT are
f_nyquist/l_fft spaced.
Best regards,
Marcus
On 17.06.2016 17:57, avinash kalyanaraman wrote:
> Thanks Marcus - that helps.
>
> Could you please let me know what's the
Thanks Marcus - that helps.
Could you please let me know what's the bandwidth of each sub-carrier? How
can I calculate that and reconfigure the same?
On Sat, Jun 18, 2016 at 12:50 AM, Marcus Müller
wrote:
> Hi Avinash,
>
> On 06/16/2016 03:29 PM, avinash kalyanaraman
Hi Avinash,
On 06/16/2016 03:29 PM, avinash kalyanaraman wrote:
> i) These 64 complex values (a + ib) represent the 64 sub-carriers and
> I can get the amplitude and phase of each sub-carrier as sqrt( a^2 +
> b^2) and arctan(b/a) respectively ?
Yes.
>
> ii) I see that the CSI calculation is per
Hi Marcus,
Thanks for the email. I connected the debug tag to OFDM Channel Estimation
and noted that the ofdm_sync_chan_taps key has 64 complex values.
Could you please confirm the following two things ?
i) These 64 complex values (a + ib) represent the 64 sub-carriers and I can
get the
Hi Avinash,
when you attach a "tag debug" after the "ofdm channel estimation" block,
you'll see stream tags containing CSI estimates flying by.
For more information on stream tags and how to handle them, I'd refer
you to the Guided Tutorials [1], chapter 1-5.
Best regards,
Marcus
[1]