As a quick followup to my previous post, I confirm that the R820T is well
suited for GPS
signal decoding. I was not expecting the huge frequency offset ( 100 kHz at
1.57 GHz) and
was not searching far enough from the expected carrier frequency during the
acquisition phase.
However these results
On 03/28/2015 10:23 AM, jean-michel.fri...@femto-st.fr wrote:
As a quick followup to my previous post, I confirm that the R820T is well
suited for GPS
signal decoding. I was not expecting the huge frequency offset ( 100 kHz at
1.57 GHz) and
was not searching far enough from the expected
On 03/28/2015 10:56 AM, jmfriedt wrote:
well I have been *extremely* lucky then because I have been running 48 hours of
monitoring GPS
signals by recording one second every 5 minutes
(http://jmfriedt.sequanux.org/gps.avi, X axis
is the PRN number and Y axis is the frequency offset) and have
On 03/28/2015 11:29 AM, jan-michel.fri...@femto-st.fr wrote:
this is very confusing ... it works. I did upgrade yesterday from gnuradio
3.7.3 to 3.7.5, but
surely enough both osmocom_fft -f 1575.420e6 -g 30 and a basic flowgraph from
gnuradio-companion
using a 2 MHz sampling rate, osmocom
Your results are consistent with what I've heard about the R820T above
1500MHz or so. It starts to become
deaf, and then as you move higher, the PLL won't lock at all.
I loose 10 dB sensitivity from 1.50 GHz to 1.575 GHz ! At 1.5 GHz the R820T was
more sensitive
than the E4k, but now
As briefly mentioned on the #gnuradio IRC mailing list, I am facing an issue
with tuning a R820T
channel
[...]
I have completed the following experiment:
* a frequency synthesizer (Rohde
