[Discuss-gnuradio] [UHD] 3.14.0.0 Release Announcement

[Michael West]

UHD 3.14.0.0 is now available!  This is an API release spawning the new
UHD-3.14 branch.  This API release introduces support for the N320 and N321
USRPs soon to be released (watch for the announcement on ettus.com!), a
DPDK-based transport, and several other features and bug fixes.  This
release includes all bug fixes and enhancements in the 3.13.0.1, 3.13.0.2,
and 3.13.1.0 maintenance releases.

Installers for Windows and Fedora are available here:
http://files.ettus.com/binaries/uhd/uhd_003.014.000.000-release/

The PPA for Ubuntu will be available soon and will be found here:
https://launchpad.net/~ettusresearch/+archive/ubuntu/uhd

The tag for this release is located here:
https://github.com/EttusResearch/uhd/releases/tag/v3.14.0.0

There have been 466 commits since the last API release which can be viewed
here:
https://github.com/EttusResearch/uhd/compare/v3.13.0.0...v3.14.0.0

Please report any bugs found on the UHD issue tracker:
http://github.com/EttusResearch/uhd/issues
* Please do not use the issue tracker for help or support.

Pull requests for direct code changes can be submitted to the UHD or FPGA
repositories:
http://github.com/EttusResearch/uhd/pulls
http://github.com/EttusResearch/fpga/pulls

As always, we at Ettus Research would like to thank all of the UHD users in
the open source SDR community.  This release contains commits from users in
the community that submitted pull requests against the UHD
 and FPGA
 repositories as well as many
commits that are a direct result of issues reported back to us by users
like you through the UHD  and
FPGA  issue trackers,
the USRP-users
mailing list
, and Ettus
support .  You have all helped contribute to the
continued improvement of UHD.  Thank you!

CHANGELOG:
## 003.014.000.000
* N320: Add support for N320 and N321
* USRP-2974: Add support for USRP-2974
* DPDK: Add DPDK-based sockets-like library (for N3xx)
* N3xx: clocking API changes for transitioning clock and time sources
* N3xx: Bump max rev to G/6
* N3xx: Improve error messages for invalid clock/time settings
* N3xx: Get RFNoC crossbar baseport from FPGA
* N3xx: init peripherals before loading FPGA (to fix SFP0 init issues)
* N3xx: Move Linux kernel to 4.15
* N3xx/E320: Prepend SDK filename with device name
* N3xx: Update max rev to 7 (H)
* N3xx: Remove DDR3 from standard BIST collection
* N3xx: BIST: Improve DDR3 BIST to check for DmaFIFO
* N3xx: BIST: Auto-load the AA image for the ddr3 BIST
* N3xx: BIST: DDR3 test only enumerates first block
* N310: Modify AD9371 reset function to keep it in reset
* N310: move init_rf_cal before JESD de/framer bringup
* N310: Fix sporadic power on failures (requires firmware update)
* E3xx: Increase spp limit for E3xx radio
* E320: bist: Fix ref_clock lock test implementation
* E320: bist: Add link_up test
* E320: Add all 5 temp sensors, fan sensor and rssi sensors per channel
* E320: Fix tx/rx atr - antenna and frequency settings
* E320: Enable devtest for E320
* E320: images: Separate images package for Aurora image
* E320: Get RFNoC crossbar baseport from FPGA
* E320: add fpga_version_hash to e320 device info
* E310: Fix initialization of antenna and frequency values
* E31x: Destruct RFNoC before loading idle image
* X300: Reduce default send_frame_size to 4000 over Ethernet
* X300: Change Ethernet buffering
* X300: Log git hash and compat number as debug message
* X300: Move defaults to their own header
* X300: Use constrained_args
* X300: Enable clock_source and time_source device args
* X300: NIRIO: Demote RPC client cancel/abort to TRACE
* X300: remove default_buff_args properties
* X300: Remove 120 MHz master_clock_rate option
* X300: Set minimum master clock rate to 184.32 MHz
* X300: Factor our PID -> MB type and MB type -> product name mapping
* X300: Remove usage of boost::bind
* X300: Fix compiler warnings related to type conversions
* X300: Fix tick and sample rate setting
* X300: Enable ADC gain through RFNoC API
* X300: Demote NIRIO rpc client start/stop log messages to DEBUG
* X300: Enable 11.52 MHz and 23.04 MHz system ref rates
* X300: Enable x300_device_args.to_string()
* X300: Catch more inconsistencies in x300_device_args
* X300: Removed invalid 200 MHz sysref rate
* X300: Change PLL CP currents in x300_clock_ctrl
* B200: Remove superfluous fake lambda
* B200: Add support for user regs
* B200: Fix compiler warnings related to type conversions
* B100: Move fifo_ctrl_excelsior to b100 subdir
* B100: Fix fifo_ctrl_excelsior not exiting
* B100: Remove all Boostisms from fifo_ctrl_excelsior
* B100: Demote some clocking-related log messages to trace
* MPM: Get list of temperatures from all thermal zones
* MPM: add link_speed xport_info
* MPM: Add __mpm_device__ as usrp_hwd module variable
* MPM: Add 

[Discuss-gnuradio] Software Defined Radio Academy 2019

[Markus Heller]

Dear lists,

please find our Call for Papers below.

BR / vy73
Markus Heller, M.A. DL8RDS
Prof. Dr. Michael Hartje DK5HH

> 
> 
> > 
> > 
> > > 
> > > 
> > > > 
> > > > 
> > > > > 
> > > > > 
> > > > > 
** apologies for cross-posting **
Call for Papers: SDRA-2019 Friedrichshafen

HAMRADIO Friedrichshafen Software Defined Radio Academy 2019 (SDRA-
2019)

Date: Saturday 22.06.2019

Conference Websites:

http://www.hamradio-friedrichshafen.de
http://2019.sdra.io

SDRA-2019 invites radio amateurs and researchers from acadaemia and
industry to submit papers for oral and poster presentations on recent
research that addresses theoretical aspects, algorithms, applications,
hardware and software architectures for applied Software Defined Radio
systems and resources and other aspects of SDR, as well as survey and
discussion papers. The invitation particularly addresses open source
research and projects. We also particularly invite specialists giving
introductory talks and tutorials on SDR technologies.
SDRA Topics:

Advances in GNURadio related projects and research
Algorithms, applications, architectures in SDR systems
Real Time signal processing
Innovative applications using modern ADC/DAC environments

Submission Information

How to submit: Please send an abstract of approximately 250 words to:

s...@darc.de

Please include the following information:

Paper title
Author's name (and callsign). Names and callsigns of all authors if
multiple authors.
Author's affiliation
Country
Email address of the main author

All accepted papers will be published. Publication details will be
available at a later point of time.

We ask authors to keep a limit of 6 pages. If there is a reason why the
paper should be longer, please contact us.

We also solicit Posters and Demo papers: Poster/Demo papers describe a
small focused result, a negative result, or a late-breaking result, or
a description of a system that can be demonstrated on-site at the
conference.

Papers should be formatted using the IEEE A4 templates: http://www.ieee
.org/conferences_events/conferences/publishing/templates.html
Organization

Prof. Dr. Michael Hartje, DK5HH
Markus Heller, M.A., DL8RDS

Senior Programme Committee

Prof. Dr. Michael Hartje, HS Bremen, DK5HH
Prof. Dr. Michael Niemetz, OTH Regensburg, DG2RAM
Prof. Dr. Michael Mächtel, HTWG Konstanz, DL2SBS

Important Dates:

Abstract Submission: 31.03.2019
Acceptance Notification: 15.04.2019
Presentation Slides: 31.05.2019
Paper Presentation: 22.06.2019
Paper Submission: 31.07.2019

Contact

For enquiries and paper submission details please do not hesitate to
contact us:

Email: s...@darc.de Tel.: +49.89.420956305-0

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

Re: [Discuss-gnuradio] Block Output as a Variable for Another Block

[Luis Felipe Albarracin Sanchez]

Thank you Martin,

I will try that and let everybody knows about the result.

Kind regards.

On Thu, Mar 21, 2019 at 12:25 PM Martin Braun 
wrote:

> On Mon, Mar 18, 2019 at 02:44:30PM -0500, Luis Felipe Albarracin Sanchez
> wrote:
> >Hello all,
> >I am trying to make the output of a block a variable for other
> blocks, as
> >explained here:
> >
> https://lists.gnu.org/archive/html/discuss-gnuradio/2012-02/msg00581.html
> >My flowgraph is as follows:
> >Captura de pantalla 2019-03-18 a la(s) 2.38.42 p. m..png
> >The  configuration of the block "Variable" is:
> >Captura de pantalla 2019-03-18 a la(s) 2.38.54 p. m..png
> >I was wondering if there are other ways for doing this?Is there a
> >specific control block that changes an output to a variable?.is
> there
> >any other way of making an output as a variable?.Â
> >Once again, thank you for the help.
>
> Usually, the easiest way is to pipe your output into a Python block, and
> then do whatever Pythonic thing you want to do from there.
>
> -- M
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>


-- 
Eng. Luis Felipe Albarracin
Msc. Telematics / MBA
PMP
CCNA/CCDA/CCNP/CCDP/CCIP
ITIL v3 Foundation
"Die Grenzen meiner Sprache bedeuten die Grenzen meiner Welt"
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] OOT modules on Android

[Ben Hilburn]

Hey Laura -

Yes, you can build OOTM for use on Android - you'll just have to build them
using a manual process (e.g., Android Studio) rather than something more
automatic like PyBOMBS.

Keep us posted on your progress! Excited to hear you'll be working on this
=)

Cheers,
Ben

On Tue, Mar 26, 2019 at 1:21 AM Laura Arjona  wrote:

> Thank you very much Ben,
>
> The OOT blocks that I want to run in Android are written in C++ entirely.
> My question is related to your comment "as long as they are built
> appropriately".
> That is, if it is possible to build OOT blocks to use in Android. But
> reading your message, I assume that is possible.
>
> I knew the link, thanks, but haven't started the android project yet,
> staring this week. Excited to start my project.
>
> Thanks
>
>
>
>
>
>
>
> On Mon, Mar 25, 2019 at 11:11 AM Ben Hilburn 
> wrote:
>
>> Hi Laura -
>>
>> Sorry for the delayed response, here.
>>
>> So, I'm not entirely sure I understand your question, actually. Once GNU
>> Radio is running in Android, using blocks from any module, in- or
>> out-of-tree, shouldn't be a problem as long as they are built
>> appropriately. Are you asking if you need to re-write Python-only blocks in
>> C++? If the OOTM only provides Python blocks, then yes, you'll want to put
>> those into C++ for use on Android.
>>
>> Also, I assume you've already seen the pages linked here, which provide a
>> lot more detail on that build process -- although the information is pretty
>> severely dated at this point, and almost certainly won't work as-is.
>>
>> https://wiki.gnuradio.org/index.php/Android
>>
>> Cheers,
>> Ben
>>
>> On Fri, Mar 22, 2019 at 12:36 PM Laura Arjona  wrote:
>>
>>> I might have been thinking about this in the wrong way.
>>>
>>> The way to proceed would be to re-write the blocks in Android studio,
>>> using C++?
>>> (instead of importing the blocks created with gr-modtool)
>>>
>>>
>>> Thank you and good weeked!
>>>
>>> On Thu, Mar 21, 2019 at 7:44 PM Laura Arjona  wrote:
>>>
 Hi everyone,

 I want to build an Android App to communicate with an USRP B200-mini,
 and this app should use one OOT module with several oot blocks.

 How should I proceed to import my OOT module?

 Thank you


>>>
>>> --
>>> *Laura Arjona *
>>> Washington Research Foundation Innovation Postdoctoral Fellow in
>>> Neuroengineering
>>>
>>> *Paul G. Allen School of Computer Science & Engineering*
>>> 185 E Stevens Way NE
>>> University of Washington
>>> Seattle, WA 98195-2350
>>> ___
>>> Discuss-gnuradio mailing list
>>> Discuss-gnuradio@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>
>
> --
> *Laura Arjona *
> Washington Research Foundation Innovation Postdoctoral Fellow in
> Neuroengineering
>
> *Paul G. Allen School of Computer Science & Engineering*
> 185 E Stevens Way NE
> University of Washington
> Seattle, WA 98195-2350
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] howto create multiple carriers with usrp

[Ron Economos]

A multiply constant block is needed to reduce the level for actual 
transmission with an SDR. It should be set to 1 / (number of active 
carriers).


Also an odd number of carriers produces a cleaner spectrum. Updated flow 
graph attached.


Ron

On 3/26/19 04:55, Ron Economos wrote:


Just use an inverse FFT. Flow graph attached.

In the vector source, just zero out carriers you don't want.

Ron

On 3/26/19 00:45, on4...@telenet.be wrote:

Hi group,

I want to create 10 or 20 or 30 carriers all spaced evenly at 250Khz 
apart.

How can i do this, any tips?

thanks

___
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


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

Re: [Discuss-gnuradio] howto create multiple carriers with usrp

[Ron Economos]

Just use an inverse FFT. Flow graph attached.

In the vector source, just zero out carriers you don't want.

Ron

On 3/26/19 00:45, on4...@telenet.be wrote:

Hi group,

I want to create 10 or 20 or 30 carriers all spaced evenly at 250Khz 
apart.

How can i do this, any tips?

thanks

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


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

Re: [Discuss-gnuradio] howto create multiple carriers with usrp

[Michael Dickens]

Use a polyphase filterbank. It's not runtime reconfigurable in GR, but if you 
create the correct spacing with the max you'll ever need then you can always 
optionally direct the output of some to a null sink. Hope this is useful! - MLD

On Tue, Mar 26, 2019, at 3:46 AM, on4...@telenet.be wrote:
> Hi group,
> 
> I want to create 10 or 20 or 30 carriers all spaced evenly at 250Khz apart.
> How can i do this, any tips?
> 
> thanks
> ___
> 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] Runtime error

[5G SOLUTIONS _Pvt_ Ltd]

Hi Everyone.
can u please let me know how to solve runtime error issue and also somtimes
device serial number not found.
Thanking you

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

[Discuss-gnuradio] howto create multiple carriers with usrp

[on4bhm]

Hi group, 

I want to create 10 or 20 or 30 carriers all spaced evenly at 250Khz apart. 
How can i do this, any tips? 

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