http://gnuradio.org/redmine/wiki/gnuradio/OpenBTSUHD

http://gnuradio.org/redmine/wiki/gnuradio/OpenBTSE100

./configure --with-usrp1

http://github.com/ttsou/openbts-uhd/commits

git clone git://github.com/ttsou/openbts-uhd.git

git clone -b sms-split clone git://github.com/ttsou/openbts-uhd.git

Hi Alonso, The not is not connecting to the network, I mean, After it detects the test network "00101", The phone is just not able to latch on to the network. It says "Connecting failed". The openbts.config file has the line Control.OpenRegistration. The signal power as i can see from the spectrum analyzer is -50dbm with OPenBTS running and around -80 when it is not at the frequency given by ARFCN number 35(942MHz). Does phone registering to the network got to do with the external clock to be employed(10 MHz) ?? I would also try with a BlackBerry phone if possible. Thank you for your reply, Madhuri On Thu, Jun 2, 2011 at 2:08 PM, <usrp-users-request@lists.ettus.com> wrote: > Send USRP-users mailing list submissions to > usrp-users@lists.ettus.com > > 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 > usrp-users-request@lists.ettus.com > > You can reach the person managing the list at > usrp-users-owner@lists.ettus.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of USRP-users digest..." > > > Today's Topics: > > 1. Re: Question regarding using gnuradio (Phone Naing MYINT) > 2. [ANNOUNCE] OpenBTS on the USRP E100 (Thomas Tsou) > 3. Re: Question regarding using gnuradio (Josh Blum) > 4. Re: Fwd: OpenBTS-UHD with USRP2 (abhinav anand) > 5. Re: Fwd: OpenBTS-UHD with USRP2 (Alonso) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 2 Jun 2011 04:11:03 +0000 > From: Phone Naing MYINT <PhoneNaing.MYINT@sg.panasonic.com> > To: "josh@ettus.com" <josh@ettus.com> > Cc: "usrp-users@lists.ettus.com" <usrp-users@lists.ettus.com> > Subject: Re: [USRP-users] Question regarding using gnuradio > Message-ID: > <2FB6EEB79274234AAF674D741F8660050562C02E@pslexc02.psl.local> > Content-Type: text/plain; charset="us-ascii" > > Alright I will give a try with dpsk2 blk. May I know why don't packet > decoder wirte anything to file, is that expected? > > ANT > > -----Original Message----- > From: Josh Blum [mailto:josh@joshknows.com] On Behalf Of Josh Blum > Sent: Thursday, June 02, 2011 12:06 PM > To: Phone Naing MYINT > Cc: usrp-users@lists.ettus.com > Subject: Re: [USRP-users] Question regarding using gnuradio > > > > On 06/01/2011 08:20 PM, Phone Naing MYINT wrote: > > Here is the screen shot.. > > > > Well it looks like there is a frequency offset, and perhaps the receiver > cannot compensate. You can shift this out manually by a tuning offset to > see what happens. You may want to try the dpsk2 version of the blocks > that Tom has put some good work into. You also might want to ask this on > the gnuradio mailing list. > > -josh > > > -----Original Message----- > > From: usrp-users-bounces@lists.ettus.com [mailto: > usrp-users-bounces@lists.ettus.com] On Behalf Of Josh Blum > > Sent: Thursday, June 02, 2011 10:42 AM > > To: usrp-users@lists.ettus.com > > Subject: Re: [USRP-users] Question regarding using gnuradio > > > > > > > > On 06/01/2011 07:35 PM, Phone Naing MYINT wrote: > >> I connect two USRP2 through RF cable (do I need attenuator here??). > >> > > > > A good recommendation, yes. > > > >> I added in the packet encoder/decoder. At encoder I set 2 bits/symbol > >> for DQPSK. But receiver decoder doesn't write anything to a file. :( > >> I check encoder and decoder without UHD-USRP2, they are working > >> fine. > >> > > > > Did you look at the received spectrum, is it what you expected? Do you > > see a frequency offset, etc...? > > > >> ANT > >> > >> -----Original Message----- From: Mike Clark > >> [mailto:undefinedspace@gmail.com] Sent: Thursday, June 02, 2011 7:46 > >> AM To: Phone Naing MYINT Cc: usrp-users@lists.ettus.com Subject: Re: > >> [USRP-users] Question regarding using gnuradio > >> > >> I would try putting a packet encoder before the modulation and a > >> packet decoder after the demodulation. > >> > >> Also, are you running the tests over the air or are you using a > >> cabled setup with attenuators? If it is over the air, what is the > >> distance between the devices? > >> > >> Mike > >> > >> On Tue, May 31, 2011 at 4:32 AM, Phone Naing MYINT > >> <PhoneNaing.MYINT@sg.panasonic.com> wrote: > >>> Hi lists, > >>> > >>> > >>> > >>> I want to test data transfer between two USRP2 boards. I created > >>> Transmitter and Receiver in GRC (as attached pictures) and using > >>> DQPSK modem scheme. Transmit data is stored in a file and Receive > >>> data is sinked to a file. Transmit data is just repeated binary > >>> pattern (eg. 0xAA). I tried different pattern, most of the patterns > >>> I don't receive at receiver. > >>> > >>> > >>> > >>> Is the GRC design something missing or wrong? Or some parameters > >>> adjustment needs to be done? > >>> > >>> > >>> > >>> ANT > >>> > >>> _______________________________________________ USRP-users mailing > >>> list USRP-users@lists.ettus.com > >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >>> > >>> > >> > >> _______________________________________________ USRP-users mailing > >> list USRP-users@lists.ettus.com > >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > > _______________________________________________ > > USRP-users mailing list > > USRP-users@lists.ettus.com > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > > ------------------------------ > > Message: 2 > Date: Wed, 1 Jun 2011 22:07:51 -0700 > From: Thomas Tsou <ttsou@vt.edu> > To: openbts-discuss@lists.sourceforge.net, usrp-users > <usrp-users@lists.ettus.com> > Subject: [USRP-users] [ANNOUNCE] OpenBTS on the USRP E100 > Message-ID: <BANLkTinOsHhCQqaeDtaGQkiys_pFZcf3BQ@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I recently pushed to the OpenBTS-UHD tree a large collection of > patches that adds 52 MHz transceiver support on the E100 using UHD. > Myself and a few others have been testing this setup over the past two > weeks with encouraging results. Currently, we're able to support two > TCH channels (out of a potential 7) in a stable configuration; > additional channels are limited by embedded processor constraints. > > To support more simultaneous calls, we're looking at ARM NEON > optimizations of various operations along with using the available DSP > in the longer term. Contributions from any developers with experience > in this area are certainly welcome. > > Among other notable changes are runtime gain settings for the non-52 > MHz transceiver, and the previously separate branch for single board > RFX, WBX, and SBX on the USRP1 is merged. Also included are a few bug > fixes and outside patches for long run stability. Additional changes > can be found in the commit log. > > The recommended method for installing OpenBTS on the E100 is to use > downloadable images that include all dependencies. OpenBTS itself can > be built natively on the E100. Thanks to the work of Philip Balister > and the OpenEmbedded community, all required image files are available > for download. Instructions for downloading and installation can be > found in the recently updated wiki pages. > > http://gnuradio.org/redmine/wiki/gnuradio/OpenBTSUHD > > http://gnuradio.org/redmine/wiki/gnuradio/OpenBTSE100 > > For existing users of OpenBTS-UHD, please note that the default > configure options have changed - UHD is now the default setting. USRP1 > users (for single board, WBX, SBX) will need to use the build option, > > ./configure --with-usrp1 > > Commit log: > > http://github.com/ttsou/openbts-uhd/commits > > Git: > > git clone git://github.com/ttsou/openbts-uhd.git > > Alexander Chemeris's sms-split branch is also tracked: > > git clone -b sms-split clone git://github.com/ttsou/openbts-uhd.git > > And that's all I have. Please post any questions or comments to the > openbts-discuss mailing list. Testing, bug reports, patches, and other > contributions are all very much appreciated. Thanks. > > Thomas > > > > ------------------------------ > > Message: 3 > Date: Wed, 01 Jun 2011 22:23:36 -0700 > From: Josh Blum <josh@ettus.com> > To: Phone Naing MYINT <PhoneNaing.MYINT@sg.panasonic.com> > Cc: "usrp-users@lists.ettus.com" <usrp-users@lists.ettus.com> > Subject: Re: [USRP-users] Question regarding using gnuradio > Message-ID: <4DE71E58.7070506@ettus.com> > Content-Type: text/plain; charset=ISO-8859-1 > > > > On 06/01/2011 09:11 PM, Phone Naing MYINT wrote: > > Alright I will give a try with dpsk2 blk. May I know why don't packet > decoder wirte anything to file, is that expected? > > > > Either the file sink didnt flush to disk or no packets were decoded. > > Another thought, you are transmitting full-scale samples into the usrp > sink, so you might be clipping in the DSP. Try transmitting lower > amplitude, like 0.3 for example. > > > ANT > > > > -----Original Message----- > > From: Josh Blum [mailto:josh@joshknows.com] On Behalf Of Josh Blum > > Sent: Thursday, June 02, 2011 12:06 PM > > To: Phone Naing MYINT > > Cc: usrp-users@lists.ettus.com > > Subject: Re: [USRP-users] Question regarding using gnuradio > > > > > > > > On 06/01/2011 08:20 PM, Phone Naing MYINT wrote: > >> Here is the screen shot.. > >> > > > > Well it looks like there is a frequency offset, and perhaps the receiver > > cannot compensate. You can shift this out manually by a tuning offset to > > see what happens. You may want to try the dpsk2 version of the blocks > > that Tom has put some good work into. You also might want to ask this on > > the gnuradio mailing list. > > > > -josh > > > >> -----Original Message----- > >> From: usrp-users-bounces@lists.ettus.com [mailto: > usrp-users-bounces@lists.ettus.com] On Behalf Of Josh Blum > >> Sent: Thursday, June 02, 2011 10:42 AM > >> To: usrp-users@lists.ettus.com > >> Subject: Re: [USRP-users] Question regarding using gnuradio > >> > >> > >> > >> On 06/01/2011 07:35 PM, Phone Naing MYINT wrote: > >>> I connect two USRP2 through RF cable (do I need attenuator here??). > >>> > >> > >> A good recommendation, yes. > >> > >>> I added in the packet encoder/decoder. At encoder I set 2 bits/symbol > >>> for DQPSK. But receiver decoder doesn't write anything to a file. :( > >>> I check encoder and decoder without UHD-USRP2, they are working > >>> fine. > >>> > >> > >> Did you look at the received spectrum, is it what you expected? Do you > >> see a frequency offset, etc...? > >> > >>> ANT > >>> > >>> -----Original Message----- From: Mike Clark > >>> [mailto:undefinedspace@gmail.com] Sent: Thursday, June 02, 2011 7:46 > >>> AM To: Phone Naing MYINT Cc: usrp-users@lists.ettus.com Subject: Re: > >>> [USRP-users] Question regarding using gnuradio > >>> > >>> I would try putting a packet encoder before the modulation and a > >>> packet decoder after the demodulation. > >>> > >>> Also, are you running the tests over the air or are you using a > >>> cabled setup with attenuators? If it is over the air, what is the > >>> distance between the devices? > >>> > >>> Mike > >>> > >>> On Tue, May 31, 2011 at 4:32 AM, Phone Naing MYINT > >>> <PhoneNaing.MYINT@sg.panasonic.com> wrote: > >>>> Hi lists, > >>>> > >>>> > >>>> > >>>> I want to test data transfer between two USRP2 boards. I created > >>>> Transmitter and Receiver in GRC (as attached pictures) and using > >>>> DQPSK modem scheme. Transmit data is stored in a file and Receive > >>>> data is sinked to a file. Transmit data is just repeated binary > >>>> pattern (eg. 0xAA). I tried different pattern, most of the patterns > >>>> I don't receive at receiver. > >>>> > >>>> > >>>> > >>>> Is the GRC design something missing or wrong? Or some parameters > >>>> adjustment needs to be done? > >>>> > >>>> > >>>> > >>>> ANT > >>>> > >>>> _______________________________________________ USRP-users mailing > >>>> list USRP-users@lists.ettus.com > >>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >>>> > >>>> > >>> > >>> _______________________________________________ USRP-users mailing > >>> list USRP-users@lists.ettus.com > >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >> > >> _______________________________________________ > >> USRP-users mailing list > >> USRP-users@lists.ettus.com > >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > > ------------------------------ > > Message: 4 > Date: Thu, 2 Jun 2011 01:21:20 -0700 > From: abhinav anand <a.abhinav100@gmail.com> > To: madhuri gontala <mads3009@gmail.com>, usrp-users@lists.ettus.com > Subject: Re: [USRP-users] Fwd: OpenBTS-UHD with USRP2 > Message-ID: <BANLkTimkLnsKyRg6C+AMsFRbGQxdVTW6pA@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > If phones are able to see the BTS signal then the problem may be with the > Asterisk server. > Did you install Asterisk ? If yes then in the same machine or in the > different machine ? > You need to provide the IP address of Asterisk in OpenBTS.config file for > 'Asterisk.IP' field. > (127.0.0.1 if installed locally otherwise remote IP address) > > -- > Abhinav > > On Wed, Jun 1, 2011 at 10:07 AM, madhuri gontala <mads3009@gmail.com> > wrote: > > > > > > > ---------- Forwarded message ---------- > > From: madhuri gontala <mads3009@gmail.com> > > Date: Wed, Jun 1, 2011 at 10:36 PM > > Subject: Re: [USRP-users] OpenBTS-UHD with USRP2 > > To: Thomas Tsou <ttsou@vt.edu> > > > > > > Hi Thomas, > > I'm using the frequency 955MHz corresponding to the ARFCN number 100 > that > > i gave in the openBTS.config file. The GSM band is 900. My nokia phones > are > > not able to detect the signal. > > Today I had a progress in the project. I gave the MCC=001 and MNC=01 > in > > the openbts.config file (i.e. in the test mode) and one samsung mobile is > > able to detect the signal from USRP2 but not able to register to it. Do > you > > know the reason why its not registering?? > > > > Thank you, > > Madhuri. > > > > On Wed, Jun 1, 2011 at 6:17 AM, Thomas Tsou <ttsou@vt.edu> wrote: > > > >> On Tue, May 31, 2011 at 9:03 AM, madhuri gontala <mads3009@gmail.com> > >> wrote: > >> > > >> > 1306776537.770203 139910568118048: > >> > Starting the system... > >> > 1306776537.7821 ALARM 139910568118048 OpenBTS.cpp:129:main: OpenBTS > >> > starting, ver 2.6PUBLIC build date May 26 2011 > >> > linux; GNU C++ version 4.4.5; Boost_104200; UHD_003.001.000-unknown > >> > > >> > 1306776538.0996 FORCE 140146832955168 Logger.cpp:198:gLogInit: Setting > >> > initial global logging level to NOTICE > >> > -- Opening a USRP2/N-Series device... > >> > -- Current recv frame size: 1472 bytes > >> > -- Current send frame size: 1472 bytes > >> > > >> > UHD Warning: > >> > The recv buffer could not be resized sufficiently. > >> > Target sock buff size: 50000000 bytes. > >> > Actual sock buff size: 131071 bytes. > >> > See the transport application notes on buffer resizing. > >> > Please run: sudo sysctl -w net.core.rmem_max=50000000 > >> > > >> > UHD Warning: > >> > The recv buffer could not be resized sufficiently. > >> > Target sock buff size: 50000000 bytes. > >> > Actual sock buff size: 131071 bytes. > >> > See the transport application notes on buffer resizing. > >> > Please run: sudo sysctl -w net.core.rmem_max=50000000 > >> > -- mboard0 is MIMO master > >> > 1306776542.8219 ALARM 139910568118048 TRXManager.cpp:447:setMaxDelay: > >> > SETMAXDLY failed with status -1 > >> > 1306776542.8220 ALARM 139910568118048 TRXManager.cpp:458:setRxGain: > >> > SETRXGAIN failed with status -1 > >> > 1306776543.209978 139910568118048: > >> > >> These are normal messages. The SETRXGAIN warning will go away if you > >> update your copy of OpenBTS. What frequency are you operating on, and > >> is it supported by your phone? Have you read this page? > >> > >> http://gnuradio.org/redmine/wiki/gnuradio/OpenBTSMS_Camping > >> > >> > I dont understnd the port configeration in the OPenBTS.config file. my > >> USRP2 > >> > has an IP address of 192.168.10.2. So pleaseeee accordingly tell me > >> where > >> > all i need to change the IP addresses in the config file (if any). As > i > >> have > >> > told USRP2 is properly connected and seen in the spectrometer. > >> > >> You should not have to change any ports in your config file. The USRP2 > >> connected on 192.168.10.2 is independent of the address and port > >> settings in OpenBTS. > >> > >> Thomas > >> > > > > > > > > _______________________________________________ > > USRP-users mailing list > > USRP-users@lists.ettus.com > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > > >