Also bothered

2023-02-06 Thread Matt Young
In ham radio we have twenty manufacturer all writing and producing their
own LCD screens and menus. A nightmare.s Thy all started with DSP function
then suddenly loads of investments into screens.

Just add a USB port to the machines and plug in a chromebook, which costs
155.  Three hundred dollars save at the shack, money spent on pre and post
analog for dealing with this chaotic atmosphere.

The DSP is simple, we need in and out DACs at 8 mHz, 16 bit. We need ar
least 80 Mflops of fixed point 32 bit signal 'taps'. Add in a
separate center frequency LO on output.  Opens the market big time.
Floating point does no good, if you did you Z transforms, everything should
be scaled.
Your source code really is set of pure linear discrete inductance,
capacitance and transconductance.  There are no parasitics.  We can
generate assembly from Spice, then each DSP makerwrits thor own linker from
Spice to DSP..

Code never changes across bands.  The local oscillator mixes in the high
precision interface to the antenna.  We really want the isolation of the
digital from the horrors of atmospheric RF static.


Re: Also bothered

2023-02-06 Thread Marcus Müller

Dear Matt,

this is just a quick reminder that this is the GNU Radio mailing list – 
we're pretty open about the topics we discuss here, but your last three 
emails were a bit far off.


Since (I think) you're new in this community: In case you wonder what 
GNU Radio is exactly, there's a really nice introduction,

https://wiki.gnuradio.org/index.php?title=What_Is_GNU_Radio

Best regards,
Marcus

On 2/6/23 09:28, Matt Young wrote:
In ham radio we have twenty manufacturer all writing and producing 
their own LCD screens and menus. A nightmare.s Thy all started with 
DSP function then suddenly loads of investments into screens.


Just add a USB port to the machines and plug in a chromebook, which 
costs 155.  Three hundred dollars save at the shack, money spent on 
pre and post analog for dealing with this chaotic atmosphere.


The DSP is simple, we need in and out DACs at 8 mHz, 16 bit. We need 
ar least 80 Mflops of fixed point 32 bit signal 'taps'. Add in a 
separate center frequency LO on output.  Opens the market big time.  
Floating point does no good, if you did you Z transforms, 
everything should be scaled.
Your source code really is set of pure linear discrete inductance, 
capacitance and transconductance.  There are no parasitics.  We can 
generate assembly from Spice, then each DSP makerwrits thor own linker 
from Spice to DSP..


Code never changes across bands.  The local oscillator mixes in the 
high precision interface to the antenna.  We really want the isolation 
of the digital from the horrors of atmospheric RF static.




Installation of Gnuradio on Windows 11

2023-02-06 Thread George Edwards
Dear GNURadio Community,

I plan to buy a PC with Windows 11. I looked online to see if folks were
installing Gnuradio on Windows 11 and found nothing definitive. Please
advise me if Gnuradio works on Windows 11.

I also noticed online that there was an installation package for Windows
Debugging, does this mean one can develop their own OOT custom block in the
Windows environment similar to the Linux environment?

Thank you very much!

Regards
George


Re: Installation of Gnuradio on Windows 11

2023-02-06 Thread Aditya Arun Kumar
I’d prefer not using windows for GR as it’s not that comfy for development

On Mon, 6 Feb 2023 at 21:37, George Edwards  wrote:

> Dear GNURadio Community,
>
> I plan to buy a PC with Windows 11. I looked online to see if folks were
> installing Gnuradio on Windows 11 and found nothing definitive. Please
> advise me if Gnuradio works on Windows 11.
>
> I also noticed online that there was an installation package for Windows
> Debugging, does this mean one can develop their own OOT custom block in the
> Windows environment similar to the Linux environment?
>
> Thank you very much!
>
> Regards
> George
>
-- 
S. Aditya Arun Kumar
+919123517465


Re: Also bothered

2023-02-06 Thread Chris Vine
Read it again and you will see the posting was a spoof, artificially
mashed up by a random expression generator from a radio/electronics
related expression list.  Either ignore him or blacklist him from the
mailing list.

---
On Mon, 6 Feb 2023 16:00:45 +0100
Marcus Müller  wrote:
> Dear Matt,
> 
> this is just a quick reminder that this is the GNU Radio mailing list – 
> we're pretty open about the topics we discuss here, but your last three 
> emails were a bit far off.
> 
> Since (I think) you're new in this community: In case you wonder what 
> GNU Radio is exactly, there's a really nice introduction,
> https://wiki.gnuradio.org/index.php?title=What_Is_GNU_Radio
> 
> Best regards,
> Marcus
> 
> On 2/6/23 09:28, Matt Young wrote:
> > In ham radio we have twenty manufacturer all writing and producing 
> > their own LCD screens and menus. A nightmare.s Thy all started with 
> > DSP function then suddenly loads of investments into screens.
> >
> > Just add a USB port to the machines and plug in a chromebook, which 
> > costs 155.  Three hundred dollars save at the shack, money spent on 
> > pre and post analog for dealing with this chaotic atmosphere.
> >
> > The DSP is simple, we need in and out DACs at 8 mHz, 16 bit. We need 
> > ar least 80 Mflops of fixed point 32 bit signal 'taps'. Add in a 
> > separate center frequency LO on output.  Opens the market big time.  
> > Floating point does no good, if you did you Z transforms, 
> > everything should be scaled.
> > Your source code really is set of pure linear discrete inductance, 
> > capacitance and transconductance.  There are no parasitics.  We can 
> > generate assembly from Spice, then each DSP makerwrits thor own linker 
> > from Spice to DSP..
> >
> > Code never changes across bands.  The local oscillator mixes in the 
> > high precision interface to the antenna.  We really want the isolation 
> > of the digital from the horrors of atmospheric RF static.



Re: Also bothered

2023-02-06 Thread Bogdan Diaconescu
 Indeed Chris, that is right.
ChatGPT is that you?

On Monday, February 6, 2023 at 06:12:54 PM GMT+2, Chris Vine 
 wrote:  
 
 Read it again and you will see the posting was a spoof, artificially
mashed up by a random expression generator from a radio/electronics
related expression list.  Either ignore him or blacklist him from the
mailing list.

---
On Mon, 6 Feb 2023 16:00:45 +0100
Marcus Müller  wrote:
> Dear Matt,
> 
> this is just a quick reminder that this is the GNU Radio mailing list – 
> we're pretty open about the topics we discuss here, but your last three 
> emails were a bit far off.
> 
> Since (I think) you're new in this community: In case you wonder what 
> GNU Radio is exactly, there's a really nice introduction,
> https://wiki.gnuradio.org/index.php?title=What_Is_GNU_Radio
> 
> Best regards,
> Marcus
> 
> On 2/6/23 09:28, Matt Young wrote:
> > In ham radio we have twenty manufacturer all writing and producing 
> > their own LCD screens and menus. A nightmare.s Thy all started with 
> > DSP function then suddenly loads of investments into screens.
> >
> > Just add a USB port to the machines and plug in a chromebook, which 
> > costs 155.  Three hundred dollars save at the shack, money spent on 
> > pre and post analog for dealing with this chaotic atmosphere.
> >
> > The DSP is simple, we need in and out DACs at 8 mHz, 16 bit. We need 
> > ar least 80 Mflops of fixed point 32 bit signal 'taps'. Add in a 
> > separate center frequency LO on output.  Opens the market big time.  
> > Floating point does no good, if you did you Z transforms, 
> > everything should be scaled.
> > Your source code really is set of pure linear discrete inductance, 
> > capacitance and transconductance.  There are no parasitics.  We can 
> > generate assembly from Spice, then each DSP makerwrits thor own linker 
> > from Spice to DSP..
> >
> > Code never changes across bands.  The local oscillator mixes in the 
> > high precision interface to the antenna.  We really want the isolation 
> > of the digital from the horrors of atmospheric RF static.

  

Re: Installation of Gnuradio on Windows 11

2023-02-06 Thread Ryan Volz

Hi George,

The conda installation method and radioconda should work fine on Windows 11:

https://wiki.gnuradio.org/index.php/CondaInstall
https://github.com/ryanvolz/radioconda

This doesn't come in a debug-build version, but it is still possible 
develop OOT blocks on Windows in the same way that it is done on Linux 
by running `gr_modtool`, etc. Instructions for building OOTs within a 
conda environment can be found here:


https://wiki.gnuradio.org/index.php/CondaInstall#Building_OOT_modules_to_use_with_conda-installed_GNU_Radio

Cheers,
Ryan

On 2/6/23 11:07 AM, George Edwards wrote:

Dear GNURadio Community,

I plan to buy a PC with Windows 11. I looked online to see if folks were 
installing Gnuradio on Windows 11 and found nothing definitive. Please 
advise me if Gnuradio works on Windows 11.


I also noticed online that there was an installation package for Windows 
Debugging, does this mean one can develop their own OOT custom block in 
the Windows environment similar to the Linux environment?


Thank you very much!

Regards
George




Re: Installation of Gnuradio on Windows 11

2023-02-06 Thread John Sallay
Ryan has done a great job maintaining Windows support in conda. I'll throw
out that if you prefer, you can use the Windows subsystem for Linux to run
Linux based docker containers.

On Mon, Feb 6, 2023, 2:03 PM Ryan Volz  wrote:

> Hi George,
>
> The conda installation method and radioconda should work fine on Windows
> 11:
>
> https://wiki.gnuradio.org/index.php/CondaInstall
> https://github.com/ryanvolz/radioconda
>
> This doesn't come in a debug-build version, but it is still possible
> develop OOT blocks on Windows in the same way that it is done on Linux
> by running `gr_modtool`, etc. Instructions for building OOTs within a
> conda environment can be found here:
>
>
> https://wiki.gnuradio.org/index.php/CondaInstall#Building_OOT_modules_to_use_with_conda-installed_GNU_Radio
>
> Cheers,
> Ryan
>
> On 2/6/23 11:07 AM, George Edwards wrote:
> > Dear GNURadio Community,
> >
> > I plan to buy a PC with Windows 11. I looked online to see if folks were
> > installing Gnuradio on Windows 11 and found nothing definitive. Please
> > advise me if Gnuradio works on Windows 11.
> >
> > I also noticed online that there was an installation package for Windows
> > Debugging, does this mean one can develop their own OOT custom block in
> > the Windows environment similar to the Linux environment?
> >
> > Thank you very much!
> >
> > Regards
> > George
>
>


Re: Installation of Gnuradio on Windows 11

2023-02-06 Thread George Edwards
Hi Ryan,

Thanks you very much!

Thanks you everyone for your suggestion!

Regards,
George

On Mon, Feb 6, 2023, 12:03 PM Ryan Volz  wrote:

> Hi George,
>
> The conda installation method and radioconda should work fine on Windows
> 11:
>
> https://wiki.gnuradio.org/index.php/CondaInstall
> https://github.com/ryanvolz/radioconda
>
> This doesn't come in a debug-build version, but it is still possible
> develop OOT blocks on Windows in the same way that it is done on Linux
> by running `gr_modtool`, etc. Instructions for building OOTs within a
> conda environment can be found here:
>
>
> https://wiki.gnuradio.org/index.php/CondaInstall#Building_OOT_modules_to_use_with_conda-installed_GNU_Radio
>
> Cheers,
> Ryan
>
> On 2/6/23 11:07 AM, George Edwards wrote:
> > Dear GNURadio Community,
> >
> > I plan to buy a PC with Windows 11. I looked online to see if folks were
> > installing Gnuradio on Windows 11 and found nothing definitive. Please
> > advise me if Gnuradio works on Windows 11.
> >
> > I also noticed online that there was an installation package for Windows
> > Debugging, does this mean one can develop their own OOT custom block in
> > the Windows environment similar to the Linux environment?
> >
> > Thank you very much!
> >
> > Regards
> > George
>
>


compiling GR 3.10.5.1 with ENABLE_GR_SOAPY=ON

2023-02-06 Thread aardric
I executed the following steps which I think are consistent with
documentation on the wiki.

(1) local installation of SoapySDR 0.7.2 appears to work.
(2) build and local install of gnuradio 3.10.5.1 works as expected with
-DENABLE_GR_SOAPY=OFF
(3) delete the gnuradio/build folder and run cmake with
-DENABLE_GR_SOAPY=ON configures without an obvious problem.
(4) however, make fails with:
include/gnuradio/soapy/soapy_types.h:15:10: fatal error:
SoapySDR/Types.hpp: No such file or directory
    15 | #include 

I'm hoping to get advice on whether the above procedure was reasonable
before I (as a non developer) attempts to reverse engineer and debug the
above process. I hesitate to raise an issue for something which may be
obvious or a problem with my particular installation.

Rick





Re: compiling GR 3.10.5.1 with ENABLE_GR_SOAPY=ON

2023-02-06 Thread Ron Economos

You probably need the development package.

sudo apt-get install libsoapysdr-dev

Ron

On 2/6/23 18:37, aardric wrote:

I executed the following steps which I think are consistent with
documentation on the wiki.

(1) local installation of SoapySDR 0.7.2 appears to work.
(2) build and local install of gnuradio 3.10.5.1 works as expected with
-DENABLE_GR_SOAPY=OFF
(3) delete the gnuradio/build folder and run cmake with
-DENABLE_GR_SOAPY=ON configures without an obvious problem.
(4) however, make fails with:
include/gnuradio/soapy/soapy_types.h:15:10: fatal error:
SoapySDR/Types.hpp: No such file or directory
     15 | #include 

I'm hoping to get advice on whether the above procedure was reasonable
before I (as a non developer) attempts to reverse engineer and debug the
above process. I hesitate to raise an issue for something which may be
obvious or a problem with my particular installation.

Rick