discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Internal delays (due to clock path, ...) & jitter


From: Mattia Rizzi
Subject: Re: [Discuss-gnuradio] Internal delays (due to clock path, ...) & jitter, between tx e rx path in USRP 1 device
Date: Fri, 29 Jul 2011 16:35:01 +0200

>Normally, the TX path and RX would only be connected through the host computer software--either "roll your own+UHD" or with,
Gnu Radio.
 
Perphas i’m not well explained. I’m talking about samples that are inside internal buffers of USRP. At time=t0 one sample is acquired and two sample are sent over RF front-end. What i want to know is the temporal disaligment (due to clock path delays, etc) between these two tasks.
Thank you for your response.
 
Sent: Friday, July 29, 2011 3:57 PM
Subject: Re: [Discuss-gnuradio] Internal delays (due to clock path, ...) & jitter, between tx e rx path in USRP 1 device
 
On 29/07/2011 8:42 AM, Mattia Rizzi wrote:
Hello.
Are there some people from Ettus Research?
I have an USRP 1 device.  Since USRP1 has 64Ms/s for RX and 128Ms/s for TX, after 1/64M of second one sample is acquired and two sample are sent over the air. My question is how the time-offset is between these two stream (in % of clock period) and how is the jitter. Thank you.

Normally, the TX path and RX would only be connected through the host computer software--either "roll your own+UHD" or with,
Gnu Radio. So making any kind of statements about latency and jitter would be pretty difficult.

The TX and RX sampling and RF PLL clocks are all slaved to the 64MHz master clock on the USRP1, if that's helpful information.
  But RX-to-TX jitter and latency information is something that is highly, highly, highly, dependent on the host side of things.




_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

reply via email to

[Prev in Thread] Current Thread [Next in Thread]