Re: [Discuss-gnuradio] Question about packet sequence

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.

Re: [Discuss-gnuradio] Question about packet sequence

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

Re: [Discuss-gnuradio] 3.7.9.2 Win64 binaries ready + Build scripts

All, Some may recall in the fall I posted a link to a beta windows installer. I'm happy to report that I'm releasing new versions today for the 3.7.9.2 release, compatible with Windows 7/8/10. All dependencies are included, and all are built natively using MSVC 2015, no Cygwin or MinGW required.

Re: [Discuss-gnuradio] Docker

> > I think it would be really helpful for the GNU Radio project to support a >> standard, basic gnuradio docker install with uhd and grc enabled as well as >> an example or two to demonstrate sane ways to run OOT modules on top of >> that image. As Ben mentioned, Docker seems like a pretty

Re: [Discuss-gnuradio] Question about packet sequence

On 04/14/2016 01:20 AM, Laur Joost wrote: > 1. The sequence of the packets is important. It would be rather bad if > two bunches of samples in your IQ stream suddenly switched places. > 2. The host PC network stack does no reordering. It can't, by definition > of UDP, as there's nothing to reorder

Re: [Discuss-gnuradio] Docker

On Thu, Apr 14, 2016 at 3:54 PM Nicholas McCarthy wrote: > Three points to make about this OOT Docker example. > 1) Everything you're doing manually here can be accomplished using > pybombs2... and pybombs2 makes itself quite amenable to existing within the > Docker image

Re: [Discuss-gnuradio] Docker

Three points to make about this OOT Docker example. 1) Everything you're doing manually here can be accomplished using pybombs2... and pybombs2 makes itself quite amenable to existing within the Docker image both as an interface to what's already installed on the image and a handy way to install

[Discuss-gnuradio] Synced MIMO cable clock of both boards changes at every call to tb.start()?

Does the start() function in GNURadio reinitialize the clocks on the USRPs every time it is called? I have two USRPs connected via MIMO cable, so they are synced, but my flowgraph calls start() after every loop, which I'm realizing may be changing the constant but random offset of the clock every

Re: [Discuss-gnuradio] Docker

Yeah, this is one of the things I like most about Dockerfiles... the self documenting aspect. However... have you noticed how many times you end up dealing with Docker images apart from their Dockerfiles? For a lot of useful images, it's difficult (maybe impossible?) to track the Dockerfile

Re: [Discuss-gnuradio] Docker

On Thu, Apr 14, 2016 at 5:40 PM Nicholas McCarthy wrote: > Yeah, this is one of the things I like most about Dockerfiles... the self > documenting aspect. However... have you noticed how many times you end up > dealing with Docker images apart from their Dockerfiles? For a

Re: [Discuss-gnuradio] gr-osmosdr python question

On 04/14/2016 10:44 PM, Richard Bell wrote: I'm new to using gr-osmosdr and I'm trying to implement the equivalent set of USRP function calls for a HackRF set_center_freq(target_freq) get_sensor("lo_locked") which amounts to measuring how long it takes to command a frequency change and lock

[Discuss-gnuradio] Looking for Inmarsat Documentation Diagram - "Figure A2-1"

Hi All: Here’s an esoteric request: I am working on an Inmarsat decoder for 600 bps P-Channel frames. Gnuradio on the front end, and a C program for decoding the recovered data frames. I’m using an Ettus B200 for the reception and gnuradio as the demodulator. The satellite is on 1545.110

Re: [Discuss-gnuradio] Docker

and then there's this https://github.com/docker/docker/issues/12053 I'm not even sure what version of Docker I used when I did the compression thing... it wasn't 1.10. Cheers, Nick M. On Thu, Apr 14, 2016 at 8:40 PM Nicholas McCarthy wrote: > Yeah, this is one of the

[Discuss-gnuradio] gr-osmosdr python question

I'm new to using gr-osmosdr and I'm trying to implement the equivalent set of USRP function calls for a HackRF set_center_freq(target_freq) get_sensor("lo_locked") which amounts to measuring how long it takes to command a frequency change and lock at the new frequency. The set_center_freq

Re: [Discuss-gnuradio] Overflow error in benchmark receiver side "DDDD"

Hii, Thank you for your help. That "" issue is not coming with original benchmark files. I added one python block in between the chain in benchmark code. I think due to which it was not fast enough to process the incoming data resulting "" issue. Regards, Monika On Tue, Apr 5, 2016 at

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

Hi Rob, first feeling: make sure you've actually got enough RAM on your Pi; the "VOLK: Error allocating memory" errors are kind of unusual. Best regards, Marcus On 13.04.2016 13:45, Rob Roschewsk wrote: > > Marcus, > > Thanks for responding. > > I'm looking to build a headless FM receiver to

Re: [Discuss-gnuradio] Question about packet sequence

SangHyuk, I'm really getting desparate. The fact that your application generates 400B over-the-air packets has *nothing* to do with the size of the sample packets going through Ethernet. Stop assuming that. > I expected one send() be represented one packet at wireshark. You should not expect

Re: [Discuss-gnuradio] B2xx rates

61.44 MHz with the latest UHD stuff. Ralph. > -Original Message- > From: Discuss-gnuradio [mailto:discuss-gnuradio- > bounces+ralph=schmid@gnu.org] On Behalf Of Ron Economos > Sent: Wednesday, April 13, 2016 4:56 PM > To: discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio]

Re: [Discuss-gnuradio] 3.7.9.2 Win64 binaries ready + Build scripts

On Thu, Apr 14, 2016 at 10:51 AM, Geof Nieboer wrote: > Tom, > > Not a problem, glad to help. If you give my username edit access, I'll > update the wiki to point people there if interested. > > Geof > Done. You should be able to edit the wiki. Tom > On Thu, Apr 14,

Re: [Discuss-gnuradio] Docker

Having almost no experience with Docker myself, I unfortunately don't have much in the way of worthwhile technical input on this. That said, I really do want to encourage this conversation. Installation of GNU Radio on one machine can be a pain for many people, and doing it on many machines over

Re: [Discuss-gnuradio] Read file metadata

Hi Tom, Thank you for your kind remind, I find the problem that I stored the metadata file as inline type and I don’t need to add ‘.hdr’ with it. Many Thanks, Yan From: trond...@trondeau.com [mailto:trond...@trondeau.com] On Behalf Of Tom Rondeau Sent: 14 April 2016 14:57 To: Yan Huang Cc:

Re: [Discuss-gnuradio] gr-osmosdr python question

None of the common host libraries seem to have that kind of an API call: https://github.com/librtlsdr/librtlsdr/blob/master/include/rtl-sdr.h https://github.com/mossmann/hackrf/blob/master/host/libhackrf/src/hackrf.h https://github.com/airspy/host/blob/master/libairspy/src/airspy.h But here's

Re: [Discuss-gnuradio] [GRC] Print samples when saving screenshot

On Tue, Apr 12, 2016 at 4:55 PM, Merlin Chlosta < merlin.chlosta+gnura...@ruhr-uni-bochum.de> wrote: > Hi all, > > GRC is very handy and so is the screenshot function. It's much faster to > take a screenshot than to record all data and plot it afterwards. However I > found myself taking a lot of

Re: [Discuss-gnuradio] Read file metadata

On Thu, Apr 14, 2016 at 7:44 AM, Yan Huang wrote: > Hi all, > > > > I’m using Message Strobe to control UHD: USRP Source to receive signal > with specified frequency(2.4GHz), but I find flow graph start running > before Message Strobe set the frequency as 2.4 GHz. > > >

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

On Wed, Apr 13, 2016 at 11:13 PM, Marcus D. Leech wrote: > 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

Re: [Discuss-gnuradio] 3.7.9.2 Win64 binaries ready + Build scripts

Hey Geof - I downloaded the any-arch installer and ran it on a SurfacePro4 Windows10 machine I have here, and it worked perfectly. I'm now using GRC and have VOLK Profile running in the background, and everything is working beautifully. Thanks so much for taking the time to put this together - I

Re: [Discuss-gnuradio] 3.7.9.2 Win64 binaries ready + Build scripts

On Thu, Apr 14, 2016 at 6:23 AM, Geof Nieboer wrote: > All, > > Some may recall in the fall I posted a link to a beta windows installer. > I'm happy to report that I'm releasing new versions today for the 3.7.9.2 > release, compatible with Windows 7/8/10. All dependencies

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

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. Martin, Is pybombs rebuild a pybombs2 thing? It doesn't seem to be a valid command in the older pybombs. ~J

Re: [Discuss-gnuradio] 3.7.9.2 Win64 binaries ready + Build scripts

Tom, Not a problem, glad to help. If you give my username edit access, I'll update the wiki to point people there if interested. Geof On Thu, Apr 14, 2016 at 4:58 PM, Tom Rondeau wrote: > On Thu, Apr 14, 2016 at 6:23 AM, Geof Nieboer > wrote: > >>