From: David L. <Dav...@ma...> - 2014-07-30 23:52:08
|
Hello I've built OpenBTS on an Ubuntu 12.04 machine (old Lenovo T60 laptop) and I can't get the service to start properly. I always see some transceiver.cpp errors - I've linked Transceiver52m/transceiver to my ./apps/ directory. This is start-up detail: OpenBTS Copyright 2008, 2009, 2010 Free Software Foundation, Inc. Copyright 2010 Kestrel Signal Processing, Inc. Copyright 2011, 2012, 2013, 2014 Range Networks, Inc. Release 5.0.0-prealpha+a5473eedf1 CommonLibs:3ad343b97b P formal build date 2014-07-30T08:49:27 "OpenBTS" is a registered trademark of Range Networks, Inc. Contributors: Range Networks, Inc.: David Burgess, Harvind Samra, Donald Kirker, Doug Brown, Pat Thompson, Kurtis Heimerl, Michael Iedema, Dave Gotwisner Kestrel Signal Processing, Inc.: David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga GNU Radio: Johnathan Corgan Others: Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy Alexander Chemeris, Alberto Escudero-Pascual Incorporated L/GPL libraries and components: libortp, LGPL, 2.1 Copyright 2001 Simon MORLAT sim...@li... libusb, LGPL 2.1, various copyright holders, www.libusb.org libzmq, LGPL 3: Copyright (c) 2009-2011 250bpm s.r.o. Copyright (c) 2011 Botond Ballo Copyright (c) 2007-2009 iMatix Corporation Incorporated BSD/MIT-style libraries and components: A5/1 Pedagogical Implementation, Simplified BSD License, Copyright 1998-1999 Marc Briceno, Ian Goldberg, and David Wagner JsonBox, Copyright 2011 Anhero Inc. Google Core Dumper, BSD 3-Clause License, Copyright (c) 2005-2007, Google Inc. Incorporated public domain libraries and components: sqlite3, released to public domain 15 Sept 2001, www.sqlite.org This program comes with ABSOLUTELY NO WARRANTY. Use of this software may be subject to other legal restrictions, including patent licensing and radio spectrum licensing. All users of this software are expected to comply with applicable regulations and laws. See the LEGAL file in the source code for more information. Note to US Government Users: The OpenBTS software applications and associated documentation are "Commercial Item(s)," as that term is defined at 48 C.F.R. Section 2.101, consisting of "Commercial Computer Software" and "Commercial Computer Software Documentation," as such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202, as applicable. Consistent with 48 C.F.R. 12.212 or 48 C.F.R. Sections 227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions of Range Networks' software licenses and master customer agreement. 1406763106.876470 3072763648: Starting the system... ALERT 3278:3285 2014-07-30T16:31:51.9 OpenBTS.cpp:174:startTransceiver: starting transceiver ./transceiver with 1 ARFCNs linux; GNU C++ version 4.6.3; Boost_105400; UHD_003.007.002-49-g9eb403f4 Using internal clock reference -- Loading firmware image: /usr/local/share/uhd/images/usrp_b200_fw.hex... done -- Loading FPGA image: /usr/local/share/uhd/images/usrp_b210_fpga.bin... 10%ALERT 3278:3278 2014-07-30T16:32:06.9 TRXManager.cpp:402:tune: RXTUNE(128) failed with status -1 18%EMERG 3278:3317 2014-07-30T16:32:11.9 TRXManager.cpp:107:clockHandler: TRX clock interface timed out, assuming TRX is dead. root@dlake-ThinkPad-T60:~/openbts/ap done -- Operating over USB 2. -- Detecting internal GPSDO.... No GPSDO found -- not found -- Initialize CODEC control... -- Initialize Radio control... -- Performing register loopback test... pass -- Performing register loopback test... pass -- Performing CODEC loopback test... pass -- Performing CODEC loopback test... pass -- Asking for clock rate 32.000000 MHz -- Actually got clock rate 32.000000 MHz -- Performing timer loopback test... pass -- Performing timer loopback test... pass -- Asking for clock rate 26.000000 MHz -- Actually got clock rate 26.000000 MHz -- Performing timer loopback test... pass -- Performing timer loopback test... pass Thanks in advance David |
From: Tom T. <to...@ts...> - 2014-07-31 00:18:09
|
On Wed, Jul 30, 2014 at 7:37 PM, David Lake <Dav...@ma...> wrote: > linux; GNU C++ version 4.6.3; Boost_105400; UHD_003.007.002-49-g9eb403f4 > > Using internal clock reference > -- Loading firmware image: /usr/local/share/uhd/images/usrp_b200_fw.hex... > done > -- Loading FPGA image: /usr/local/share/uhd/images/usrp_b210_fpga.bin... > 10% Try running uhd_usrp_probe before OpenBTS. It seems there may be a USB hiccup during the FPGA load. -TT |
From: David L. <Dav...@ma...> - 2014-07-31 04:48:05
|
Hmm... So, if I run usrp_uhd_probe before starting OpenBTS, things look better, but I still can't find the network when I scan from any of my 8 phones (default database settings). This is what I see on start-up now: root@dlake-ThinkPad-T60:~/openbts/apps# ./OpenBTS ALERT 2997:2997 2014-07-30T21:44:27.0 OpenBTS.cpp:600:main: OpenBTS (re)starting, ver 5.0.0-prealpha build date/time 2014-07-30T08:53:59 ALERT 2997:2997 2014-07-30T21:44:27.0 OpenBTS.cpp:601:main: OpenBTS reading config file /etc/OpenBTS/OpenBTS.db 1406781867.049901 3072497408: OpenBTS Copyright 2008, 2009, 2010 Free Software Foundation, Inc. Copyright 2010 Kestrel Signal Processing, Inc. Copyright 2011, 2012, 2013, 2014 Range Networks, Inc. Release 5.0.0-prealpha+a5473eedf1 CommonLibs:3ad343b97b P formal build date 2014-07-30T08:49:27 "OpenBTS" is a registered trademark of Range Networks, Inc. Contributors: Range Networks, Inc.: David Burgess, Harvind Samra, Donald Kirker, Doug Brown, Pat Thompson, Kurtis Heimerl, Michael Iedema, Dave Gotwisner Kestrel Signal Processing, Inc.: David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga GNU Radio: Johnathan Corgan Others: Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy Alexander Chemeris, Alberto Escudero-Pascual Incorporated L/GPL libraries and components: libortp, LGPL, 2.1 Copyright 2001 Simon MORLAT sim...@li... libusb, LGPL 2.1, various copyright holders, www.libusb.org libzmq, LGPL 3: Copyright (c) 2009-2011 250bpm s.r.o. Copyright (c) 2011 Botond Ballo Copyright (c) 2007-2009 iMatix Corporation Incorporated BSD/MIT-style libraries and components: A5/1 Pedagogical Implementation, Simplified BSD License, Copyright 1998-1999 Marc Briceno, Ian Goldberg, and David Wagner JsonBox, Copyright 2011 Anhero Inc. Google Core Dumper, BSD 3-Clause License, Copyright (c) 2005-2007, Google Inc. Incorporated public domain libraries and components: sqlite3, released to public domain 15 Sept 2001, www.sqlite.org This program comes with ABSOLUTELY NO WARRANTY. Use of this software may be subject to other legal restrictions, including patent licensing and radio spectrum licensing. All users of this software are expected to comply with applicable regulations and laws. See the LEGAL file in the source code for more information. Note to US Government Users: The OpenBTS software applications and associated documentation are "Commercial Item(s)," as that term is defined at 48 C.F.R. Section 2.101, consisting of "Commercial Computer Software" and "Commercial Computer Software Documentation," as such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202, as applicable. Consistent with 48 C.F.R. 12.212 or 48 C.F.R. Sections 227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions of Range Networks' software licenses and master customer agreement. 1406781867.149869 3072497408: Starting the system... ALERT 2997:3004 2014-07-30T21:44:32.2 OpenBTS.cpp:174:startTransceiver: starting transceiver ./transceiver with 1 ARFCNs linux; GNU C++ version 4.6.3; Boost_105400; UHD_003.007.002-49-g9eb403f4 Using internal clock reference -- Operating over USB 2. -- Initialize CODEC control... -- Initialize Radio control... -- Performing register loopback test... pass -- Performing register loopback test... pass -- Performing CODEC loopback test... pass -- Performing CODEC loopback test... pass -- Asking for clock rate 32.000000 MHz -- Actually got clock rate 32.000000 MHz -- Performing timer loopback test... pass -- Performing timer loopback test... pass -- Asking for clock rate 26.000000 MHz -- Actually got clock rate 26.000000 MHz -- Performing timer loopback test... pass -- Performing timer loopback test... pass ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 GSML1FEC.cpp:575:handoverPending: SCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 GSML1FEC.cpp:575:handoverPending: FCCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 GSML1FEC.cpp:575:handoverPending: BCCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0 handover clear failed ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.0 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1 handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2 handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3 handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(1) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(1) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(2) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(2) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(3) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(3) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(4) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(4) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(5) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(5) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(6) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(6) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F-SACCH handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.2 TRXManager.cpp:565:clearHandover: NOHANDOVER(7) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F handover clear failed ALERT 2997:2997 2014-07-30T21:44:40.2 TRXManager.cpp:565:clearHandover: NOHANDOVER(7) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F-SACCH handover clear failed 1406781880.212909 3072497408: system ready 1406781880.213018 3072497408: use the OpenBTSCLI utility to access CLI 1406781880.213334 3072497408: OpenBTSCLI network socket support for tcp:49300 OpenBTS> David ________________________________________ From: Tom Tsou <to...@ts...> Sent: 30 July 2014 17:18 To: David Lake Cc: ope...@li... Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 On Wed, Jul 30, 2014 at 7:37 PM, David Lake <Dav...@ma...> wrote: > linux; GNU C++ version 4.6.3; Boost_105400; UHD_003.007.002-49-g9eb403f4 > > Using internal clock reference > -- Loading firmware image: /usr/local/share/uhd/images/usrp_b200_fw.hex... > done > -- Loading FPGA image: /usr/local/share/uhd/images/usrp_b210_fpga.bin... > 10% Try running uhd_usrp_probe before OpenBTS. It seems there may be a USB hiccup during the FPGA load. -TT |
From: Ralph A. S. d. <ra...@sc...> - 2014-07-31 07:47:20
|
Do you have something to verify if the thing emits RF of whatever kind? Like a 19.99$-RTL2832-SDR on a second PC, or even measuring equipment like a spectrum analyzer? What happens if you enter for example the "noise" command on the openbts cli? Ralph. > -----Original Message----- > From: David Lake [mailto:Dav...@ma...] > Sent: Thursday, July 31, 2014 6:48 AM > To: Tom Tsou > Cc: ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > Hmm... So, if I run usrp_uhd_probe before starting OpenBTS, things look > better, but I still can't find the network when I scan from any of my 8 phones > (default database settings). > > This is what I see on start-up now: > > root@dlake-ThinkPad-T60:~/openbts/apps# ./OpenBTS ALERT 2997:2997 > 2014-07-30T21:44:27.0 OpenBTS.cpp:600:main: OpenBTS (re)starting, ver > 5.0.0-prealpha build date/time 2014-07-30T08:53:59 ALERT 2997:2997 2014-07- > 30T21:44:27.0 OpenBTS.cpp:601:main: OpenBTS reading config file > /etc/OpenBTS/OpenBTS.db > 1406781867.049901 3072497408: > > OpenBTS > Copyright 2008, 2009, 2010 Free Software Foundation, Inc. > Copyright 2010 Kestrel Signal Processing, Inc. > Copyright 2011, 2012, 2013, 2014 Range Networks, Inc. > Release 5.0.0-prealpha+a5473eedf1 CommonLibs:3ad343b97b P formal build > date 2014-07-30T08:49:27 "OpenBTS" is a registered trademark of Range > Networks, Inc. > > Contributors: > Range Networks, Inc.: > David Burgess, Harvind Samra, Donald Kirker, Doug Brown, > Pat Thompson, Kurtis Heimerl, Michael Iedema, Dave Gotwisner > Kestrel Signal Processing, Inc.: > David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga > GNU Radio: > Johnathan Corgan > Others: > Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy > Alexander Chemeris, Alberto Escudero-Pascual Incorporated L/GPL > libraries and components: > libortp, LGPL, 2.1 Copyright 2001 Simon MORLAT > sim...@li... > libusb, LGPL 2.1, various copyright holders, www.libusb.org > libzmq, LGPL 3: > Copyright (c) 2009-2011 250bpm s.r.o. > Copyright (c) 2011 Botond Ballo > Copyright (c) 2007-2009 iMatix Corporation Incorporated BSD/MIT-style > libraries and components: > A5/1 Pedagogical Implementation, Simplified BSD License, Copyright 1998- > 1999 Marc Briceno, Ian Goldberg, and David Wagner > JsonBox, Copyright 2011 Anhero Inc. > Google Core Dumper, BSD 3-Clause License, Copyright (c) 2005-2007, Google > Inc. > Incorporated public domain libraries and components: > sqlite3, released to public domain 15 Sept 2001, www.sqlite.org > > > This program comes with ABSOLUTELY NO WARRANTY. > > Use of this software may be subject to other legal restrictions, including > patent licensing and radio spectrum licensing. > All users of this software are expected to comply with applicable regulations > and laws. See the LEGAL file in the source code for more information. > > Note to US Government Users: > The OpenBTS software applications and associated documentation are > "Commercial Item(s)," as that term is defined at 48 C.F.R. Section 2.101, > consisting of "Commercial Computer Software" and "Commercial Computer > Software Documentation," > as such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202, as > applicable. Consistent with 48 C.F.R. 12.212 or 48 C.F.R. Sections 227.7202-1 > through 227.7202-4, as applicable, the Commercial Computer Software and > Commercial Computer Software Documentation are being licensed to U.S. > Government end users (a) only as Commercial Items and (b) with only those > rights as are granted to all other end users pursuant to the terms and > conditions of Range Networks' software licenses and master customer > agreement. > > > 1406781867.149869 3072497408: > Starting the system... > ALERT 2997:3004 2014-07-30T21:44:32.2 OpenBTS.cpp:174:startTransceiver: > starting transceiver ./transceiver with 1 ARFCNs linux; GNU C++ version 4.6.3; > Boost_105400; UHD_003.007.002-49-g9eb403f4 > > Using internal clock reference > -- Operating over USB 2. > -- Initialize CODEC control... > -- Initialize Radio control... > -- Performing register loopback test... pass > -- Performing register loopback test... pass > -- Performing CODEC loopback test... pass > -- Performing CODEC loopback test... pass > -- Asking for clock rate 32.000000 MHz > -- Actually got clock rate 32.000000 MHz > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass > -- Asking for clock rate 26.000000 MHz > -- Actually got clock rate 26.000000 MHz > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass ALERT 2997:2997 2014-07- > 30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed > with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: SCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: FCCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: BCCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.0 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(1) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(1) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(2) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(2) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(3) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(3) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(4) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(4) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(5) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(5) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(6) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(6) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.2 > TRXManager.cpp:565:clearHandover: NOHANDOVER(7) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.2 TRXManager.cpp:565:clearHandover: > NOHANDOVER(7) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F-SACCH handover clear > failed > 1406781880.212909 3072497408: > system ready > > 1406781880.213018 3072497408: > use the OpenBTSCLI utility to access CLI > > 1406781880.213334 3072497408: OpenBTSCLI network socket support for > tcp:49300 > > OpenBTS> > > > David > ________________________________________ > From: Tom Tsou <to...@ts...> > Sent: 30 July 2014 17:18 > To: David Lake > Cc: ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > On Wed, Jul 30, 2014 at 7:37 PM, David Lake <Dav...@ma...> > wrote: > > linux; GNU C++ version 4.6.3; Boost_105400; > > UHD_003.007.002-49-g9eb403f4 > > > > Using internal clock reference > > -- Loading firmware image: > /usr/local/share/uhd/images/usrp_b200_fw.hex... > > done > > -- Loading FPGA image: > /usr/local/share/uhd/images/usrp_b210_fpga.bin... > > 10% > > Try running uhd_usrp_probe before OpenBTS. It seems there may be a USB > hiccup during the FPGA load. > > -TT > > ---------------------------------------------------------------------------- -- > Infragistics Professional > Build stunning WinForms apps today! > Reboot your WinForms applications with our WinForms controls. > Build a bridge from your legacy apps to the future. > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.cl > ktrk > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss |
From: David L. <Dav...@ma...> - 2014-08-01 07:40:02
|
I should add that I know the B210 works as it has been running as a DAB system for some days... ________________________________________ From: Ralph A. Schmid, dk5ras <ra...@sc...> Sent: 31 July 2014 00:47 To: David Lake; 'Tom Tsou' Cc: ope...@li... Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 Do you have something to verify if the thing emits RF of whatever kind? Like a 19.99$-RTL2832-SDR on a second PC, or even measuring equipment like a spectrum analyzer? What happens if you enter for example the "noise" command on the openbts cli? Ralph. > -----Original Message----- > From: David Lake [mailto:Dav...@ma...] > Sent: Thursday, July 31, 2014 6:48 AM > To: Tom Tsou > Cc: ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > Hmm... So, if I run usrp_uhd_probe before starting OpenBTS, things look > better, but I still can't find the network when I scan from any of my 8 phones > (default database settings). > > This is what I see on start-up now: > > root@dlake-ThinkPad-T60:~/openbts/apps# ./OpenBTS ALERT 2997:2997 > 2014-07-30T21:44:27.0 OpenBTS.cpp:600:main: OpenBTS (re)starting, ver > 5.0.0-prealpha build date/time 2014-07-30T08:53:59 ALERT 2997:2997 2014-07- > 30T21:44:27.0 OpenBTS.cpp:601:main: OpenBTS reading config file > /etc/OpenBTS/OpenBTS.db > 1406781867.049901 3072497408: > > OpenBTS > Copyright 2008, 2009, 2010 Free Software Foundation, Inc. > Copyright 2010 Kestrel Signal Processing, Inc. > Copyright 2011, 2012, 2013, 2014 Range Networks, Inc. > Release 5.0.0-prealpha+a5473eedf1 CommonLibs:3ad343b97b P formal build > date 2014-07-30T08:49:27 "OpenBTS" is a registered trademark of Range > Networks, Inc. > > Contributors: > Range Networks, Inc.: > David Burgess, Harvind Samra, Donald Kirker, Doug Brown, > Pat Thompson, Kurtis Heimerl, Michael Iedema, Dave Gotwisner > Kestrel Signal Processing, Inc.: > David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga > GNU Radio: > Johnathan Corgan > Others: > Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy > Alexander Chemeris, Alberto Escudero-Pascual Incorporated L/GPL > libraries and components: > libortp, LGPL, 2.1 Copyright 2001 Simon MORLAT > sim...@li... > libusb, LGPL 2.1, various copyright holders, www.libusb.org > libzmq, LGPL 3: > Copyright (c) 2009-2011 250bpm s.r.o. > Copyright (c) 2011 Botond Ballo > Copyright (c) 2007-2009 iMatix Corporation Incorporated BSD/MIT-style > libraries and components: > A5/1 Pedagogical Implementation, Simplified BSD License, Copyright 1998- > 1999 Marc Briceno, Ian Goldberg, and David Wagner > JsonBox, Copyright 2011 Anhero Inc. > Google Core Dumper, BSD 3-Clause License, Copyright (c) 2005-2007, Google > Inc. > Incorporated public domain libraries and components: > sqlite3, released to public domain 15 Sept 2001, www.sqlite.org > > > This program comes with ABSOLUTELY NO WARRANTY. > > Use of this software may be subject to other legal restrictions, including > patent licensing and radio spectrum licensing. > All users of this software are expected to comply with applicable regulations > and laws. See the LEGAL file in the source code for more information. > > Note to US Government Users: > The OpenBTS software applications and associated documentation are > "Commercial Item(s)," as that term is defined at 48 C.F.R. Section 2.101, > consisting of "Commercial Computer Software" and "Commercial Computer > Software Documentation," > as such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202, as > applicable. Consistent with 48 C.F.R. 12.212 or 48 C.F.R. Sections 227.7202-1 > through 227.7202-4, as applicable, the Commercial Computer Software and > Commercial Computer Software Documentation are being licensed to U.S. > Government end users (a) only as Commercial Items and (b) with only those > rights as are granted to all other end users pursuant to the terms and > conditions of Range Networks' software licenses and master customer > agreement. > > > 1406781867.149869 3072497408: > Starting the system... > ALERT 2997:3004 2014-07-30T21:44:32.2 OpenBTS.cpp:174:startTransceiver: > starting transceiver ./transceiver with 1 ARFCNs linux; GNU C++ version 4.6.3; > Boost_105400; UHD_003.007.002-49-g9eb403f4 > > Using internal clock reference > -- Operating over USB 2. > -- Initialize CODEC control... > -- Initialize Radio control... > -- Performing register loopback test... pass > -- Performing register loopback test... pass > -- Performing CODEC loopback test... pass > -- Performing CODEC loopback test... pass > -- Asking for clock rate 32.000000 MHz > -- Actually got clock rate 32.000000 MHz > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass > -- Asking for clock rate 26.000000 MHz > -- Actually got clock rate 26.000000 MHz > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass ALERT 2997:2997 2014-07- > 30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed > with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: SCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: FCCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: BCCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.0 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(1) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(1) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(2) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(2) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(3) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(3) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(4) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(4) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(5) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(5) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(6) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(6) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.2 > TRXManager.cpp:565:clearHandover: NOHANDOVER(7) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.2 TRXManager.cpp:565:clearHandover: > NOHANDOVER(7) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F-SACCH handover clear > failed > 1406781880.212909 3072497408: > system ready > > 1406781880.213018 3072497408: > use the OpenBTSCLI utility to access CLI > > 1406781880.213334 3072497408: OpenBTSCLI network socket support for > tcp:49300 > > OpenBTS> > > > David > ________________________________________ > From: Tom Tsou <to...@ts...> > Sent: 30 July 2014 17:18 > To: David Lake > Cc: ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > On Wed, Jul 30, 2014 at 7:37 PM, David Lake <Dav...@ma...> > wrote: > > linux; GNU C++ version 4.6.3; Boost_105400; > > UHD_003.007.002-49-g9eb403f4 > > > > Using internal clock reference > > -- Loading firmware image: > /usr/local/share/uhd/images/usrp_b200_fw.hex... > > done > > -- Loading FPGA image: > /usr/local/share/uhd/images/usrp_b210_fpga.bin... > > 10% > > Try running uhd_usrp_probe before OpenBTS. It seems there may be a USB > hiccup during the FPGA load. > > -TT > > ---------------------------------------------------------------------------- -- > Infragistics Professional > Build stunning WinForms apps today! > Reboot your WinForms applications with our WinForms controls. > Build a bridge from your legacy apps to the future. > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.cl > ktrk > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss |
From: David L. <Dav...@ma...> - 2014-08-01 07:41:37
|
OK - now I am seeing something I don't like in OpenBTS.log: transceiver: NOTICE 3275:3360 2014-08-01T00:39:30.2 Transceiver.cpp:191:pushRadioVector: dumping STALE burst in TRX->USRP interface ________________________________________ From: David Lake Sent: 01 August 2014 00:39 To: Ralph A. Schmid, dk5ras; 'Tom Tsou' Cc: ope...@li... Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 I should add that I know the B210 works as it has been running as a DAB system for some days... ________________________________________ From: Ralph A. Schmid, dk5ras <ra...@sc...> Sent: 31 July 2014 00:47 To: David Lake; 'Tom Tsou' Cc: ope...@li... Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 Do you have something to verify if the thing emits RF of whatever kind? Like a 19.99$-RTL2832-SDR on a second PC, or even measuring equipment like a spectrum analyzer? What happens if you enter for example the "noise" command on the openbts cli? Ralph. > -----Original Message----- > From: David Lake [mailto:Dav...@ma...] > Sent: Thursday, July 31, 2014 6:48 AM > To: Tom Tsou > Cc: ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > Hmm... So, if I run usrp_uhd_probe before starting OpenBTS, things look > better, but I still can't find the network when I scan from any of my 8 phones > (default database settings). > > This is what I see on start-up now: > > root@dlake-ThinkPad-T60:~/openbts/apps# ./OpenBTS ALERT 2997:2997 > 2014-07-30T21:44:27.0 OpenBTS.cpp:600:main: OpenBTS (re)starting, ver > 5.0.0-prealpha build date/time 2014-07-30T08:53:59 ALERT 2997:2997 2014-07- > 30T21:44:27.0 OpenBTS.cpp:601:main: OpenBTS reading config file > /etc/OpenBTS/OpenBTS.db > 1406781867.049901 3072497408: > > OpenBTS > Copyright 2008, 2009, 2010 Free Software Foundation, Inc. > Copyright 2010 Kestrel Signal Processing, Inc. > Copyright 2011, 2012, 2013, 2014 Range Networks, Inc. > Release 5.0.0-prealpha+a5473eedf1 CommonLibs:3ad343b97b P formal build > date 2014-07-30T08:49:27 "OpenBTS" is a registered trademark of Range > Networks, Inc. > > Contributors: > Range Networks, Inc.: > David Burgess, Harvind Samra, Donald Kirker, Doug Brown, > Pat Thompson, Kurtis Heimerl, Michael Iedema, Dave Gotwisner > Kestrel Signal Processing, Inc.: > David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga > GNU Radio: > Johnathan Corgan > Others: > Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy > Alexander Chemeris, Alberto Escudero-Pascual Incorporated L/GPL > libraries and components: > libortp, LGPL, 2.1 Copyright 2001 Simon MORLAT > sim...@li... > libusb, LGPL 2.1, various copyright holders, www.libusb.org > libzmq, LGPL 3: > Copyright (c) 2009-2011 250bpm s.r.o. > Copyright (c) 2011 Botond Ballo > Copyright (c) 2007-2009 iMatix Corporation Incorporated BSD/MIT-style > libraries and components: > A5/1 Pedagogical Implementation, Simplified BSD License, Copyright 1998- > 1999 Marc Briceno, Ian Goldberg, and David Wagner > JsonBox, Copyright 2011 Anhero Inc. > Google Core Dumper, BSD 3-Clause License, Copyright (c) 2005-2007, Google > Inc. > Incorporated public domain libraries and components: > sqlite3, released to public domain 15 Sept 2001, www.sqlite.org > > > This program comes with ABSOLUTELY NO WARRANTY. > > Use of this software may be subject to other legal restrictions, including > patent licensing and radio spectrum licensing. > All users of this software are expected to comply with applicable regulations > and laws. See the LEGAL file in the source code for more information. > > Note to US Government Users: > The OpenBTS software applications and associated documentation are > "Commercial Item(s)," as that term is defined at 48 C.F.R. Section 2.101, > consisting of "Commercial Computer Software" and "Commercial Computer > Software Documentation," > as such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202, as > applicable. Consistent with 48 C.F.R. 12.212 or 48 C.F.R. Sections 227.7202-1 > through 227.7202-4, as applicable, the Commercial Computer Software and > Commercial Computer Software Documentation are being licensed to U.S. > Government end users (a) only as Commercial Items and (b) with only those > rights as are granted to all other end users pursuant to the terms and > conditions of Range Networks' software licenses and master customer > agreement. > > > 1406781867.149869 3072497408: > Starting the system... > ALERT 2997:3004 2014-07-30T21:44:32.2 OpenBTS.cpp:174:startTransceiver: > starting transceiver ./transceiver with 1 ARFCNs linux; GNU C++ version 4.6.3; > Boost_105400; UHD_003.007.002-49-g9eb403f4 > > Using internal clock reference > -- Operating over USB 2. > -- Initialize CODEC control... > -- Initialize Radio control... > -- Performing register loopback test... pass > -- Performing register loopback test... pass > -- Performing CODEC loopback test... pass > -- Performing CODEC loopback test... pass > -- Asking for clock rate 32.000000 MHz > -- Actually got clock rate 32.000000 MHz > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass > -- Asking for clock rate 26.000000 MHz > -- Actually got clock rate 26.000000 MHz > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass ALERT 2997:2997 2014-07- > 30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed > with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: SCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: FCCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: BCCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.0 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(1) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(1) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(2) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(2) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(3) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(3) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(4) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(4) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(5) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(5) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(6) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(6) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.2 > TRXManager.cpp:565:clearHandover: NOHANDOVER(7) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.2 TRXManager.cpp:565:clearHandover: > NOHANDOVER(7) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F-SACCH handover clear > failed > 1406781880.212909 3072497408: > system ready > > 1406781880.213018 3072497408: > use the OpenBTSCLI utility to access CLI > > 1406781880.213334 3072497408: OpenBTSCLI network socket support for > tcp:49300 > > OpenBTS> > > > David > ________________________________________ > From: Tom Tsou <to...@ts...> > Sent: 30 July 2014 17:18 > To: David Lake > Cc: ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > On Wed, Jul 30, 2014 at 7:37 PM, David Lake <Dav...@ma...> > wrote: > > linux; GNU C++ version 4.6.3; Boost_105400; > > UHD_003.007.002-49-g9eb403f4 > > > > Using internal clock reference > > -- Loading firmware image: > /usr/local/share/uhd/images/usrp_b200_fw.hex... > > done > > -- Loading FPGA image: > /usr/local/share/uhd/images/usrp_b210_fpga.bin... > > 10% > > Try running uhd_usrp_probe before OpenBTS. It seems there may be a USB > hiccup during the FPGA load. > > -TT > > ---------------------------------------------------------------------------- -- > Infragistics Professional > Build stunning WinForms apps today! > Reboot your WinForms applications with our WinForms controls. > Build a bridge from your legacy apps to the future. > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.cl > ktrk > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss |
From: David L. <Dav...@ma...> - 2014-08-01 15:37:18
|
Hmm - in that case, this may be my problem. The PC I am using is an old T60 with an Intel Centrino Duo CPU and 2G of RAM. Time to find a new box in the cupboard.... ________________________________________ From: Tom Tsou <to...@ts...> Sent: 01 August 2014 06:51 To: David Lake Cc: Ralph A. Schmid, dk5ras; ope...@li... Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 On Fri, Aug 1, 2014 at 3:41 AM, David Lake <Dav...@ma...> wrote: > OK - now I am seeing something I don't like in OpenBTS.log: > > transceiver: NOTICE 3275:3360 2014-08-01T00:39:30.2 Transceiver.cpp:191:pushRadioVector: dumping STALE burst in TRX->USRP interface This means a burst from the upper stack arrived late at the transceiver and missed the transmit timing window. The underlying cause is either CPU or OS scheduling related - GSM has real time requirements. The message is generally not a concern as long as it doesn't appear repeatedly and continuously. -TT |
From: Tom T. <to...@ts...> - 2014-08-01 13:42:23
|
On Thu, Jul 31, 2014 at 12:47 AM, David Lake <Dav...@ma...> wrote: > Hmm... So, if I run usrp_uhd_probe before starting OpenBTS, things look better, but I still can't find the network when I scan from any of my 8 phones (default database settings). Do you have access to an external 10 MHz reference source? -TT |
From: David L. <Dav...@ma...> - 2014-08-01 07:28:46
|
________________________________________ From: Ralph A. Schmid, dk5ras <ra...@sc...> Sent: 31 July 2014 00:47 To: David Lake; 'Tom Tsou' Cc: ope...@li... Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 Do you have something to verify if the thing emits RF of whatever kind? Like a 19.99$-RTL2832-SDR on a second PC, or even measuring equipment like a spectrum analyzer? > No - at least, not at the moment. Trying to find something. What happens if you enter for example the "noise" command on the openbts cli? OpenBTS> noise noise RSSI is -70 dB wrt full scale MS RSSI target is -50 dB wrt full scale INFO: the current noise level is acceptable. OpenBTS> Ralph. > -----Original Message----- > From: David Lake [mailto:Dav...@ma...] > Sent: Thursday, July 31, 2014 6:48 AM > To: Tom Tsou > Cc: ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > Hmm... So, if I run usrp_uhd_probe before starting OpenBTS, things look > better, but I still can't find the network when I scan from any of my 8 phones > (default database settings). > > This is what I see on start-up now: > > root@dlake-ThinkPad-T60:~/openbts/apps# ./OpenBTS ALERT 2997:2997 > 2014-07-30T21:44:27.0 OpenBTS.cpp:600:main: OpenBTS (re)starting, ver > 5.0.0-prealpha build date/time 2014-07-30T08:53:59 ALERT 2997:2997 2014-07- > 30T21:44:27.0 OpenBTS.cpp:601:main: OpenBTS reading config file > /etc/OpenBTS/OpenBTS.db > 1406781867.049901 3072497408: > > OpenBTS > Copyright 2008, 2009, 2010 Free Software Foundation, Inc. > Copyright 2010 Kestrel Signal Processing, Inc. > Copyright 2011, 2012, 2013, 2014 Range Networks, Inc. > Release 5.0.0-prealpha+a5473eedf1 CommonLibs:3ad343b97b P formal build > date 2014-07-30T08:49:27 "OpenBTS" is a registered trademark of Range > Networks, Inc. > > Contributors: > Range Networks, Inc.: > David Burgess, Harvind Samra, Donald Kirker, Doug Brown, > Pat Thompson, Kurtis Heimerl, Michael Iedema, Dave Gotwisner > Kestrel Signal Processing, Inc.: > David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga > GNU Radio: > Johnathan Corgan > Others: > Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy > Alexander Chemeris, Alberto Escudero-Pascual Incorporated L/GPL > libraries and components: > libortp, LGPL, 2.1 Copyright 2001 Simon MORLAT > sim...@li... > libusb, LGPL 2.1, various copyright holders, www.libusb.org > libzmq, LGPL 3: > Copyright (c) 2009-2011 250bpm s.r.o. > Copyright (c) 2011 Botond Ballo > Copyright (c) 2007-2009 iMatix Corporation Incorporated BSD/MIT-style > libraries and components: > A5/1 Pedagogical Implementation, Simplified BSD License, Copyright 1998- > 1999 Marc Briceno, Ian Goldberg, and David Wagner > JsonBox, Copyright 2011 Anhero Inc. > Google Core Dumper, BSD 3-Clause License, Copyright (c) 2005-2007, Google > Inc. > Incorporated public domain libraries and components: > sqlite3, released to public domain 15 Sept 2001, www.sqlite.org > > > This program comes with ABSOLUTELY NO WARRANTY. > > Use of this software may be subject to other legal restrictions, including > patent licensing and radio spectrum licensing. > All users of this software are expected to comply with applicable regulations > and laws. See the LEGAL file in the source code for more information. > > Note to US Government Users: > The OpenBTS software applications and associated documentation are > "Commercial Item(s)," as that term is defined at 48 C.F.R. Section 2.101, > consisting of "Commercial Computer Software" and "Commercial Computer > Software Documentation," > as such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202, as > applicable. Consistent with 48 C.F.R. 12.212 or 48 C.F.R. Sections 227.7202-1 > through 227.7202-4, as applicable, the Commercial Computer Software and > Commercial Computer Software Documentation are being licensed to U.S. > Government end users (a) only as Commercial Items and (b) with only those > rights as are granted to all other end users pursuant to the terms and > conditions of Range Networks' software licenses and master customer > agreement. > > > 1406781867.149869 3072497408: > Starting the system... > ALERT 2997:3004 2014-07-30T21:44:32.2 OpenBTS.cpp:174:startTransceiver: > starting transceiver ./transceiver with 1 ARFCNs linux; GNU C++ version 4.6.3; > Boost_105400; UHD_003.007.002-49-g9eb403f4 > > Using internal clock reference > -- Operating over USB 2. > -- Initialize CODEC control... > -- Initialize Radio control... > -- Performing register loopback test... pass > -- Performing register loopback test... pass > -- Performing CODEC loopback test... pass > -- Performing CODEC loopback test... pass > -- Asking for clock rate 32.000000 MHz > -- Actually got clock rate 32.000000 MHz > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass > -- Asking for clock rate 26.000000 MHz > -- Actually got clock rate 26.000000 MHz > -- Performing timer loopback test... pass > -- Performing timer loopback test... pass ALERT 2997:2997 2014-07- > 30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed > with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: SCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: FCCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: BCCH handover clear failed ALERT > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.0 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3 handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3-SACCH handover > clear failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(1) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(1) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(2) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(2) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(3) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(3) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(4) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(4) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(5) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(5) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: NOHANDOVER(6) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.1 > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.1 TRXManager.cpp:565:clearHandover: > NOHANDOVER(6) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F-SACCH handover clear > failed ALERT 2997:2997 2014-07-30T21:44:40.2 > TRXManager.cpp:565:clearHandover: NOHANDOVER(7) failed with status 1 > ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F handover clear failed > ALERT 2997:2997 2014-07-30T21:44:40.2 TRXManager.cpp:565:clearHandover: > NOHANDOVER(7) failed with status 1 ALERT 2997:2997 2014-07-30T21:44:40.2 > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F-SACCH handover clear > failed > 1406781880.212909 3072497408: > system ready > > 1406781880.213018 3072497408: > use the OpenBTSCLI utility to access CLI > > 1406781880.213334 3072497408: OpenBTSCLI network socket support for > tcp:49300 > > OpenBTS> > > > David > ________________________________________ > From: Tom Tsou <to...@ts...> > Sent: 30 July 2014 17:18 > To: David Lake > Cc: ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > On Wed, Jul 30, 2014 at 7:37 PM, David Lake <Dav...@ma...> > wrote: > > linux; GNU C++ version 4.6.3; Boost_105400; > > UHD_003.007.002-49-g9eb403f4 > > > > Using internal clock reference > > -- Loading firmware image: > /usr/local/share/uhd/images/usrp_b200_fw.hex... > > done > > -- Loading FPGA image: > /usr/local/share/uhd/images/usrp_b210_fpga.bin... > > 10% > > Try running uhd_usrp_probe before OpenBTS. It seems there may be a USB > hiccup during the FPGA load. > > -TT > > ---------------------------------------------------------------------------- -- > Infragistics Professional > Build stunning WinForms apps today! > Reboot your WinForms applications with our WinForms controls. > Build a bridge from your legacy apps to the future. > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.cl > ktrk > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss |
From: Ralph A. S. d. <ra...@sc...> - 2014-08-01 12:28:33
|
Is this noise value always the same, or does it change, when you repeat it a few times? > -----Original Message----- > From: David Lake [mailto:Dav...@ma...] > Sent: Friday, August 1, 2014 9:29 AM > To: Ralph A. Schmid, dk5ras; 'Tom Tsou' > Cc: ope...@li... > Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > > ________________________________________ > From: Ralph A. Schmid, dk5ras <ra...@sc...> > Sent: 31 July 2014 00:47 > To: David Lake; 'Tom Tsou' > Cc: ope...@li... > Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > Do you have something to verify if the thing emits RF of whatever kind? Like > a 19.99$-RTL2832-SDR on a second PC, or even measuring equipment like a > spectrum analyzer? > > > No - at least, not at the moment. Trying to find something. > > What happens if you enter for example the "noise" command on the > openbts cli? > > OpenBTS> noise > noise RSSI is -70 dB wrt full scale > MS RSSI target is -50 dB wrt full scale > INFO: the current noise level is acceptable. > OpenBTS> > > > Ralph. > > > > -----Original Message----- > > From: David Lake [mailto:Dav...@ma...] > > Sent: Thursday, July 31, 2014 6:48 AM > > To: Tom Tsou > > Cc: ope...@li... > > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > > > Hmm... So, if I run usrp_uhd_probe before starting OpenBTS, things > > look better, but I still can't find the network when I scan from any > > of my 8 > phones > > (default database settings). > > > > This is what I see on start-up now: > > > > root@dlake-ThinkPad-T60:~/openbts/apps# ./OpenBTS ALERT 2997:2997 > > 2014-07-30T21:44:27.0 OpenBTS.cpp:600:main: OpenBTS (re)starting, ver > > 5.0.0-prealpha build date/time 2014-07-30T08:53:59 ALERT 2997:2997 > 2014-07- > > 30T21:44:27.0 OpenBTS.cpp:601:main: OpenBTS reading config file > > /etc/OpenBTS/OpenBTS.db > > 1406781867.049901 3072497408: > > > > OpenBTS > > Copyright 2008, 2009, 2010 Free Software Foundation, Inc. > > Copyright 2010 Kestrel Signal Processing, Inc. > > Copyright 2011, 2012, 2013, 2014 Range Networks, Inc. > > Release 5.0.0-prealpha+a5473eedf1 CommonLibs:3ad343b97b P formal > build > > date 2014-07-30T08:49:27 "OpenBTS" is a registered trademark of Range > > Networks, Inc. > > > > Contributors: > > Range Networks, Inc.: > > David Burgess, Harvind Samra, Donald Kirker, Doug Brown, > > Pat Thompson, Kurtis Heimerl, Michael Iedema, Dave Gotwisner > > Kestrel Signal Processing, Inc.: > > David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga > > GNU Radio: > > Johnathan Corgan > > Others: > > Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy > > Alexander Chemeris, Alberto Escudero-Pascual Incorporated L/GPL > > libraries and components: > > libortp, LGPL, 2.1 Copyright 2001 Simon MORLAT > > sim...@li... > > libusb, LGPL 2.1, various copyright holders, www.libusb.org > > libzmq, LGPL 3: > > Copyright (c) 2009-2011 250bpm s.r.o. > > Copyright (c) 2011 Botond Ballo > > Copyright (c) 2007-2009 iMatix Corporation Incorporated > BSD/MIT-style > > libraries and components: > > A5/1 Pedagogical Implementation, Simplified BSD License, Copyright > > 1998- > > 1999 Marc Briceno, Ian Goldberg, and David Wagner > > JsonBox, Copyright 2011 Anhero Inc. > > Google Core Dumper, BSD 3-Clause License, Copyright (c) 2005-2007, > Google > > Inc. > > Incorporated public domain libraries and components: > > sqlite3, released to public domain 15 Sept 2001, www.sqlite.org > > > > > > This program comes with ABSOLUTELY NO WARRANTY. > > > > Use of this software may be subject to other legal restrictions, > > including patent licensing and radio spectrum licensing. > > All users of this software are expected to comply with applicable > regulations > > and laws. See the LEGAL file in the source code for more information. > > > > Note to US Government Users: > > The OpenBTS software applications and associated documentation are > > "Commercial Item(s)," as that term is defined at 48 C.F.R. Section > > 2.101, consisting of "Commercial Computer Software" and "Commercial > > Computer Software Documentation," > > as such terms are used in 48 C.F.R. 12.212 or 48 C.F.R. 227.7202, as > > applicable. Consistent with 48 C.F.R. 12.212 or 48 C.F.R. Sections > 227.7202-1 > > through 227.7202-4, as applicable, the Commercial Computer Software > > and Commercial Computer Software Documentation are being licensed to > U.S. > > Government end users (a) only as Commercial Items and (b) with only > > those rights as are granted to all other end users pursuant to the > > terms and conditions of Range Networks' software licenses and master > > customer agreement. > > > > > > 1406781867.149869 3072497408: > > Starting the system... > > ALERT 2997:3004 2014-07-30T21:44:32.2 OpenBTS.cpp:174:startTransceiver: > > starting transceiver ./transceiver with 1 ARFCNs linux; GNU C++ > > version > 4.6.3; > > Boost_105400; UHD_003.007.002-49-g9eb403f4 > > > > Using internal clock reference > > -- Operating over USB 2. > > -- Initialize CODEC control... > > -- Initialize Radio control... > > -- Performing register loopback test... pass > > -- Performing register loopback test... pass > > -- Performing CODEC loopback test... pass > > -- Performing CODEC loopback test... pass > > -- Asking for clock rate 32.000000 MHz > > -- Actually got clock rate 32.000000 MHz > > -- Performing timer loopback test... pass > > -- Performing timer loopback test... pass > > -- Asking for clock rate 26.000000 MHz > > -- Actually got clock rate 26.000000 MHz > > -- Performing timer loopback test... pass > > -- Performing timer loopback test... pass ALERT 2997:2997 2014-07- > > 30T21:44:39.8 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed > > with status 1 ALERT 2997:2997 2014-07-30T21:44:39.8 > > GSML1FEC.cpp:575:handoverPending: SCH handover clear failed ALERT > > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:39.8 > > GSML1FEC.cpp:575:handoverPending: FCCH handover clear failed ALERT > > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:39.8 > > GSML1FEC.cpp:575:handoverPending: BCCH handover clear failed ALERT > > 2997:2997 2014-07-30T21:44:39.8 TRXManager.cpp:565:clearHandover: > > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:39.8 > > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0 handover clear > failed > > ALERT 2997:2997 2014-07-30T21:44:39.8 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:39.8 > > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-0-SACCH handover > clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.0 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1 handover clear > failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-1-SACCH handover > clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2 handover clear > failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-2-SACCH handover > clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3 handover clear > failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(0) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T0 SDCCH/4-3-SACCH handover > clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(1) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F handover clear failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(1) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T1 TCH/F-SACCH handover clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(2) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F handover clear failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(2) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T2 TCH/F-SACCH handover clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(3) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F handover clear failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(3) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T3 TCH/F-SACCH handover clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(4) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F handover clear failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(4) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T4 TCH/F-SACCH handover clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(5) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F handover clear failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(5) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T5 TCH/F-SACCH handover clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.1 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(6) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.1 > > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F handover clear failed > > ALERT 2997:2997 2014-07-30T21:44:40.1 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(6) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.2 > > GSML1FEC.cpp:575:handoverPending: C0T6 TCH/F-SACCH handover clear > > failed ALERT 2997:2997 2014-07-30T21:44:40.2 > > TRXManager.cpp:565:clearHandover: NOHANDOVER(7) failed with status 1 > > ALERT 2997:2997 2014-07-30T21:44:40.2 > > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F handover clear failed > > ALERT 2997:2997 2014-07-30T21:44:40.2 > TRXManager.cpp:565:clearHandover: > > NOHANDOVER(7) failed with status 1 ALERT 2997:2997 > > 2014-07-30T21:44:40.2 > > GSML1FEC.cpp:575:handoverPending: C0T7 TCH/F-SACCH handover clear > > failed > > 1406781880.212909 3072497408: > > system ready > > > > 1406781880.213018 3072497408: > > use the OpenBTSCLI utility to access CLI > > > > 1406781880.213334 3072497408: OpenBTSCLI network socket support for > > tcp:49300 > > > > OpenBTS> > > > > > > David > > ________________________________________ > > From: Tom Tsou <to...@ts...> > > Sent: 30 July 2014 17:18 > > To: David Lake > > Cc: ope...@li... > > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > > > On Wed, Jul 30, 2014 at 7:37 PM, David Lake > > <Dav...@ma...> > > wrote: > > > linux; GNU C++ version 4.6.3; Boost_105400; > > > UHD_003.007.002-49-g9eb403f4 > > > > > > Using internal clock reference > > > -- Loading firmware image: > > /usr/local/share/uhd/images/usrp_b200_fw.hex... > > > done > > > -- Loading FPGA image: > > /usr/local/share/uhd/images/usrp_b210_fpga.bin... > > > 10% > > > > Try running uhd_usrp_probe before OpenBTS. It seems there may be a > USB > > hiccup during the FPGA load. > > > > -TT > > > > > ---------------------------------------------------------------------------- > -- > > Infragistics Professional > > Build stunning WinForms apps today! > > Reboot your WinForms applications with our WinForms controls. > > Build a bridge from your legacy apps to the future. > > > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg. > > cl > > ktrk > > _______________________________________________ > > Openbts-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openbts-discuss |
From: Tom T. <to...@ts...> - 2014-08-01 13:51:24
|
On Fri, Aug 1, 2014 at 3:41 AM, David Lake <Dav...@ma...> wrote: > OK - now I am seeing something I don't like in OpenBTS.log: > > transceiver: NOTICE 3275:3360 2014-08-01T00:39:30.2 Transceiver.cpp:191:pushRadioVector: dumping STALE burst in TRX->USRP interface This means a burst from the upper stack arrived late at the transceiver and missed the transmit timing window. The underlying cause is either CPU or OS scheduling related - GSM has real time requirements. The message is generally not a concern as long as it doesn't appear repeatedly and continuously. -TT |
From: Ralph A. S. d. <ra...@sc...> - 2014-08-01 16:21:03
|
Should be fine. My guesses go into Toms direction; the reference frequency may be a bit off, so you don't meet the strict accuracy required by GSM. Ralph. > -----Original Message----- > From: David Lake [mailto:Dav...@ma...] > Sent: Friday, 1 August, 2014 17:37 > To: Tom Tsou > Cc: Ralph A. Schmid, dk5ras; ope...@li... > Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > Hmm - in that case, this may be my problem. The PC I am using is an old T60 with an Intel Centrino Duo CPU and 2G of RAM. > > Time to find a new box in the cupboard.... > ________________________________________ > From: Tom Tsou <to...@ts...> > Sent: 01 August 2014 06:51 > To: David Lake > Cc: Ralph A. Schmid, dk5ras; ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > On Fri, Aug 1, 2014 at 3:41 AM, David Lake <Dav...@ma...> wrote: > > OK - now I am seeing something I don't like in OpenBTS.log: > > > > transceiver: NOTICE 3275:3360 2014-08-01T00:39:30.2 > > Transceiver.cpp:191:pushRadioVector: dumping STALE burst in TRX->USRP > > interface > > This means a burst from the upper stack arrived late at the transceiver and missed the transmit timing window. The underlying cause > is either CPU or OS scheduling related - GSM has real time requirements. The message is generally not a concern as long as it doesn't > appear repeatedly and continuously. > > -TT |
From: David L. <Dav...@ma...> - 2014-08-01 17:47:54
|
I need to scratch around and see if I can find a timing source. David ________________________________________ From: Ralph A. Schmid, dk5ras <ra...@sc...> Sent: 01 August 2014 09:20 To: David Lake; 'Tom Tsou' Cc: ope...@li... Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 Should be fine. My guesses go into Toms direction; the reference frequency may be a bit off, so you don't meet the strict accuracy required by GSM. Ralph. > -----Original Message----- > From: David Lake [mailto:Dav...@ma...] > Sent: Friday, 1 August, 2014 17:37 > To: Tom Tsou > Cc: Ralph A. Schmid, dk5ras; ope...@li... > Subject: RE: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > Hmm - in that case, this may be my problem. The PC I am using is an old T60 with an Intel Centrino Duo CPU and 2G of RAM. > > Time to find a new box in the cupboard.... > ________________________________________ > From: Tom Tsou <to...@ts...> > Sent: 01 August 2014 06:51 > To: David Lake > Cc: Ralph A. Schmid, dk5ras; ope...@li... > Subject: Re: [Openbts-discuss] Problem with OpenBTS 5.0.0 and B210 > > On Fri, Aug 1, 2014 at 3:41 AM, David Lake <Dav...@ma...> wrote: > > OK - now I am seeing something I don't like in OpenBTS.log: > > > > transceiver: NOTICE 3275:3360 2014-08-01T00:39:30.2 > > Transceiver.cpp:191:pushRadioVector: dumping STALE burst in TRX->USRP > > interface > > This means a burst from the upper stack arrived late at the transceiver and missed the transmit timing window. The underlying cause > is either CPU or OS scheduling related - GSM has real time requirements. The message is generally not a concern as long as it doesn't > appear repeatedly and continuously. > > -TT |