Thursday, October 31, 2019

Gnuradio for windows

Hi, 

It looks like the link for downloading gnuradio for windows in wiki is broken and the website is down. Is there anywhere other than Pothos that I can download gnuradio binary files for windows? I am having some problems with Pothos UHD drivers and I am trying to stay away from it. 

Regards,
Ali

GNURadio hardware acceleration on Zynq

Hello,

Is there an updated wiki/tutorial about GNURadio hardware acceleration on Zynq?
This one is obsolete:

Any new works/feedback about offloading GR blocks to FPGA?

Thanks.

Best Regards,

Re: How to efficiently implement dechannelization (combine multiple narrowband signals into a single broadband spectrum)

On Mon, Oct 28, 2019 at 10:12 PM Amr Bekhit <amrbekhit@gmail.com> wrote:
I'm working on an SDR project where I need to transmit a narrow
baseband signal on multiple different carriers simultaneously, over a
relatively wide bandwidth (1Mhz). … an external audio
source is then AM modulated and transmitted on several channels …
 
In my case the output channels are arbitrary, …
 
If you do not need precisely selected frequencies and amplitudes, a computationally cheap way to generate many copies of a signal is to multiply the baseband by a carrier signal high in harmonics (such as a square or sawtooth wave). The signal will appear at the frequency (and amplitude) of each harmonic. In order for the spectrum to be otherwise clean, make sure the carrier frequency is an even division of the sample rate.

This is similar to the effect where a signal overloading a SDR receiver will appear duplicated across the received spectrum.

Re: Lunar Orbiting Platform Gateway

Yes - I'm attempting to get a copy of the slides from recent ARISS presentations. There was a diagram with planned frequencies. Plenty to work with. 

-Michelle W5NYV




On Wed, Oct 30, 2019 at 11:57 AM John Malsbury <jmalsbury.personal@gmail.com> wrote:
And you mentioned something about amateur radio portions, Michelle?

On Wed, Oct 30, 2019 at 11:52 AM Kevin K Gifford <kevin.gifford@colorado.edu> wrote:
Hi -

I am involved in recommending the radio communications architecture for Gateway which is baselined to utilize CCSDS (see cases.org) protocols.

For long-haul RF links (Gateway to Earth) Unified Space Link Protocol (USLP).  

For short-haul RF (Gateway to lunar surface): Proximity-1 and AOS

For proximity wireless networks (around Gateway and on lunar surface) 802.11 n/ac baselined, 802.11ax and LTE are under strong consideration.

Please feel free to respond directly if additional information is needed and I'll strive to assist.

Kevin

From: Discuss-gnuradio <discuss-gnuradio-bounces+kevin.gifford=colorado.edu@gnu.org> on behalf of John Malsbury <jmalsbury.personal@gmail.com>
Sent: Wednesday, October 30, 2019 12:34 PM
To: Michelle Thompson <mountain.michelle@gmail.com>
Cc: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
Subject: Re: Lunar Orbiting Platform Gateway
 
It was a cheap joke on my part (and not at all commentary on the gateway concept).  Disregard.

I'd be down to collaborate on something open source.  Could you point to publicly available documents that summarize the standards/specs?  

-John

On Wed, Oct 30, 2019 at 8:50 AM Michelle Thompson <mountain.michelle@gmail.com> wrote:
I was hesitant to ask why, but I'm curious now. 

I know the Gateway is controversial. I understand there's a lot of doubt it will actually happen. The heavy emphasis on commercial activity is another aspect. 

However, I've been asked for help on a receiving station for the amateur radio portions that might be included. There's a lot of overlap between what I do and the type of communications proposed. 

Comment and critique would be very appreciated here. 

-Michelle W5NYV




On Wed, Oct 30, 2019 at 7:14 AM Müller, Marcus (CEL) <mueller@kit.edu> wrote:
Hey John,

> > Anyone working on…
> Definitely not

Does that imply they're finished?

Best regards,
Marcus

Wednesday, October 30, 2019

Re: Lunar Orbiting Platform Gateway

ccsds.org (not cases.org, auto-correct got me)...

Kevin

From: Discuss-gnuradio <discuss-gnuradio-bounces+kevin.gifford=colorado.edu@gnu.org> on behalf of Kevin K Gifford <kevin.gifford@colorado.edu>
Sent: Wednesday, October 30, 2019 12:52 PM
To: John Malsbury <jmalsbury.personal@gmail.com>; Michelle Thompson <mountain.michelle@gmail.com>
Cc: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
Subject: Re: Lunar Orbiting Platform Gateway
 
Hi -

I am involved in recommending the radio communications architecture for Gateway which is baselined to utilize CCSDS (see cases.org) protocols.

For long-haul RF links (Gateway to Earth) Unified Space Link Protocol (USLP).  

For short-haul RF (Gateway to lunar surface): Proximity-1 and AOS

For proximity wireless networks (around Gateway and on lunar surface) 802.11 n/ac baselined, 802.11ax and LTE are under strong consideration.

Please feel free to respond directly if additional information is needed and I'll strive to assist.

Kevin

From: Discuss-gnuradio <discuss-gnuradio-bounces+kevin.gifford=colorado.edu@gnu.org> on behalf of John Malsbury <jmalsbury.personal@gmail.com>
Sent: Wednesday, October 30, 2019 12:34 PM
To: Michelle Thompson <mountain.michelle@gmail.com>
Cc: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
Subject: Re: Lunar Orbiting Platform Gateway
 
It was a cheap joke on my part (and not at all commentary on the gateway concept).  Disregard.

I'd be down to collaborate on something open source.  Could you point to publicly available documents that summarize the standards/specs?  

-John

On Wed, Oct 30, 2019 at 8:50 AM Michelle Thompson <mountain.michelle@gmail.com> wrote:
I was hesitant to ask why, but I'm curious now. 

I know the Gateway is controversial. I understand there's a lot of doubt it will actually happen. The heavy emphasis on commercial activity is another aspect. 

However, I've been asked for help on a receiving station for the amateur radio portions that might be included. There's a lot of overlap between what I do and the type of communications proposed. 

Comment and critique would be very appreciated here. 

-Michelle W5NYV




On Wed, Oct 30, 2019 at 7:14 AM Müller, Marcus (CEL) <mueller@kit.edu> wrote:
Hey John,

> > Anyone working on…
> Definitely not

Does that imply they're finished?

Best regards,
Marcus

Re: Lunar Orbiting Platform Gateway

And you mentioned something about amateur radio portions, Michelle?

On Wed, Oct 30, 2019 at 11:52 AM Kevin K Gifford <kevin.gifford@colorado.edu> wrote:
Hi -

I am involved in recommending the radio communications architecture for Gateway which is baselined to utilize CCSDS (see cases.org) protocols.

For long-haul RF links (Gateway to Earth) Unified Space Link Protocol (USLP).  

For short-haul RF (Gateway to lunar surface): Proximity-1 and AOS

For proximity wireless networks (around Gateway and on lunar surface) 802.11 n/ac baselined, 802.11ax and LTE are under strong consideration.

Please feel free to respond directly if additional information is needed and I'll strive to assist.

Kevin

From: Discuss-gnuradio <discuss-gnuradio-bounces+kevin.gifford=colorado.edu@gnu.org> on behalf of John Malsbury <jmalsbury.personal@gmail.com>
Sent: Wednesday, October 30, 2019 12:34 PM
To: Michelle Thompson <mountain.michelle@gmail.com>
Cc: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
Subject: Re: Lunar Orbiting Platform Gateway
 
It was a cheap joke on my part (and not at all commentary on the gateway concept).  Disregard.

I'd be down to collaborate on something open source.  Could you point to publicly available documents that summarize the standards/specs?  

-John

On Wed, Oct 30, 2019 at 8:50 AM Michelle Thompson <mountain.michelle@gmail.com> wrote:
I was hesitant to ask why, but I'm curious now. 

I know the Gateway is controversial. I understand there's a lot of doubt it will actually happen. The heavy emphasis on commercial activity is another aspect. 

However, I've been asked for help on a receiving station for the amateur radio portions that might be included. There's a lot of overlap between what I do and the type of communications proposed. 

Comment and critique would be very appreciated here. 

-Michelle W5NYV




On Wed, Oct 30, 2019 at 7:14 AM Müller, Marcus (CEL) <mueller@kit.edu> wrote:
Hey John,

> > Anyone working on…
> Definitely not

Does that imply they're finished?

Best regards,
Marcus

Re: Lunar Orbiting Platform Gateway

Hi -

I am involved in recommending the radio communications architecture for Gateway which is baselined to utilize CCSDS (see cases.org) protocols.

For long-haul RF links (Gateway to Earth) Unified Space Link Protocol (USLP).  

For short-haul RF (Gateway to lunar surface): Proximity-1 and AOS

For proximity wireless networks (around Gateway and on lunar surface) 802.11 n/ac baselined, 802.11ax and LTE are under strong consideration.

Please feel free to respond directly if additional information is needed and I'll strive to assist.

Kevin

From: Discuss-gnuradio <discuss-gnuradio-bounces+kevin.gifford=colorado.edu@gnu.org> on behalf of John Malsbury <jmalsbury.personal@gmail.com>
Sent: Wednesday, October 30, 2019 12:34 PM
To: Michelle Thompson <mountain.michelle@gmail.com>
Cc: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
Subject: Re: Lunar Orbiting Platform Gateway
 
It was a cheap joke on my part (and not at all commentary on the gateway concept).  Disregard.

I'd be down to collaborate on something open source.  Could you point to publicly available documents that summarize the standards/specs?  

-John

On Wed, Oct 30, 2019 at 8:50 AM Michelle Thompson <mountain.michelle@gmail.com> wrote:
I was hesitant to ask why, but I'm curious now. 

I know the Gateway is controversial. I understand there's a lot of doubt it will actually happen. The heavy emphasis on commercial activity is another aspect. 

However, I've been asked for help on a receiving station for the amateur radio portions that might be included. There's a lot of overlap between what I do and the type of communications proposed. 

Comment and critique would be very appreciated here. 

-Michelle W5NYV




On Wed, Oct 30, 2019 at 7:14 AM Müller, Marcus (CEL) <mueller@kit.edu> wrote:
Hey John,

> > Anyone working on…
> Definitely not

Does that imply they're finished?

Best regards,
Marcus

Re: Lunar Orbiting Platform Gateway

It was a cheap joke on my part (and not at all commentary on the gateway concept).  Disregard.

I'd be down to collaborate on something open source.  Could you point to publicly available documents that summarize the standards/specs?  

-John

On Wed, Oct 30, 2019 at 8:50 AM Michelle Thompson <mountain.michelle@gmail.com> wrote:
I was hesitant to ask why, but I'm curious now. 

I know the Gateway is controversial. I understand there's a lot of doubt it will actually happen. The heavy emphasis on commercial activity is another aspect. 

However, I've been asked for help on a receiving station for the amateur radio portions that might be included. There's a lot of overlap between what I do and the type of communications proposed. 

Comment and critique would be very appreciated here. 

-Michelle W5NYV




On Wed, Oct 30, 2019 at 7:14 AM Müller, Marcus (CEL) <mueller@kit.edu> wrote:
Hey John,

> > Anyone working on…
> Definitely not

Does that imply they're finished?

Best regards,
Marcus

Re: Subject Line Prefix Missing

To drive this more Off-Topic than it already is...

> Mailing list software for decades inserts unique headers for filtering
> purpose. "List-Id" is AFAICT the most common one, which is also used
> by GNU mailman. It has been specified in 2001 in RFC2919

Even non-Mailinglist software, e.g. GitHub, EBay, Deutsche Bahn, are
supplying custom List-Id headers for separate topics. In case of GitHub
one can use List-Id headers to automatically separate mails for
different repositories without looking at the content or Subject.

Cheers
Andrej

FM and FreeDV cross-mode repeater with qradiolink

Hi,

I just wanted to let you know that I have created an AppImage of qradiolink based on Debian Buster libraries. There have been some changes recently, and now the VOIP GUI can do cross-mode repeat from FM to FreeDV and viceversa. Other modes like AM and SSB work a little as well, but despite all my efforts I was unable to write a good enough SSB demodulator. I think I have either a problem understanding the AGC in GNU radio or a problem understanding how SSB should be demodulated.
Many thanks to A. Maitland Bottoms who exposed the FreeDV API and maintains the Debian GNU radio package, making it possible for people like me who don't own SSB radios anymore to use FreeDV.


Best regards,
Adrian

Re: Subject Line Prefix Missing

This is getting OT, but...

On Wed, Oct 30, 2019 at 02:21:12PM +0000, Johannes Demel wrote:
> My solution
> 1. If "Mail From 'discuss-gnuradio@gnu.org'"
> 2. If "Mail To 'discuss-gnuradio@gnu.org'"

Mailing list software for decades inserts unique headers for filtering
purpose. "List-Id" is AFAICT the most common one, which is also used by
GNU mailman. It has been specified in 2001 in RFC2919
http://www.faqs.org/rfcs/rfc2919.html

Regards,
Harald
--
- Harald Welte <laforge@osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)

Re: Subject Line Prefix Missing

Hi,

FWIW, I filter mailing lists based on the List-Id field, which still
works fine.

Just found out that this seems to be a thing :-)
https://www.ietf.org/rfc/rfc2919.txt

Best,
Bastian

On 10/30/19 3:21 PM, Johannes Demel wrote:
> Hi all,
>
> I was wondering about that mailing list behavior as well.
>
> My solution
> 1. If "Mail From 'discuss-gnuradio@gnu.org'"
> 2. If "Mail To 'discuss-gnuradio@gnu.org'"
> In my case: move to folder.
> 1. covers original mails
> 2. covers replies.
>
> I had to split this into 2 separate rules but that's due to my email
> service provider.
> This solution is more verbose about who receives such an email. e.g.
> off-list replies should not end up to be caught by these rules.
>
> Anyways, I just wanted to share my 2 cents on that. Maybe someone finds
> this info useful.
>
> Cheers
> Johannes
>
>
>
> On 30.10.19 15:11, Müller, Marcus (CEL) wrote:
>> Hi Ed,
>>
>> "deliberate" would be wrong. Surprising, not really, if we'd have read
>> the info mails from the gnu.org mailing list admin more carefully:
>>
>> In the process of respecting DMARC in the ML infrastructure, they
>> disabled rewriting of the subject line for outgoing mail servers that
>> signal strict DMARC compliance. The mailing list seems to think your
>> server does (I don't know why, to be honest, can't seem to find those
>> DNS entries).
>>
>> So, for now, my understanding is that there's nothing *we* can do about
>> it. (We should be able to change the settings of the ML; but in which
>> range, and what we'd break on the way, isn't quite clear to us at this
>> point.)
>>
>> For some reason, my university mail server seems to sort these mails
>> correctly, and so do GMail instances. Probably a list header?
>>
>> Best regards,
>> Marcus
>>
>> On Wed, 2019-10-30 at 09:17 -0400, Ed Criscuolo wrote:
>>> I've noticed that recent postings to the list are missing
>>> the "[Discuss-gnuradio] prefix that was automatically
>>> added to the subject line.
>>>
>>> Was this a deliberate change? I hope not, as I find that
>>> feature very useful in picking out the list messages
>>> from amid all the spam.
>>>
>>>
>>> @(^.^)@ Ed
>>>

--
Dr. Bastian Bloessl
Secure Mobile Networking Lab (SEEMOO)
TU Darmstadt, Germany

www.bastibl.net
GitHub/Twitter: @bastibl

Re: Lunar Orbiting Platform Gateway

I was hesitant to ask why, but I'm curious now. 

I know the Gateway is controversial. I understand there's a lot of doubt it will actually happen. The heavy emphasis on commercial activity is another aspect. 

However, I've been asked for help on a receiving station for the amateur radio portions that might be included. There's a lot of overlap between what I do and the type of communications proposed. 

Comment and critique would be very appreciated here. 

-Michelle W5NYV




On Wed, Oct 30, 2019 at 7:14 AM Müller, Marcus (CEL) <mueller@kit.edu> wrote:
Hey John,

> > Anyone working on…
> Definitely not

Does that imply they're finished?

Best regards,
Marcus

Re: Subject Line Prefix Missing

Hi all,

I was wondering about that mailing list behavior as well.

My solution
1. If "Mail From 'discuss-gnuradio@gnu.org'"
2. If "Mail To 'discuss-gnuradio@gnu.org'"
In my case: move to folder.
1. covers original mails
2. covers replies.

I had to split this into 2 separate rules but that's due to my email
service provider.
This solution is more verbose about who receives such an email. e.g.
off-list replies should not end up to be caught by these rules.

Anyways, I just wanted to share my 2 cents on that. Maybe someone finds
this info useful.

Cheers
Johannes



On 30.10.19 15:11, Müller, Marcus (CEL) wrote:
> Hi Ed,
>
> "deliberate" would be wrong. Surprising, not really, if we'd have read
> the info mails from the gnu.org mailing list admin more carefully:
>
> In the process of respecting DMARC in the ML infrastructure, they
> disabled rewriting of the subject line for outgoing mail servers that
> signal strict DMARC compliance. The mailing list seems to think your
> server does (I don't know why, to be honest, can't seem to find those
> DNS entries).
>
> So, for now, my understanding is that there's nothing *we* can do about
> it. (We should be able to change the settings of the ML; but in which
> range, and what we'd break on the way, isn't quite clear to us at this
> point.)
>
> For some reason, my university mail server seems to sort these mails
> correctly, and so do GMail instances. Probably a list header?
>
> Best regards,
> Marcus
>
> On Wed, 2019-10-30 at 09:17 -0400, Ed Criscuolo wrote:
>> I've noticed that recent postings to the list are missing
>> the "[Discuss-gnuradio] prefix that was automatically
>> added to the subject line.
>>
>> Was this a deliberate change? I hope not, as I find that
>> feature very useful in picking out the list messages
>> from amid all the spam.
>>
>>
>> @(^.^)@ Ed
>>

Re: Lunar Orbiting Platform Gateway

Hey John,

> > Anyone working on…
> Definitely not

Does that imply they're finished?

Best regards,
Marcus

Re: Subject Line Prefix Missing

Hi Ed,

"deliberate" would be wrong. Surprising, not really, if we'd have read
the info mails from the gnu.org mailing list admin more carefully:

In the process of respecting DMARC in the ML infrastructure, they
disabled rewriting of the subject line for outgoing mail servers that
signal strict DMARC compliance. The mailing list seems to think your
server does (I don't know why, to be honest, can't seem to find those
DNS entries).

So, for now, my understanding is that there's nothing *we* can do about
it. (We should be able to change the settings of the ML; but in which
range, and what we'd break on the way, isn't quite clear to us at this
point.)

For some reason, my university mail server seems to sort these mails
correctly, and so do GMail instances. Probably a list header?

Best regards,
Marcus

On Wed, 2019-10-30 at 09:17 -0400, Ed Criscuolo wrote:
> I've noticed that recent postings to the list are missing
> the "[Discuss-gnuradio] prefix that was automatically
> added to the subject line.
>
> Was this a deliberate change? I hope not, as I find that
> feature very useful in picking out the list messages
> from amid all the spam.
>
>
> @(^.^)@ Ed
>

Re: named fifo (byte - byte transfer)

Hi,

we've covered pretty much exactly your three questions in a mailing
list thread earlier this month. Let me link to the archive:

https://lists.gnu.org/archive/html/discuss-gnuradio/2019-10/index.html

It's the mails with subject "fifo / file source".

In essence, "cat" is buffered, and so you need to use a different
program that makes sure the fstream it outputs is unbuffered. GNU Radio
has no influence on the buffering your writing process does.

Best regards,
Marcus

On Wed, 2019-10-30 at 14:19 +0200, hamzeh elsayed wrote:
> Hi,
>
> I did the following:
> 1) in linux terminal I create a fifo file as :
> $ mkfifo in
> 2) in gnuradio I did:
> file source (file name : in)-> throttle -> file sink (output file: out.txt)
>
>
>
> then for running, I did the following:
> 1) run the flowgraph
> 2) in terminal, I run
> $ cat > in
>
> then only if I wrote a large number for characters, those characters are transferred.
>
> for example if I wrote 10 bytes in fifo in to transmit them, any byte is not written in the file out.txt. while, if 15000 bytes are written in fifo in the some of these 15000 bytes are transferred to out.txt but not all of them.
>
> it seems to me that fifo in gnuradio does not transfer each byte alone, is saves a number of bytes as a packet then it send them together.
>
> my question is :
>
> 1) how to transfer each byte alone in my flowgraph example using unix pipe?
>
> 2) if I can not transfer each byte alone, what is the size of packet that are buffered and the transferred together?
>
> 3) If the last bytes are less than packet size, then they are not transferred. therefore, how I can I transfer them?
>
> if I have to do padding then I have to know the size of the buffer or packet? Is it fixed or not?
>
> Thanks for your time and help
>
> Best regards

Subject Line Prefix Missing

I've noticed that recent postings to the list are missing
the "[Discuss-gnuradio] prefix that was automatically
added to the subject line.

Was this a deliberate change? I hope not, as I find that
feature very useful in picking out the list messages
from amid all the spam.


@(^.^)@ Ed

named fifo (byte - byte transfer)

Hi,

I did the following:
1) in linux terminal I create a fifo file as :
    $ mkfifo in
2) in gnuradio I did:
file source (file name : in)-> throttle -> file sink (output file: out.txt)


then for running, I did the following:
1) run the flowgraph
2) in terminal, I run
    $ cat > in

then only if I wrote a large number for characters, those characters are transferred.

for example if I wrote 10 bytes in fifo in to transmit them, any byte is not written in the file out.txt. while, if 15000 bytes are written in fifo in the some of these 15000 bytes are transferred to out.txt but not all of them.

it seems to me that fifo in gnuradio does not transfer each byte alone, is saves a number of bytes as a packet then it send them together.

my question is :

1) how to transfer each byte alone in my flowgraph example using unix pipe?

2) if I can not transfer each byte alone, what is the size of packet that are buffered and the transferred together?

3) If the last bytes are less than packet size, then they are not transferred. therefore, how I can I transfer them?

if I have to do padding then I have to know the size of the buffer or packet? Is it fixed or not?

Thanks for your time and help

Best regards

Tuesday, October 29, 2019

Re: switching its frequency (hopping) when it decode the message(matches password)

Thank  you so much! 
I will try to implement, and will try to consult you for clarification, thank you for your response sir 

On Wed, 30 Oct 2019 at 12:20 AM, Michael Dickens <michael.dickens@ettus.com> wrote:
Hi Madhuri - Please keep this discussion on the GR discussion list where it started: more people reading it increases the chances of someone providing help!

Nobody here is going to provide you with the programs as you describe. This email discussion group is, broadly, about providing advice ... you have to do the actual work & ask specific enough questions to get reasonable feedback. You've provided some specifics now, and the best advice I can give is the following:

If you look through GNU Radio examples, both from GR itself as well as "out of tree" (OOT) modules, you'll find some interesting GRC flowgraphs. None will do -everything- that you're looking out of the box, but you can piece together enough from various places to do what you want, plus or minus.

Cheers! - MLD

On Tue, Oct 29, 2019 at 11:26 AM Madhuri Gummineni <madhuri.vijay2003@gmail.com> wrote:
Dear sir,
i have USRPN210 (UBX Daughterboard ) transceiver .
If  i (from one usrp)send any message say  password is -23 
on the otherside the other  usrp  should decode it and verify it. if it is 23 then it has to hop from f1(96Mhz) to f2(98Mhz) 

Therefore it requires two programs 
TX side-grc flowgraph for sending message  
program on RX side
1) grc hopping flowgraph for Hopping 
2) grc flowgraph  for decoding (for password verification)
3)connecting 1) and 2) to implement it.
 Sir remaining parameters BW-75K, modulation -PSK .
please guide me sir

Thank you sir
--
Michael Dickens
Ettus Research Technical Support
Email: support@ettus.com
Web: https://ettus.com/

Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

diff -ur gnuradio-3.8.0.0_o/grc/core/platform.py gnuradio-3.8.0.0/grc/core/platform.py
--- gnuradio-3.8.0.0_o/grc/core/platform.py 2019-08-09 22:40:34.000000000 +0100
+++ gnuradio-3.8.0.0/grc/core/platform.py 2019-10-29 23:00:17.161851477 +0000
@@ -194,7 +194,10 @@

self._docstring_extractor.finish()
# self._docstring_extractor.wait()
- utils.hide_bokeh_gui_options_if_not_installed(self.blocks['options'])
+ try:
+ utils.hide_bokeh_gui_options_if_not_installed(self.blocks['options'])
+ except KeyError: #this happens if there's no 'options' block
+ pass

def _iter_files_in_block_path(self, path=None, ext='yml'):
"""Iterator for block descriptions and category trees"""
On 27/10/2019 11:58, Marcus Müller wrote:
> ah! I missed the part where you said you're not used to Python.
>
> In Python, indentation is structure-defining, and the error message
> sadly doesn't really give context, but it looks like the most probable
> explanation is that the line you've inserted is not correctly indented.
>
> Make sure you're using the same characters to indent (spaces) and the
> same amount of additional spaces to indent the content of the try:-
> block.
>
> Best regards,
> Marcus
>

Thanks Marcus,
I did not realize about indentation in python.
I have corrected this by using tabs only as used by similar structures
in the same file.
On running grc I get:

[baz@jackodesktop gnuradio]$ gnuradio-companion
Traceback (most recent call last):
File
"/usr/lib/python3.8/site-packages/gnuradio/grc/gui/Application.py", line
102, in do_activate
self.main_window = MainWindow(self, self.platform)
File
"/usr/lib/python3.8/site-packages/gnuradio/grc/gui/MainWindow.py", line
84, in __init__
generate_modes = platform.get_generate_options()
File
"/usr/lib/python3.8/site-packages/gnuradio/grc/core/platform.py", line
379, in get_generate_options
for param in self.block_classes['options'].parameters_data:
File "/usr/lib64/python3.8/collections/__init__.py", line 891, in
__getitem__
return self.__missing__(key) # support subclasses that
define __missing__
File "/usr/lib64/python3.8/collections/__init__.py", line 883, in
__missing__
raise KeyError(key)
KeyError: 'options'

The patch applying your change is attached.

Regards,
Barry

Re: Lunar Orbiting Platform Gateway

Definitely not 

On Tue, Oct 29, 2019 at 3:59 PM Michelle Thompson <mountain.michelle@gmail.com> wrote:
Anyone working on blocks specifically for Lunar Orbiting Platform Gateway? Or interested in doing so? 

-Michelle W5NYV 
--
-Michelle W5NYV

"Potestatem obscuri lateris nescis."

Lunar Orbiting Platform Gateway

Anyone working on blocks specifically for Lunar Orbiting Platform Gateway? Or interested in doing so? 

-Michelle W5NYV 
--
-Michelle W5NYV

"Potestatem obscuri lateris nescis."

Synchronous recording with two USRP B210

Hi,

I am trying to use GNURadio to receive signals and record them to files from two USRP B210(each has two channels). Both SDRs are connected to an CDA-2990 external clock. In gnuRadio I had to put two UHD source blocks and use "serial=xxx" to point them to each SDR and connect each output channel to 4 file Sink blocks. I also changed the clock and time source to "external" and synced to "unknown PPS".  However, a couple of files are different in size from the other couple. Apparently if I want to start them synchronously, all four channels should be in one source block, but how can I do that and point out each 2 channels come from a different device? When I try one USRP source block with "serial0=31A3C93,serial1=31A3D4B", I face an error bellow:
Traceback (most recent call last):
  File "E:\Alireza\sdr_A20\top_block.py", line 207, in <module>
    main()
  File "E:\Alireza\sdr_A20\top_block.py", line 201, in main
    tb = top_block_cls()
  File "E:\Alireza\sdr_A20\top_block.py", line 125, in __init__
    self.uhd_usrp_source_0.set_clock_source('external', 1)
  File "E:\Program Files\PothosSDR\lib\python2.7\site-packages\gnuradio\uhd\uhd_swig.py", line 2987, in set_clock_source
    return _uhd_swig.usrp_source_sptr_set_clock_source(self, source, mboard)
RuntimeError: LookupError: IndexError: multi_usrp::mb_root(1) - LookupError: IndexError: multi_usrp::mb_root(1) - path not found

Is there any example available on how I can synchronously start recording from different devices? I assume this is a trivial task but I have been searching for this for a few days right now and I can't find any helpful answer. I am attaching my .grc files.

Thank you,
Ali

Re: switching its frequency (hopping) when it decode the message(matches password)

Hi Madhuri - Please keep this discussion on the GR discussion list where it started: more people reading it increases the chances of someone providing help!

Nobody here is going to provide you with the programs as you describe. This email discussion group is, broadly, about providing advice ... you have to do the actual work & ask specific enough questions to get reasonable feedback. You've provided some specifics now, and the best advice I can give is the following:

If you look through GNU Radio examples, both from GR itself as well as "out of tree" (OOT) modules, you'll find some interesting GRC flowgraphs. None will do -everything- that you're looking out of the box, but you can piece together enough from various places to do what you want, plus or minus.

Cheers! - MLD

On Tue, Oct 29, 2019 at 11:26 AM Madhuri Gummineni <madhuri.vijay2003@gmail.com> wrote:
Dear sir,
i have USRPN210 (UBX Daughterboard ) transceiver .
If  i (from one usrp)send any message say  password is -23 
on the otherside the other  usrp  should decode it and verify it. if it is 23 then it has to hop from f1(96Mhz) to f2(98Mhz) 

Therefore it requires two programs 
TX side-grc flowgraph for sending message  
program on RX side
1) grc hopping flowgraph for Hopping 
2) grc flowgraph  for decoding (for password verification)
3)connecting 1) and 2) to implement it.
 Sir remaining parameters BW-75K, modulation -PSK .
please guide me sir

Thank you sir
--
Michael Dickens
Ettus Research Technical Support
Email: support@ettus.com
Web: https://ettus.com/

[Discuss-gnuradio] How to convert a binary file input to a PMT?

Attempting to transmit a wifi packet with gr-ieee802.11. I'm reading in the payload binary from a file source. The output of the file source block is a gr_stream. But the Wifi MAC block requires a gr_message input, which I gather to be in PMT format.

How can I turn my payload into something that the Wifi MAC block can understand? My current attempt, below, runs it through a stream-to-tagged-stream block and then a tagged-stream-to-PDU block, which feeds into a message strobe. This generates a flowchart fine but segfaults ~3 seconds into execution, so I must be doing something terribly wrong.



Thanks!


--
Eamon Heaney
Fleet Commander
President, Model UN at Virginia Tech

Re: [Discuss-gnuradio] DARPA SC2 Team MarmotE modem is open sourced

Hi Miklos -

This is fantastic! I'm really excited to see where you take your technology and design going forward, and I'm sure the community will greatly benefit from you sharing it.

Congratulations again on your 2nd place victory at the challenge!

Cheers,
Ben

On Sun, Oct 27, 2019 at 8:21 AM Michael Dickens <michael.dickens@ettus.com> wrote:
Hi Miklos - Excellent! Thanks for sharing your work! - MLD

On Thu, Oct 17, 2019 at 9:02 PM Miklos Maroti <mmaroti@gmail.com> wrote:
Dear Fellow GNURadio Users,

We are happy to announce that we are open sourcing the MarmotE modem
that we have developed for the DARPA Spectrum Collaboration Challenge
under the GPLv3 license at https://gitlab.com/marmote/gr-marmote3.
This is an FBMC based modem capable of using up to 40MHz of bandwidth
with a good computer, but can be used with a simple laptop with lower
sampling rates. There might be a few rough edges in the code base
specifically tailored for the Colosseum and SC2 challenge, but we have
created a simplified version of the modem that works with any USRP or
other SDR. The code base has lots of interesting components, including
good error correcting codes, SSE optimized fractional FBMC channelizer
and synthesizer, variable length packets, multiple MCS settings, ARQ,
TCP/UDP port based QoS settings, etc. We plan to write a manual, but
till then enjoy the short README, the raw code and the flow graphs.
Finally, please cheer for Team MarmotE on the DARPA SC2 championship
event at MWC Los Angeles 2019, October 23.

Best,
Miklos

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


--
Michael Dickens
Ettus Research Technical Support
Email: support@ettus.com
Web: https://ettus.com/

Re: A 21cm sky map of a goodly chunk of the northern sky

On 10/29/2019 08:23 AM, Glen Langston wrote:
> Very nice work Marcus!
>
> Did you put your .grc file on GitHub?
>
> FYI I've made some good progress on simultaneously mapping in spectral line
> mode and detecting transient radio flashes.
>
> This design is obtained with
>
> git clone http://www.github.com/WVURAIL/gr-radio_astro
>
> then building and running
>
> cd gr-radio_astro/examples
>
> gnuradio-companion NsfWatch45.grc
>
> This uses a PlutoSdr, and modification would be required for other SDRs.
We'll be building a "mini CHIME" in the spring, with the purpose of
looking for FRBs at 611MHz in a zenith-oriented swath above the observatory.

>
> The code is running on three Pi 4Bs and an Odroid N2.
> I look for coincidences in the transient event times.
>
> Again, great work on the map! Also I confirm that the outer part of our
> Milky Way galaxy is much brighter than the inner galaxy in HI.
> This puzzled me for a while.
>
> Best Regards,
>
> Glen
The memo points to all the GIT repositories involved.

>
>> On Oct 28, 2019, at 11:42 PM, Marcus D. Leech <patchvonbraun@gmail.com> wrote:
>>
>> On 10/28/2019 12:55 PM, Daniel Estévez wrote:
>>> El 28/10/19 a las 1:02, Marcus D. Leech escribió:
>>>> Here's the latest version of our 21cm sky map, derived from nearly 5
>>>> months worth of data from our 21cm spectrometer instrument.
>>>>
>>>> All of the real-time processing is handled, naturally, with Gnu Radio,
>>>> and then some Python post-processing.
>>>>
>>>> http://www.ccera.ca/files/21cm.png
>>> Hi Marcus,
>>>
>>> Very interesting. Is there any information online about how the map was
>>> made (both GNU Radio and post-processing)?
>>>
>>> Best,
>>>
>>> Daniel.
>>>
>>>
>> Finally finalized the memo on this:
>>
>> http://www.ccera.ca/files/memos/ccera-memo-0011.pdf
>>
>>
>>

Re: switching its frequency (hopping) when it decode the message(matches password)

Hi Madhuri - Your question is -very- open ended ... there are plenty of ways to implement such a system ... much depends on specifications & constraints that you haven't mentioned: limits on RF bandwidth? timing constraints? what SDR HW capabilities? what CPU HW capabilities? what sort of RF channels are you expecting? I'd recommend starting with some practical DSP & SDR books to get started; there are lots here < https://wiki.gnuradio.org/index.php/SuggestedReading >. If you can narrow down your specifications / note specific constraints, we might be able to provide some specific insights ... until then, you'll just get generalities such as this reply. Hope this is useful! - MLD

On Tue, Oct 29, 2019 at 7:20 AM Madhuri Gummineni <madhuri.vijay2003@gmail.com> wrote:
hi,
i am trying to write grc flow graph  to switch(hop) from one frequency to other if it detects  the password.
if one usrp send a message as switch it should to other frequency.
for this what are blocks that are required.
planning like a remote operation to switch a sdr or usrp to switch or hop based on password.
if one usrp send a message as password, then other usrp/sdr should hop if password is correct otherwise it will not hop
 please help me sir


--
Michael Dickens
Ettus Research Technical Support
Email: support@ettus.com
Web: https://ettus.com/

Re: A 21cm sky map of a goodly chunk of the northern sky

Very nice work Marcus!

Did you put your .grc file on GitHub?

FYI I've made some good progress on simultaneously mapping in spectral line
mode and detecting transient radio flashes.

This design is obtained with

git clone http://www.github.com/WVURAIL/gr-radio_astro

then building and running

cd gr-radio_astro/examples

gnuradio-companion NsfWatch45.grc

This uses a PlutoSdr, and modification would be required for other SDRs.

The code is running on three Pi 4Bs and an Odroid N2.
I look for coincidences in the transient event times.

Again, great work on the map! Also I confirm that the outer part of our
Milky Way galaxy is much brighter than the inner galaxy in HI.
This puzzled me for a while.

Best Regards,

Glen

> On Oct 28, 2019, at 11:42 PM, Marcus D. Leech <patchvonbraun@gmail.com> wrote:
>
> On 10/28/2019 12:55 PM, Daniel Estévez wrote:
>> El 28/10/19 a las 1:02, Marcus D. Leech escribió:
>>> Here's the latest version of our 21cm sky map, derived from nearly 5
>>> months worth of data from our 21cm spectrometer instrument.
>>>
>>> All of the real-time processing is handled, naturally, with Gnu Radio,
>>> and then some Python post-processing.
>>>
>>> http://www.ccera.ca/files/21cm.png
>> Hi Marcus,
>>
>> Very interesting. Is there any information online about how the map was
>> made (both GNU Radio and post-processing)?
>>
>> Best,
>>
>> Daniel.
>>
>>
> Finally finalized the memo on this:
>
> http://www.ccera.ca/files/memos/ccera-memo-0011.pdf
>
>
>

Re: Dynamic instances in hierarchical blocks

Hi Marcus,
I implemented the hierarchical block directly in python and it worked!
Thanks for support.

Ivan

> Il giorno 29 ott 2019, alle ore 00:35, Müller, Marcus (CEL) <mueller@kit.edu> ha scritto:
>
> Hi Ivan,
>
> that sounds a classical case of impossible to do in graphical, trivial
> to do in Python.
> So, write your hier block in Python – you could also base it on your
> GRC-generated python file (and save it somewhere else, so that it
> doesn't get overwritten).
>
> Best regards,
> Marcus
>
>> On Mon, 2019-10-28 at 22:18 +0100, Ivan Iudice wrote:
>> Hi all!
>> I'm implementing my own testbed in GRC using hierarchical blocks to
>> obtain a clearer flowgraph.
>> I need to have a dynamic amount of instances of a particular sub-
>> block, that I can set as parameter of the higher level block.
>> How can I solve my problem? It could be very cool!
>> Thank you.
>>
>> Ivan
>>

switching its frequency (hopping) when it decode the message(matches password)

hi,
i am trying to write grc flow graph  to switch(hop) from one frequency to other if it detects  the password.
if one usrp send a message as switch it should to other frequency.
for this what are blocks that are required.
planning like a remote operation to switch a sdr or usrp to switch or hop based on password.
if one usrp send a message as password, then other usrp/sdr should hop if password is correct otherwise it will not hop
 please help me sir

Re: How to efficiently implement dechannelization (combine multiple narrowband signals into a single broadband spectrum)

Is this the same baseband signals copied at several place ?
It is yes.

What you can do is :

 * First modulate the signal to a narrow sample-rate (just enough for
the modulation)

 * Upsample that signal to 1 Msps.
   - Depending on the ration between the narrow rate and wide rate, it might be
     beneficial to do that in several steps.
   - So for instance you would go from 10 kHz to 100 kHz first with a
filter that's relatively sharp
   - Then you would go from 100 kHz to 1 MHz with a second filter than
can be much more relaxed (i.e. larger transition bandwidth and so much
less CPU usage)

 * Then use several rotators to position it at the various places you
need it in the 1MHz bandwidth

 * And finally add the output of all the rotators.

Thanks for the suggestion. I'll give that a go.


There is also the so called Polyphase Filter Banks, but that only
works if you need carriers that are all equally spaced. And is also
only a benefic if you really fill a significant number of them.
In my case the output channels are arbitrary, so your first suggestion sounds like the one I need to implement.

Thanks for taking the time to respond.

Re: How to efficiently implement dechannelization (combine multiple narrowband signals into a single broadband spectrum)

Hi,

> I'm working on an SDR project where I need to transmit a narrow
> baseband signal on multiple different carriers simultaneously, over a
> relatively wide bandwidth (1Mhz).

Is this the same baseband signals copied at several place ?

What you can do is :

* First modulate the signal to a narrow sample-rate (just enough for
the modulation)

* Upsample that signal to 1 Msps.
- Depending on the ration between the narrow rate and wide rate, it might be
beneficial to do that in several steps.
- So for instance you would go from 10 kHz to 100 kHz first with a
filter that's relatively sharp
- Then you would go from 100 kHz to 1 MHz with a second filter than
can be much more relaxed (i.e. larger transition bandwidth and so much
less CPU usage)

* Then use several rotators to position it at the various places you
need it in the 1MHz bandwidth

* And finally add the output of all the rotators.


There is also the so called Polyphase Filter Banks, but that only
works if you need carriers that are all equally spaced. And is also
only a benefic if you really fill a significant number of them.

Cheers,

Sylvain

Monday, October 28, 2019

How to efficiently implement dechannelization (combine multiple narrowband signals into a single broadband spectrum)

Hello all,

I'm working on an SDR project where I need to transmit a narrow
baseband signal on multiple different carriers simultaneously, over a
relatively wide bandwidth (1Mhz). Essentially, when working normally,
the system acts as a radio passthrough, retransmitting the existing
channels, but then when an input is triggered, an external audio
source is then AM modulated and transmitted on several channels
instead of the original baseband.

I've been implementing the system in GNU Radio Companion and
essentially have the following for each channel:

External in -> AM mod -
|-Selector -> Band Pass filter
-> Add -> TX
Baseband in --------------

Now although this works, in practice as the number of channels
increases, performance becomes an issue, as you'd expect. The main
culprit here is primarily the band pass filter, which is responsible
for about 60% of the CPU usage (the modulation is responsible for
about 30%). Using an FFT filter for the bandpass filter definitely
helped performance, but I need to improve it more. After researching
online, I understand that the problem is primarily due to having to
deal with a very wide baseband compared to the narrowband signal that
I'm trying to filter (AM audio at 10kHz bandwidth). Unfortunately, I
can't see how I can reduce the sample rate. At the moment, everything
runs at the 1Mhz sample rate apart from the external input, which runs
at a lower rate until I have to multiply it with the AM carrier.

What is an efficient way of de-channelizing and taking multiple narrow
channels and combining them into a wide spectrum?

Re: A 21cm sky map of a goodly chunk of the northern sky

On 10/28/2019 12:55 PM, Daniel Estévez wrote:
> El 28/10/19 a las 1:02, Marcus D. Leech escribió:
>> Here's the latest version of our 21cm sky map, derived from nearly 5
>> months worth of data from our 21cm spectrometer instrument.
>>
>> All of the real-time processing is handled, naturally, with Gnu Radio,
>> and then some Python post-processing.
>>
>> http://www.ccera.ca/files/21cm.png
> Hi Marcus,
>
> Very interesting. Is there any information online about how the map was
> made (both GNU Radio and post-processing)?
>
> Best,
>
> Daniel.
>
>
Finally finalized the memo on this:

http://www.ccera.ca/files/memos/ccera-memo-0011.pdf

Re: AM demodulation

Hi Barry and Bill,

> I don't know how wide a spectrum the PLL can handle.

Generally, that's not really inherently limited by anything but the
loop bandwidth.

It's a really simple PLL, with a complex sample-argument phase
detector.

In other words: if you set the loop bandwidth too high, the PLL will
jump around like crazy in the presence of noise, or might lock onto
data instead of carrier.

Pick a bandwidth too small, and it won't be able to ever lock to even
the cleanest carrier if it's further away. It also won't be able to
"follow" a changing carrier frequency (might be pretty relevant for
satcom, if it's not geosync.

Best regards,
Marcus

Re: AM demodulation

Hi Markus,

yeah, that sounds right, but:
You'd probably want to use a PLL frequency detector (similarly
parameterized) to detect these and output a frequency estimate, and
then do some math on that estimate, and use it to correct the system.

Best regards,
Marcus

On Mon, 2019-10-28 at 16:41 +0100, Markus Heller wrote:
> Dear OMs,
>
> I guess this carrier tracking block would be useful to handle
> frequency
> drift of cheap (unstabilized) devices, when working QO-100 satellite
> connections. This block could be used to find the band end beacons
> and
> derive the frequency shift and correct it accordingly. Right?
>
> vy73
> markus
> dl8rds
>
> Am Montag, den 28.10.2019, 09:44 -0500 schrieb Bill Dailey:
> > Can you give a little primer on using that PLL tracking? I would
> > love to use that to just track carriers random frequencies. For
> > instance 10mhz. Ultimately I want to track and periodically log
> > and
> > offset from true predicted frequency. Like every 10 seconds.
> >
> > Bill Dailey
> >
> > Negativity always wins the short game. But positivity wins the long
> > game. - Gary Vaynerchuk
> >
> > Don't be easy to understand,
> > Be impossible to misunderstand
> > - Steve Sims
> >
> > > On Oct 28, 2019, at 9:27 AM, Barry Duggan <barry@dcsmail.net>
> > > wrote:
> > >
> > > Hi Albin and Volker,
> > >
> > > I added a PLL Carrier Tracking block to take care of the tuning
> > > problem. See the revised
> > > https://wiki.gnuradio.org/index.php/File:FunCube_AM.png
> > >
> > > Albin, that 'spike' is the carrier! This is AM ;)
> > >
> > > Thank you both for your suggestions.
> > > ---
> > > Barry Duggan KV4FV
> > >
> > >
> > > On 2019-10-27 07:13, Albin Stigö wrote:
> > > > Hi Barry,
> > > > Some thoughts:
> > > > You have a large DC spike at the center, try using the
> > > > frequency
> > > > xlating
> > > > fir filter to tune an offset frequency.
> > > > Why don't you decimate at the channel filter?
> > > > Try observing the signal at various points using the frequency
> > > > sink.
> > > > Good luck,
> > > > Albin SM6WJM
> > > > On Sat, Oct 26, 2019, 21:02 Barry Duggan <barry@dcsmail.net>
> > > > wrote:
> > > > > Hi,
> > > > > I've been working on a gnuradio AM broadcast receiver, and
> > > > > have
> > > > > found
> > > > > that the tuning is very critical to obtaining clear audio. My
> > > > > flowgraph
> > > > > can be seen at
> > > > > https://wiki.gnuradio.org/index.php/File:FunCube_AM.png.
> > > > > Are there any alternate demodulation methods which are not so
> > > > > sensitive
> > > > > to exact tuning?
> > > > > Thanks,
> > > > > --
> > > > > Barry Duggan KV4FV
>
>

Re: Dynamic instances in hierarchical blocks

Hi Ivan,

that sounds a classical case of impossible to do in graphical, trivial
to do in Python.
So, write your hier block in Python – you could also base it on your
GRC-generated python file (and save it somewhere else, so that it
doesn't get overwritten).

Best regards,
Marcus

On Mon, 2019-10-28 at 22:18 +0100, Ivan Iudice wrote:
> Hi all!
> I'm implementing my own testbed in GRC using hierarchical blocks to
> obtain a clearer flowgraph.
> I need to have a dynamic amount of instances of a particular sub-
> block, that I can set as parameter of the higher level block.
> How can I solve my problem? It could be very cool!
> Thank you.
>
> Ivan
>

Dynamic instances in hierarchical blocks

Hi all!
I'm implementing my own testbed in GRC using hierarchical blocks to obtain a clearer flowgraph.
I need to have a dynamic amount of instances of a particular sub-block, that I can set as parameter of the higher level block.
How can I solve my problem? It could be very cool!
Thank you.

Ivan

Re: AM demodulation

To all who gave me good ideas and insights,

Thank you for your help. Based on all of your comments, I have a new and
improved AM receiver which automatically corrects small tuning errors.
Attached is a picture of the flowgraph.

Best regards,
---
Barry Duggan KV4FV


On 2019-10-28 12:21, Albin Stigö wrote:
> Last time I looked I found the AM demod block less than ideal so I just
> used a complex to mag and a DC blocker and found that worked better for
> my
> experiments.
>
> 73 Albin SM6WJM
>
> On Mon, Oct 28, 2019, 16:43 Barry Duggan <barry@dcsmail.net> wrote:
>
>> Hi Albin,
>>
>> Hmm.. Good to know. I had tried a frequency translating filter to
>> create
>> a 10khz IF, but it didn't seem to make any difference. I need to take
>> another look at that.
>>
>> Thanks!
>> ---
>> Barry Duggan KV4FV
>>
>>
>> On 2019-10-28 11:32, Albin Stigö wrote:
>> > A direct conversation SDR receiver like the funcube dongle pro plus has
>> > a
>> > large DC spike, it's not the carrier, it will mask your carrier
>> > though.. IQ
>> > correction will remove it, but that will also remove an AM carrier at
>> > 0Hz
>> > so it's common practice to offset a bit with a frequency translating
>> > filter.
>> >
>> > On Mon, Oct 28, 2019, 15:24 Barry Duggan <barry@dcsmail.net> wrote:
>> >
>> >> Hi Albin and Volker,
>> >>
>> >> I added a PLL Carrier Tracking block to take care of the tuning
>> >> problem.
>> >> See the revised
>> >> https://wiki.gnuradio.org/index.php/File:FunCube_AM.png
>> >>
>> >> Albin, that 'spike' is the carrier! This is AM ;)
>> >>
>> >> Thank you both for your suggestions.
>> >> ---
>> >> Barry Duggan KV4FV
>> >>
>> >>
>> >> On 2019-10-27 07:13, Albin Stigö wrote:
>> >> > Hi Barry,
>> >> >
>> >> > Some thoughts:
>> >> >
>> >> > You have a large DC spike at the center, try using the frequency
>> >> > xlating
>> >> > fir filter to tune an offset frequency.
>> >> >
>> >> > Why don't you decimate at the channel filter?
>> >> >
>> >> > Try observing the signal at various points using the frequency sink.
>> >> >
>> >> > Good luck,
>> >> > Albin SM6WJM
>> >> >
>> >> > On Sat, Oct 26, 2019, 21:02 Barry Duggan <barry@dcsmail.net> wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> I've been working on a gnuradio AM broadcast receiver, and have found
>> >> >> that the tuning is very critical to obtaining clear audio. My
>> >> >> flowgraph
>> >> >> can be seen at
>> >> >> https://wiki.gnuradio.org/index.php/File:FunCube_AM.png.
>> >> >> Are there any alternate demodulation methods which are not so
>> >> >> sensitive
>> >> >> to exact tuning?
>> >> >>
>> >> >> Thanks,
>> >> >> --
>> >> >> Barry Duggan KV4FV
>> >> >>
>> >> >>
>> >>
>>

Re: A 21cm sky map of a goodly chunk of the northern sky

I'm working on the technical memo at the moment.

Sent from my iPhone

> On Oct 28, 2019, at 2:26 PM, Daniel Estévez <daniel@destevez.net> wrote:
>
> El 28/10/19 a las 1:02, Marcus D. Leech escribió:
>> Here's the latest version of our 21cm sky map, derived from nearly 5
>> months worth of data from our 21cm spectrometer instrument.
>>
>> All of the real-time processing is handled, naturally, with Gnu Radio,
>> and then some Python post-processing.
>>
>> http://www.ccera.ca/files/21cm.png
>
> Hi Marcus,
>
> Very interesting. Is there any information online about how the map was
> made (both GNU Radio and post-processing)?
>
> Best,
>
> Daniel.
>
>

Re: [Discuss-gnuradio] Packet transmission questions from a newb

The final aim is to build a transmitter and receiver for 802.11p DSRC packets.

The receiver is currently using 802.11a, for testing purposes, but I do have a flowchart they successfully receives 802.11p instead.

I've figured out what I need to put in the file source (message binary, not .pcap), but I'm unsure how to translate that from a gr_stream to a gr_message, so I can feed it into the Wifi MAC block.

Thanks!

On Mon, Oct 28, 2019, 5:12 AM sumit kumar <sumitstop@gmail.com> wrote:
" but my wi-fi packet receiver works just dandy without any OFDM blocks" --> Can you check the standard which your wifi receiver is following ? If it is 802.11b, then it wont work with gr-ieee 80211 because gr-ieee 80211 is based on OFDM based WiFi. 

You cannot use .pcap file as file source for the wifi_tx.grc. 

May I know your final aim for this experiment so that I can put my suggestions ? 

Regards
Sumit 

On Sun, 27 Oct 2019 at 20:10, Eamon Heaney <heaneye@vt.edu> wrote:
Hi,

I'm trying to create a wi-fi transmitter in GNURadio that can take a file source and transmit it as an 802.11 packet. I'm using this example as a basis, and trying to follow the guides here.

Frankly, though, a lot of what's in that guide goes way over my head. I have a general understanding of what OFDM is, but my wi-fi packet receiver works just dandy without any OFDM blocks. So is it still necessary to incorporate such blocks into a transmitter?

Secondly, I can't just plug a .pcap file source into the transmitter; it doesn't generate, and I get the feeling that .pcap isn't the proper format for transmission anyways. How can I figure out which blocks to put after the file source to make it gel with the next block in the example (WiFi MAC)?

Thanks!

--
Eamon Heaney
Fleet Commander
President, Model UN at Virginia Tech


--
Sumit Kumar



The information contained in this communication is confidential and may be legally privileged. It is intended solely for use by the intended recipient and others authorized to receive it. If you have received this communication in error, you are hereby notified that any disclosure, copying, distribution or taking action in reliance of the contents of this information is strictly prohibited and may be unlawful.

Re: A 21cm sky map of a goodly chunk of the northern sky

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEOn0gFAd3OQG8ow6EtFwrk3lBwykFAl23HX0ACgkQtFwrk3lB
wyl57w//amG5lCM62md6tkljETQev/v0NAYrnHfktC4Py+Ks1ypWVSJUHv5JGMcC
V1o8gNCUL7TtynBJsf9yBgfzQoncYuDt8f//+pi14Gr30JekfeMlHzSc8JKxBOtC
kWAAITPmubWRsqrNaD2HpQKs2VD1R9VEEU+oRi8lNnqzY5DAvneXlxdFbld11y27
QOrNEG/EE7HgshUdhkTt7sA5nuGs+6PnDecRdhZCQEWnfyRRDJWay/kx5ykmY9Ej
q8tkrDrZEelBGGcsrS9WhyvvTWxtTY7OpE2BQyviudetCe3N4hA12gX6gX13eBZu
wb/uRgRyLx7ubD69KMEWrMn0pF0pOC+KuTHbadojh0Ob+fuC/398/DeRtp7pqjZQ
peTR9w3jyuGqiBi+KFMI0oZMsyI5UYQDGHsSZLCV1V/sWy5GUgpQzxC2kpGGp97R
TRNbK0epqoW4vyOFg1Y1n+4iKJGRMnE46EHFoMWtxhxzf5K9QonM8zCS1juUFULI
+GV3xO7GzoRAScXJ15zO7XgkuDwNZySROkO0AaiI+rIQmxLh6caDFruqZ+JuoFCK
Pe5bA+1Bd6YSOMfWzvyQSZJJz0dfBKNWRunhiItHWnO2CJ+/oy/O6DJLi6aP43vZ
VA4di2Tw4JJs+yreEVRuXWPvZo9PjBB2hXS82RFAB9kOgxaP4PI=
=IwXX
-----END PGP SIGNATURE-----
El 28/10/19 a las 1:02, Marcus D. Leech escribió:
> Here's the latest version of our 21cm sky map, derived from nearly 5
> months worth of data from our 21cm spectrometer instrument.
>
> All of the real-time processing is handled, naturally, with Gnu Radio,
> and then some Python post-processing.
>
> http://www.ccera.ca/files/21cm.png

Hi Marcus,

Very interesting. Is there any information online about how the map was
made (both GNU Radio and post-processing)?

Best,

Daniel.

Re: AM demodulation

The PLL Freq Det is the one I would like to figure out.

Bill Dailey

Negativity always wins the short game. But positivity wins the long game. - Gary Vaynerchuk


Don't be easy to understand, 
Be impossible to misunderstand 
- Steve Sims

On Oct 28, 2019, at 11:01 AM, Barry Duggan <barry@dcsmail.net> wrote:

Hi Markus,

From what I can tell, the PLL Carrier Tracking block does the correction, but it doesn't tell you what it did, so I'm not sure you can log the offsets. There are other PLL blocks I haven't looked at yet, so I don't know about them. See https://wiki.gnuradio.org/index.php/Category:Block_Docs for a list of all the blocks. Not all of them have been updated yet! That's what I am working on. Especially the example flowgraphs.

73
---
Barry Duggan KV4FV


On 2019-10-28 11:41, Markus Heller wrote:
Dear OMs,
I guess this carrier tracking block would be useful to handle frequency
drift of cheap (unstabilized) devices, when working QO-100 satellite
connections. This block could be used to find the band end beacons and
derive the frequency shift and correct it accordingly. Right?
vy73
markus
dl8rds
Am Montag, den 28.10.2019, 09:44 -0500 schrieb Bill Dailey:
Can you give a little primer on using that PLL tracking?    I would
love to use that to just track carriers random frequencies.  For
instance 10mhz.  Ultimately I want to track and periodically log and
offset from true predicted frequency. Like every 10 seconds.
Bill Dailey
Negativity always wins the short game. But positivity wins the long
game. - Gary Vaynerchuk
Don't be easy to understand,
Be impossible to misunderstand
- Steve Sims
> On Oct 28, 2019, at 9:27 AM, Barry Duggan <barry@dcsmail.net>
> wrote:
>
> Hi Albin and Volker,
>
> I added a PLL Carrier Tracking block to take care of the tuning
> problem. See the revised
> https://wiki.gnuradio.org/index.php/File:FunCube_AM.png
>
> Albin, that 'spike' is the carrier! This is AM ;)
>
> Thank you both for your suggestions.
> ---
> Barry Duggan KV4FV
>
>
> On 2019-10-27 07:13, Albin Stigö wrote:
> > Hi Barry,
> > Some thoughts:
> > You have a large DC spike at the center, try using the frequency
> > xlating
> > fir filter to tune an offset frequency.
> > Why don't you decimate at the channel filter?
> > Try observing the signal at various points using the frequency
> > sink.
> > Good luck,
> > Albin SM6WJM
> > On Sat, Oct 26, 2019, 21:02 Barry Duggan <barry@dcsmail.net>
> > wrote:
> > > Hi,
> > > I've been working on a gnuradio AM broadcast receiver, and have
> > > found
> > > that the tuning is very critical to obtaining clear audio. My
> > > flowgraph
> > > can be seen at
> > > https://wiki.gnuradio.org/index.php/File:FunCube_AM.png.
> > > Are there any alternate demodulation methods which are not so
> > > sensitive
> > > to exact tuning?
> > > Thanks,
> > > --
> > > Barry Duggan KV4FV