[USRP-users] N210 + new WBX v3 daughterboard does not work, but with old WBX v2 it works (OpenBTS)

Marcus D. Leech mleech at ripnet.com
Thu Sep 25 08:19:20 EDT 2014


On 09/25/2014 07:31 AM, Martin via USRP-users wrote:
> Hi,
>
> I seem to have found the problem.
> I had to lower the rxgain dramaticly.
>
> With old WBX v2 an  rxgain of 47 would work fine. Even with phones as 
> close as 1.5 meter from the USRP receive antenna.
> With WBX v3 I had to lower the rxgain to 10 to get it to work at this 
> distance.
>
> With an rxgain setting of 18, it would work with phones at 5 meter or 
> further away, but not closer.
>
> I am a bit surprised that the large-signal tolerance is so much less 
> with new WBX v3 in comparison with old WBX v2.
>
> The absolute rxgain settings seem to not mean the same.
>
> I am not sure if the new WBX is much more sensitive, so you need to 
> use lower gain settings, or that the new WBX has a lower large-signal 
> tolerance before it saturates.
>
>
> With best regards,
>
> Martin Dudok van Heel
>
Both WBX use the same 31.5dB step attenuator in the receive path.

Is it possible that your "old" WBX has a damaged LNA, and so it's 
somewhat deaf?


> On 25-09-14 10:02, Martin via USRP-users wrote:
>> Hi,
>>
>> I am trying to use OpenBTS 4.0 git with a USRP N210 + WBX daughterboard
>> + GPSDO.
>> When I use a N210 + old WBX v2 everything works.
>> Phones, see the network, they can register and call each other.
>>
>> But with new WBX v3 daughterboards or with a new SBX daughterboard, it
>> does not work.
>> Phones cannot register.
>> The phones see the OpenBTS network, but they never successfully
>> communicate with it.
>> No registration, no calls.
>>
>> I tried OpenBTS with two old WBX v2 daughterboards which both result in
>> a working OpenBTS setup.
>> I tried with two new WBX v3 daughterboards and one new SBX daughterbord
>> which all fail.
>> Phones cannot register.
>>
>> Can someone tell me what the differences are between WBX v2 and WBX v3.
>> I know the TX gain setting has a different range  (31.5 dB versus 25 dB)
>> and that the TX/RX RX2 connectors switched place, but other then that I
>> have no idea.
>>
>> Does the UHD driver handle them differently?
>> I used UHD_003.007.002 (driver and firmware and fpga code)
>>
>> I did notice that with uhd_usrp_probe there is a quite long line for
>> daughterboard id: WBX + Simple GDB, WBX v3 + Simple GDB, WBX v4 + Simple
>> GDB, WBX-120 + Simple GDB (0x004f)
>> Is it supposed to have all WBX types in the ID?
>>
>> See attached uhd_usrp_probe logs with both an old and a new WBX.
>> (I do not know if the list will accept text attachments)
>>
>>
>> This was all with the openBTS 4.0 git checkout of this week.
>> With the following added small patch to have it build for USRP N210
>>
>>
>> openbts/debian/rules.git_4.0_2014091801_unmodified_missing_EXTRA_CONFIGURE_FLAGS 
>>
>>
>>    2014-09-18 13:23:48.000000000 +0200
>>    +++ openbts/debian/rules    2014-09-18 14:09:33.000000000 +0200
>>    @@ -26,7 +26,7 @@
>>       configure-stamp: configure
>>           dh_testdir
>>           # Add here commands to configure the package.
>>    -    ./configure $(confflags)
>>    +    ./configure $(confflags) $(EXTRA_CONFIGURE_FLAGS)
>>           touch configure-stamp
>>
>> With an older OpenBTS 2.8 release phones can register, even with the new
>> WBX v3 daughterboards.
>> (in my setup, old OpenBTS 2.8 uses a different UHD driver + UHD firmware
>> version, which may be of influence)
>>
>> I am not sure what the cause of this is or how to debug this.
>>
>> I have set Log to INFO so I could see the gain settings.
>> OpenBTS seems to handle this well.
>> With old WBX v2 the txgain starts at 25 dB and then goes down to 16 dB.
>> With new WBXv3 the txgain starts at 31.5 dB and then goes down to 
>> 22.5 dB.
>> So this sounds about right.
>>
>>
>> There might be a difference in how the UHD driver handles them.
>> There may also be a small groupdelay difference.
>>
>> ....
>>
>> Any ideas what may cause the difference in behaviour?
>>
>> With best regards,
>>
>> Martin
>>
>>
>> On 20-09-14 17:53, Martin wrote:
>>> Hi Michael,
>>>
>>> The fix of today, resolves the sqlite and libzmq issues.
>>> The build completes.
>>>
>>> The next issue is that the current code will always build for RAD1,
>>> independent of what hardware is specified with  build.sh HARDWARE
>>> So ./build.sh N210 will still build for RAD1.
>>>
>>> I fixed this by patching openbts/debian/rules by adding
>>> $(EXTRA_CONFIGURE_FLAGS) to the ./configure call
>>>
>>> ---
>>> openbts/debian/rules.git_4.0_2014091801_unmodified_missing_EXTRA_CONFIGURE_FLAGS 
>>>
>>>
>>> 2014-09-18 13:23:48.000000000 +0200
>>> +++ openbts/debian/rules    2014-09-18 14:09:33.000000000 +0200
>>> @@ -26,7 +26,7 @@
>>>    configure-stamp: configure
>>>        dh_testdir
>>>        # Add here commands to configure the package.
>>> -    ./configure $(confflags)
>>> +    ./configure $(confflags) $(EXTRA_CONFIGURE_FLAGS)
>>>        touch configure-stamp
>>>
>>>    #Architecture
>>>
>>> I suggest you add this to git.
>>>
>>> Now openbts builds for N210 and openBTS and OpenBTSCLI will start.
>>>
>>> I then still had a few problems.
>>> With Openregistration the phones could call testnumber 2600, but the
>>> phones could not call each other because  asterisk was notable to open
>>> the /var/lib/asterisk/sqlite3.db
>>> This has to do with wrong permissions on
>>> /var/lib/asterisk/sqlite3dir/sqlite3.db
>>> /var/lib/asterisk/sqlite3dir/sqlite3.db-war
>>> /var/lib/asterisk/sqlite3dir/sqlite3.db-shm
>>> I could work around this with: sudo chmod a+rw
>>> /var/lib/asterisk/sqlite3dir/sqlite3.db*
>>> I later saw that rebooting is probably required, since this will call
>>> the updated /etc/rc.local from range-configs.deb which will change the
>>> permissions on /var/lib/asterisk/sqlite3dir/sqlite3.db*
>>>
>>> I now seem to have a working OpenBTS 4.x with N210.
>>>
>>> Regards,
>>>
>>> Martin
>>>
>>>
>>> On 18-09-14 13:19, Michael Iedema wrote:
>>>> Hi Martin,
>>>>
>>>> A fix committed today to the dev repo should resolve your issue with
>>>> the empty sqlite3 directories when compiling 4.x. Maybe give it
>>>> another try?
>>>>
>>>> The dev repo contains scripts used to build and install the different
>>>> OpenBTS suite components. The openbts repo contains only OpenBTS.
>>>>
>>>> The current master of openbts isn't stable. It's a preview of the
>>>> upcoming 5.0 release. For now, I'd stick to the 4.x branch. Older
>>>> releases are also available in the individual repositories but have
>>>> not been automated with the dev scripts.
>>>>
>>>> Regards,
>>>> -Michael
>>>>
>>>> On Sep 18, 2014, at 12:30 PM, Martin <openbtsmail at olifantasia.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have been running OpenBTS 2.8 successfully for many years on ettus
>>>>> N210 based systems.
>>>>> Now I am trying to work with more recent OpenBTS releases, but I am
>>>>> having trouble getting any current openbts release to build and work
>>>>> with N210.
>>>>>
>>>>> http://openbts.org/get-the-code/
>>>>>
>>>>> v5.x
>>>>> -current git dev master (5.x) does build on ubuntu 14.04 but I could
>>>>> not get it working with N210. registration does not complete (no
>>>>> reject, just no completed registration or reject)
>>>>> v4.x
>>>>> -current git dev v4.0 branch does not compile without manual hacks
>>>>> (missing sqlite3/Makefile.in) and after that the CLI does not seem
>>>>> to work
>>>>> v4.0.0
>>>>> -v4.0.0-source.zip does not have a build.sh script. I have not yet
>>>>> tried to build by hand. Current git branch 4.0 checkout of build.sh
>>>>> and friends does not work without manual changes.
>>>>> v3.1.x
>>>>> -I am not sure where to download older v3.1.x releases
>>>>>
>>>>> Does anybody have experience with a stable release that works with
>>>>> N210?
>>>>> How can I download that release?
>>>>> Are there any special build or configure instructions?
>>>>>
>>>>> How can I download older releases?
>>>>> Can I still download a source package of v3.1.x.?
>>>>> Or can I  checkout a specific git commit  which corresponds to
>>>>> v3.1.x) or even  svn checkout (svn co
>>>>> http://wush.net/svn/range/software/public public)
>>>>>
>>>>> I know you can do a git development checkout for branch v4 or v5.
>>>>> But this is always a moving target.
>>>>> I could find two openbts git repositories at
>>>>> https://github.com/RangeNetworks/dev and at
>>>>> https://github.com/RangeNetworks/openbts
>>>>>
>>>>> Are they different?
>>>>> Which one is stable?
>>>>>
>>>>> The quickstart references the only dev version
>>>>>
>>>>> Are there also stable releases which can be downloaded as zip or
>>>>> tar.gz or checked out with git?
>>>>>
>>>>> Below my experiences with the current releases
>>>>> http://openbts.org/get-the-code/
>>>>>
>>>>> follow the quickstart and checkout git dev
>>>>> https://github.com/RangeNetworks/dev/wiki
>>>>> OpenBTS 5.x:
>>>>>
>>>>> git clone https://github.com/RangeNetworks/dev.git
>>>>> cd dev
>>>>> ./clone.sh
>>>>>
>>>>> ./switchto.sh master  (This should switch to the current git
>>>>> development branche of openbts
>>>>> 5.x)
>>>>>
>>>>> Build completes on ubuntu 14.04 i386.
>>>>>
>>>>> There is both
>>>>>
>>>>> But running openbts does not work stable. Phones do not seem to
>>>>> register. I tried both adding the IMSIs to SIP_BUDDIES in sqlite3.db
>>>>> and adding 001 as openbregistration string to allow all phones with
>>>>> MCC 001 (IMSI starting with 001)
>>>>> When I scan for networks with a phone, sometimes the openbts network
>>>>> shows up and sometimes it does not showup.
>>>>> When it does see the network, I cannot register. Not because my
>>>>> phone is rejected, but it seems that the registration or rejection
>>>>> does not complete.
>>>>> I am using this with a N210 with GPS-synced GPSDO 10 Mhz refclock
>>>>> which works fine with OpenBTS 2.8
>>>>>
>>>>> OpenBTS 4.x:
>>>>> git clone https://github.com/RangeNetworks/dev.git
>>>>> cd dev ./clone.sh
>>>>> ./switchto.sh 4.0   (This should switch to the current git
>>>>> development branche of openbts 4.x)
>>>>> When trying to build, I get errors of missing
>>>>> openbts/libsqlite3/Makefile.in in the following places:
>>>>> ./smqueue/sqlite3
>>>>> ./smqueue/SR/sqlite3
>>>>> ./subscriberRegistry/sqlite3
>>>>> ./openbts/sqlite3
>>>>>
>>>>> When I manually copy the sqlite3 directories from the
>>>>> v4.0.0-source.zip the build finished.
>>>>> Installation of the resulting debs fails, because it requires a
>>>>> range-zmq package
>>>>> When I copy the zeromq-3.2.2 directory from v4.0.0-source.zip, do
>>>>> into the dir and run autoreconf and dpkg-buildpackage -us -uc then
>>>>> it builds the range-libzmq_3.2.2.3 deb package I can now install the
>>>>> debs
>>>>> Running openbts, asterisk, sipauthserver and smsqueue does indicate
>>>>> starting up openbts but the CLI does not communicate with OpenBTS
>>>>> (ps -e | grep openbts shows that openbts is running)
>>>>> OpenBTS/OpenBTSCLI
>>>>> config
>>>>> sending datagram: No such file or directory
>>>>> There is both
>>>>> Is the remote application running?
>>>>>
>>>>> I vaguely remember that there was a CLI problem with early v4.0
>>>>> releases and that there was a manual fix, but I could not find the 
>>>>> fix.
>>>>>
>>>>> I have not tested if openbts is working even though the CLI is not
>>>>> working.
>>>>>
>>>>> OpenBTS 4.0.0 from git:
>>>>> As suggested on the quickstart:
>>>>> git clone https://github.com/RangeNetworks/dev.git
>>>>> cd dev ./clone.sh ./switchto.sh v4.0.0
>>>>> This does not work. Branch v4.0.0 does not exist.
>>>>> What is the git commit for v4.0.0 or for v3.1
>>>>>
>>>>> OpenBTS 4.0.0 from downloaded zip:
>>>>> https://github.com/RangeNetworks/dev/releases/download/v4.0.0/v4.0.0-source.zip 
>>>>>
>>>>>
>>>>>
>>>>> There is no build.sh script
>>>>> build.sh from current git v4.0 branch does not work
>>>>>
>>>>> I have not tried to build by hand or checkout an older build.sh from
>>>>> git
>>>>>
>>>>> What is the git commit for v4.0.0 or for v3.1?
>>>>>
>>>>> Are there stable releases which can be downloaded as zip or tar.gz
>>>>> or checked out with git?
>>>>>
>>>>> Thanks and with best regards,
>>>>>
>>>>> Martin
>>>>>
>>>>> ------------------------------------------------------------------------------ 
>>>>>
>>>>>
>>>>> Want excitement?
>>>>> Manually upgrade your production database.
>>>>> When you want reliability, choose Perforce
>>>>> Perforce version control. Predictably reliable.
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk_______________________________________________ 
>>>>>
>>>>>
>>>>> Openbts-discuss mailing list
>>>>> Openbts-discuss at lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/openbts-discuss
>>>
>>> ------------------------------------------------------------------------------ 
>>>
>>>
>>> Slashdot TV.  Video for Nerds.  Stuff that Matters.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk 
>>>
>>>
>>> _______________________________________________
>>> Openbts-discuss mailing list
>>> Openbts-discuss at lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/openbts-discuss
>>
>>
>>
>>
>>
>> _______________________________________________
>> USRP-users mailing list
>> USRP-users at lists.ettus.com
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>
>
> _______________________________________________
> USRP-users mailing list
> USRP-users at lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>


-- 
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org





More information about the USRP-users mailing list