Re: [Discuss-gnuradio] multi-rtl phase synchronization

[Juha Vierinen]

Thanks for the informative post. I've been searching for a way to turn off
the dithering.

The I/Q plot show complex cross-correlation between two noise signals at
100 MHz center frequency (2.4 MHz bandwidth noise). The phase of the signal
can be converted into time and Allan deviation, but I never did. I was just
happy to see a straight line.

juha

On Fri, Jul 7, 2017 at 08:05 jmfriedt 
wrote:

> I am tackling again the coherence issue with multi-RTL dongles for
> interferometric measurements.
> I have two R820T2 based DVB-T dongles connected to the same USB bus (USB
> hub) and am feeding
> both dongles with a high quality 100-MHz source (-34 dBm output of a
> Rohde&Schwarz SML03 synthesizer,
> 30 dB gain on the RF frontend of the dongles) -- setup shown at
> http://jmfriedt.sequanux.org/DSC06032.JPG.
>
> I am trying to reproduce the graph "IQ plot of the z_1/z_2 relative phase
> signal over ~6000 seconds at
> 1 Hz sample rate" from
> http://kaira.sgo.fi/2013/09/16-dual-channel-coherent-digital.html
> Actually I notice that this graph shows something in units in the tens of
> thousands: what is
> "Z1/Z2 relative phase" ? How can I convert this axis to angle in degrees ?
>
> I have manually applied the patch described at
> http://www.rtl-sdr.com/forum/viewtopic.php?f=1&t=531 to
> turn off dithering (I have checked that the function is called when
> starting gr-osmosdr -- whether
> dithering is actually disabled is challenging to assess). The resulting
> phase measurement -- recording
> either with multi-rtl source or two osmosdr sources, multiplying one
> output by the complex conjugate
> of the other, complex to phase and saving the resulting phase at 200 Hz
> rate, is at
> http://jmfriedt.sequanux.org/allan.pdf (left is time domain plot, right
> is Allan deviation). On the
> short term we have sub-degree stability, on the long term several degree
> drift. I have checked that
> thermal transfer between the two dongles is of utmost importance: if I
> cool one of the dongles and keep
> the other at room temperature, I observe phase rotations of several tens
> of degrees. I believe such
> long term phase instability is of little concern for passive radar
> measurements where coherence over
> several ms only is needed, but I find conflicting conclusions on long term
> phase stability.
>
> Can other experimenters on this topic comment and assess whether
> http://jmfriedt.sequanux.org/allan.pdf
> can be improved, or if is in line with the expected behaviour of these
> dongles ?
>
> Thanks, Jean-Michel
>
> --
> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe, 25000
> Besancon, France
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC 17] DAB: Updates

[Moritz Luca Schmid]

Hi everyone,

this week I dealt with the mp4 decoder for my DAB receiver.

I still got issues with the Reed Solomon error repair, but I hope that 
the gr-dab module will soon be playing some nice music!


In my latest blog post  are 
further details about my latest work.



Best

Luca

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

Re: [Discuss-gnuradio] multi-rtl phase synchronization

[jmfriedt]

> The I/Q plot show complex cross-correlation between two noise signals at
> 100 MHz center frequency (2.4 MHz bandwidth noise). The phase of the signal
> can be converted into time and Allan deviation, but I never did. I was just
> happy to see a straight line.

I continued the measurement this morning after having the temperature of the 
dongles 
stabilized overnight: I gain a factor 10 stability on a 2 hour measurement: 
http://jmfriedt.sequanux.org/3allan.pdf

Actually I just discovered something fascinating: I was contemplating which 
radio
source would be best suited for the passive radar experiment. Not being able to
find any suitable source while scanning the environment with a yagi antenna, I 
decided
to tune to the 143.05 MHz frequency of the GRAVES [1] bistatic emitter which 
happens not to
be too far away. To my great surprise, after replacing the quartz (drifting far 
too much)
with a hydrogen maser referenced synthesized tuned to 28.8 MHz, I get amazing 
doppler
shifted traces of reflectors between the emitter and my receiver. I didn't 
expect
such a low quality receiver to be able to extract this signal: example of a 
waterfall trace
at http://jmfriedt.sequanux.org/graves.pdf

JM

[1] https://en.wikipedia.org/wiki/Graves_%28system%29

-- 
JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe,
25000 Besancon, France

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

[Discuss-gnuradio] TUNTAP PDU with rds example

[Markley da Silva Mendes]

Hi all,

I would like to know if there is any example where I have captured the data
rds (radio data sistem), using an RTL-2832u, and transformed into ethernet
frames using the TUNTAP PDU block? And if there is any documentation
explaining how I can use the TUNTAP PDU block with other technologies
(zigbee, bluetooth, zWave ...)?

Best Regards,

Markley
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] [GSoC 2017] gr-bokehgui: Updates week 8

[Kartik Patel]

Hello all,

This week I tried to integrate base sink to the remaining sinks. Solving
the issues of it kept me busy this week. For more details, check out my
blog here .

Regards,
Kartik Patel
ᐧ
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] gr-scan fine window and coarse window bandwidth

[GNUBeginner]

Hello,

Could anyone please tell me what fine window and coarse window bandwidth are
in gr-scan program?

Thanks



--
View this message in context: 
http://gnuradio.4.n7.nabble.com/gr-scan-fine-window-and-coarse-window-bandwidth-tp64509.html
Sent from the GnuRadio mailing list archive at Nabble.com.

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

Re: [Discuss-gnuradio] gr-scan fine window and coarse window bandwidth

[Marcus Müller]

Dear GNU Beginner,

the source code can.

Also, I've told you multiple times to please stop using Nabble.

Respectfully,

Marcus


On 07.07.2017 21:25, GNUBeginner wrote:
> Hello,
>
> Could anyone please tell me what fine window and coarse window bandwidth are
> in gr-scan program?
>
> Thanks
>
>
>
> --
> View this message in context: 
> http://gnuradio.4.n7.nabble.com/gr-scan-fine-window-and-coarse-window-bandwidth-tp64509.html
> Sent from the GnuRadio mailing list archive at Nabble.com.
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


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

Re: [Discuss-gnuradio] gr-scan fine window and coarse window bandwidth

[GNUBeginner]

Dear Marcus,

I do apologize that I do not know what nabble is. I subscribed this mailing
list using my e-mail address.

I truly appreciate your help to understand what gr-scan does. I have been
reviewing the source code and do not understand what these fine and coarse
window bandwidth options are.

Best



--
View this message in context: 
http://gnuradio.4.n7.nabble.com/gr-scan-fine-window-and-coarse-window-bandwidth-tp64509p64511.html
Sent from the GnuRadio mailing list archive at Nabble.com.

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

Re: [Discuss-gnuradio] gr-scan fine window and coarse window bandwidth

[Marcus Müller]

Hi GNU Beginner,

we might be misunderstanding each other.

Nabble is the website you're using. Look at the address bar; the actual
mailing list is something you get directly delivered via email, and
posting there, unlike Nabble, doesn't add lines like the following

View this message in context: http://gnuradio.4.n7.nabble.com/…

to each and every message, and more importantly, the Nabble website just
acts like a subscriber to the mailing list and displays the mails as if
they were a web forum. They're not. They're emails in threads, and you
can have trees (in the graph theory sense of "tree") of discussions.
Nabble users are known to miss useful answers to their questions, simply
because the linear forum shape doesn't reflect the multiple branches an
email discussion can take. That's the only reason I strongly advertise
*against* using Nabble – it makes the mailing list *less* usable for
you, and more ugly for us.

Best regards,
Marcus

On 07.07.2017 21:52, GNUBeginner wrote:
> Dear Marcus,
>
> I do apologize that I do not know what nabble is. I subscribed this mailing
> list using my e-mail address.
>
> I truly appreciate your help to understand what gr-scan does. I have been
> reviewing the source code and do not understand what these fine and coarse
> window bandwidth options are.
>
> Best
>
>
>
> --
> View this message in context: 
> http://gnuradio.4.n7.nabble.com/gr-scan-fine-window-and-coarse-window-bandwidth-tp64509p64511.html
> Sent from the GnuRadio mailing list archive at Nabble.com.
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


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

Re: [Discuss-gnuradio] gr-scan fine window and coarse window bandwidth

[GNUBeginner]

Dear Marcus,

Finally, I now know what you have been talking about. Thank you so much for
the clarification.

Could you please help me understand the gr-scan code, fine and coarse window
bandwidth, threshold, etc options and how this code could be utilized for
scanning 2.4 GHz band in a detailed explanation before I stop using nabble?  
:-)

I would truly appreciate your guidance.

Best,



--
View this message in context: 
http://gnuradio.4.n7.nabble.com/gr-scan-fine-window-and-coarse-window-bandwidth-tp64509p64513.html
Sent from the GnuRadio mailing list archive at Nabble.com.

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

Re: [Discuss-gnuradio] gr-scan fine window and coarse window bandwidth

[Marcus Müller]

No. Stop using Nabble. It's easy to sign up to the mailing list directly:

https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Best regards,
Marcus

On 07.07.2017 22:08, GNUBeginner wrote:
> Dear Marcus,
>
> Finally, I now know what you have been talking about. Thank you so much for
> the clarification.
>
> Could you please help me understand the gr-scan code, fine and coarse window
> bandwidth, threshold, etc options and how this code could be utilized for
> scanning 2.4 GHz band in a detailed explanation before I stop using nabble?  
> :-)
>
> I would truly appreciate your guidance.
>
> Best,
>
>
>
> --
> View this message in context: 
> http://gnuradio.4.n7.nabble.com/gr-scan-fine-window-and-coarse-window-bandwidth-tp64509p64513.html
> Sent from the GnuRadio mailing list archive at Nabble.com.
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


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

Re: [Discuss-gnuradio] gr-scan fine window and coarse window bandwidth

[GNUBeginner]

Hello Marcus,

This is what I have been trying to tell you...I am already subscribed to the
mailing list. Please see below:

An attempt was made to subscribe your address to the mailing list
discuss-gnuradio@gnu.org.  You are already subscribed to this mailing list.

Note that the list membership is not public, so it is possible that a bad
person was trying to probe the list for its membership.  This would be a
privacy violation if we let them do this, but we didn't.

If you submitted the subscription request and forgot that you were already
subscribed to the list, then you can ignore this message.  If you suspect
that
an attempt is being made to covertly discover whether you are a member of
this
list, and you are worried about your privacy, then feel free to send a
message
to the list administrator at discuss-gnuradio-ow...@gnu.org.



--
View this message in context: 
http://gnuradio.4.n7.nabble.com/gr-scan-fine-window-and-coarse-window-bandwidth-tp64509p64515.html
Sent from the GnuRadio mailing list archive at Nabble.com.

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

Re: [Discuss-gnuradio] gr-scan fine window and coarse window bandwidth

[Cinaed Simson]

On 07/07/2017 01:20 PM, GNUBeginner wrote:
> Hello Marcus,
> 
> This is what I have been trying to tell you...I am already subscribed to the
> mailing list. Please see below:
> 
> An attempt was made to subscribe your address to the mailing list
> discuss-gnuradio@gnu.org.  You are already subscribed to this mailing list.

Unsubscribe from the list in the same manner as you subscribed.

Wait for a little while then go to this URL

  https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

and re-subscribe.

If you have any trouble changing your subscription, send email to
administrators - their emails are on the bottom of the above URL.

-- Cinaed



> 
> Note that the list membership is not public, so it is possible that a bad
> person was trying to probe the list for its membership.  This would be a
> privacy violation if we let them do this, but we didn't.
> 
> If you submitted the subscription request and forgot that you were already
> subscribed to the list, then you can ignore this message.  If you suspect
> that
> an attempt is being made to covertly discover whether you are a member of
> this
> list, and you are worried about your privacy, then feel free to send a
> message
> to the list administrator at discuss-gnuradio-ow...@gnu.org.
> 
> 
> 
> --
> View this message in context: 
> http://gnuradio.4.n7.nabble.com/gr-scan-fine-window-and-coarse-window-bandwidth-tp64509p64515.html
> Sent from the GnuRadio mailing list archive at Nabble.com.
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 


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

Re: [Discuss-gnuradio] [GSoC 2017] gr-bokehgui: Updates week 8

[Martin Braun]

On 07/07/2017 10:49 AM, Kartik Patel wrote:
> Hello all,
> 
> This week I tried to integrate base sink to the remaining sinks. Solving
> the issues of it kept me busy this week. For more details, check out my
> blog here .

Kartik,

thanks a lot for your updates. As a suggestion for your next blog post:
Could you add a screencast (YT video for example) of how the entire
thing looks like? It's a bit of a hurdle to run the modified GR branches
etc. for some people.

Cheers,
Martin

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

Re: [Discuss-gnuradio] Decoding 2FSK Compensating for carrier jitter/skewing (CFO)

[Cinaed Simson]

On 07/07/2017 09:50 AM, HLL wrote:
> Hi all,
> 
> I'm relatively new to DSP and gnuradio but I tried tons of stuff and I
> couldn't decode a fairly simple FSK data.
> baudrate seems around 600-700 bps and fsk deviation is less then 3k.

Take a look at

  inspectrum - Offline radio signal analyser

  https://github.com/miek/inspectrum

> 
> As I understand, in order to properly decode this transmission i need
> for frequency to be oscillating around the center freq (i.e. 0) so that
> "Quadrature demod" block output would look nice and pretty much
> symmetrical (-1 1 edges).
> Note: I Know sometimes I can get away with signal that is not properly
> aligned, but I even tried my own python script to search zero crossing,
> CFO makes it impossible to detect zero crossing in timely manner.
> 
> I've recorded around 6 samples of the signal, in all of them the signal
> starts off ok, and then later on, sometimes, the carrier drifts, up to
> the point where it (quadrature demod) even does not cross zero (see pic)
> and sometimes, the jitter (CFO?) is even worse then that.
> I Understood that I needed to compensate for the carrier drift using a
> PLL that would keep the carrier frequancy centered, for this I have
> these next tools to my disposal :
> 1. PLL Ref out - Outputs a sinusoidal whose phase and freq are "/what
> the PLL think is the carrier freq/"
> 2. PLL Freq det -  PLL Ref out + quadrature demod, I.E. the center
> frequency value.
> 3. PLL Carrier tracking -  input signal shifted by "PLL Freq det" hz. -
> I.E. Compensates for the CFO and centers the signal.
> 
> I Guess that the min max are the absolute limits of the carrier freq, so
> this is a symmetrical value around 0. The loop bandwidth controls the
> relation between what is considered a CFO and an actual FSK data.
> The higher the BW, the faster the loop adapts to the new frequency and
> centers it, rendering the current freq to 0. hence, if it's an actual
> FSK data, and the loop considers it as noise, it would be zero out.
> The lower BW, the slower the loop adapts to new frequency and loop will
> not compensate for the frequency jitter, and when passed on to
> quadrature demod, outputs a erroneous signal that either falsely cross
> zero or doesn't cross at all or at wrong timings. as I mentioned, some
> of the CFO Jitter starts off very fast and then revert to normal slowly
> (see that pic again)
> 
> I Tried tons of different configuration, and I couldn't get the carrier
> frequency in the center of the quadrature demodulation block's output
> (before compensation).
> In visual analysis, it takes a fraction of a seconds to deduce the highs
> and lows, how can one automate this? I have no clue where to begin.
>  
> Example of what jitter i'm talking about, a specific configuration PLL
> freq det is in red, while quad demod (gain 1) is in blue
> 
> ​
> And this is the graph that used to take the screenshots
> I Did tried, of course multiple configurations for the PLL. 
> ​
> Question time:
> 1. Am I doing something wrong? how can I extract the data that is
> obviously there and get the bits? sure there can be occasional noise but
> I tried multiple times to get a very clean capture and I wasn't able to, 
> 2. Can the transition width (I.E. the `speed` of transition between high
> to low), the difference between high and low (FSK deviation) or other
> information could be Incorporated to enhance demodulation [both of which
> seems pretty much constant throughout transmission] ? How?
> 3. This is probably asked in the past, and I looked it up and wasn't
> able to come to a conclusion, How can I decode manchester in gnuradio?
> 
> The source, 8khz sample rate, 32 bit float I/Q captured,roughly centered
> is attached to this mail
> 
> 
> Some extra information:
> -I Only have access to trigger communication of the device.
> -All captures taken from very close proximity (~10 cm) the device is
> intended to work over hundreds of meters outdoors
> -I Have access to FCC docs, but since I don't live in the US, *I'm not
> sure what actual* "primary" *freq* of the device is.

Try looking up the FCC Id at

  https://fcc.io/

Would you post the FCC Id? If I have the FCC id I may play with it when
while I'm commuting.


 I might be picking
> up some sideband noise (if that's the proper definition, you know, when
> a signal also mirrors itself with decreasing attenuations across some
> wide band). The vendor is also able to configure the device freq, to
> some extent..
> -Data looks like manchester encoding since there are no long lows or
> highs. also it starts off with a sync of high freq low freq "long"
> repeating, which under Manchester is 010101... 
> 
> Thanks for the help
> HLL.
> 
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gn

Re: [Discuss-gnuradio] TUNTAP PDU with rds example

[Cinaed Simson]

On 07/07/2017 10:06 AM, Markley da Silva Mendes wrote:
> Hi all,
> 
> I would like to know if there is any example where I have captured the
> data rds (radio data sistem), using an RTL-2832u, and transformed into
> ethernet frames using the TUNTAP PDU block? And if there is any
> documentation explaining how I can use the TUNTAP PDU block with other
> technologies (zigbee, bluetooth, zWave ...)?

Also take a look at the zmq examples in

 /share/gnuradio/examples/zeromq

which uses sockets.

I believe you can use tagged streams with them too - although I haven't
tried it. You can also pass messages.

There's a lot information online too

  http://zeromq.org/intro:read-the-manual

-- Cinaed


> 
> Best Regards,
> 
> Markley
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 


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

Re: [Discuss-gnuradio] [GSoC 2017] gr-bokehgui: Updates week 8

[Kartik Patel]

Hello Martin,
Thank you for the suggestions. I will incorporate the screencast in next
blog.

On 6:20am, Sat 08-Jul-2017 Martin Braun,  wrote:

On 07/07/2017 10:49 AM, Kartik Patel wrote:
> Hello all,
>
> This week I tried to integrate base sink to the remaining sinks. Solving
> the issues of it kept me busy this week. For more details, check out my
> blog here .

Kartik,

thanks a lot for your updates. As a suggestion for your next blog post:
Could you add a screencast (YT video for example) of how the entire
thing looks like? It's a bit of a hurdle to run the modified GR branches
etc. for some people.

Cheers,
Martin

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


-- 

Regards,
Kartik Patel
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio