Send USRP-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."


Today's Topics:

   1. GPSDO and B210 (Sharath)
   2. Re: GPSDO and B210 (Marcus D. Leech)
   3. Additional parameters for uhd::stream_args_t (Dario Fertonani)
   4. FW:  Can ping but not find_device on N210 (Aaron Henderson)
   5. Re: Can ping but not find_device on N210 (Marcus M?ller)
   6. Re: Can ping but not find_device on N210 (Aaron Henderson)
   7. Re: Can ping but not find_device on N210 (Marcus M?ller)
   8. Re: Can ping but not find_device on N210 (Neel Pandeya)
   9. Re: Can ping but not find_device on N210 (Marcus D. Leech)


----------------------------------------------------------------------

Message: 1
Date: Mon, 6 Jul 2015 01:11:26 +0000 (UTC)
From: Sharath <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] GPSDO and B210
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="utf-8"

Hello,
Reposting an old thread to see if there has been any progress.I installed a 
board mounted GPSDO on my B210.?The problem is that this now requires a valid 
GPS fix to proceed, else I get a "No GPRMC message found".Now with an active 
GPS antenna, outdoors, the GPSDO picks up a signal easily. Indoors it is still 
iffy. Without the active GPS antenna, there is very little hope indoors even 
near a window. So my strategy now is to go outdoors, get the GPS fix and then 
continue my work indoors. Not ideal...Now my questions:
(i) Is there a way to force the B2100 to use the internal clock and not wait 
for the GPS fix for all applications? For example I don't want to change the 
uhd_usrp_proble executable, but would like the board to use the internal clock 
and not wait for GPS fix. Is there a way to toggle the mode from automatic to 
internal clock for all applications via a jumper or other means? I don't want 
to recompile other working applications just because I have installed the GPSDO.

Separately:(ii) Once the GPS actually starts working, how can I use gpsd to get 
the gps data. That is the web page 
http://files.ettus.com/manual/page_gpsdo_b2x0.html says "Other information can 
be fetched as well. You can query the lock status with the gps_locked sensor, 
as well as obtain raw NMEA sentences using the gps_gprmc, and gps_gpgga 
sensors. Location information can be parsed out of the gps_gpgga sensor by 
using gpsd or another NMEA parser."
I am able to get some of the data, but it seems that the $GPGSV string is not 
part of the code currently. Anyway the code can be updated to get these strings 
also output by default?Any suggestions are welcome.

Thanks, Sharath
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150706/c904fb00/attachment-0001.html>

------------------------------

Message: 2
Date: Sun, 05 Jul 2015 21:37:37 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] GPSDO and B210
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"

On 07/05/2015 09:11 PM, Sharath via USRP-users wrote:
> Hello,
> Reposting an old thread to see if there has been any progress.
> I installed a board mounted GPSDO on my B210. The problem is that this now 
> requires a valid GPS fix to proceed, else I get a "No GPRMC message found".
> Now with an active GPS antenna, outdoors, the GPSDO picks up a signal easily. 
> Indoors it is still iffy. Without the active GPS antenna, there is very 
> little hope indoors even near a window. So my strategy now is to go outdoors, 
> get the GPS fix and then continue my work indoors. Not ideal...
> Now my questions:
> (i) Is there a way to force the B2100 to use the internal clock and not wait 
> for the GPS fix for all applications? For example I don't want to change the 
> uhd_usrp_proble executable, but would like the board to use the internal 
> clock and not wait for GPS fix. Is there a way to toggle the mode from 
> automatic to internal clock for all applications via a jumper or other means? 
> I don't want to recompile other working applications just because I have 
> installed the GPSDO.
Any application can  ask for internal clock:

http://files.ettus.com/manual/classuhd_1_1usrp_1_1multi__usrp.html#a73ed40009d0d3787c183d42423d25026

And an application that  doesn't use that API call, or specifies 
"default" will use the GPSDO, if present, otherwise it will use "internal".

Global, all-application, device-parameter management is rather outside 
the scope of what amounts to a device-driver should be doing, since
  that type of functionality really belongs in the application layer, 
not in the driver layer.


> Separately:
> (ii) Once the GPS actually starts working, how can I use gpsd to get the gps 
> data. That is the web pagehttp://files.ettus.com/manual/page_gpsdo_b2x0.html  
> says "Other information can be fetched as well. You can query the lock status 
> with the gps_locked sensor, as well as obtain raw NMEA sentences using the 
> gps_gprmc, and gps_gpgga sensors. Location information can be parsed out of 
> the gps_gpgga sensor by using gpsd or another NMEA parser."
> I am able to get some of the data, but it seems that the $GPGSV string is not 
> part of the code currently. Anyway the code can be updated to get these 
> strings also output by default?
> Any suggestions are welcome.
You'd  have to write an interface to GPSD yourself.

I'm not aware of any immediate plans to expand the variety of NMEA 
sentences that are  parsed by the UHD software.  Keep in mind that the 
primary purpose of the GPSDO in USRP hardware is to provide 10Mhz and 
1PPS outputs for purposes of precise system-clock management.
The fact that the modules in use *also* produce NMEA navigation messages 
is rather secondary to their intended purpose in USRP hardware.

>
> Thanks, Sharath
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150705/d0282060/attachment-0001.html>

------------------------------

Message: 3
Date: Sun, 5 Jul 2015 20:36:47 -0700
From: Dario Fertonani <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Additional parameters for uhd::stream_args_t
Message-ID:
        <CAJGEdAj-6qOfcz+gZNXcsx4wujN-8G=gg5j5vxr863foeam...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

On this list I have been reading about the effectiveness of parameters
like recv_frame_size and num_recv_frames, so I'll try too, with the usual
goal of minimizing TX errors (U/L) and RX errors (O).
Is the usage in the following code correct? In particular, my concern is
how the four parameters (recv_frame_size, num_recv_frames, send_frame_size,
num_send_frames) are allocated to rxStream and txStream. Any way to verify
from the logs that the request was actually granted? I understand that the
65536 value is too big for my B210, but memory waste is not a concern at
the moment.
Thanks,
Dario

    //create rx streamer
    uhd::stream_args_t rxStreamParams;
    /*other stuff*/
    rxStreamParams.args[ "spp" ] = str( boost::format( "%d" ) %
ChunkSamples );
    rxStreamParams.args[ "recv_frame_size" ] = str( boost::format( "%d" ) %
65536 );
    rxStreamParams.args[ "num_recv_frames" ] = str( boost::format( "%d" ) %
256 );
    rxStream = rfBoard->get_rx_stream( rxStreamParams );

    //create tx streamer
    uhd::stream_args_t txStreamParams;
    /*other stuff*/
    txStreamParams.args[ "spp" ] = str( boost::format( "%d" ) %
ChunkSamples );
    txStreamParams.args[ "send_frame_size" ] = str( boost::format( "%d" ) %
65536 );
    txStreamParams.args[ "num_send_frames" ] = str( boost::format( "%d" ) %
256 );
    txStream = rfBoard->get_tx_stream( txStreamParams );
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150705/66750631/attachment-0001.html>

------------------------------

Message: 4
Date: Mon, 6 Jul 2015 07:32:12 -0500
From: Aaron Henderson <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] FW:  Can ping but not find_device on N210
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"



From: [email protected]
To: [email protected]
Subject: RE: [USRP-users] Can ping but not find_device on N210
Date: Mon, 6 Jul 2015 07:31:44 -0500




Hotmail was telling me it wasn't sending, but obviously it was.

uhd_usrp_probe offers the same error, and my PC's IP address is set to 
10.51.14.35.

Aaron

Date: Wed, 1 Jul 2015 18:49:11 +0200
To: [email protected]
Subject: Re: [USRP-users] Can ping but not find_device on N210
From: [email protected]


  
    
  
  
    Hi Aaron,

    I got your mail four times, so maybe there's something wrong with
    your mail server?

    

    Does 

    

    uhd_usrp_probe --args "addr=192.168.10.2"

    

    work?

    What is your PC's IP address?

    

    Best regards,

    Marcus

    

    On 07/01/2015 04:24 PM, Aaron Henderson
      via USRP-users wrote:

    
    
      
      Hello again list,

        

        I am in a different part of my project and am running into an
        issue with finding my device.

        

        I have found multiple listings on the Internet about this issue
        but it is all overwhelming. Meaning I am not sure which
        information will be beneficial to me or not.

        

        The steps I have taken so far are:

        1. I have pinged the device and it is communicating with the
        computer.

        2. I have ran uhd_find_devices and uhd_usrp_probe(with and
        without the IP address as an arguement), for uhd_find_devices I
        get this error message, 'No UHD Devices Found', and for
        uhd_usrp_probe I get this error message, 

        'Error: LookupError: KeyError: No devices found for ----->

        Device Address:

            addr: 192.168.10.2'

        3. I have disabled my firewall and still the same issue
        persists.

        4. I have started in safe mode and still the same issue
        persists.

        

        Can someone point me to a reliable webpage with a similar issue
        if it exists, or give me some pointers?

        

        Aaron 
      

      
      

      _______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

    
    

  


_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com              
                                                                  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150706/b13bed68/attachment-0001.html>

------------------------------

Message: 5
Date: Mon, 06 Jul 2015 15:24:09 +0200
From: Marcus M?ller <[email protected]>
To: Aaron Henderson <[email protected]>,
        "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Can ping but not find_device on N210
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"

Hi Aaron,

the situation is the following: your PC is in a different subnet than
your USRP, hence the USRP doesn't know where to send packets to your PC
directly, and tries to send them to the configured default gateway.
Probably, this doesn't work either (that gateway probably doesn't exist).

The easiest solution to this is giving your PC an IP address from the
same subnet, e.g. if you're on linux, a

sudo ip address add 192.168.10.100 dev eth0

(assuming eth0 is the network interface you want to use)

Then, add a route through that:

sudo ip route add 192.168.10.0/24 dev eth0

to tell your computer that all packets for any address in the
192.168.10.* network should directly go through eth0.

Best regards,
Marcus

On 07/06/2015 02:31 PM, Aaron Henderson wrote:
> Hotmail was telling me it wasn't sending, but obviously it was.
>
> uhd_usrp_probe offers the same error, and my PC's IP address is set to
> 10.51.14.35.
>
> Aaron
>
> ------------------------------------------------------------------------
> Date: Wed, 1 Jul 2015 18:49:11 +0200
> To: [email protected]
> Subject: Re: [USRP-users] Can ping but not find_device on N210
> From: [email protected]
>
> Hi Aaron,
> I got your mail four times, so maybe there's something wrong with your
> mail server?
>
> Does
>
> uhd_usrp_probe --args "addr=192.168.10.2"
>
> work?
> What is your PC's IP address?
>
> Best regards,
> Marcus
>
> On 07/01/2015 04:24 PM, Aaron Henderson via USRP-users wrote:
>
>     Hello again list,
>
>     I am in a different part of my project and am running into an
>     issue with finding my device.
>
>     I have found multiple listings on the Internet about this issue
>     but it is all overwhelming. Meaning I am not sure which
>     information will be beneficial to me or not.
>
>     The steps I have taken so far are:
>     1. I have pinged the device and it is communicating with the computer.
>     2. I have ran uhd_find_devices and uhd_usrp_probe(with and without
>     the IP address as an arguement), for uhd_find_devices I get this
>     error message, 'No UHD Devices Found', and for uhd_usrp_probe I
>     get this error message,
>     'Error: LookupError: KeyError: No devices found for ----->
>     Device Address:
>         addr: 192.168.10.2'
>     3. I have disabled my firewall and still the same issue persists.
>     4. I have started in safe mode and still the same issue persists.
>
>     Can someone point me to a reliable webpage with a similar issue if
>     it exists, or give me some pointers?
>
>     Aaron
>
>
>     _______________________________________________
>     USRP-users mailing list
>     [email protected] <mailto:[email protected]>
>     http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
> _______________________________________________ USRP-users mailing
> list [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150706/463262a9/attachment-0001.html>

------------------------------

Message: 6
Date: Mon, 6 Jul 2015 09:29:34 -0500
From: Aaron Henderson <[email protected]>
To: Marcus M?ller <[email protected]>,
        "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Can ping but not find_device on N210
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

Now my N210 is not being recognized by the hub I am using.

Does this mean my N210 has gone bad?

Aaron

Date: Mon, 6 Jul 2015 15:24:09 +0200
From: [email protected]
To: [email protected]; [email protected]
Subject: Re: [USRP-users] Can ping but not find_device on N210


  
    
  
  
    Hi Aaron,

    

    the situation is the following: your PC is in a different subnet
    than your USRP, hence the USRP doesn't know where to send packets to
    your PC directly, and tries to send them to the configured default
    gateway. Probably, this doesn't work either (that gateway probably
    doesn't exist).

    

    The easiest solution to this is giving your PC an IP address from
    the same subnet, e.g. if you're on linux, a

    

    sudo ip address add 192.168.10.100 dev eth0 

    

    (assuming eth0 is the network interface you want to use)

    

    Then, add a route through that:

    

    sudo ip route add 192.168.10.0/24 dev eth0 

    

    to tell your computer that all packets for any address in the
    192.168.10.* network should directly go through eth0.

    

    Best regards,

    Marcus

    

    On 07/06/2015 02:31 PM, Aaron Henderson
      wrote:

    
    
      
      Hotmail was telling me it wasn't sending, but
        obviously it was.

        

        uhd_usrp_probe offers the same error, and my PC's IP address is
        set to 10.51.14.35.

        

        Aaron

        

        
          Date: Wed, 1 Jul 2015 18:49:11 +0200

          To: [email protected]

          Subject: Re: [USRP-users] Can ping but not find_device on N210

          From: [email protected]

          

          Hi Aaron,

          I got your mail four times, so maybe there's something wrong
          with your mail server?

          

          Does 

          

          uhd_usrp_probe --args "addr=192.168.10.2"

          

          work?

          What is your PC's IP address?

          

          Best regards,

          Marcus

          

          On 07/01/2015 04:24 PM, Aaron
            Henderson via USRP-users wrote:

          
          
            
            Hello again list,

              

              I am in a different part of my project and am running into
              an issue with finding my device.

              

              I have found multiple listings on the Internet about this
              issue but it is all overwhelming. Meaning I am not sure
              which information will be beneficial to me or not.

              

              The steps I have taken so far are:

              1. I have pinged the device and it is communicating with
              the computer.

              2. I have ran uhd_find_devices and uhd_usrp_probe(with and
              without the IP address as an arguement), for
              uhd_find_devices I get this error message, 'No UHD Devices
              Found', and for uhd_usrp_probe I get this error message, 

              'Error: LookupError: KeyError: No devices found for
              ----->

              Device Address:

                  addr: 192.168.10.2'

              3. I have disabled my firewall and still the same issue
              persists.

              4. I have started in safe mode and still the same issue
              persists.

              

              Can someone point me to a reliable webpage with a similar
              issue if it exists, or give me some pointers?

              

              Aaron 
            

            
            

            _______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

          
          

          

          _______________________________________________
          USRP-users mailing list
          [email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
      
    
    
                                          
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150706/8494f368/attachment-0001.html>

------------------------------

Message: 7
Date: Mon, 06 Jul 2015 16:36:11 +0200
From: Marcus M?ller <[email protected]>
To: Aaron Henderson <[email protected]>,
        "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Can ping but not find_device on N210
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"

Although this is a totally new symptom, and can't be explained by the
network configuration: N210s seldom go bad.
Power Cycle your N210; directly attach your USRP to your PC; do the
network LEDs light up?
Your Network manager will try to configure your direct connection, and
will fail. Manually configure the network connection, and you should be
fine.

Best regards,
Marcus
On 07/06/2015 04:29 PM, Aaron Henderson wrote:
> Now my N210 is not being recognized by the hub I am using.
>
> Does this mean my N210 has gone bad?
>
> Aaron
>
> ------------------------------------------------------------------------
> Date: Mon, 6 Jul 2015 15:24:09 +0200
> From: [email protected]
> To: [email protected]; [email protected]
> Subject: Re: [USRP-users] Can ping but not find_device on N210
>
> Hi Aaron,
>
> the situation is the following: your PC is in a different subnet than
> your USRP, hence the USRP doesn't know where to send packets to your
> PC directly, and tries to send them to the configured default gateway.
> Probably, this doesn't work either (that gateway probably doesn't exist).
>
> The easiest solution to this is giving your PC an IP address from the
> same subnet, e.g. if you're on linux, a
>
> sudo ip address add 192.168.10.100 dev eth0
>
> (assuming eth0 is the network interface you want to use)
>
> Then, add a route through that:
>
> sudo ip route add 192.168.10.0/24 dev eth0
>
> to tell your computer that all packets for any address in the
> 192.168.10.* network should directly go through eth0.
>
> Best regards,
> Marcus
>
> On 07/06/2015 02:31 PM, Aaron Henderson wrote:
>
>     Hotmail was telling me it wasn't sending, but obviously it was.
>
>     uhd_usrp_probe offers the same error, and my PC's IP address is
>     set to 10.51.14.35.
>
>     Aaron
>
>     ------------------------------------------------------------------------
>     Date: Wed, 1 Jul 2015 18:49:11 +0200
>     To: [email protected] <mailto:[email protected]>
>     Subject: Re: [USRP-users] Can ping but not find_device on N210
>     From: [email protected] <mailto:[email protected]>
>
>     Hi Aaron,
>     I got your mail four times, so maybe there's something wrong with
>     your mail server?
>
>     Does
>
>     uhd_usrp_probe --args "addr=192.168.10.2"
>
>     work?
>     What is your PC's IP address?
>
>     Best regards,
>     Marcus
>
>     On 07/01/2015 04:24 PM, Aaron Henderson via USRP-users wrote:
>
>         Hello again list,
>
>         I am in a different part of my project and am running into an
>         issue with finding my device.
>
>         I have found multiple listings on the Internet about this
>         issue but it is all overwhelming. Meaning I am not sure which
>         information will be beneficial to me or not.
>
>         The steps I have taken so far are:
>         1. I have pinged the device and it is communicating with the
>         computer.
>         2. I have ran uhd_find_devices and uhd_usrp_probe(with and
>         without the IP address as an arguement), for uhd_find_devices
>         I get this error message, 'No UHD Devices Found', and for
>         uhd_usrp_probe I get this error message,
>         'Error: LookupError: KeyError: No devices found for ----->
>         Device Address:
>             addr: 192.168.10.2'
>         3. I have disabled my firewall and still the same issue persists.
>         4. I have started in safe mode and still the same issue persists.
>
>         Can someone point me to a reliable webpage with a similar
>         issue if it exists, or give me some pointers?
>
>         Aaron
>
>
>         _______________________________________________
>         USRP-users mailing list
>         [email protected] <mailto:[email protected]>
>         http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
>     _______________________________________________ USRP-users mailing
>     list [email protected]
>     <mailto:[email protected]>
>     http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150706/9c27db36/attachment-0001.html>

------------------------------

Message: 8
Date: Mon, 6 Jul 2015 07:39:22 -0700
From: Neel Pandeya <[email protected]>
To: Aaron Henderson <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Can ping but not find_device on N210
Message-ID:
        <cacaxmv-n23jc4twmbfmxqgbkyoptxqr5z9ej2xtehdatirh...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Your host computer and the N210 should be on the same subnet, but with
different IP addresses, such as 192.168.10.2/24 and 192.168.10.99/24. The
ping uses ICMP Echo, but the uhd_find_devices uses broadcast IP packets. If
you have a hub, switch, or router in between the host computer and the
N210, then it might be blocking these IP packets. Are you able to run
(replace the correct IP address for your N210):

uhd_usrp_probe --args="addr=192.168.10.2"

--Neel



On 6 July 2015 at 07:29, Aaron Henderson via USRP-users <
[email protected]> wrote:

> Now my N210 is not being recognized by the hub I am using.
>
> Does this mean my N210 has gone bad?
>
> Aaron
>
> ------------------------------
> Date: Mon, 6 Jul 2015 15:24:09 +0200
> From: [email protected]
> To: [email protected]; [email protected]
> Subject: Re: [USRP-users] Can ping but not find_device on N210
>
> Hi Aaron,
>
> the situation is the following: your PC is in a different subnet than your
> USRP, hence the USRP doesn't know where to send packets to your PC
> directly, and tries to send them to the configured default gateway.
> Probably, this doesn't work either (that gateway probably doesn't exist).
>
> The easiest solution to this is giving your PC an IP address from the same
> subnet, e.g. if you're on linux, a
>
> sudo ip address add 192.168.10.100 dev eth0
>
> (assuming eth0 is the network interface you want to use)
>
> Then, add a route through that:
>
> sudo ip route add 192.168.10.0/24 dev eth0
>
> to tell your computer that all packets for any address in the 192.168.10.*
> network should directly go through eth0.
>
> Best regards,
> Marcus
>
> On 07/06/2015 02:31 PM, Aaron Henderson wrote:
>
> Hotmail was telling me it wasn't sending, but obviously it was.
>
> uhd_usrp_probe offers the same error, and my PC's IP address is set to
> 10.51.14.35.
>
> Aaron
>
>  ------------------------------
> Date: Wed, 1 Jul 2015 18:49:11 +0200
> To: [email protected]
> Subject: Re: [USRP-users] Can ping but not find_device on N210
> From: [email protected]
>
> Hi Aaron,
> I got your mail four times, so maybe there's something wrong with your
> mail server?
>
> Does
>
> uhd_usrp_probe --args "addr=192.168.10.2"
>
> work?
> What is your PC's IP address?
>
> Best regards,
> Marcus
>
> On 07/01/2015 04:24 PM, Aaron Henderson via USRP-users wrote:
>
> Hello again list,
>
> I am in a different part of my project and am running into an issue with
> finding my device.
>
> I have found multiple listings on the Internet about this issue but it is
> all overwhelming. Meaning I am not sure which information will be
> beneficial to me or not.
>
> The steps I have taken so far are:
> 1. I have pinged the device and it is communicating with the computer.
> 2. I have ran uhd_find_devices and uhd_usrp_probe(with and without the IP
> address as an arguement), for uhd_find_devices I get this error message,
> 'No UHD Devices Found', and for uhd_usrp_probe I get this error message,
> 'Error: LookupError: KeyError: No devices found for ----->
> Device Address:
>     addr: 192.168.10.2'
> 3. I have disabled my firewall and still the same issue persists.
> 4. I have started in safe mode and still the same issue persists.
>
> Can someone point me to a reliable webpage with a similar issue if it
> exists, or give me some pointers?
>
> Aaron
>
>
> _______________________________________________
> USRP-users mailing 
> [email protected]http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
> _______________________________________________ USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150706/dbe9af10/attachment-0001.html>

------------------------------

Message: 9
Date: Mon, 06 Jul 2015 10:45:31 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Can ping but not find_device on N210
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"

On 07/06/2015 10:39 AM, Neel Pandeya via USRP-users wrote:
> Your host computer and the N210 should be on the same subnet, but with 
> different IP addresses, such as 192.168.10.2/24 
> <http://192.168.10.2/24> and 192.168.10.99/24 
> <http://192.168.10.99/24>. The ping uses ICMP Echo, but the 
> uhd_find_devices uses broadcast IP packets. If you have a hub, switch, 
> or router in between the host computer and the N210, then it might be 
> blocking these IP packets. Are you able to run (replace the correct IP 
> address for your N210):
>
> uhd_usrp_probe --args="addr=192.168.10.2"
>
> --Neel
>
>
Also, and I've said this in the past.  The 1GiGe port on the USRPs 
shouldn't be thought of as a general-purpose network port, but as a 
convenient
   and cheap "data bus" between you computer and the USRP.  The USRPs 
don't have a full IP routing stack on them, so the more IP and
   ethernet-switching "plumbing" that is placed between the USRP and 
your host computer, the more likely it is that you'll have problems,
   particularly if you're not familiar with IP network design and 
configuration.  Further, MANY 1GiGe switches apparently cannot sustain high
   data rates across their switching fabric, and start losing frames 
when streaming samples from USRPs.


>
> On 6 July 2015 at 07:29, Aaron Henderson via USRP-users 
> <[email protected] <mailto:[email protected]>> wrote:
>
>     Now my N210 is not being recognized by the hub I am using.
>
>     Does this mean my N210 has gone bad?
>
>     Aaron
>
>     ------------------------------------------------------------------------
>     Date: Mon, 6 Jul 2015 15:24:09 +0200
>     From: [email protected] <mailto:[email protected]>
>     To: [email protected] <mailto:[email protected]>;
>     [email protected] <mailto:[email protected]>
>     Subject: Re: [USRP-users] Can ping but not find_device on N210
>
>     Hi Aaron,
>
>     the situation is the following: your PC is in a different subnet
>     than your USRP, hence the USRP doesn't know where to send packets
>     to your PC directly, and tries to send them to the configured
>     default gateway. Probably, this doesn't work either (that gateway
>     probably doesn't exist).
>
>     The easiest solution to this is giving your PC an IP address from
>     the same subnet, e.g. if you're on linux, a
>
>     sudo ip address add 192.168.10.100 dev eth0
>
>     (assuming eth0 is the network interface you want to use)
>
>     Then, add a route through that:
>
>     sudo ip route add 192.168.10.0/24 <http://192.168.10.0/24> dev eth0
>
>     to tell your computer that all packets for any address in the
>     192.168.10.* network should directly go through eth0.
>
>     Best regards,
>     Marcus
>
>     On 07/06/2015 02:31 PM, Aaron Henderson wrote:
>
>         Hotmail was telling me it wasn't sending, but obviously it was.
>
>         uhd_usrp_probe offers the same error, and my PC's IP address
>         is set to 10.51.14.35.
>
>         Aaron
>
>         
> ------------------------------------------------------------------------
>         Date: Wed, 1 Jul 2015 18:49:11 +0200
>         To: [email protected] <mailto:[email protected]>
>         Subject: Re: [USRP-users] Can ping but not find_device on N210
>         From: [email protected]
>         <mailto:[email protected]>
>
>         Hi Aaron,
>         I got your mail four times, so maybe there's something wrong
>         with your mail server?
>
>         Does
>
>         uhd_usrp_probe --args "addr=192.168.10.2"
>
>         work?
>         What is your PC's IP address?
>
>         Best regards,
>         Marcus
>
>         On 07/01/2015 04:24 PM, Aaron Henderson via USRP-users wrote:
>
>             Hello again list,
>
>             I am in a different part of my project and am running into
>             an issue with finding my device.
>
>             I have found multiple listings on the Internet about this
>             issue but it is all overwhelming. Meaning I am not sure
>             which information will be beneficial to me or not.
>
>             The steps I have taken so far are:
>             1. I have pinged the device and it is communicating with
>             the computer.
>             2. I have ran uhd_find_devices and uhd_usrp_probe(with and
>             without the IP address as an arguement), for
>             uhd_find_devices I get this error message, 'No UHD Devices
>             Found', and for uhd_usrp_probe I get this error message,
>             'Error: LookupError: KeyError: No devices found for ----->
>             Device Address:
>                 addr: 192.168.10.2'
>             3. I have disabled my firewall and still the same issue
>             persists.
>             4. I have started in safe mode and still the same issue
>             persists.
>
>             Can someone point me to a reliable webpage with a similar
>             issue if it exists, or give me some pointers?
>
>             Aaron
>
>
>             _______________________________________________
>             USRP-users mailing list
>             [email protected]  <mailto:[email protected]>
>             http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
>         _______________________________________________ USRP-users
>         mailing list [email protected]
>         <mailto:[email protected]>
>         http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
>     _______________________________________________
>     USRP-users mailing list
>     [email protected] <mailto:[email protected]>
>     http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150706/192d2cce/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com


------------------------------

End of USRP-users Digest, Vol 59, Issue 6
*****************************************

Reply via email to