Re: [Discuss-gnuradio] DVB-S2/X Block Party at GNU Radio Conference 2018

[Michelle Thompson]

"Enthusiastic Yes" on RFNoC.

Our assumption is that we will need RFNoC. I think we could certainly use
some advice on workflow.

The LDPC FEC decode effort right now includes attempts with Xilinx SDSoC to
convert functions from the GPU codebase into hardware accelerated FPGA
code. From there, package for RFNoC.

This plan has advantages and disadvantages. We're here to learn and
contribute whatever we can.

We have several SDSoC licenses and several full Vivado licenses. We have at
least one X310, several B210s, and a variety of other FPGA dev boards
(Snickerdoodls, Ultra96, etc).

We have plenty of Plutos and some LimeSDRs.

-Michelle W5NYV


On Wed, Jun 20, 2018 at 3:42 PM, Dan CaJacob  wrote:

> I'd suggest incorporating RFNOC at least as an option. I suspect actual
> use of DVBS2X might be rather boring if you're stuck on a processor.
>
> On Wed, Jun 20, 2018 at 4:38 PM Michelle Thompson <
> mountain.miche...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> GNU Radio Conference is coming up in September. If you haven't registered
>> and want to go, please do at https://www.gnuradio.org/grcon-2018/
>>
>> There's a special event this year called Block Party.
>>
>> It's an effort to get DVB-S2 and DVB-S2X receivers in GNU Radio.
>>
>> We will have our own room and tables and swag. We will have docents
>> enthusiasm and test equipment. We're looking for more! We'll have
>> documentation and refreshments.
>>
>> We need blocks!
>>
>> Most blocks needed for DVB-S2/X receive do, in some form, already exist.
>> Some do not. Some just need additional modulation and codings added to
>> them.
>>
>> Receiver design is hard, but breaking it up into small blocks makes it
>> tractable.
>>
>> The DVB protocol documents are all open. There are implementation
>> guidelines. See https://www.dvb.org/
>>
>> There are several community members that are experts in this area. There
>> is a team (Phase 4 Ground - find out more at https://phase4ground.github.
>> io/) that needs DVB-S2/X to work in GNU Radio. There is a lot of
>> interest from a variety of other groups including Libre Space, ARRL, AMSAT,
>> and TAPR.
>>
>> If you are able to contribute to this effort, I want to know about it! I
>> am here to support it. I'd like nothing better than to complete the Block
>> Party at GNU Radio Conference with working, tested, documented blocks for a
>> DVB-S2/X receiver. This contribution makes our open source terrestrial and
>> space radio designs for Phase 4 Ground possible, and also opens up a lot of
>> other work.
>>
>> The thing that is considered the hardest part is the LDPC FEC decode. We
>> have an open source implementation that targets GPUs. We want to take this
>> and get it into RFNoC. If you are working on this as well, we want to
>> collaborate and support and combine and promote.
>>
>> The GPU implementation (by Charles Brain G4GUO) of LDPC decode can be
>> found at our repository folder here: https://github.com/
>> phase4ground/DVB-receiver/tree/master/G4GUO-LDPC-on-GPU/DVB-S2XTxRx
>>
>> Phase 4 Ground is devoted to an open source implementation of DVB-S2 and
>> DVB-S2X for amateur radio terrestrial and space use. We are part of Open
>> Research Institute. Learn more about this non-profit here:
>> https://openresearch.institute/
>>
>> -Michelle W5NYV
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
> --
> Very Respectfully,
>
> Dan CaJacob
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Project Call Tomorrow!

[Martin Braun]

Many apologies, but we're cancelling the call last-minute due to
short-term scheduling conflicts.

Cheers,
Martin

On 06/20/2018 07:02 PM, Martin Braun wrote:
> Hi all,
> 
> there's another project call coming tomorrow 10 AM Pacific, or 19:00 EU
> time. I'll send out coordinates closer to the call, if you want to join,
> come to #gnuradio on Freenode or Slack.
> 
> Cheers,
> Martin
> 
> ___
> 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] Regarding usrp b200mini

[Marcus D. Leech]

On 06/21/2018 12:53 PM, Sai Parepalli Laxman wrote:

Hello,
Thanks for the info.

Also, I tried installing gnuradio and uhd from the build-gnuradio 
script and "make failed"


I have attached the screen shot below.
Could you point me in the right direction?

Thanks
Looks like some code deep-down in the gr-fec tree isn't compiling on 
your system.


You could have build-gnuradio pull from "master":

build-gnuradio -m -v

And see if that changes anything.




On Thu, Jun 21, 2018 at 11:52 AM, Marcus D. Leech > wrote:


On 06/21/2018 09:26 AM, Sai Parepalli Laxman wrote:

Hello,

I was trying to ping usrp b200mini at 192.168.10.2 from the host
computer but there is no repsonse from the device.

--- 192.168.10.2 ping statistics ---
17 packets transmitted, 0 received, 100% packet loss, time 16365ms

What could be the issue?

Thanks

The issue is that the B2xxx (and, indeed, all of the USB-connected
USRPs) are not network-connected devices.  They don't have an IP
address--
  they don't speak IP.  They're connected over USB, not ethernet.





On Wed, Jun 20, 2018 at 3:57 PM, Marcus D. Leech
mailto:mle...@ripnet.com>> wrote:

On 06/20/2018 03:13 PM, Sai Parepalli Laxman wrote:

Yes, I will refer that.

I am trying to decode the P25 signal using b200mini on
ubuntu 16.04 using gnuradio.

I have the P25 receiver(demodulator + receiver) open source
code compiled and running but how do I make it work
with usrp b200mini?

How would I go about that?

I'm sorry if I am vague but I am ready to provide additional
details.

Thanks

There's probably an e-mail list devoted specifically to that
software--you might try there.






On Wed, Jun 20, 2018 at 3:00 PM, Marcus D. Leech
mailto:mle...@ripnet.com>> wrote:

On 06/20/2018 02:55 PM, Sai Parepalli Laxman wrote:

The device address should be entered as the one that
shows up when I command uhd_find_devices?

This shows up when I run uhd_find_devices

UHD Device 0

Device Address:
serial: 31216B8
name:B200mini
type: b200

Thanks for your time

https://files.ettus.com/manual/page_identification.html


In your case:

type=b200

Will work, but I suggest spending some time with the
online UHD manual, and the Ettus Knowledge base:

https://kb.ettus.com/Knowledge_Base





On Wed, Jun 20, 2018 at 2:51 PM, Marcus D. Leech
mailto:mle...@ripnet.com>> wrote:

On 06/20/2018 02:40 PM, Sai Parepalli Laxman wrote:

Both Gnuradio and UHD support was build from
source code with all dependencies. The block shows
up but I am not able to run the flow graph?

What does "not able to run the flow-graph" mean,
precisely? We can only help you if we have details
and "it doesn't work" is too hand-wavy
  to provide adequate assistance.



Does GNURadio companion identify the device?
What do you mean by "identify the device".  
There's a "device address" field in any UHD

source/sink.   It must be filled out to tell it what
  UHD device you'd like your flow-graph to talk
to.  You could have more than one on a system, and
there are many different types of
  USRP devices. UHD (and by inference, Gnu Radio)
has no way of knowing what your intention is.  You
have to tell it.




On Wed, Jun 20, 2018 at 2:35 PM, Marcus D. Leech
mailto:mle...@ripnet.com>> wrote:

On 06/20/2018 02:17 PM, Sai Parepalli Laxman
wrote:

Hey guys,

I am fairly new to gnuradio companion but
I was trying to use the UHD: USRP source
block in the environment with my usrp
b200mini but it does not show up.

How do I verify this?
What do I need to put in the device address?

-> uhd_find_devices and uhd_usrp_probe are
able to load the image and the device
correctly.

Thanks in advance.

You mean the block doesn't show up in Gnu Radio?

If so, that means your local instance of Gnu
Radio was built without UHD support.  How was
   

[Discuss-gnuradio] Need help with docs/sphinx

[Gisle Vanem]

I'm on Windows-10 trying to build the Python docs using
'sphinx-build -b html'. As the README says, it's really
best suited for Unix with it's run_sphinx_build.sh.

Anyway, I tried with this GNU-make snippet
in docs/my-doc.mak:

PY_PATH  = $(SITE_DIR)
PYD_PATH = ... all the paths under $(SITE_DIR)/gnuradio here

define generate_sphinx
  echo "Creating Sphinx documentation in: $(realpath $(2))."
  export PYTHONPATH='$(PY_PATH);$(PYD_PATH);$(PYTHONPATH)' ; \
  sphinx-build -q -T --no-color -b html $(1) $(2) 2> sphinx.log
endef

# And BTW, I need to export with PYTHONPATH in quotes, otherwise
# 'bash' complains.

sphinx/source/conf.py: sphinx/source/conf.py.in
  sed -e 's|@VERSION@|$(VERSION)|g'  \
  -e 's|@CMAKE_CURRENT_SOURCE_DIR@|$(realpath sphinx)|g' \
  -e 's|@CMAKE_INSTALL_PREFIX@|$(BUILD_DIR)|g'   \
  -e 's|@GR_PYTHON_DIR@|lib/site-packages|g'  < $< >> $@

sphinx: sphinx/source/conf.py
   $(call generate_sphinx, sphinx/source, sphinx/out)

--

It doesn't work; I get 15600 lines of traceback and errors in the
sphinx.log file; none (few?) of the .pyd files are found. I think
I'm invoking sphinx-build with the correct PYTHONPATH.
Here is one of those errors:

WARNING: F:\gv\dx-radio\gnuradio\docs\sphinx\source\analog.rst:4:
(WARNING/2) autodoc: failed to import class u'cpm' from module 
u'gnuradio.analog';
the following exception was raised:
Traceback (most recent call last):
  File "f:\programfiler\python27\lib\site-packages\sphinx\ext\autodoc.py", line 
658, in import_object
__import__(self.modname)
  File 
"F:\gv\dx-radio\gnuradio\MSVC-build\lib\site-packages\gnuradio\analog\__init__.py", 
line 33, in 
from analog_swig import *
  File 
"F:\gv\dx-radio\gnuradio\MSVC-build\lib\site-packages\gnuradio\analog\analog_swig.py",
 line 26, in 
_analog_swig = swig_import_helper()
  File "F:\gv\dx-radio\gnuradio\MSVC-build\lib\site-packages\gnuradio\analog\analog_swig.py", line 22, in 
swig_import_helper

_mod = imp.load_module('_analog_swig', fp, pathname, description)
ImportError: DLL load failed: The given module was not found << translated from 
Norwegian.

---

even though I have a
F:\gv\dx-radio\gnuradio\MSVC-build\lib\site-packages\gnuradio\analog\_analog_swig.pyd

and obviously a 'analog_swig.py' in the correct place, no?
Where is the Swig-generated code expecting the .pyd to exist?

And do I really need all these paths for Sphinx to find it's stuff?
It seems it wants more PATHS than that.

I'm not sure what '@GR_PYTHON_DIR@' should be substituted with.
But with the above, it writes this in the generated shpinx/source/conf.py:
  sys.path.insert(0, os.path.abspath('F:/gv/dx-radio/gnuradio/docs/sphinx'))
  sys.path.insert(0, 'F:/gv/dx-radio/gnuradio/MSVC-build/lib/site-packages')

Is that correct?

--
--gv

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