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. Re: problem with my rx daughterboard
(Marcus M?ller via USRP-users)
2. USRP N210 IF question (Dimitris Siafarikas via USRP-users)
3. USRP2 detection problem (Soham Chakraborti via USRP-users)
4. Re: problem with my rx daughterboard (Martin Braun via USRP-users)
5. Re: USRP2 detection problem (Martin Braun via USRP-users)
6. Re: USRP N210 IF question (Martin Braun via USRP-users)
----------------------------------------------------------------------
Message: 1
Date: Sun, 01 Jun 2014 20:24:11 +0200
From: Marcus M?ller via USRP-users <[email protected]>
To: usrp-users <[email protected]>
Subject: Re: [USRP-users] problem with my rx daughterboard
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
Hi Riana,
please ask follow up questions to the mailing list.
>honestly, i don't know mailing list about openbts, except this usrp-users
Usrp-Users is *not* an OpenBTS mailing list, really. Many people running
OpenBTS are using USRPs, yes, and for any problems that are *directly*
related to USRPs, this will be the right mailing list,
but your problems, at least from the log you inserted, are purely
OpenBTS-related, and should be discussed on the OpenBTS mailing lists.
You will have to search the internet for the official mailing list.
Anyway, even with old hardware, you should update your software,
especially get rid of libusrp and install uhd, if you haven't done so
already; the number of people that still know how to use the old libusrp
is very very limited.
Also, Ubuntu 10.10 is nearly four years old, please consider updating
that, because of all the library, compiler and operating system problems
you might encounter.
> i get a new PC, i think it more faster than before
Good luck!
Greetings,
Marcus
On 01.06.2014 19:49, Riana Risnawati wrote:
> thank you Mr. Marcus
>
> i get a new PC, i think it more faster than before
> and maximal usb/throughput in my PC now 32 mb/sec
>
> now i use ubuntu 10.10 desktop, not in virtual machine again
> USRP 1
>
> but i got a problem again , when i run openbts, there are still some failed
> data
>
> Starting the system...
> 1401644563.9733 FORCE 3079083728 Logger.cpp:109:gSetLogFile: setting
> log path to test.out
> 1401644563.9735 ALARM 3079083728 ControlCommon.cpp:560:load: TMSITable
> cannot open TMSITable.txt for reading
> 1401644563.9737 ALARM 3079083728 OpenBTS.cpp:129:main: OpenBTS
> starting, ver 2.6.0Mamou build date Jun 2 2014
> 1401644563.9792 FORCE 3079010528 Logger.cpp:194:gLogInit: Setting
> initial global logging level to NOTICE
> 1401644563.9794 FORCE 3079010528 Logger.cpp:109:gSetLogFile: setting
> log path to test.TRX.out
> 1401644568.9983 ALARM 3079097200 Transceiver.cpp:551:driveControl: TX
> failed to tune
> 1401644568.9985 ALARM 3079083728 TRXManager.cpp:349:tune: TXTUNE
> failed with status 1
> 1401644569.535781 3079083728:
>
> do you know why ? can you help me again ?
> honestly, i don't know mailing list about openbts, except this usrp-users
>
> thank you
> riana
>
> On 5/31/14, Marcus M?ller <[email protected]> wrote:
>> Hi Rianam
>>
>> wrong mailing list for question 1) -- this is not the openBTS user
>> mailing list.
>>
>> 2) I think I vaguely remember that command from GNU Radio 3.3 or 3.4...
>> I'd assume that if you're still using it, you're probably having a lot
>> of problems because of how old your GNU Radio software is.
>> However, overruns never have to do with daughterboards.
>> Your computer is too slow, your sampling rate is to high for your USB
>> link or there is something else wrong,
>> intercepting with your transmission. You get 4MB/s, which is about
>> 32MBit/s, faster than USB1, so I guess you're using a computer that's
>> too slow to keep up with your tasks. I've never seen this at a rate as
>> low as this.
>>
>> 3) I'd assume your harddrive is very slow, you're in a virtual machine,
>> you have a very "special" (ie. broken) USB controller, you have hard
>> drive defects or you are running on something with less than 1 GHz of
>> CPU frequency. These are signs that your computer is too slow.
>>
>> Do next: Update GNU Radio, UHD, openBTS, get a faster PC.
>>
>> Greetings,
>> Marcus
>>
>> On 31.05.2014 16:24, Riana Risnawati via USRP-users wrote:
>>> hello everyone,
>>> i need your help for my deadline thesis to solve this problem.
>>> i think my rx daughterboard is broken.
>>> i am using usrp1, anything that i running in my OpenBTS program always
>>> failed and it because RX daughterboard. like example :
>>>
>>> 1) when i running ./OpenBTS :
>>> i got result :
>>> Starting the system...
>>> 1401532271.5140 FORCE 3077900512 Logger.cpp:109:gSetLogFile: setting
>>> log path to test.out
>>> 1401532271.5141 ALARM 3077900512 ControlCommon.cpp:560:load: TMSITable
>>> cannot open TMSITable.txt for reading
>>> 1401532271.5142 ALARM 3077900512 OpenBTS.cpp:129:main: OpenBTS
>>> starting, ver 2.6.0Mamou build date May 31 2014
>>> 1401532271.5941 FORCE 3079440608 Logger.cpp:194:gLogInit: Setting
>>> initial global logging level to NOTICE
>>> 1401532271.5941 FORCE 3079440608 Logger.cpp:109:gSetLogFile: setting
>>> log path to test.TRX.out
>>> 1401532276.5713 ALARM 3077900512 TRXManager.cpp:447:setMaxDelay:
>>> SETMAXDLY failed with status -1
>>> 1401532276.5716 ALARM 3077900512 TRXManager.cpp:458:setRxGain:
>>> SETRXGAIN failed with status -1
>>> 1401532276.927067 3077900512:
>>>
>>> look at the last alarm, failed in set RX gain.
>>>
>>> 2) when i run ./test_usrp_standar_rx the result are :
>>> ./test_usrp_standar_rx hasilnya :
>>> xfered 1.34e+08 bytes in 33.3 seconds. 4.03e+06 bytes/sec. cpu time =
>>> 1.452
>>> noverruns = 51
>>>
>>> the overruns is so large compared with tx only 12 overruns
>>>
>>> 3) i run /usrp_rx_cfile.py -R B -f 900M risultato.txt the result are :
>>> Using RX d'board B: Flex 900 Rx
>>> USB sample rate 3.25M
>>> uOuOuOuOuOuOuOuOuOuOuOuOuOuO^C
>>>
>>> do you know how to solve it ? can you give me idea what must i do next?
>>> please reply
>>> thank you
>>>
>>>
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected]
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
------------------------------
Message: 2
Date: Fri, 30 May 2014 11:36:26 +0300
From: Dimitris Siafarikas via USRP-users <[email protected]>
To: <[email protected]>
Subject: [USRP-users] USRP N210 IF question
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi list,
just a quick question.
I am trying to understand the architecture of the usrp n210. I have not
managed so far to figure out the use of the Numerically Controlled
Oscillator (NCO). I do not see anyone mention the IF bandwidth but from what
I can see, NCO has to convert IF signal to baseband signal. Is this correct?
If so, why to do that? After the SBX daughterboard, isn't the signal at
baseband already?
Please enlighten me.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140530/66751273/attachment-0001.html>
------------------------------
Message: 3
Date: Fri, 30 May 2014 16:44:04 +0530
From: Soham Chakraborti via USRP-users <[email protected]>
To: [email protected]
Subject: [USRP-users] USRP2 detection problem
Message-ID:
<CAPMbYk56=mm-yb4u4nujgj5pybhqkybqj_mks-66mmsqgv7...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I am unable to detect the usrp2 which is connected to my pc through a 1gb
Ethernet cable .
when i run the USRP2_probe command to search for usrp2 i get the following
error..
no usrp2 device found ..
1) I have usrp2_probe when i run it i get the following error
socket(PF_PACKET, SOCK_RAW, htons(0xBEEF)): Operation not permitted
em1: socket: No such file or directory
No USRP2 found.
em1 is the ethernet name in linux which i get on ifconfig .
2)I am unable to ping the usrp2 192.168.10.2 ,my host has ip add of
192.168.10.1
3)led sequence lights up as per properly all blinks with D and F remaining
lighted and ethernet cable on both side is alight.
Thanks for the help,
soham
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140530/21d18b1a/attachment-0001.html>
------------------------------
Message: 4
Date: Mon, 02 Jun 2014 09:13:32 +0200
From: Martin Braun via USRP-users <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] problem with my rx daughterboard
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
On 06/01/2014 08:24 PM, Marcus M?ller via USRP-users wrote:
> Hi Riana,
>
> please ask follow up questions to the mailing list.
>
>> honestly, i don't know mailing list about openbts, except this usrp-users
You can find openbts-discuss here:
https://lists.sourceforge.net/lists/listinfo/openbts-discuss
Good luck with your setup!
M
------------------------------
Message: 5
Date: Mon, 02 Jun 2014 09:20:35 +0200
From: Martin Braun via USRP-users <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] USRP2 detection problem
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Soham,
it looks like you're running an old version of our software.
It might make sense to update to a current UHD version, as well as the
image on the device, and then retry.
You can find instructions to update here:
http://code.ettus.com/redmine/ettus/projects/uhd/wiki, and once that's
done you can run uhd_images_downloader to get new images and
usrp2_card_burner to update the image on the SD card.
M
On 05/30/2014 01:14 PM, Soham Chakraborti via USRP-users wrote:
> I am unable to detect the usrp2 which is connected to my pc through a
> 1gb Ethernet cable .
> when i run the USRP2_probe command to search for usrp2 i get the
> following error..
> no usrp2 device found ..
>
> 1) I have usrp2_probe when i run it i get the following error
>
> socket(PF_PACKET, SOCK_RAW, htons(0xBEEF)): Operation not permitted
> em1: socket: No such file or directory
> No USRP2 found.
>
> em1 is the ethernet name in linux which i get on ifconfig .
>
> 2)I am unable to ping the usrp2 192.168.10.2 ,my host has ip add of
> 192.168.10.1
>
>
> 3)led sequence lights up as per properly all blinks with D and F
> remaining lighted and ethernet cable on both side is alight.
>
> Thanks for the help,
> soham
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 6
Date: Mon, 02 Jun 2014 09:24:23 +0200
From: Martin Braun via USRP-users <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] USRP N210 IF question
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Hey Dimitris,
first, note that all digital IF signals will always be at baseband, and
you don't have to consider that in your software.
If you're interested in how the device works: The TVRX, for example,
actually has an IF, so we'd need it there. As for the SBX, the
synthesizer can't actually exactly tune to any frequency, so we correct
that using the CORDIC as well.
Cheers,
Martin
On 05/30/2014 10:36 AM, Dimitris Siafarikas via USRP-users wrote:
> Hi list,
>
>
>
> just a quick question.
>
>
>
> I am trying to understand the architecture of the usrp n210. I have not
> managed so far to figure out the use of the Numerically Controlled
> Oscillator (NCO). I do not see anyone mention the IF bandwidth but from
> what I can see, NCO has to convert IF signal to baseband signal. Is this
> correct? If so, why to do that? After the SBX daughterboard, isn?t the
> signal at baseband already?
>
>
>
>
>
> Please enlighten me.
>
>
>
>
>
> Thank you.
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
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 46, Issue 2
*****************************************
