[Discuss-gnuradio] How to use tunnel.py to web browse?

[Jane Chen]

Hi all,
 
On machine A: 
The README mentions that I should be able to ssh between the machines, web 
browse, etc. I use ifconfig  gr0 xxx.xxx.53.230 and ifconfig  gr0 
xxx..xxx.53.229 to give IP addresses to two machines (A and B).  The machine 
A connects to the Internet through eth0 with IP address: xxx.xxx.53.231. The 
machine B does not connect to the Internet. I ping xxx.xxx.53.232 (a machines 
running WinXP), and the terminal shows follows:
 
ping xxx.xxx.53.232
PING xxx.xxx.53.232 (xxx.xxx.53.232) 56(84) bytes of data.
>From xxx.xxx.53.230 icmp_seq=2 Destination Host Unreachable
>From xxx.xxx.53.230 icmp_seq=3 Destination Host Unreachable
>From xxx.xxx.53.230 icmp_seq=4 Destination Host Unreachable
>From xxx.xxx.53.230 icmp_seq=6 Destination Host Unreachable
 
If anyone knows what's wrong in this case or how to do the web browse, please 
give me some hints.
 
Thank you so much.
Jane
 


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

Re: [Discuss-gnuradio] low cost df angle simulator?

[Eric Blossom]

On Sat, May 09, 2009 at 09:13:19AM -0400, Clark Pope wrote:
> 
> I'm looking for a cheap df angle simulator. I need something that
> outputs four channels with programmable delays to simulate a DF
> antenna. Any links, tips are appreciated.
>  

How much bandwidth do you need?
What RF frequency ranges are acceptable?



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

Re: [Discuss-gnuradio] Can we generate .py file with old versions of GRC

[Josh Blum]

you could checkout gnuradio trunk or 3.2

./bootstrap
./configure
cd grc
make
sudo make install

that will install only grc, and it just might be compatible with 
gnuradio 3.1. Some things may not work, I cant say what will happen.


-Josh

Mir Ali wrote:

Is there a way that we can have the python code like the newer versions of
GRC. This would be convinient to me. The reason why I need this is I am
currently looking at Ed Criscuolo's GMSK_SPACESTATION project from CGRAN and
this project is dependent on gnuradio 3.1.3 which doesn't have a GRC module
in it.

Thanks,
Ali

On Mon, May 11, 2009 at 9:25 PM, Josh Blum  wrote:


GRC 0.70 and below dynamically generated the flowgraph at runtime from
saved flow graph files.

The GRC in gnuradio 3.2 and trunk, generates python flow graphs, and then
executes the python code.

-Josh

Mir Ali wrote:


Hi,

Is it possible to generate the .py files using the GRC or does it only
create .xml files? I am using GRC 0.70 .

Thanks,
Ali





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






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

Re: [Discuss-gnuradio] Can we generate .py file with old versions of GRC

[Mir Ali]

Is there a way that we can have the python code like the newer versions of
GRC. This would be convinient to me. The reason why I need this is I am
currently looking at Ed Criscuolo's GMSK_SPACESTATION project from CGRAN and
this project is dependent on gnuradio 3.1.3 which doesn't have a GRC module
in it.

Thanks,
Ali

On Mon, May 11, 2009 at 9:25 PM, Josh Blum  wrote:

> GRC 0.70 and below dynamically generated the flowgraph at runtime from
> saved flow graph files.
>
> The GRC in gnuradio 3.2 and trunk, generates python flow graphs, and then
> executes the python code.
>
> -Josh
>
> Mir Ali wrote:
>
>> Hi,
>>
>> Is it possible to generate the .py files using the GRC or does it only
>> create .xml files? I am using GRC 0.70 .
>>
>> Thanks,
>> Ali
>>
>>
>>
>> 
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Can we generate .py file with old versions of GRC

[Josh Blum]

GRC 0.70 and below dynamically generated the flowgraph at runtime from 
saved flow graph files.


The GRC in gnuradio 3.2 and trunk, generates python flow graphs, and 
then executes the python code.


-Josh

Mir Ali wrote:

Hi,

Is it possible to generate the .py files using the GRC or does it only
create .xml files? I am using GRC 0.70 .

Thanks,
Ali





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



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

Re: [Discuss-gnuradio] How can I set mux for two daughterboards(rfx 400 and rfx

[Ling Huang]

Hi, I just try many times :(
finaly I use a tool from a old version of grc called usrp probe, It gave the
mux value of each daughterboard, so I just mix the two values.
I think the mux value for two rfx2400 should also be 0x2301


Bruhtesfa Ebrahim-2 wrote:
> 
> Ling Huang wrote:
>> set.mux(0x32103210)
> 
> Dude, how do you calculate the Mux value you need?
> 
> For instance what's the maths behind calculating the mux for two RFX2400 
> daughterboards?
> -- 
> Posted via http://www.ruby-forum.com/.
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-can-I-set-mux-for-two-daughterboards%28rfx-400-and-rfx-2400%29-receiving-simultaneously--tp22408001p23495038.html
Sent from the GnuRadio mailing list archive at Nabble.com.



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

[Discuss-gnuradio] Can we generate .py file with old versions of GRC

[Mir Ali]

Hi,

Is it possible to generate the .py files using the GRC or does it only
create .xml files? I am using GRC 0.70 .

Thanks,
Ali
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] A question about bbn_80211/trunk/src/80211_mac/simple_mac.py

[Jane Chen]

Hi all,
 
My kernel is 2.6.26.6-79.fc9.i686 (Fedor 9)
GNURadio is 3.1.3
 
I ran the simple_mac.py and got an error as following:
 
# ./simple_mac.py 
Traceback (most recent call last):
  File "./simple_mac.py", line 51, in 
    from transmit_path import transmit_path
ImportError: No module named transmit_path
 
The simple_mac.py has codes to import transmit_path as follows:









50
# from current dir

51
from transmit_path import transmit_path

52
from receive_path import receive_path

53
from mac_utils import *

54
from framing import *

55

import fusb_options
 
 
However, the 80211_mac folder only has files as follows:




Name 
Size 
Rev
Age 
Last Change


.../ 

framing.py 
14.3 KB
93 
6 months 
gnychis: adding in initial code 

mac_utils.py 
4.1 KB
93 
6 months 
gnychis: adding in initial code 

Makefile.am 
245 bytes
93 
6 months 
gnychis: adding in initial code 

README.simple_mac 
5.4 KB
93 
6 months 
gnychis: adding in initial code 

README.testing 
4.7 KB
93 
6 months 
gnychis: adding in initial code 

README.txt 
111 bytes
93 
6 months 
gnychis: adding in initial code 

simple-config.sample 
88 bytes
93 
6 months 
gnychis: adding in initial code 

simple_mac.py
 
 
How can the simple_mac.py import transmit_path?
I read the mailing list, but no one mentions this problem. I follow the  
instruction of README.simple_mac. I guess I did something wrong.
Could anyone please tell what's wrong here?
 
Thank you,
Jane


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

[Discuss-gnuradio] Re: How can I set mux for two daughterboards(rfx 400 and rfx

[William Sherman]

Ling Huang wrote:
> set.mux(0x32103210)

Dude, how do you calculate the Mux value you need?

For instance what's the maths behind calculating the mux for two RFX2400 
daughterboards?
-- 
Posted via http://www.ruby-forum.com/.


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

Re: [Discuss-gnuradio] 2-channel AM demodulation on USRP2

[ematlis]

Some progress with my USRP2-  I am able to demodulate 1 channel while using
the translating filters which I was unable to do previously.  However, I
don't seem to be capturing from the second channel of my LFRX.  What makes
me think this is that when I introduce a deinterleave block to sequence the
second channel, I am seeing the frequency of the demodulated result increase
by a factor of two.  In other words, it seems to be deinterleaving just one
stream of data so I am affectively doubling the frequency of the signal.

What code do I need to implement to tell the USRP2 to capture two channels,
one from each input of the LFRX?

thanks,
eric


ematlis wrote:
> 
> Hi all-
> 
> I have a USRP2 with a LFRX daughterboard.  I'm trying to acquire two 
> channels each at a separate frequency where Ch0 is amplitude modulated and 
> Ch1 is not.  As per suggestions made to me from this list, to capture two 
> channels at separate frequencies I was advised to tune the USRP2 to an 
> average frequency and then use translating filters to capture the band 
> around each frequency separately.  Typically the AM carrier on Ch0 is at 
> about 1 MHz, and the signal on Ch1 is about 5 kHz. For both channels I'm 
> interested in no more than 5 kHz of bandwidth.
> 
> I'm using svn 10991 with the SD card updated to the latest fpga and 
> firmware images on a Fedora 10 x86_64 machine.  I don't think I'm doing 
> this correctly since my spectra is all wrong; perhaps somebody can help me 
> out.  First let me post my USRP1 code that does this, as this was my 
> starting point:
> 
> USRP1: options.decim = 128
> 
>  usrp_decim=options.decim
>  self.u = usrp.source_c(0, usrp_decim)
>  self.u.set_dc_offset_cl_enable(int(0),int(15)) # dc removal off
>  adc_rate = self.u.adc_rate()# 64 MS/s
> 
>  # Set the decimation in the FPGA
>  usrp_rate = adc_rate / usrp_decim   # 500 kS/s
> 
>  #set the decimation in software on the host PC
>  sw_decim = 10
>  demod_rate = usrp_rate / sw_decim # 50 kS/s
> 
>  if not self.u.set_nchannels(nchan):   #nchan = 2
>  sys.stderr.write('set_nchannels(%d) failed\n' % (nchan,))
>  raise SystemExit
> 
>  self.subdev = self.u.db(0) + self.u.db(1)
> 
>  if (len(self.subdev) != 6 or
>  self.u.db(0,0).dbid() != usrp_dbid.LF_RX):
>  sys.stderr.write('This code requires a Basic Rx board on Side
> A\n')
>  sys.exit(1)
> 
>  self.u.set_mux(gru.hexint(0xf0f0f1f0))
> 
>  # deinterleave two channels from FPGA
>  self.di = gr.deinterleave(gr.sizeof_gr_complex)
> 
>  # Channelize the signal of interest.
>  lpf_coeffs = gr.firdes.low_pass (1,   # gain
>  usrp_rate,   # sampling rate
>  demod_rate/2, # passband
> cutoff
>  500,   # width of
> transition band
>  gr.firdes.WIN_HANN)
> 
>  self.lpf_0 =  gr.fir_filter_fff (sw_decim,lpf_coeffs)
>  self.lpf_1 =  gr.fir_filter_fff (sw_decim,lpf_coeffs)
> 
>  # Demodulate with classic sqrt (I*I + Q*Q)
>  self.magblock_0 = gr.complex_to_mag()
> 
>  # Get real part of Ch1
>   self.splitter_1 = gr.complex_to_float()
> 
>  # now wire it all together
>  self.connect (self.u, self.di)
> 
>   # Ch 0
>   self.connect ((self.di,0), self.magblock_0)
>   self.connect (self.magblock_0, self.lpf_0)
> 
>   # Ch 1
>   self.connect ((self.di,1), self.splitter_1)
>   self.connect ((self.splitter_1,0),self.lpf_1)
> etc
> 
> Then I define two set_freq functions, one for each subdevice.  Ch0 is 
> tuned to the carrier frequency of the AM signal, Ch1 is tuned to 0 Hz.
> 
> Now, on the USRP2- since I have only one ddc, I can only tune to one 
> frequency:
> 
>  options.decim = 128
>  freq = 1.e6
> 
>  self.u = usrp2.source_32fc(options.interface, options.mac_addr)
>  self.u.set_decim(options.decim)
> 
>  adc_rate = self.u.adc_rate()# 100 MS/s
> 
>   #set the decimation in the FPGA
>  input_rate = self.u.adc_rate() / self.u.decim()# 781.25 kS/s
> 
>   #set the decimation in software on the host PC
>  sw_decim = 16
>  demod_rate = input_rate / sw_decim # 48.828 kS/s
> 
>  # deinterleave four channels from FPGA
>  self.di = gr.deinterleave(gr.sizeof_gr_complex)
> 
>  # Channelize the signal of interest.
>  lpf_coeffs = gr.firdes.low_pass (1,   # gain
>  input_rate,   # sampling rate
>  demod_rate/2, # passband
> cutoff
>  500,  # width of transition
> band
> 

Re: [Discuss-gnuradio] 2-channel AM demodulation on USRP2

[ematlis]

On Sun, 10 May 2009, davek wrote:


have you had success with your translating filters ?
dave


Dave-

thanks much for responding.  I have not yet succeeded in making my 
application work.  Let me just review what I am trying to do.  I want to 
capture with the USRP2 two signals; one AM with a carrier at 1 MHz and a 
modulation at 5 kHz.  The other unmodulated at 5 kHz.  I did realize after 
my last posting that my decimation in the FPGA was too high (sampling rate 
too low) to capture the bandwidth I was interested in, which is (at first 
anyway) 1 MHz (since my two center frequencies are separated by about that 
much).  So I decreased the decimation to give an effective sampling rate 
in the FPGA of just over 2 MHz, which should be sufficient to capture 
(just barely) the 1 MHz AM signal and the regular one at 5 kHz.  However, 
I still did not see what I expected.  The only thing I am seeing (in 
addition to a random spectra in my fft sinks) is "S" printed to the 
screen.  I'm not sure what this is exactly but it's probably an under-run 
error of some kind analogous to the Uu in the USRP1.  For completeness, my 
new decimation rates are: 48 instead of 128 in the FPGA (gives a sampling 
rate of 2.083 MHz instead of 781.25 kHz) and 42 instead of 16 in software 
on the host PC to give a final acquisition rate of 49.6 kHz, which is 
about what I had previously (I'm interested ultimately in resolving a 5 
kHz signal, so I wanted to oversample by a factor of 10).  Anyway, I'll 
continue to look at my code and see if I can figure out what's going on. 
I was just hoping that writing out my approach in detail would reveal (to 
myself or to someone on the list) the stupid error that I was previously 
overlooking!


Thanks,
eric




On Fri, May 8, 2009 at 3:02 PM,  wrote:
  Hi all-

  I have a USRP2 with a LFRX daughterboard.  I'm trying to acquire two 
channels each at a separate frequency where Ch0 is amplitude
  modulated and Ch1 is not.  As per suggestions made to me from this list, 
to capture two channels at separate frequencies I was
  advised to tune the USRP2 to an average frequency and then use 
translating filters to capture the band around each frequency
  separately.  Typically the AM carrier on Ch0 is at about 1 MHz, and the 
signal on Ch1 is about 5 kHz. For both channels I'm
  interested in no more than 5 kHz of bandwidth.

  I'm using svn 10991 with the SD card updated to the latest fpga and 
firmware images on a Fedora 10 x86_64 machine.  I don't think I'm
  doing this correctly since my spectra is all wrong; perhaps somebody can 
help me out.  First let me post my USRP1 code that does
  this, as this was my starting point:

  USRP1: options.decim = 128

         usrp_decim=options.decim
         self.u = usrp.source_c(0, usrp_decim)
         self.u.set_dc_offset_cl_enable(int(0),int(15)) # dc removal off
         adc_rate = self.u.adc_rate()                # 64 MS/s

         # Set the decimation in the FPGA
         usrp_rate = adc_rate / usrp_decim           # 500 kS/s

         #set the decimation in software on the host PC
         sw_decim = 10
         demod_rate = usrp_rate / sw_decim     # 50 kS/s

         if not self.u.set_nchannels(nchan):   #nchan = 2
             sys.stderr.write('set_nchannels(%d) failed\n' % (nchan,))
             raise SystemExit

         self.subdev = self.u.db(0) + self.u.db(1)

         if (len(self.subdev) != 6 or
             self.u.db(0,0).dbid() != usrp_dbid.LF_RX):
             sys.stderr.write('This code requires a Basic Rx board on Side 
A\n')
             sys.exit(1)

         self.u.set_mux(gru.hexint(0xf0f0f1f0))

         # deinterleave two channels from FPGA
         self.di = gr.deinterleave(gr.sizeof_gr_complex)

         # Channelize the signal of interest.
         lpf_coeffs = gr.firdes.low_pass (1,           # gain
                                             usrp_rate,   # sampling rate
                                             demod_rate/2, # passband cutoff
                                             500,       # width of 
transition band
                                             gr.firdes.WIN_HANN)

         self.lpf_0 =  gr.fir_filter_fff (sw_decim,lpf_coeffs)
         self.lpf_1 =  gr.fir_filter_fff (sw_decim,lpf_coeffs)

         # Demodulate with classic sqrt (I*I + Q*Q)
         self.magblock_0 = gr.complex_to_mag()

         # Get real part of Ch1
         self.splitter_1 = gr.complex_to_float()

         # now wire it all together
         self.connect (self.u, self.di)

         # Ch 0
         self.connect ((self.di,0), self.magblock_0)
         self.connect (self.magblock_0, self.lpf_0)

         # Ch 1
         self.connect ((self.di,1), self.splitter_1)
         self.connect ((self.splitter_1,0),self.lpf_1)
  etc

[Discuss-gnuradio] modified scopesink

[ematlis]

I'm not sure if my email got sent out, so I'm re-posting

Hi all-

I have attached a modified scopesink that I believe fixes some sizing 
bugs.  The issue is that the scope window would intrude on the controls 
below when sizes other than the default 640 by 240 is specified in the 
scopesink code.  The credit goes to Michael Dickens, who provided these 
fixes to me a while back in a personal communication.  I have been 
updating the various versions of scopesink for my own use and have done so 
for the current (as of svn 10991) implementation of scopesink_nongl.py 
which I provide here, with the hopes that somebody more knowledgeable in 
creating patches can provide a formal one to fix this issue.  The fixes 
are very simple; other than resizing the defaults window sizes to a 
smaller value suitable for a smaller resolution screen (such as for a 
laptop), the changes are either lines that have "size=size" or "| 
wx.EXPAND)" added to them.  All the lines with changes have the note 
"#mdickens" after them to aid in identification.


I would be happy to provide any other information; please let me know.

thanks,
eric#!/usr/bin/env python
#
# Copyright 2003,2004,2006,2007 Free Software Foundation, Inc.
# 
# This file is part of GNU Radio
# 
# GNU Radio is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 3, or (at your option)
# any later version.
# 
# GNU Radio is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
# 
# You should have received a copy of the GNU General Public License
# along with GNU Radio; see the file COPYING.  If not, write to
# the Free Software Foundation, Inc., 51 Franklin Street,
# Boston, MA 02110-1301, USA.
# 

from gnuradio import gr, gru, eng_notation
from gnuradio.wxgui import stdgui2
import wx
import gnuradio.wxgui.plot as plot
import numpy
import threading
import struct

default_scopesink_size = (200, 100) #from 640 240 by mdickens
default_v_scale = 1000
default_frame_decim = gr.prefs().get_long('wxgui', 'frame_decim', 1)

class scope_sink_f(gr.hier_block2):
def __init__(self, parent, title='', sample_rate=1,
 size=default_scopesink_size, frame_decim=default_frame_decim,
 v_scale=default_v_scale, t_scale=None, num_inputs=1, **kwargs):

gr.hier_block2.__init__(self, "scope_sink_f",
gr.io_signature(num_inputs, num_inputs, 
gr.sizeof_float),
gr.io_signature(0,0,0))

msgq = gr.msg_queue(2) # message queue that holds at most 2 
messages
self.guts = gr.oscope_sink_f(sample_rate, msgq)
for i in range(num_inputs):
  self.connect((self, i), (self.guts, i))

self.win = scope_window(win_info (msgq, sample_rate, frame_decim,
   v_scale, t_scale, self.guts, title), 
parent, size=size) #mdickens added size=size

def set_sample_rate(self, sample_rate):
self.guts.set_sample_rate(sample_rate)
self.win.info.set_sample_rate(sample_rate)

class scope_sink_c(gr.hier_block2):
def __init__(self, parent, title='', sample_rate=1,
 size=default_scopesink_size, frame_decim=default_frame_decim,
 v_scale=default_v_scale, t_scale=None, num_inputs=1, **kwargs):

gr.hier_block2.__init__(self, "scope_sink_c",
gr.io_signature(num_inputs, num_inputs, 
gr.sizeof_gr_complex),
gr.io_signature(0,0,0))

msgq = gr.msg_queue(2) # message queue that holds at most 2 
messages
self.guts = gr.oscope_sink_f(sample_rate, msgq)
for i in range(num_inputs):  
c2f = gr.complex_to_float()  
self.connect((self, i), c2f)
self.connect((c2f, 0), (self.guts, 2*i+0))
self.connect((c2f, 1), (self.guts, 2*i+1))

self.win = scope_window(win_info(msgq, sample_rate, frame_decim,
 v_scale, t_scale, self.guts, title), 
parent, size=size) #mdickens added size=size

def set_sample_rate(self, sample_rate):
self.guts.set_sample_rate(sample_rate)
self.win.info.set_sample_rate(sample_rate)

class constellation_sink(scope_sink_c):
def __init__(self, parent, title='Constellation', sample_rate=1,
 size=default_scopesink_size, frame_decim=default_frame_decim):
scope_sink_c.__init__(self, parent=parent, title=title, 
sample_rate=sample_rate,
 size=size, frame_decim=frame_decim)
self.win.info.xy = True #constellation mode

# 


time_base_

Re: [Discuss-gnuradio] usrp2: timestamp absolute ?

[Juha Vierinen]

> my question is about the time stamp in rx_metadata->timestamp. I've got the
> rx_streaming_samples running and now I wondering what the time value is about.
> In the code I've found this:
> uint32_t        timestamp;      // time of rx or tx (100 MHz)
>
> Can you tell me what the timestamp exactly refers to. Is it just a counter?

It is a 32-bit counter (I remember somebody saying that this will soon
be a 64-bit counter) that just counts 100 MHz samples, so it will
overflow quite often. In normal operation this isn't tied to any
absolute clock.

> When/How is it started/reseted?

If you call sync_to_pps() and provide a PPS input (one second digital
pulse), the system will start streaming samples at the next PPS pulse.
This resets the timestamp to zero, which makes it possible to attach
an absolute time to your samples. I'm not sure exactly how accurate
this is, as I haven't properly tested this yet. If your sample clock
is locked to a good GPS syncronized reference clock, I'd guess the
accuracy could be better than 1e-8 s. I guess some of the "big guys"
might know more about this.

> Or to be more precisely: How do I calculate an absolute time like the extended
> unix time stamp with uSec and nSec?

The remaing us and ns are 0 if you are locked to a reference. You can
calculate the absolute time by counting the number of samples
received, assuming no buffer overflows have occured (which you can
detect from timestamp difference anomalies or missing frame sequence
numbers).

When streaming the data, you will have to throw away a small amount of
samples in the beginning, but you can quite easily determine where the
real first sample is located by looking at the time stamps of the
incoming frames.

If you are interested, I have a modified rx_streaming_samples.cc that
configures the sync_to_pps and determines where the true beginning of
samples is located at.

juha


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

Re: [Discuss-gnuradio] usrp2: timestamp absolute ?

[Eric Blossom]

On Mon, May 11, 2009 at 08:12:08PM +0200, Michael Sprauer wrote:
> Hello list,
> 
> my question is about the time stamp in rx_metadata->timestamp. I've got the 
> rx_streaming_samples running and now I wondering what the time value is about.
> In the code I've found this:
> uint32_t  timestamp;  // time of rx or tx (100 MHz)
> 
> Can you tell me what the timestamp exactly refers to. Is it just a counter? 

It's a counter clocked by the 100 MHz s.ample clock.

> When/How is it started/reseted?

If you don't do anything, it's initialized to 0 at power up.

You can arrange so that it's reset to zero on the next pulse on the
pulse-per-second input using usrp2::sync_to_pps.


> Or to be more precisely: How do I calculate an absolute time like the 
> extended 
> unix time stamp with uSec and nSec?

At this point you don't.  We'll be moving to a 64-bit format when we
convert the USRP2 to use the VRT on-the-wire format


> Thanks for reading :)

You're welcome :-)

Eric


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

Re: [Discuss-gnuradio] Software troubes - gr_vmcircbuf ...?

[Eric Blossom]

On Mon, May 11, 2009 at 10:51:47AM -0600, wallen wrote:
> On Fri, 2009-05-08 at 18:32 -0700, Eric Blossom wrote:
> > On Fri, May 08, 2009 at 02:04:59PM -0600, wallen wrote:
> > > I've been trying to get Gnuradio running with my USRP2, and am still
> > > having some troubles.  My computer is an older Dell Inspiron 5100 laptop
> > > running Debian (Lenny).  I've installed a D-Link DGE-660TD Gigabit
> > > Cardbus adapter, and have compiled what I believe is the most recent
> > > release of the code per the instructions in the README file.
> > > 
> > > I can find the USRP2 by running the find_usrps command, but oddly enough
> > > this occasionally segfaults.  So far what looks like the most intriguing
> > > error message I got when trying to run usrp2_fft.py.  This looks like:  
> > > 
> > >usrp2_fft.py
> > >usrp2: failed to enable realtime scheduling
> > 
> > Edit /etc/security/limits.conf and add this line:
> > 
> > @usrp  - rtprio 50
> > 
> > then logout and back in.
> 
> Well ... that doesn't seem to change anything.  I still get the same
> error if I try running as a regular user.  Running as root gives me
> different errors.  Running this as root after trying as a regular user I
> got:
> 
>"/usr/local/lib/python2.5/site-packages/gnuradio/wxgui/stdgui2.py",
> line 
>81, in __init__
>self.top_block = top_block_maker (frame, self, vbox, sys.argv)
>  File "./usrp2_fft.py", line 70, in __init__
>self.u = usrp2.source_32fc(options.interface, options.mac_addr)
>  File "/usr/local/lib/python2.5/site-packages/gnuradio/usrp2.py",
> line 
>621, in source_32fc
>return _usrp2.source_32fc(*args, **kwargs)
>RuntimeError: Unable to retrieve daughterboard info

This error makes me think that you don't have the current firmware and
fpga images installed on the SD Card.

You can download them here:

  http://gnuradio.org/releases/usrp2-bin/trunk/txrx_edk10.1_r10925.bin
  http://gnuradio.org/releases/usrp2-bin/trunk/u2_rev3_ise10.1sp3_r10766.bin

Eric


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

[Discuss-gnuradio] usrp2: timestamp absolute ?

[Michael Sprauer]

Hello list,

my question is about the time stamp in rx_metadata->timestamp. I've got the 
rx_streaming_samples running and now I wondering what the time value is about.
In the code I've found this:
uint32_ttimestamp;  // time of rx or tx (100 MHz)

Can you tell me what the timestamp exactly refers to. Is it just a counter? 
When/How is it started/reseted?
Or to be more precisely: How do I calculate an absolute time like the extended 
unix time stamp with uSec and nSec?

Thanks for reading :)

kind regards
Michael


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

Re: [Discuss-gnuradio] The Debian directory

[Johnathan Corgan]

On Mon, May 11, 2009 at 9:53 AM, wallen  wrote:

> OK ... so can I register this directory as a source for the package
> manager?

No.  The 'debian' directory in the source tree contains the packaging
scripts that *we* use to create the binary installation packages for
Ubuntu.  The packages themselves are stored on gnuradio.org.  Please
see the Wiki:

http://gnuradio.org/trac/wiki/DebianPackages

...for instructions on how to modify your package source configuration
to install these.

Johnathan


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

Re: [Discuss-gnuradio] Software troubes - gr_vmcircbuf ...?

[wallen]

On Fri, 2009-05-08 at 18:32 -0700, Eric Blossom wrote:
> On Fri, May 08, 2009 at 02:04:59PM -0600, wallen wrote:
> > I've been trying to get Gnuradio running with my USRP2, and am still
> > having some troubles.  My computer is an older Dell Inspiron 5100 laptop
> > running Debian (Lenny).  I've installed a D-Link DGE-660TD Gigabit
> > Cardbus adapter, and have compiled what I believe is the most recent
> > release of the code per the instructions in the README file.
> > 
> > I can find the USRP2 by running the find_usrps command, but oddly enough
> > this occasionally segfaults.  So far what looks like the most intriguing
> > error message I got when trying to run usrp2_fft.py.  This looks like:  
> > 
> >usrp2_fft.py
> >usrp2: failed to enable realtime scheduling
> 
> Edit /etc/security/limits.conf and add this line:
> 
> @usrp  - rtprio 50
> 
> then logout and back in.

Well ... that doesn't seem to change anything.  I still get the same
error if I try running as a regular user.  Running as root gives me
different errors.  Running this as root after trying as a regular user I
got:

./usrp2_fft.py
   Traceback (most recent call last):
 File "./usrp2_fft.py", line 273, in 
   main ()
 File "./usrp2_fft.py", line 269, in main
   app = stdgui2.stdapp(app_top_block, "USRP2 FFT", nstatus=1)
 File 
   "/usr/local/lib/python2.5/site-packages/gnuradio/wxgui/stdgui2.py",
line 
   36, in __init__
   wx.App.__init__ (self, redirect=False)
 File 
   "/usr/lib/python2.5/site-packages/wx-2.8-gtk2-unicode/wx/_core.py",
line 
   7836, in __init__
   self._BootstrapApp()
 File 
   "/usr/lib/python2.5/site-packages/wx-2.8-gtk2-unicode/wx/_core.py",
line 
   7433, in _BootstrapApp
   return _core_.PyApp__BootstrapApp(*args, **kwargs)
 File 
   "/usr/local/lib/python2.5/site-packages/gnuradio/wxgui/stdgui2.py",
line 
   39, in OnInit
   frame = stdframe (self.top_block_maker, self.title,
self._nstatus)
 File 
   "/usr/local/lib/python2.5/site-packages/gnuradio/wxgui/stdgui2.py",
line 
   60, in __init__
   self.panel = stdpanel (self, self, top_block_maker)
 File 
   "/usr/local/lib/python2.5/site-packages/gnuradio/wxgui/stdgui2.py",
line 
   81, in __init__
   self.top_block = top_block_maker (frame, self, vbox, sys.argv)
 File "./usrp2_fft.py", line 70, in __init__
   self.u = usrp2.source_32fc(options.interface, options.mac_addr)
 File "/usr/local/lib/python2.5/site-packages/gnuradio/usrp2.py",
line 
   621, in source_32fc
   return _usrp2.source_32fc(*args, **kwargs)
   RuntimeError: Unable to retrieve daughterboard info

Trying to run again as root I get:

./usrp2_fft.py
   usrp2: channel 0 not receiving
   usrp2::rx_samples() failed

Not quite sure where to look to resolve what is going on here.

- Wayde









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

Re: [Discuss-gnuradio] The Debian directory

[wallen]

On Fri, 2009-05-08 at 18:34 -0700, Eric Blossom wrote:
> On Fri, May 08, 2009 at 07:07:27PM -0400, davek wrote:
> > a quick and easy install of trunk on debian lenny here...
> > 
> > apt-get install subversion autoconf libtool swig python-dev fftw3-dev
> > libcppunit-dev libboost1.35-dev libgsl0-dev guile-1.8-dev sdcc libusb-dev
> > sdcc-nf python-wxgtk2.8 python-lxml python-cheetah pkg-config python-numpy
> > python-gtk2 make
> > svn co http://gnuradio.org/svn/gnuradio/trunk gnuradio
> > cd gnuradio
> > ./configure --enable-gnuradio-core --enable-usrp --enable-gr-usrp
> > --enable-gr-wxgui --enable-gr-audio-osx --enable-gnuradio-examples
> > --enable-gr-utils --enable-gr-how-to-write-a-block --enable-omnithread
> > --enable-pmt --enable-guile --enable-grc --disable-gr-audio-osx
> > make -j4
> > make install
> > 
> > the stuff in the debian directory is needed to give your non root users
> > permission to access the usrp otherwise thats it...
> 
> No, the stuff in the debian directory is the debian packaging information.

OK ... so can I register this directory as a source for the package
manager?

- Wayde



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

Re: [Discuss-gnuradio] Re: error compiling gnuradio trunk

[Johnathan Corgan]

On Mon, May 4, 2009 at 12:56 PM, Eric Blossom  wrote:

> On Mon, May 04, 2009 at 03:37:05PM -0400, Achilleas Anastasopoulos wrote:
>> I found out that
>>
>> AC_PROG_MKDIR_P is defined only on autoconf 2.60, while
>> gnuradio requires only autoconf 2.57 and above.
>>
>> After a google search, I found this patch:

> Thanks for sorting this out.  Johnathan or I will make sure that it
> gets into the trunk and the 3.2 release.

This has been applied to the trunk as of r11001.  Thanks.

Johnathan


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

Re: Fwd: [Discuss-gnuradio] USRP2 eth_buffer

[Johnathan Corgan]

On Thu, Apr 23, 2009 at 9:40 PM, Eric Blossom  wrote:

> Juha, thanks for the patch!

This has been applied to the trunk at revision 11000.

Johnathan


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

Re: [Discuss-gnuradio] Software troubes - gr_vmcircbuf ...?

[wallen]

On Fri, 2009-05-08 at 18:32 -0700, Eric Blossom wrote:
> On Fri, May 08, 2009 at 02:04:59PM -0600, wallen wrote:
> > I've been trying to get Gnuradio running with my USRP2, and am still
> > having some troubles.  My computer is an older Dell Inspiron 5100 laptop
> > running Debian (Lenny).  I've installed a D-Link DGE-660TD Gigabit
> > Cardbus adapter, and have compiled what I believe is the most recent
> > release of the code per the instructions in the README file.
> > 
> > I can find the USRP2 by running the find_usrps command, but oddly enough
> > this occasionally segfaults.  So far what looks like the most intriguing
> > error message I got when trying to run usrp2_fft.py.  This looks like:  
> > 
> >usrp2_fft.py
> >usrp2: failed to enable realtime scheduling
> 
> Edit /etc/security/limits.conf and add this line:
> 
> @usrp  - rtprio 50
> 
> then logout and back in.

OK, I'll give that a try shortly.

> >gr_vmcircbuf_createfilemapping: createfilemapping is not available
> 
> This is a little odd.  Does it pass "make check"?
> 
> >usrp2: channel 0 not receiving
> >usrp2::rx_samples() failed
> > 
> > Does this provide any clues to those of you more familiar with the
> > software?
> 
> Does it pass "make check"?

Yes, it seems to.  Didn't get anything that sad it failed.

- Wayde




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

RE: [Discuss-gnuradio] a problem on running the BBN 802.11 on the GnuRadion

[Abdul Hakeem]

Hi,

Does anyone knows how many client connections this is able to support ?

Cheers,
Abdul Hakeem

 

 

From: discuss-gnuradio-bounces+alhakeem=gmail@gnu.org
[mailto:discuss-gnuradio-bounces+alhakeem=gmail@gnu.org] On Behalf Of
Colby Boyer
Sent: Sunday, May 10, 2009 5:13 PM
To: 汤图杨
Cc: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] a problem on running the BBN 802.11 on the
GnuRadion

 

Hi XiaoMing,

If you are using the USRP I, I recommend you go here to download the code
https://www.cgran.org/wiki/BBN80211. Follow the instructions to download the
correct version of gnu radio from the SVN and compile the BBN source. There
should be a README file that comes with the BBN code that will help explain
how to use it.

--Colby

2009/5/10 汤图杨 

Hi:
   I am using the USRP for the first time, and my target is to run the BBN
802.11 with Gnu Radio on the USRP ,can anyone give me some advice for
detailed operattion?
   Because I haven't use GnuRadio before , please give me some suggestion in
studying and using this greate tool, too! 
   I will be very grateful to hear from your letter! Thank you!
 
 
XiaoMing
 

  _  

使用新一代 Windows Live Messenger 轻松交流和共享！   立刻下载！


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

 

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

[Discuss-gnuradio] wxPython GUI blocking

[Adriann]

Hy,
I have developed a GUI using wxPython which consists of a parent frame and
another frame in which I want to plot the results of each FFT calculation.
The problem is that sometimes when I run the "OnTune" or "OnStop" function i
get the following error:
"python: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int)
((xcb_req) - (dpy->request)) >= 0)' failed."

Thank you very much! 

Here is some part of the code:
   def OnTune(self,event):
self.t = Tuner.Tuner(self) //Tuner is a class from another file 
called
Tuner.py
self.thread = threading.Thread(target=self.__run)
self.thread.start()
def __run(self):
wx.CallAfter(self.AfterRun, "Tuner has started")
self.t.StartTune()
self.SetStatusText("Tunning Complete...")
def AfterRun(self,msg):
pass
def OnStop(self, event):
self.t.StopTune()
#
in class Tuner I have:
# 
def __init__(self, frame):
wx.Frame.__init__(self, None, -1, "Tunning Stats")
self.frame = frame
self.Stop = False

def StartTune (self):
self.fftwindow = wx.Frame(self.frame,-1, "Tunning",

style=wx.FRAME_FLOAT_ON_PARENT|wx.CAPTION|wx.CLOSE_BOX,
pos=(200,170), 
size=(500,500))

# Create FFT Plot
self.plot = wx.lib.plot.PlotCanvas(fftwindow, style=wx.RAISED_BORDER)
#start flow-graph
  while(True):
tb = TunerFlowGraph(cf, fs, fsize) #TunerFlowGraph is the class where
the FlowGraph is defined
tb.start()
time.sleep(2)
# Make another processing not related to displaying 
tb.stop()
tb.wait()
self.fftwindow = wx.Frame(self.frame,-1, "Tunning",

style=wx.FRAME_FLOAT_ON_PARENT|wx.CAPTION|wx.CLOSE_BOX,
pos=(200,170), 
size=(500,500))

# Create FFT Plot
self.plot = wx.lib.plot.PlotCanvas(fftwindow, style=wx.RAISED_BORDER)
data = []
x = [i for i in range(fsize)]
y = tb.v_sink_fft.out()//output data from fft 
n = 0
for xx in x:
data.append((xx, y[n]))
n += 1
data_line = wx.lib.plot.PolyLine(data, colour='blue', width=1)
gc = wx.lib.plot.PlotGraphics([data_line],  "CoPolar", "time(s)", "dB")
self.plot.Draw(gc, xAxis=(0, fsize), yAxis=(-150, 0))   

def StopTune(self):
 self.Stop = True

-- 
View this message in context: 
http://www.nabble.com/wxPython-GUI-blocking-tp23481508p23481508.html
Sent from the GnuRadio mailing list archive at Nabble.com.



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

[Discuss-gnuradio] Re: sample and hold Ctrl Input

[feldmaus]

Is there any Source i can connect to the Ctrl Sample and Hold ?
A normal Signal Source(float) doesnt fit the Sink(Ctrl S&H).
Any Ideas ?

regards Markus




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

[Discuss-gnuradio] sample and hold Ctrl Input

[feldmaus]

Hi All,

i am using the Sample and Hold Element, but there seems to be
some needed conversion for the Ctrl Input. my source uses a vector which is 4
times bigger than the ctrl input sink. My source send only 0 or 1, so it should
be no problem to lessen this vector.

I didn't find any examples.
Is there an example i didnt saw ?
Which conversion Element is the right one ?
I think vectorSource[4] to vectorSink[0] should be nice, so that only
the LSB will be transfered, for example:
(Source) --> 0(Sink)
(Source)0001 --> 1(Sink)
But this wished Element doesn't exist in GRC.
Am i right ?

Regards Markus




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

Re: [Discuss-gnuradio] [Douglas Geiger BBN 802.11b] Porting code on USRP2 problems

[Ben Yahmed]

Hi,

I do not encounter this problem, the simple_mac run in a correct way for 
me. Do you use the latest versions of the firmware and fpga?


Ben Yahmed

Miklos Christine wrote:

Hello Ben,

When I try to run the version of simple_mac that you posted, I get an 
error.

It seems like an infinite loop that prints to stdout:

2nstreams:  


It happens at the call to fg.rxpath.start() .

Do you have the same problem?

Thanks,
Miklos Christine

On Wed, May 6, 2009 at 10:46 AM, Ben Yahmed 
> wrote:


Hi all,
I modified the gain in the bbn_80211_rx.py file from 46 to 27 and
the loss ratio has fallen down to 15-20%. Do you have any idea
about the best value to put?
this is the ping capture:


# ping 10.0.0.1PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1 : icmp_seq=1 ttl=64
time=51.9 ms
64 bytes from 10.0.0.1 : icmp_seq=2 ttl=64
time=52.0 ms
64 bytes from 10.0.0.1 : icmp_seq=3 ttl=64
time=52.0 ms
64 bytes from 10.0.0.1 : icmp_seq=4 ttl=64
time=49.2 ms
64 bytes from 10.0.0.1 : icmp_seq=5 ttl=64
time=49.4 ms
64 bytes from 10.0.0.1 : icmp_seq=6 ttl=64
time=46.3 ms
64 bytes from 10.0.0.1 : icmp_seq=7 ttl=64
time=45.7 ms
64 bytes from 10.0.0.1 : icmp_seq=10 ttl=64
time=35.2 ms
64 bytes from 10.0.0.1 : icmp_seq=12 ttl=64
time=35.1 ms
64 bytes from 10.0.0.1 : icmp_seq=13 ttl=64
time=34.3 ms
64 bytes from 10.0.0.1 : icmp_seq=15 ttl=64
time=32.5 ms
64 bytes from 10.0.0.1 : icmp_seq=16 ttl=64
time=33.0 ms
64 bytes from 10.0.0.1 : icmp_seq=17 ttl=64
time=29.7 ms
64 bytes from 10.0.0.1 : icmp_seq=18 ttl=64
time=29.8 ms
64 bytes from 10.0.0.1 : icmp_seq=19 ttl=64
time=28.7 ms
64 bytes from 10.0.0.1 : icmp_seq=20 ttl=64
time=28.1 ms
64 bytes from 10.0.0.1 : icmp_seq=21 ttl=64
time=27.2 ms
64 bytes from 10.0.0.1 : icmp_seq=22 ttl=64
time=25.8 ms
64 bytes from 10.0.0.1 : icmp_seq=23 ttl=64
time=24.2 ms
64 bytes from 10.0.0.1 : icmp_seq=24 ttl=64
time=23.6 ms
64 bytes from 10.0.0.1 : icmp_seq=25 ttl=64
time=22.4 ms
64 bytes from 10.0.0.1 : icmp_seq=26 ttl=64
time=20.4 ms
64 bytes from 10.0.0.1 : icmp_seq=27 ttl=64
time=21.5 ms
64 bytes from 10.0.0.1 : icmp_seq=28 ttl=64
time=11.1 ms
64 bytes from 10.0.0.1 : icmp_seq=29 ttl=64
time=10.9 ms
64 bytes from 10.0.0.1 : icmp_seq=30 ttl=64
time=10.2 ms
64 bytes from 10.0.0.1 : icmp_seq=31 ttl=64
time=11.3 ms
64 bytes from 10.0.0.1 : icmp_seq=32 ttl=64
time=11.2 ms
64 bytes from 10.0.0.1 : icmp_seq=33 ttl=64
time=10.7 ms
64 bytes from 10.0.0.1 : icmp_seq=34 ttl=64
time=11.2 ms
64 bytes from 10.0.0.1 : icmp_seq=36 ttl=64
time=9.74 ms
64 bytes from 10.0.0.1 : icmp_seq=38 ttl=64
time=11.2 ms
64 bytes from 10.0.0.1 : icmp_seq=39 ttl=64
time=10.7 ms
64 bytes from 10.0.0.1 : icmp_seq=40 ttl=64
time=11.2 ms
64 bytes from 10.0.0.1 : icmp_seq=41 ttl=64
time=10.8 ms
64 bytes from 10.0.0.1 : icmp_seq=44 ttl=64
time=9.83 ms
64 bytes from 10.0.0.1 : icmp_seq=45 ttl=64
time=10.4 ms
64 bytes from 10.0.0.1 : icmp_seq=47 ttl=64
time=9.91 ms
64 bytes from 10.0.0.1 : icmp_seq=48 ttl=64
time=10.1 ms
64 bytes from 10.0.0.1 : icmp_seq=49 ttl=64
time=11.1 ms
64 bytes from 10.0.0.1 : icmp_seq=50 ttl=64
time=10.4 ms
64 bytes from 10.0.0.1 : icmp_seq=51 ttl=64
time=10.4 ms
64 bytes from 10.0.0.1 : icmp_seq=52 ttl=64
time=10.7 ms
64 bytes from 10.0.0.1 : icmp_seq=53 ttl=64
time=10.0 ms
64 bytes from 10.0.0.1 : icmp_seq=54 ttl=64
time=16.3 ms
64 bytes from 10.0.0.1 : icmp_seq=55 ttl=64
time=10.1 ms
64 bytes from 10.0.0.1 : icmp_seq=56 ttl=64
time=10.6 ms
64 bytes from 10.0.0.1 : icmp_seq=58 ttl=64
time=9.69 ms
64 bytes from 10.0.0.1 : icmp_seq=60 ttl=64
time=10.2 ms
64 bytes from 10.0.0.1 : icmp_seq=62 ttl=64
time=9.91 ms
64 bytes from 10.0.0.1 : icmp_seq=63 ttl=64
time=10