[Discuss-gnuradio] USRP2 reference clock

2016-04-13 Thread Nils Hollmach
Dear Sir or Madam, At present I work with 2 different USRPs. One of this is the USRP2 and the another one a newer device is the X300. This devices communicate each about QPSK and a test algorithm. For the USRP2 I use the reference input and use reference clock output from the x300 device to com

Re: [Discuss-gnuradio] raspi FAQ/HOWTO/recipe ??????

2016-04-13 Thread Marcus Müller
Hi Rob, so, first of all: I recommend doing the compilation on a PC (cross-compiling). In all experiences I've known of, compiling on something as weak and RAM-sparse as the Pi takes nights, and needs a lot of swap memory, making it impractical. Also note that setting up the cross-compilation envi

Re: [Discuss-gnuradio] USRP2 reference clock

2016-04-13 Thread Marcus Müller
Hi Nils, So, could you share your flow graph, or a sketch of it? Especially (asked you on SO, too): Do you use one uhd_usrp_source, or two? And: how do you tell the source(s) which USRP to use? To answer the easy-to-answer questions right now: > Is it possible to set the master clock at the USRP

[Discuss-gnuradio] Setting up a new block

2016-04-13 Thread Ankit Saharia
I looked for setting up a new block in windows version of GNURadio. I wanted to know whether it is possible or not? Thank You ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Setting up a new block

2016-04-13 Thread Marcus Müller
Yes; why not? Have you gone through the guided tutorials [1]? They explain the process pretty well. Just a note: If you're new to GNU Radio, I'd actually recommend using Linux, for example the liveSDR environment[2], which works without installation. That will save you a lot of trouble of the kind

Re: [Discuss-gnuradio] raspi FAQ/HOWTO/recipe ??????

2016-04-13 Thread Rob Roschewsk
Marcus, Thanks for responding. I'm looking to build a headless FM receiver to record and stream public service communication (fire, police, etc.). We will stream as many channels as possible that fall into a given passband. I already have a system running on a PC and now would like to port it to

[Discuss-gnuradio] B2xx rates

2016-04-13 Thread Alexander Levedahl
Hello, Is there a list of sample rates and associated bandwidths supported by the B2xx series or a way to generate the list? E.g., the list for the X310 is to take 120MHz, 184.32MHz, and 200MHz and divide by an integer. Thanks, Alex ___ Discuss-gnuradi

[Discuss-gnuradio] Feedback with Transmitters and Receiver

2016-04-13 Thread Pavan Yedavalli
Hi, I have been trying to do some research using MIMO transmitters and feedback from a receiver. Specifically, I have two antennas connected to two USRPs, and I am transmitting the same signal from both of those (MIMO synchronized) to another USRP and antenna.This receive USRP and antenna needs to

Re: [Discuss-gnuradio] B2xx rates

2016-04-13 Thread Ron Economos
The B2X0 series has a programmable master clock. You can set it to anything from 200 kHz to 56 MHz. Ron On 04/13/2016 05:55 AM, Alexander Levedahl wrote: Hello, Is there a list of sample rates and associated bandwidths supported by the B2xx series or a way to generate the list? E.g., the lis

Re: [Discuss-gnuradio] B2xx rates

2016-04-13 Thread Ron Economos
Correction. The master clock rate can be set to anything from 5 MHz to 56 MHz. The bandwidth is 200 kHz to 56 MHz. Ron On 04/13/2016 07:46 AM, Ron Economos wrote: The B2X0 series has a programmable master clock. You can set it to anything from 200 kHz to 56 MHz. Ron On 04/13/2016 05:55 AM,

Re: [Discuss-gnuradio] B2xx rates

2016-04-13 Thread Alexander Levedahl
So, it can be set to say 50.3+pi/10MHz? On Wed, Apr 13, 2016 at 10:55 AM, Ron Economos wrote: > Correction. The master clock rate can be set to anything from 5 MHz to 56 > MHz. The bandwidth is 200 kHz to 56 MHz. > > Ron > > > On 04/13/2016 07:46 AM, Ron Economos wrote: > >> The B2X0 series has

Re: [Discuss-gnuradio] B2xx rates

2016-04-13 Thread Ron Economos
Yes. I routinely set it to ((800 * 6) / 7) * 4 for DVB-T2 applications. Ron On 04/13/2016 08:32 AM, Alexander Levedahl wrote: So, it can be set to say 50.3+pi/10MHz? On Wed, Apr 13, 2016 at 10:55 AM, Ron Economos > wrote: Correction. The master clock rate ca

[Discuss-gnuradio] problem with gr-osmosdr so file

2016-04-13 Thread Jason Matusiak
> I tried blowing away osmosdr and rebuilding, but that doesn't seem tohelp. What am I missing here? It objdump on the culprit so, I see: objdump -x /home/jmat/target/lib/libosmodsp.so.0.0.0 > BFD: /home/jmat/target/lib/libosmodsp.so.0.0.0: don't know how to handlesection `' [0x 1b] BFD:

Re: [Discuss-gnuradio] problem with gr-osmosdr so file

2016-04-13 Thread Ron Economos
I'm going to guess it's actually a problem with gr-iqbal. gr-iqbal has a submodule for libosmodsp, so the correct build procedure is: git clone git://git.osmocom.org/gr-iqbal.git cd gr-iqbal git submodule init git submodule update mkdir build cd build cmake .. make sudo make install Ron On 04/

Re: [Discuss-gnuradio] problem with gr-osmosdr so file

2016-04-13 Thread Jason Matusiak
Gents, thanks for jumping in! So in the OP case, the first option was chosen. Best is to just download libosmodsp and rebuild it on its own. Rebuilding gr-iqbal won't really do anything. I ran pybombs uninstall libosmosdr-dsp and then pybombs install libosmosdr-dsp (the older pybombs) and it a

Re: [Discuss-gnuradio] problem with gr-osmosdr so file

2016-04-13 Thread Sylvain Munaut
gr-iqbal can work in two modes : - If it finds libosmodsp installed and available on the system, it will use that and dynamic link to it - If it doesn't, then it can use a submodule checkout of it and just directly build in the required .c file. In that mode, it won't link to libosmodsp.so at al

Re: [Discuss-gnuradio] B2xx rates

2016-04-13 Thread Ian Buckley
For what (little) it's worth I removed the H/W constraints in B2x0 that forced a minimum of 5MHz master clock rate when UHD 3.9.x was released. Running AD9361 at low clock rates isn't the best way to utilize its capabilities but it may help for certain niche narrow band applications. -Ian On Wed

[Discuss-gnuradio] Docker

2016-04-13 Thread Nicholas McCarthy
Sorry I'm a few days late to the Docker party (and I don't have the original thread at hand). Thanks, Stefan, for sharing your work. I want to share something similar I worked up for my stack when Martin released pybombs2 and exposed me to the "deploy" function. https://hub.docker.com/r/namccart

Re: [Discuss-gnuradio] B2xx rates

2016-04-13 Thread Alexander Levedahl
Out of curiosity, when you say B2x0, did you mean to exclude the B205 mini? Alex On Wed, Apr 13, 2016 at 2:16 PM, Ian Buckley wrote: > For what (little) it's worth I removed the H/W constraints in B2x0 that > forced a minimum of 5MHz master clock rate when UHD 3.9.x was released. > Running AD93

Re: [Discuss-gnuradio] B2xx rates

2016-04-13 Thread Ian Buckley
OK, to be precise {B200|B205|B200mini|B210} should have the same common base platform in the FPGA including the interface used for the radio. B230 is different. If wish to understand further the exact significance of the USRP model numbers I suggest you start here: http://dilbert.com/strip/1992-04-

Re: [Discuss-gnuradio] B2xx rates

2016-04-13 Thread Martin Braun
Just want to confirm this. The correct rate range is from 220 kHz to 61.44 MHz, or 30.72 MHz for 2x2 mode. The *analog* bandwidth is capped at 56 MHz. M On 04/13/2016 11:16 AM, Ian Buckley wrote: > For what (little) it's worth I removed the H/W constraints in B2x0 that > forced a minimum of 5MH

Re: [Discuss-gnuradio] problem with gr-osmosdr so file

2016-04-13 Thread Martin Braun
I believe we have the PyBOMBS dependency issues sorted out, so if you use pybombs (and e.g. 'pybombs rebuild') it will do stuff in the right order. M On 04/13/2016 09:35 AM, Ron Economos wrote: > I'm going to guess it's actually a problem with gr-iqbal. gr-iqbal has a > submodule for libosmodsp,

Re: [Discuss-gnuradio] raspi FAQ/HOWTO/recipe ??????

2016-04-13 Thread Jean Luc
I've been trying as well to use GR on RPi (model 3), the ultimate purpose would be radio astronomy. A smaller form factor such as RPI's makes a remote installation more palatable than a full PC. I wasn't able to compile it on RPi but compromised on using a more recent version (3.7.9-3~bpo8+1) take

Re: [Discuss-gnuradio] raspi FAQ/HOWTO/recipe ??????

2016-04-13 Thread Marcus D. Leech
On 04/13/2016 11:05 PM, Jean Luc wrote: I've been trying as well to use GR on RPi (model 3), the ultimate purpose would be radio astronomy. A smaller form factor such as RPI's makes a remote installation more palatable than a full PC. I wasn't able to compile it on RPi but compromised on using

Re: [Discuss-gnuradio] raspi FAQ/HOWTO/recipe ??????

2016-04-13 Thread Anon Lister
Have you seen [1]? it looks like he hit all the same issues I did when building on a pi3(raspberrian, not Debian but you might run into some of the same). The newer 3, as long as you give it some swap space can get the compile done in only a few hours with a make -j 3 or 4. http://lukeberndt.com/2

[Discuss-gnuradio] Question about packet sequence

2016-04-13 Thread SangHyuk Kim
Hi all, I'm wondering about packet sequence. USRP sends UDP packets which is result of sampling to host PC. UDP packets tend to be out-of-order at high speed. My question is: - When USRP sends UDP packet high speed to host PC, the sequence of these packets is important ? - Do host PC reorder t

Re: [Discuss-gnuradio] Question about packet sequence

2016-04-13 Thread Laur Joost
While UDP gives no order guarantee, the USRP still sends them out in order. The uncertainty comes in cases where routing happens between the USRP and the host. Still, within a LAN you can expect with relative certainty, that packets will still arrive in order, as there is usually only one route fro

Re: [Discuss-gnuradio] Question about packet sequence

2016-04-13 Thread SangHyuk Kim
Hi, I counted number of sending packet in code and wireshark. I send 400Bytes packet, but wireshark packet be shown about 1500Bytes. While coded counter shows about 50,000 packets (data packet), wireshark captured 450,000 packets. I expected one send() be represented one packet at wireshark. W