You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(10) |
Oct
(10) |
Nov
(7) |
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
(38) |
Feb
(14) |
Mar
(25) |
Apr
(59) |
May
(25) |
Jun
(36) |
Jul
(39) |
Aug
(63) |
Sep
(98) |
Oct
(207) |
Nov
(116) |
Dec
(163) |
2010 |
Jan
(101) |
Feb
(105) |
Mar
(88) |
Apr
(68) |
May
(87) |
Jun
(46) |
Jul
(114) |
Aug
(183) |
Sep
(86) |
Oct
(70) |
Nov
(145) |
Dec
(78) |
2011 |
Jan
(80) |
Feb
(104) |
Mar
(87) |
Apr
(111) |
May
(91) |
Jun
(186) |
Jul
(204) |
Aug
(268) |
Sep
(91) |
Oct
(343) |
Nov
(351) |
Dec
(212) |
2012 |
Jan
(215) |
Feb
(205) |
Mar
(259) |
Apr
(157) |
May
(170) |
Jun
(155) |
Jul
(274) |
Aug
(172) |
Sep
(185) |
Oct
(162) |
Nov
(203) |
Dec
(218) |
2013 |
Jan
(278) |
Feb
(193) |
Mar
(155) |
Apr
(177) |
May
(204) |
Jun
(260) |
Jul
(127) |
Aug
(180) |
Sep
(185) |
Oct
(194) |
Nov
(84) |
Dec
(111) |
2014 |
Jan
(148) |
Feb
(165) |
Mar
(182) |
Apr
(365) |
May
(159) |
Jun
(224) |
Jul
(142) |
Aug
(82) |
Sep
(129) |
Oct
(128) |
Nov
(42) |
Dec
(180) |
2015 |
Jan
(198) |
Feb
(153) |
Mar
(98) |
Apr
(76) |
May
(54) |
Jun
(58) |
Jul
(42) |
Aug
(37) |
Sep
(19) |
Oct
(44) |
Nov
(49) |
Dec
(17) |
2016 |
Jan
(59) |
Feb
(50) |
Mar
(72) |
Apr
(33) |
May
(98) |
Jun
(52) |
Jul
(80) |
Aug
(28) |
Sep
(26) |
Oct
(44) |
Nov
(25) |
Dec
(33) |
2017 |
Jan
(108) |
Feb
(61) |
Mar
(42) |
Apr
(29) |
May
(34) |
Jun
(8) |
Jul
(13) |
Aug
(2) |
Sep
(2) |
Oct
|
Nov
(6) |
Dec
(5) |
2018 |
Jan
(8) |
Feb
(6) |
Mar
(13) |
Apr
(10) |
May
(13) |
Jun
(10) |
Jul
(6) |
Aug
(1) |
Sep
(4) |
Oct
(11) |
Nov
(8) |
Dec
|
2019 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
|
May
(3) |
Jun
(6) |
Jul
(1) |
Aug
(8) |
Sep
(8) |
Oct
(2) |
Nov
(1) |
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(3) |
2021 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(6) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ferdaus, F. <ff...@wi...> - 2018-06-27 20:57:36
|
Hi there, I have abled to register my programmed sim with the BTS. However, I did not get the following instructions (probably misunderstood) from OpenBTS installation page<http://openbts.org/w/index.php?title=BuildInstallRun>: "With these two tests passed, you can now test the voice connection. Call 600 from the phone (9196 with FreeSWITCH) to call the "echo" service. If that's working, congrats! Lastly, we can test SMS support. Send an SMS to 101 with a 7-10 digit number (configurable in smqueue). That is now your new number in the system. Do this with a second phone/SIM and then text between them. If this is working, congrats, your SMS services are working as well!" I am getting the following message on my mobile phone while I am calling to 600: STK This is unregister number, could not switch Could anyone please let me know, what's the problem and how can I fix it? Thanks in advance Best Regards, Farah ________________________________ From: Ferdaus, Farah Sent: Sunday, June 10, 2018 5:43 PM To: ope...@li... Subject: Regarding Programming SIM cards Hi there, I am trying to program a Super SIM 16-in-1 using the Insten_USB_SIM_Card_Writer<https://www.amazon.com/Insten-Reader-Writer-Backup-Phone/dp/B0188GHIP2/ref=pd_sbs_147_1?_encoding=UTF8&pd_rd_i=B0188GHIP2&pd_rd_r=7814918c-6ce3-11e8-8c85-6f6601b90f74&pd_rd_w=uWdRH&pd_rd_wg=JuNOy&pf_rd_i=desktop-dp-sims&pf_rd_m=ATVPDKIKX0DER&pf_rd_p=5825442648805390339&pf_rd_r=KR5JHK6G2A4ATF92VJ6S&pf_rd_s=desktop-dp-sims&pf_rd_t=40701&psc=1&refRID=KR5JHK6G2A4ATF92VJ6S> and following the steps mentioned here<http://openbts.org/w/index.php?title=ProgrammingSIMcards> and here<http://osmocom.org/projects/pysim/wiki> but unable to write the sim card. Every time I run the pcsc_scan command it stops working. Below is the output. "wslopenbts@wslopenbts-desktop:~$ pcsc_scan PC/SC device scanner V 1.4.25 (c) 2001-2011, Ludovic Rousseau <lud...@fr...> Compiled with PC/SC lite version: 1.8.14 Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...^C" Can anyone please help me regarding this issue. Thanks in advance Best Regards, Farah |
From: Serafim N. <S.N...@sk...> - 2018-06-25 18:07:06
|
Hi developers, we use the latest OpenBTS version from git and USRP N200 and X310 as radio. Now we observe to one unpleasant problem: the operating frequency, that set in the configs actually differs from the real transmitted frequency, which in turn leads to periodic connectivity problems. For example, we set the GSM.Radio.C0 parameter to the value of 107 (956.6 MHz), but on spectrum analyzer we see, that working frequency is 956.4MHz. We tried to calibrate the USRP (using default utilities uhd_cal_rx_iq_balance, uhd_cal_tx_iq_balance, uhd_cal_tx_dc_offset) and then using the GNU-radio and also using the test utilities (like, default tx_waveforms) checks, that frequency was correctly installed and her (frequency) is fully clear. Also we see that there is a "TRX.RadioFrequencyOffset" parameter in configs, but if it does not change the frequency offset ((( Do you have ideas how to fix it? Do you have opportunities to calibrate USRP and correctly installs TRX parameters in the configs (for example, TRX.RadioFrequencyOffset)? Best Regards, Serafim Novichkov |
From: wu jo <joh...@ho...> - 2018-06-19 09:39:44
|
hi all, I want to introduce an sdr that compatible with usrp b210. we develop an sdr according to b210 schematic. the performance and interface is the same as b210. it works fine with openbts, openairinterface, srslte, gnuradio, uhd and so on. anyone need a b210 and can not afford its price can use this one instead. |
From: wu jo <joh...@ho...> - 2018-06-19 08:22:13
|
Hi all, i can provide amplifier LNA and duplexer for GSM, umts, LTE. if any one need this in your project can contact me. Best Regards |
From: daniel m. <dan...@gm...> - 2018-06-13 08:50:20
|
Hi! I am using openbts and I noticed I'm not encrypting the SMS i send. I've found in this site: https://wush.net/trac/rangepublic/wiki/A3A8A5 that i have to add encryption to the system but i don't know how. Do you know how can i solve this problem? I followed the OpenBTS Getting Start tutorial to set the net but I don't know how to add encryption. Thank you! |
From: Javier V. <jav...@po...> - 2018-06-12 16:29:21
|
Hi all, I have been working for a while with USRP 2901 and finally got UHD and OpenBTS compiled. However, I can not get the phone registered on the network. I am guessing sipauthserve is not working right but I am not sure. OS - Ubuntu Server 12.04 LTS 32 bits UHD: Installed with Ettus repo (adding repo and installing with package manager) - libuhd-dev 3.9.5-0ubuntu1~precise1 - libuhd003 3.9.5-0ubuntu1~precise1 - uhd-host 3.9.5-0ubuntu1~precise1 OpenBTS - ./switchto 5.0 - ./build B210 The logs from my console: uhd_find_devices: linux; GNU C++ version 4.6.3; Boost_104601; UHD_003.009.005-release -------------------------------------------------- -- UHD Device 0 -------------------------------------------------- Device Address: type: b200 name: NI2901 serial: 310C575 product: B210 When I start my device, I stop all the services (they start from boot) and then start them again once I connect my USRP. sudo start sipauthserve sudo start smqueue sudo start asterisk sudo start openbts Then I go to my phone, and I see the "Test PLMN 001-01", so I try to register and I get a Registration Failure. So I go to OpenBTSCLI and I can not see anything in tmsis OpenBTS> tmsis IMSI TMSI IMEI AUTH CREATED ACCESSED TMSI_ASSIGNED I also registered my IMSI into my test network properly (yes, I changed the XXXX to my IMSI) ./dev/NodeManager/nmcli.py sipauthserve subscribers create "PodIMSI" IMSIXXXXXXXXXXXXXXX 666777888 And I can see the changes in the database by doing nmcli read: $ ./dev/NodeManager/nmcli.py sipauthserve subscribers read raw request: {"command":"subscribers","action":"read","key":"","value":""} raw response: { "code" : 200, "data" : [ { "imsi" : "IMSIXXXXXXXXXXXXXXX", "msisdn" : "666777888", "name" : "PodIMSI" } ] } But still I do not see anything in "tmsis" or in the logs. Does anybody have an idea of what can be happening? Regards, *Javier Vargas* Research and Innovation Pod Group jav...@po... www.podgroup.com <https://podgroup.com/> www.podm2m.com <https://podm2m.com/> www.pod.solutions <https://pod.solutions/> UK: +44 (0)1223 850 900 <+44%201223%20850900> USA: +1 415 7070 500 Spain: +34 954 050 200 <+34%20954%2005%2002%2000> [image: Facebook] <https://www.facebook.com/PodM2M/> [image: Twitter] <https://twitter.com/podm2m> [image: LinkedIn] <https://linkedin.com/company-beta/236154/> [image: Instagram] <https://www.instagram.com/podm2m/> Pod Group (formerly Podsystem) has offices in the UK (Cambridge), Spain (Seville) and the US (San Francisco). From these offices we serve customers across Europe and the US and we are able to provide coverage at a global level in specific countries throughout Asia, Australia and Africa. |
From: Ferdaus, F. <ff...@wi...> - 2018-06-10 21:43:30
|
Hi there, I am trying to program a Super SIM 16-in-1 using the Insten_USB_SIM_Card_Writer<https://www.amazon.com/Insten-Reader-Writer-Backup-Phone/dp/B0188GHIP2/ref=pd_sbs_147_1?_encoding=UTF8&pd_rd_i=B0188GHIP2&pd_rd_r=7814918c-6ce3-11e8-8c85-6f6601b90f74&pd_rd_w=uWdRH&pd_rd_wg=JuNOy&pf_rd_i=desktop-dp-sims&pf_rd_m=ATVPDKIKX0DER&pf_rd_p=5825442648805390339&pf_rd_r=KR5JHK6G2A4ATF92VJ6S&pf_rd_s=desktop-dp-sims&pf_rd_t=40701&psc=1&refRID=KR5JHK6G2A4ATF92VJ6S> and following the steps mentioned here<http://openbts.org/w/index.php?title=ProgrammingSIMcards> and here<http://osmocom.org/projects/pysim/wiki> but unable to write the sim card. Every time I run the pcsc_scan command it stops working. Below is the output. "wslopenbts@wslopenbts-desktop:~$ pcsc_scan PC/SC device scanner V 1.4.25 (c) 2001-2011, Ludovic Rousseau <lud...@fr...> Compiled with PC/SC lite version: 1.8.14 Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...^C" Can anyone please help me regarding this issue. Thanks in advance Best Regards, Farah |
From: wu jo <joh...@ho...> - 2018-06-09 08:43:07
|
question 1: the openbts set sample rate as 270.8333333333333khz(1625k / 8). and can also set the 4 times sample rate which is 1625k / 2. the arfcn interval is 200khz. question 2: set rxgain higher is better. provide affordable sdr ________________________________ 发件人: oscar llerena <osc...@gm...> 发送时间: 2018年6月3日 8:40:00 收件人: ope...@li... 主题: [Openbts-discuss] Question regarding sample_rate and rxgain on OpenBTS Hi everyone. I couldn't find any answer to this doubt: Facts: OpenBTS uses 01 ARFCN (#512 on DCS1800 in my case) as a carrier with a channel bandwidth of 200 kHz (or is it 250?). Here, with the help of Gnuradio I built a simple spectrum analyzer with my USRP-B210 and I noticed that when the LNA gain = 37 (which I suppose is the same as rxgain in OpenBTS), the max channel noise was around -82dB while the average noise was around -84dB (values which I assume they are "wrt A/D full scale" as same as OpenBTS) and also the DC Component was totally overlapped by the noise floor. Greater LNA gain values increased the noise floor. Lower LNA gain values showed DC Component. Also greater samp_rate values on the USRP-B210 (which I assume is the received channel bandwidth) lead to increase the channel noise floor. Spectrum Analyzer: UHD-Source Block ---------- QT Gui Frequency Sink. So, please help me with this doubts: Question 1: Does OpenBTS transceiver sets up USRP-B210 to work with 200 kHz + x%*(200 kHz) of sample rate such as x is around 10-20%? or does OpenBTS work with more sample rate to decode channel? Question 2: Does best the rxgain is the one that produces less received noise and at the same time makes DC Component disappear? Thanks -- Oscar Llerena |
From: oscar l. <osc...@gm...> - 2018-06-03 08:40:08
|
Hi everyone. I couldn't find any answer to this doubt: Facts: OpenBTS uses 01 ARFCN (#512 on DCS1800 in my case) as a carrier with a channel bandwidth of 200 kHz (or is it 250?). Here, with the help of Gnuradio I built a simple spectrum analyzer with my USRP-B210 and I noticed that when the LNA gain = 37 (which I suppose is the same as rxgain in OpenBTS), the max channel noise was around -82dB while the average noise was around -84dB (values which I assume they are "wrt A/D full scale" as same as OpenBTS) and also the DC Component was totally overlapped by the noise floor. Greater LNA gain values increased the noise floor. Lower LNA gain values showed DC Component. Also greater samp_rate values on the USRP-B210 (which I assume is the received channel bandwidth) lead to increase the channel noise floor. Spectrum Analyzer: UHD-Source Block ---------- QT Gui Frequency Sink. So, please help me with this doubts: Question 1: Does OpenBTS transceiver sets up USRP-B210 to work with 200 kHz + x%*(200 kHz) of sample rate such as x is around 10-20%? or does OpenBTS work with more sample rate to decode channel? Question 2: Does best the rxgain is the one that produces less received noise and at the same time makes DC Component disappear? Thanks -- Oscar Llerena |
From: Ferdaus, F. <ff...@wi...> - 2018-05-30 18:18:26
|
Dear Neel, I am really grateful that you are trying to fix mine issues with patience. I'm not sure why you're seeing this error. It almost looks like there might be a hardware problem with this N210 unit. Make sure that your MTU is 1500, and that the N210 is directly connected to the ghost computer, with no switch or router in the middle. My MTU is 1472 (default). I am not sure how can I change the default MTU. Yes, the N210 is directly connected to the host computer. Does "uhd_usrp_probe" run without any errors? Yes, it is. Here is the output. "wslopenbts@wslopenbts-Inspiron-560:~$ uhd_usrp_probe linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.003.HEAD-0-gef157678 -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes _____________________________________________________ / | Device: USRP2 / N-Series Device | _____________________________________________________ | / | | Mboard: N210r4 | | hardware: 2577 | | mac-addr: a0:36:fa:25:35:f4 | | ip-addr: 192.168.10.2 | | subnet: 255.255.255.255 | | gateway: 255.255.255.255 | | gpsdo: none | | serial: EFR15T4UP | | FW Version: 12.4 | | FPGA Version: 11.1 | | | | Time sources: none, external, _external_, mimo | | Clock sources: internal, external, mimo | | Sensors: mimo_locked, ref_locked | | _____________________________________________________ | | / | | | RX DSP: 0 | | | | | | Freq range: -50.000 to 50.000 MHz | | _____________________________________________________ | | / | | | RX DSP: 1 | | | | | | Freq range: -50.000 to 50.000 MHz | | _____________________________________________________ | | / | | | RX Dboard: A | | | ID: WBX v4, WBX v4 + Simple GDB (0x0063) | | | Serial: EER15YDXW | | | _____________________________________________________ | | | / | | | | RX Frontend: 0 | | | | Name: WBXv4 RX+GDB | | | | Antennas: TX/RX, RX2, CAL | | | | Sensors: lo_locked | | | | Freq range: 25.000 to 2200.000 MHz | | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | RX Codec: A | | | | Name: ads62p44 | | | | Gain range digital: 0.0 to 6.0 step 0.5 dB | | | | Gain range fine: 0.0 to 0.5 step 0.1 dB | | _____________________________________________________ | | / | | | TX DSP: 0 | | | | | | Freq range: -50.000 to 50.000 MHz | | _____________________________________________________ | | / | | | TX Dboard: A | | | ID: WBX v4 (0x0062) | | | Serial: EER15YDXW | | | ID: WBX + Simple GDB, WBX v3 + Simple GDB, WBX v4 + Simple GDB, WBX-120 + Simple GDB (0x004f) | | | Serial: EER15YDGS | | | _____________________________________________________ | | | / | | | | TX Frontend: 0 | | | | Name: WBXv4 TX+GDB | | | | Antennas: TX/RX, CAL | | | | Sensors: lo_locked | | | | Freq range: 25.000 to 2200.000 MHz | | | | Gain range PGA0: 0.0 to 31.0 step 1.0 dB | | | | Bandwidth range: 40000000.0 to 40000000.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | TX Codec: A | | | | Name: ad9777 | | | | Gain Elements: None" Do you have anything connected to the 10 MHz reference input, or to the 1 PPS signal input, of the N210? No, nothing is connected. It might be fastest to start over with a new fresh virgin installation of Ubuntu 16.04.4 (I would strongly suggest using Ubuntu 16.04) and of UHD 3.10.3.0. That should work out-of-the-box if you follow the Application Note, unless there is a hardware problem. Now, My environment is Ubuntu Desktop 16.04. This will be my last attempt to fix the problem. Thanks in advance Farah -{}- On 29 May 2018 at 15:05, Ferdaus, Farah <ff...@wi...<mailto:ff...@wi...>> wrote: Dear Neel, Thank you for your kind reply. Yes, after installing UHD version 3.10.3.0, I am able to install OpenBTS. But while I have tried to verify the Operation of the USRP Using UHD and GNURadio following the instruction mentioned here. I have got some error messages in two commands. Running this (./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat) command, showed the following error. wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.003.HEAD-0-gef157678 Creating the usrp device with: ... -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 10.000000 dB... Actual TX Gain: 10.000000 dB... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int _main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_samples_from_file.cpp:169 The output with error of this (./tx_waveforms --freq 915e6 --rate 5e6 --gain 0) command is given below: wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0 linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.003.HEAD-0-gef157678 Creating the usrp device with: ... -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 0.000000 dB... Actual TX Gain: 0.000000 dB... Setting device timestamp to 0... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int _main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_waveforms.cpp:221 Can you please tell me how can I fix it? Thanks in advance Farah ________________________________ From: Ferdaus, Farah Sent: Tuesday, May 29, 2018 6:00:46 PM To: Neel Pandeya Cc: ope...@li...<mailto:ope...@li...> Subject: Re: [Openbts-discuss] Suggestion regarding installation failure Dear Neel, Thank you for your kind reply. Yes, after installing UHD version 3.10.3.0, I am able to install OpenBTS. But while I have tried to verify the Operation of the USRP Using UHD and GNURadio following the instruction mentioned here<https://urldefense.proofpoint.com/v2/url?u=https-3A__kb.ettus.com_Verifying-5Fthe-5FOperation-5Fof-5Fthe-5FUSRP-5FUsing-5FUHD-5Fand-5FGNU-5FRadio&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=ztiT_CyX2tWpojE35sLwFvF9M9p2vcFedEO1k58rHJI&s=Zc_oATP8WUJFUf5lPq0-vLuZtV-X3U3OX1G50tXFNTI&e=>. I have got some error messages in two commands. Running this (./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat) command, showed the following error. wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat Creating the usrp device with: ... [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-g13c32cef [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 10.000000 dB... Actual TX Gain: 10.000000 dB... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_samples_from_file.cpp:161 The output with error of this (./tx_waveforms --freq 915e6 --rate 5e6 --gain 0) command is given below: wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0 Creating the usrp device with: ... [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-g13c32cef [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 0.000000 dB... Actual TX Gain: 0.000000 dB... Setting device timestamp to 0... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_waveforms.cpp:213 Can you please tell me how can I fix it? Thanks in advance Farah ________________________________ From: Neel Pandeya <nee...@et...<mailto:nee...@et...>> Sent: Tuesday, May 29, 2018 4:11 PM To: Ferdaus, Farah Cc: ope...@li...<mailto:ope...@li...> Subject: Re: [Openbts-discuss] Suggestion regarding installation failure Hello Farah: Attached are some instructions for installing OpenBTS. Be sure to install UHD first, before installing OpenBTS. I would suggest using UHD version 3.10.3.0. https://kb.ettus.com/Building_and_Installing_the_USRP_Open-Source_Toolchain_(UHD_and_GNU_Radio)_on_Linux<https://urldefense.proofpoint.com/v2/url?u=https-3A__kb.ettus.com_Building-5Fand-5FInstalling-5Fthe-5FUSRP-5FOpen-2DSource-5FToolchain-5F-28UHD-5Fand-5FGNU-5FRadio-29-5Fon-5FLinux&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=BRzneEEUGWi64F_I8eRIoWLiAWiInpJj4ZAe12ZTG5A&e=> --Neel Pandeya On 20 May 2018 at 14:30, Ferdaus, Farah <ff...@wi...<mailto:ff...@wi...>> wrote: Hi there, I am trying to install openbts following the steps mentioned here<https://urldefense.proofpoint.com/v2/url?u=http-3A__openbts.org_w_index.php-3Ftitle-3DBuildInstallRun&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=9xLQ3CRyUZWRwgRApGryyh9x9_Mu-vygtrpL6mn_-ng&e=>. I am using ubuntu 16.04 LTS and ettus UERP N210. Every time I am running the command (./build.sh N210) I am getting an error. Below is the list of errors that I have found. By selecting (./switchto.sh master) branch and after running the command (./build.sh N210) Error log shows the following: 2018-05-20T10:59:59\" -MT UHDDevice.lo -MD -MP -MF .deps/UHDDevice.Tpo -c UHDDevice.cpp -fPIC -DPIC -o .libs/UHDDevice.o UHDDevice.cpp:29:29: fatal error: uhd/utils/msg.hpp: No such file or directory compilation terminated. Makefile:665: recipe for target 'UHDDevice.lo' failed make[3]: *** [UHDDevice.lo] Error 1 make[3]: Leaving directory '/home/wslopenbts/dev/openbts/Transceiver52M' Makefile:572: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/wslopenbts/dev/openbts' Makefile:503: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/wslopenbts/dev/openbts' debian/rules:74: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! While I was searching, I have found someone had the same issue and he used (./switchto.sh 5.0) to fix the issue. I also tried to do so but got this error. wslopenbts@wslopenbts-Inspiron-560:~/dev$ ./build.sh N210 # checking for a supported radio type # - found # checking for a compatible build host # - fully supported host detected: Ubuntu 16.04 # # adding additional repo tools # - done # checking build dependencies # - done # make a home for this build mkdir -p BUILDS/2018-05-20--13-23-20 # libcoredumper - building Debian package and installing as dependency cd libcoredumper ./build.sh wget http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com_files_coredumper-2D1.2.1.tar.gz&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=yrCbKCc0RMIFSP6hPeAGrb3WDbmljm8h1PcaG52nrkc&e=> --2018-05-20 13:23:20-- http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com_files_coredumper-2D1.2.1.tar.gz&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=yrCbKCc0RMIFSP6hPeAGrb3WDbmljm8h1PcaG52nrkc&e=> Resolving google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=> (google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=>)... 209.85.232.82, 2607:f8b0:400d:c08::52 Connecting to google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=> (google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=>)|209.85.232.82|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2018-05-20 13:23:20 ERROR 404: Not Found. ERROR: command failed! # ERROR: command failed! Then I have tried different way by selecting (./switchto.sh 4.0) branch and after running the command (./build.sh N210) Error log shows the following: END failed--call queue aborted at /usr/bin/dh_installdirs line 243. debian/rules:69: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! By selecting (./switchto.sh v4.0.0) branch and after running the command (./build.sh N210) Error log shows the following: END failed--call queue aborted at /usr/bin/dh_installdirs line 243. debian/rules:69: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! Can anyone please help me to fix the issue. Thanks in advance. Farah ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot<https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=Irwm5saT82eLxZxwswG9s584es04OnAsUMv4e_lHG2g&e=> _______________________________________________ Openbts-discuss mailing list Ope...@li...<mailto:Ope...@li...> https://lists.sourceforge.net/lists/listinfo/openbts-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_openbts-2Ddiscuss&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=ehQN_0YOpba66Xn0fy2ZlPYGl2jYB-YvpVgR9XROdLQ&e=> |
From: Neel P. <nee...@et...> - 2018-05-29 23:14:52
|
Hello Farah: I'm not sure why you're seeing this error. It almost looks like there might be a hardware problem with this N210 unit. Make sure that your MTU is 1500, and that the N210 is directly connected to the ghost computer, with no switch or router in the middle. Does "uhd_usrp_probe" run without any errors? Do you have anything connected to the 10 MHz reference input, or to the 1 PPS signal input, of the N210? It might be fastest to start over with a new fresh virgin installation of Ubuntu 16.04.4 (I would strongly suggest using Ubuntu 16.04) and of UHD 3.10.3.0. That should work out-of-the-box if you follow the Application Note, unless there is a hardware problem. Please let me know if you are able to make any further progress. --Neel Pandeya -{}- On 29 May 2018 at 15:05, Ferdaus, Farah <ff...@wi...> wrote: > Dear Neel, > Thank you for your kind reply. Yes, after installing UHD version 3.10.3.0, > I am able to install OpenBTS. > But while I have tried to verify the Operation of the USRP Using UHD and > GNURadio following the instruction mentioned here. I have got some error > messages in two commands. Running this (*./tx_samples_from_file --freq > 915e6 --rate 5e6 --gain 10 usrp_samples.dat*) command, showed the > following error. > > *wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ > ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat* > *linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_003.010.003.HEAD-0-gef157678* > > *Creating the usrp device with: ... * > *-- Opening a USRP2/N-Series device...* > *-- Current recv frame size: 1472 bytes* > *-- Current send frame size: 1472 bytes* > *Using Device: Single USRP:* > * Device: USRP2 / N-Series Device* > * Mboard 0: N210r4* > * RX Channel: 0* > * RX DSP: 0* > * RX Dboard: A* > * RX Subdev: WBXv4 RX+GDB* > * TX Channel: 0* > * TX DSP: 0* > * TX Dboard: A* > * TX Subdev: WBXv4 TX+GDB* > > *Setting TX Rate: 5.000000 Msps... * > *Actual TX Rate: 5.000000 Msps...* > > *Setting TX Freq: 915.000000 MHz... * > *Actual TX Freq: 915.000000 MHz...* > > *Setting TX Gain: 10.000000 dB... * > *Actual TX Gain: 10.000000 dB...* > > *Checking TX: LO: unlocked ... * > *Error: AssertionError: lo_locked.to_bool()* > * in int _main(int, char**)* > * at > /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_samples_from_file.cpp:169* > > The output with error of this (*./tx_waveforms --freq 915e6 --rate 5e6 > --gain 0*) command is given below: > > *wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ > ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0* > *linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_003.010.003.HEAD-0-gef157678* > > *Creating the usrp device with: ... * > *-- Opening a USRP2/N-Series device...* > *-- Current recv frame size: 1472 bytes* > *-- Current send frame size: 1472 bytes* > *Using Device: Single USRP:* > * Device: USRP2 / N-Series Device* > * Mboard 0: N210r4* > * RX Channel: 0* > * RX DSP: 0* > * RX Dboard: A* > * RX Subdev: WBXv4 RX+GDB* > * TX Channel: 0* > * TX DSP: 0* > * TX Dboard: A* > * TX Subdev: WBXv4 TX+GDB* > > *Setting TX Rate: 5.000000 Msps... * > *Actual TX Rate: 5.000000 Msps...* > > *Setting TX Freq: 915.000000 MHz... * > *Actual TX Freq: 915.000000 MHz...* > > *Setting TX Gain: 0.000000 dB... * > *Actual TX Gain: 0.000000 dB...* > > *Setting device timestamp to 0... * > *Checking TX: LO: unlocked ...* > *Error: AssertionError: lo_locked.to_bool()* > * in int _main(int, char**)* > * at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_waveforms.cpp:221* > > Can you please tell me how can I fix it? > > Thanks in advance > Farah > > ------------------------------ > *From:* Ferdaus, Farah > *Sent:* Tuesday, May 29, 2018 6:00:46 PM > *To:* Neel Pandeya > > *Cc:* ope...@li... > *Subject:* Re: [Openbts-discuss] Suggestion regarding installation failure > > > Dear Neel, > > Thank you for your kind reply. Yes, after installing UHD version > 3.10.3.0, I am able to install OpenBTS. > > But while I have tried to verify the Operation of the USRP Using UHD and > GNURadio following the instruction mentioned here > <https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio>. > I have got some error messages in two commands. Running this (*./tx_samples_from_file > --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat*) command, showed the > following error. > > *wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ > ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat* > *Creating the usrp device with: ...* > *[INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_3.11.0.HEAD-0-g13c32cef* > *[INFO] [USRP2] Opening a USRP2/N-Series device...* > *[INFO] [USRP2] Current recv frame size: 1472 bytes* > *[INFO] [USRP2] Current send frame size: 1472 bytes* > *Using Device: Single USRP:* > *Device: USRP2 / N-Series Device* > *Mboard 0: N210r4* > *RX Channel: 0* > *RX DSP: 0* > *RX Dboard: A* > *RX Subdev: WBXv4 RX+GDB* > *TX Channel: 0* > *TX DSP: 0* > *TX Dboard: A* > *TX Subdev: WBXv4 TX+GDB* > *Setting TX Rate: 5.000000 Msps...* > *Actual TX Rate: 5.000000 Msps...* > *Setting TX Freq: 915.000000 MHz...* > *Actual TX Freq: 915.000000 MHz...* > *Setting TX Gain: 10.000000 dB...* > *Actual TX Gain: 10.000000 dB...* > *Checking TX: LO: unlocked ...* > *Error: AssertionError: lo_locked.to_bool()* > *in int main(int, char**)* > *at > /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_samples_from_file.cpp:161* > > The output with error of this (*./tx_waveforms --freq 915e6 --rate 5e6 > --gain 0*) command is given below: > > *wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ > ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0* > *Creating the usrp device with: ...* > *[INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_3.11.0.HEAD-0-g13c32cef* > *[INFO] [USRP2] Opening a USRP2/N-Series device...* > *[INFO] [USRP2] Current recv frame size: 1472 bytes* > *[INFO] [USRP2] Current send frame size: 1472 bytes* > *Using Device: Single USRP:* > *Device: USRP2 / N-Series Device* > *Mboard 0: N210r4* > *RX Channel: 0* > *RX DSP: 0* > *RX Dboard: A* > *RX Subdev: WBXv4 RX+GDB* > *TX Channel: 0* > *TX DSP: 0* > *TX Dboard: A* > *TX Subdev: WBXv4 TX+GDB* > *Setting TX Rate: 5.000000 Msps...* > *Actual TX Rate: 5.000000 Msps...* > *Setting TX Freq: 915.000000 MHz...* > *Actual TX Freq: 915.000000 MHz...* > *Setting TX Gain: 0.000000 dB...* > *Actual TX Gain: 0.000000 dB...* > *Setting device timestamp to 0...* > *Checking TX: LO: unlocked ...* > *Error: AssertionError: lo_locked.to_bool()* > *in int main(int, char**)* > *at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_waveforms.cpp:213* > > Can you please tell me how can I fix it? > > Thanks in advance > Farah > > ------------------------------ > *From:* Neel Pandeya <nee...@et...> > *Sent:* Tuesday, May 29, 2018 4:11 PM > *To:* Ferdaus, Farah > *Cc:* ope...@li... > *Subject:* Re: [Openbts-discuss] Suggestion regarding installation failure > > Hello Farah: > > Attached are some instructions for installing OpenBTS. > > Be sure to install UHD first, before installing OpenBTS. > > I would suggest using UHD version 3.10.3.0. > > https://kb.ettus.com/Building_and_Installing_the_USRP_Open- > Source_Toolchain_(UHD_and_GNU_Radio)_on_Linux > <https://urldefense.proofpoint.com/v2/url?u=https-3A__kb.ettus.com_Building-5Fand-5FInstalling-5Fthe-5FUSRP-5FOpen-2DSource-5FToolchain-5F-28UHD-5Fand-5FGNU-5FRadio-29-5Fon-5FLinux&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=BRzneEEUGWi64F_I8eRIoWLiAWiInpJj4ZAe12ZTG5A&e=> > > --Neel Pandeya > > > > > On 20 May 2018 at 14:30, Ferdaus, Farah <ff...@wi...> wrote: > > Hi there, > I am trying to install openbts following the steps mentioned here > <https://urldefense.proofpoint.com/v2/url?u=http-3A__openbts.org_w_index.php-3Ftitle-3DBuildInstallRun&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=9xLQ3CRyUZWRwgRApGryyh9x9_Mu-vygtrpL6mn_-ng&e=>. > I am using ubuntu 16.04 LTS and ettus UERP N210. Every time I am running > the command (*./build.sh N210*) I am getting an error. Below is the list > of errors that I have found. > > By selecting (*./switchto.sh master*) branch and after running the > command (./build.sh N210) Error log shows the following: > > *2018-05-20T10:59:59\" -MT UHDDevice.lo -MD -MP -MF .deps/UHDDevice.Tpo -c > UHDDevice.cpp -fPIC -DPIC -o .libs/UHDDevice.o* > *UHDDevice.cpp:29:29: fatal error: uhd/utils/msg.hpp: No such file or > directory* > *compilation terminated.* > *Makefile:665: recipe for target 'UHDDevice.lo' failed* > *make[3]: *** [UHDDevice.lo] Error 1* > *make[3]: Leaving directory '/home/wslopenbts/dev/openbts/Transceiver52M'* > *Makefile:572: recipe for target 'all-recursive' failed* > *make[2]: *** [all-recursive] Error 1* > *make[2]: Leaving directory '/home/wslopenbts/dev/openbts'* > *Makefile:503: recipe for target 'all' failed* > *make[1]: *** [all] Error 2* > *make[1]: Leaving directory '/home/wslopenbts/dev/openbts'* > *debian/rules:74: recipe for target 'install-arch' failed* > *make: *** [install-arch] Error 2* > *dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit > status 2* > *# ERROR: command failed!* > > While I was searching, I have found someone had the same issue and he used > (*./switchto.sh 5.0*) to fix the issue. I also tried to do so but got > this error. > > w*slopenbts@wslopenbts-Inspiron-560:~/dev$ ./build.sh N210* > *# checking for a supported radio type* > *# - found* > *# checking for a compatible build host* > *# - fully supported host detected: Ubuntu 16.04* > *#* > *# adding additional repo tools* > *# - done* > > *# checking build dependencies* > *# - done* > > *# make a home for this build* > *mkdir -p BUILDS/2018-05-20--13-23-20* > *# libcoredumper - building Debian package and installing as dependency* > *cd libcoredumper* > *./build.sh* > *wget > http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz > <https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com_files_coredumper-2D1.2.1.tar.gz&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=yrCbKCc0RMIFSP6hPeAGrb3WDbmljm8h1PcaG52nrkc&e=>* > *--2018-05-20 13:23:20-- > http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz > <https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com_files_coredumper-2D1.2.1.tar.gz&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=yrCbKCc0RMIFSP6hPeAGrb3WDbmljm8h1PcaG52nrkc&e=>* > *Resolving google-coredumper.googlecode.com > <https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=> > (google-coredumper.googlecode.com > <https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=>)... > 209.85.232.82, 2607:f8b0:400d:c08::52* > *Connecting to google-coredumper.googlecode.com > <https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=> > (google-coredumper.googlecode.com > <https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=>)|209.85.232.82|:80... > connected.* > *HTTP request sent, awaiting response... 404 Not Found* > *2018-05-20 13:23:20 ERROR 404: Not Found.* > > *ERROR: command failed!* > *# ERROR: command failed!* > > Then I have tried different way by selecting (*./switchto.sh 4.0*) branch > and after running the command (./build.sh N210) Error log shows the > following: > > *END failed--call queue aborted at /usr/bin/dh_installdirs line 243.* > *debian/rules:69: recipe for target 'install-arch' failed* > *make: *** [install-arch] Error 2* > *dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit > status 2* > *# ERROR: command failed!* > > By selecting (*./switchto.sh v4.0.0*) branch and after running the > command (./build.sh N210) Error log shows the following: > > > * END failed--call queue aborted at /usr/bin/dh_installdirs line 243. > debian/rules:69: recipe for target 'install-arch' failed make: *** > [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules > binary gave error exit status 2 # ERROR: command failed! * > Can anyone please help me to fix the issue. > > Thanks in advance. > Farah > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > <https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=Irwm5saT82eLxZxwswG9s584es04OnAsUMv4e_lHG2g&e=> > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_openbts-2Ddiscuss&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=ehQN_0YOpba66Xn0fy2ZlPYGl2jYB-YvpVgR9XROdLQ&e=> > > > |
From: Ferdaus, F. <ff...@wi...> - 2018-05-29 22:31:28
|
Dear Neel, Thank you for your kind reply. Yes, after installing UHD version 3.10.3.0, I am able to install OpenBTS. But while I have tried to verify the Operation of the USRP Using UHD and GNURadio following the instruction mentioned here<https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio>. I have got some error messages in two commands. Running this (./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat) command, showed the following error. wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat Creating the usrp device with: ... [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-g13c32cef [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 10.000000 dB... Actual TX Gain: 10.000000 dB... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_samples_from_file.cpp:161 The output with error of this (./tx_waveforms --freq 915e6 --rate 5e6 --gain 0) command is given below: wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0 Creating the usrp device with: ... [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-g13c32cef [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 0.000000 dB... Actual TX Gain: 0.000000 dB... Setting device timestamp to 0... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_waveforms.cpp:213 Can you please tell me how can I fix it? Thanks in advance Farah ________________________________ From: Neel Pandeya <nee...@et...> Sent: Tuesday, May 29, 2018 4:11 PM To: Ferdaus, Farah Cc: ope...@li... Subject: Re: [Openbts-discuss] Suggestion regarding installation failure Hello Farah: Attached are some instructions for installing OpenBTS. Be sure to install UHD first, before installing OpenBTS. I would suggest using UHD version 3.10.3.0. https://kb.ettus.com/Building_and_Installing_the_USRP_Open-Source_Toolchain_(UHD_and_GNU_Radio)_on_Linux<https://urldefense.proofpoint.com/v2/url?u=https-3A__kb.ettus.com_Building-5Fand-5FInstalling-5Fthe-5FUSRP-5FOpen-2DSource-5FToolchain-5F-28UHD-5Fand-5FGNU-5FRadio-29-5Fon-5FLinux&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=BRzneEEUGWi64F_I8eRIoWLiAWiInpJj4ZAe12ZTG5A&e=> --Neel Pandeya On 20 May 2018 at 14:30, Ferdaus, Farah <ff...@wi...<mailto:ff...@wi...>> wrote: Hi there, I am trying to install openbts following the steps mentioned here<https://urldefense.proofpoint.com/v2/url?u=http-3A__openbts.org_w_index.php-3Ftitle-3DBuildInstallRun&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=9xLQ3CRyUZWRwgRApGryyh9x9_Mu-vygtrpL6mn_-ng&e=>. I am using ubuntu 16.04 LTS and ettus UERP N210. Every time I am running the command (./build.sh N210) I am getting an error. Below is the list of errors that I have found. By selecting (./switchto.sh master) branch and after running the command (./build.sh N210) Error log shows the following: 2018-05-20T10:59:59\" -MT UHDDevice.lo -MD -MP -MF .deps/UHDDevice.Tpo -c UHDDevice.cpp -fPIC -DPIC -o .libs/UHDDevice.o UHDDevice.cpp:29:29: fatal error: uhd/utils/msg.hpp: No such file or directory compilation terminated. Makefile:665: recipe for target 'UHDDevice.lo' failed make[3]: *** [UHDDevice.lo] Error 1 make[3]: Leaving directory '/home/wslopenbts/dev/openbts/Transceiver52M' Makefile:572: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/wslopenbts/dev/openbts' Makefile:503: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/wslopenbts/dev/openbts' debian/rules:74: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! While I was searching, I have found someone had the same issue and he used (./switchto.sh 5.0) to fix the issue. I also tried to do so but got this error. wslopenbts@wslopenbts-Inspiron-560:~/dev$ ./build.sh N210 # checking for a supported radio type # - found # checking for a compatible build host # - fully supported host detected: Ubuntu 16.04 # # adding additional repo tools # - done # checking build dependencies # - done # make a home for this build mkdir -p BUILDS/2018-05-20--13-23-20 # libcoredumper - building Debian package and installing as dependency cd libcoredumper ./build.sh wget http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com_files_coredumper-2D1.2.1.tar.gz&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=yrCbKCc0RMIFSP6hPeAGrb3WDbmljm8h1PcaG52nrkc&e=> --2018-05-20 13:23:20-- http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com_files_coredumper-2D1.2.1.tar.gz&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=yrCbKCc0RMIFSP6hPeAGrb3WDbmljm8h1PcaG52nrkc&e=> Resolving google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=> (google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=>)... 209.85.232.82, 2607:f8b0:400d:c08::52 Connecting to google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=> (google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=>)|209.85.232.82|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2018-05-20 13:23:20 ERROR 404: Not Found. ERROR: command failed! # ERROR: command failed! Then I have tried different way by selecting (./switchto.sh 4.0) branch and after running the command (./build.sh N210) Error log shows the following: END failed--call queue aborted at /usr/bin/dh_installdirs line 243. debian/rules:69: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! By selecting (./switchto.sh v4.0.0) branch and after running the command (./build.sh N210) Error log shows the following: END failed--call queue aborted at /usr/bin/dh_installdirs line 243. debian/rules:69: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! Can anyone please help me to fix the issue. Thanks in advance. Farah ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot<https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=Irwm5saT82eLxZxwswG9s584es04OnAsUMv4e_lHG2g&e=> _______________________________________________ Openbts-discuss mailing list Ope...@li...<mailto:Ope...@li...> https://lists.sourceforge.net/lists/listinfo/openbts-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_openbts-2Ddiscuss&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=ehQN_0YOpba66Xn0fy2ZlPYGl2jYB-YvpVgR9XROdLQ&e=> |
From: Ferdaus, F. <ff...@wi...> - 2018-05-29 22:21:18
|
Dear Neel, Thank you for your kind reply. Yes, after installing UHD version 3.10.3.0, I am able to install OpenBTS. But while I have tried to verify the Operation of the USRP Using UHD and GNURadio following the instruction mentioned here. I have got some error messages in two commands. Running this (./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat) command, showed the following error. wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.003.HEAD-0-gef157678 Creating the usrp device with: ... -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 10.000000 dB... Actual TX Gain: 10.000000 dB... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int _main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_samples_from_file.cpp:169 The output with error of this (./tx_waveforms --freq 915e6 --rate 5e6 --gain 0) command is given below: wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0 linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.003.HEAD-0-gef157678 Creating the usrp device with: ... -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 0.000000 dB... Actual TX Gain: 0.000000 dB... Setting device timestamp to 0... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int _main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_waveforms.cpp:221 Can you please tell me how can I fix it? Thanks in advance Farah ________________________________ From: Ferdaus, Farah Sent: Tuesday, May 29, 2018 6:00:46 PM To: Neel Pandeya Cc: ope...@li... Subject: Re: [Openbts-discuss] Suggestion regarding installation failure Dear Neel, Thank you for your kind reply. Yes, after installing UHD version 3.10.3.0, I am able to install OpenBTS. But while I have tried to verify the Operation of the USRP Using UHD and GNURadio following the instruction mentioned here<https://kb.ettus.com/Verifying_the_Operation_of_the_USRP_Using_UHD_and_GNU_Radio>. I have got some error messages in two commands. Running this (./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat) command, showed the following error. wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_samples_from_file --freq 915e6 --rate 5e6 --gain 10 usrp_samples.dat Creating the usrp device with: ... [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-g13c32cef [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 10.000000 dB... Actual TX Gain: 10.000000 dB... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_samples_from_file.cpp:161 The output with error of this (./tx_waveforms --freq 915e6 --rate 5e6 --gain 0) command is given below: wslopenbts@wslopenbts-Inspiron-560:/usr/local/lib/uhd/examples$ ./tx_waveforms --freq 915e6 --rate 5e6 --gain 0 Creating the usrp device with: ... [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.HEAD-0-g13c32cef [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes Using Device: Single USRP: Device: USRP2 / N-Series Device Mboard 0: N210r4 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: WBXv4 RX+GDB TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: WBXv4 TX+GDB Setting TX Rate: 5.000000 Msps... Actual TX Rate: 5.000000 Msps... Setting TX Freq: 915.000000 MHz... Actual TX Freq: 915.000000 MHz... Setting TX Gain: 0.000000 dB... Actual TX Gain: 0.000000 dB... Setting device timestamp to 0... Checking TX: LO: unlocked ... Error: AssertionError: lo_locked.to_bool() in int main(int, char**) at /home/wslopenbts/workarea-uhd/uhd/host/examples/tx_waveforms.cpp:213 Can you please tell me how can I fix it? Thanks in advance Farah ________________________________ From: Neel Pandeya <nee...@et...> Sent: Tuesday, May 29, 2018 4:11 PM To: Ferdaus, Farah Cc: ope...@li... Subject: Re: [Openbts-discuss] Suggestion regarding installation failure Hello Farah: Attached are some instructions for installing OpenBTS. Be sure to install UHD first, before installing OpenBTS. I would suggest using UHD version 3.10.3.0. https://kb.ettus.com/Building_and_Installing_the_USRP_Open-Source_Toolchain_(UHD_and_GNU_Radio)_on_Linux<https://urldefense.proofpoint.com/v2/url?u=https-3A__kb.ettus.com_Building-5Fand-5FInstalling-5Fthe-5FUSRP-5FOpen-2DSource-5FToolchain-5F-28UHD-5Fand-5FGNU-5FRadio-29-5Fon-5FLinux&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=BRzneEEUGWi64F_I8eRIoWLiAWiInpJj4ZAe12ZTG5A&e=> --Neel Pandeya On 20 May 2018 at 14:30, Ferdaus, Farah <ff...@wi...<mailto:ff...@wi...>> wrote: Hi there, I am trying to install openbts following the steps mentioned here<https://urldefense.proofpoint.com/v2/url?u=http-3A__openbts.org_w_index.php-3Ftitle-3DBuildInstallRun&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=9xLQ3CRyUZWRwgRApGryyh9x9_Mu-vygtrpL6mn_-ng&e=>. I am using ubuntu 16.04 LTS and ettus UERP N210. Every time I am running the command (./build.sh N210) I am getting an error. Below is the list of errors that I have found. By selecting (./switchto.sh master) branch and after running the command (./build.sh N210) Error log shows the following: 2018-05-20T10:59:59\" -MT UHDDevice.lo -MD -MP -MF .deps/UHDDevice.Tpo -c UHDDevice.cpp -fPIC -DPIC -o .libs/UHDDevice.o UHDDevice.cpp:29:29: fatal error: uhd/utils/msg.hpp: No such file or directory compilation terminated. Makefile:665: recipe for target 'UHDDevice.lo' failed make[3]: *** [UHDDevice.lo] Error 1 make[3]: Leaving directory '/home/wslopenbts/dev/openbts/Transceiver52M' Makefile:572: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/wslopenbts/dev/openbts' Makefile:503: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/wslopenbts/dev/openbts' debian/rules:74: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! While I was searching, I have found someone had the same issue and he used (./switchto.sh 5.0) to fix the issue. I also tried to do so but got this error. wslopenbts@wslopenbts-Inspiron-560:~/dev$ ./build.sh N210 # checking for a supported radio type # - found # checking for a compatible build host # - fully supported host detected: Ubuntu 16.04 # # adding additional repo tools # - done # checking build dependencies # - done # make a home for this build mkdir -p BUILDS/2018-05-20--13-23-20 # libcoredumper - building Debian package and installing as dependency cd libcoredumper ./build.sh wget http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com_files_coredumper-2D1.2.1.tar.gz&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=yrCbKCc0RMIFSP6hPeAGrb3WDbmljm8h1PcaG52nrkc&e=> --2018-05-20 13:23:20-- http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com_files_coredumper-2D1.2.1.tar.gz&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=yrCbKCc0RMIFSP6hPeAGrb3WDbmljm8h1PcaG52nrkc&e=> Resolving google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=> (google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=>)... 209.85.232.82, 2607:f8b0:400d:c08::52 Connecting to google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=> (google-coredumper.googlecode.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__google-2Dcoredumper.googlecode.com&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=zORPmktihg_FBl_D6BFs2_1H9vwOMB3msVnWsj7hCLE&e=>)|209.85.232.82|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2018-05-20 13:23:20 ERROR 404: Not Found. ERROR: command failed! # ERROR: command failed! Then I have tried different way by selecting (./switchto.sh 4.0) branch and after running the command (./build.sh N210) Error log shows the following: END failed--call queue aborted at /usr/bin/dh_installdirs line 243. debian/rules:69: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! By selecting (./switchto.sh v4.0.0) branch and after running the command (./build.sh N210) Error log shows the following: END failed--call queue aborted at /usr/bin/dh_installdirs line 243. debian/rules:69: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! Can anyone please help me to fix the issue. Thanks in advance. Farah ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot<https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=Irwm5saT82eLxZxwswG9s584es04OnAsUMv4e_lHG2g&e=> _______________________________________________ Openbts-discuss mailing list Ope...@li...<mailto:Ope...@li...> https://lists.sourceforge.net/lists/listinfo/openbts-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_openbts-2Ddiscuss&d=DwMFaQ&c=c6MrceVCY5m5A_KAUkrdoA&r=_2fcgDL48JH6xH97k8QTr5xs5ua5oLdreTU-ysnT2Zw&m=yQUyQJoI49pBZ21Zod6pEu6p_-s3_tqeIBWJUeVTeUk&s=ehQN_0YOpba66Xn0fy2ZlPYGl2jYB-YvpVgR9XROdLQ&e=> |
From: Neel P. <nee...@et...> - 2018-05-29 20:42:11
|
Hello Farah: Attached are some instructions for installing OpenBTS. Be sure to install UHD first, before installing OpenBTS. I would suggest using UHD version 3.10.3.0. https://kb.ettus.com/Building_and_Installing_the_USRP_Open-Source_Toolchain_(UHD_and_GNU_Radio)_on_Linux --Neel Pandeya On 20 May 2018 at 14:30, Ferdaus, Farah <ff...@wi...> wrote: > Hi there, > I am trying to install openbts following the steps mentioned here > <http://openbts.org/w/index.php?title=BuildInstallRun>. I am using ubuntu > 16.04 LTS and ettus UERP N210. Every time I am running the command (*./build.sh > N210*) I am getting an error. Below is the list of errors that I have > found. > > By selecting (*./switchto.sh master*) branch and after running the > command (./build.sh N210) Error log shows the following: > > *2018-05-20T10:59:59\" -MT UHDDevice.lo -MD -MP -MF .deps/UHDDevice.Tpo -c > UHDDevice.cpp -fPIC -DPIC -o .libs/UHDDevice.o* > *UHDDevice.cpp:29:29: fatal error: uhd/utils/msg.hpp: No such file or > directory* > *compilation terminated.* > *Makefile:665: recipe for target 'UHDDevice.lo' failed* > *make[3]: *** [UHDDevice.lo] Error 1* > *make[3]: Leaving directory '/home/wslopenbts/dev/openbts/Transceiver52M'* > *Makefile:572: recipe for target 'all-recursive' failed* > *make[2]: *** [all-recursive] Error 1* > *make[2]: Leaving directory '/home/wslopenbts/dev/openbts'* > *Makefile:503: recipe for target 'all' failed* > *make[1]: *** [all] Error 2* > *make[1]: Leaving directory '/home/wslopenbts/dev/openbts'* > *debian/rules:74: recipe for target 'install-arch' failed* > *make: *** [install-arch] Error 2* > *dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit > status 2* > *# ERROR: command failed!* > > While I was searching, I have found someone had the same issue and he used > (*./switchto.sh 5.0*) to fix the issue. I also tried to do so but got > this error. > > w*slopenbts@wslopenbts-Inspiron-560:~/dev$ ./build.sh N210* > *# checking for a supported radio type* > *# - found* > *# checking for a compatible build host* > *# - fully supported host detected: Ubuntu 16.04* > *#* > *# adding additional repo tools* > *# - done* > > *# checking build dependencies* > *# - done* > > *# make a home for this build* > *mkdir -p BUILDS/2018-05-20--13-23-20* > *# libcoredumper - building Debian package and installing as dependency* > *cd libcoredumper* > *./build.sh* > *wget > http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz > <http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz>* > *--2018-05-20 13:23:20-- > http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz > <http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz>* > *Resolving google-coredumper.googlecode.com > <http://google-coredumper.googlecode.com> (google-coredumper.googlecode.com > <http://google-coredumper.googlecode.com>)... 209.85.232.82, > 2607:f8b0:400d:c08::52* > *Connecting to google-coredumper.googlecode.com > <http://google-coredumper.googlecode.com> (google-coredumper.googlecode.com > <http://google-coredumper.googlecode.com>)|209.85.232.82|:80... connected.* > *HTTP request sent, awaiting response... 404 Not Found* > *2018-05-20 13:23:20 ERROR 404: Not Found.* > > *ERROR: command failed!* > *# ERROR: command failed!* > > Then I have tried different way by selecting (*./switchto.sh 4.0*) branch > and after running the command (./build.sh N210) Error log shows the > following: > > *END failed--call queue aborted at /usr/bin/dh_installdirs line 243.* > *debian/rules:69: recipe for target 'install-arch' failed* > *make: *** [install-arch] Error 2* > *dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit > status 2* > *# ERROR: command failed!* > > By selecting (*./switchto.sh v4.0.0*) branch and after running the > command (./build.sh N210) Error log shows the following: > > > * END failed--call queue aborted at /usr/bin/dh_installdirs line 243. > debian/rules:69: recipe for target 'install-arch' failed make: *** > [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules > binary gave error exit status 2 # ERROR: command failed! * > Can anyone please help me to fix the issue. > > Thanks in advance. > Farah > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openbts-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > |
From: Amirhosein n. <ami...@ya...> - 2018-05-26 12:21:35
|
Hi everybody, In OpenBTS how can I reject mobile phones that are connected already ?Is there any command or something else ? Tnx |
From: oscar l. <osc...@gm...> - 2018-05-21 09:31:13
|
Hi everyone On the following OpenBTS parameter: OpenBTS> devconfig GSM.Radio.RSSITarget GSM.Radio.RSSITarget -50 [default] - description: Target uplink RSSI (Received Signal Strength Indication) for MS power control loop, in dB wrt to A/D full scale. The description indicates that the RSSI value is minus 50 dB with respect to the A/D full scale. Now, according to Ettus on link [1] the USRP B210 has a maximum input power of 0 dBm, although other sources [2] state that maximum input power is -15dBm. In this case, which dBm power level will mean the term "with respect to A/D full scale". Thanks [1] https://kb.ettus.com/B200/B210/B200mini/B205mini [2] https://files.ettus.com/manual/page_usrp_b200.html |
From: Ferdaus, F. <ff...@wi...> - 2018-05-21 00:02:38
|
Hi there, I am trying to install openbts following the steps mentioned here<http://openbts.org/w/index.php?title=BuildInstallRun>. I am using ubuntu 16.04 LTS and ettus UERP N210. Every time I am running the command (./build.sh N210) I am getting an error. Below is the list of errors that I have found. By selecting (./switchto.sh master) branch and after running the command (./build.sh N210) Error log shows the following: 2018-05-20T10:59:59\" -MT UHDDevice.lo -MD -MP -MF .deps/UHDDevice.Tpo -c UHDDevice.cpp -fPIC -DPIC -o .libs/UHDDevice.o UHDDevice.cpp:29:29: fatal error: uhd/utils/msg.hpp: No such file or directory compilation terminated. Makefile:665: recipe for target 'UHDDevice.lo' failed make[3]: *** [UHDDevice.lo] Error 1 make[3]: Leaving directory '/home/wslopenbts/dev/openbts/Transceiver52M' Makefile:572: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/home/wslopenbts/dev/openbts' Makefile:503: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/wslopenbts/dev/openbts' debian/rules:74: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! While I was searching, I have found someone had the same issue and he used (./switchto.sh 5.0) to fix the issue. I also tried to do so but got this error. wslopenbts@wslopenbts-Inspiron-560:~/dev$ ./build.sh N210 # checking for a supported radio type # - found # checking for a compatible build host # - fully supported host detected: Ubuntu 16.04 # # adding additional repo tools # - done # checking build dependencies # - done # make a home for this build mkdir -p BUILDS/2018-05-20--13-23-20 # libcoredumper - building Debian package and installing as dependency cd libcoredumper ./build.sh wget http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz --2018-05-20 13:23:20-- http://google-coredumper.googlecode.com/files/coredumper-1.2.1.tar.gz Resolving google-coredumper.googlecode.com (google-coredumper.googlecode.com)... 209.85.232.82, 2607:f8b0:400d:c08::52 Connecting to google-coredumper.googlecode.com (google-coredumper.googlecode.com)|209.85.232.82|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2018-05-20 13:23:20 ERROR 404: Not Found. ERROR: command failed! # ERROR: command failed! Then I have tried different way by selecting (./switchto.sh 4.0) branch and after running the command (./build.sh N210) Error log shows the following: END failed--call queue aborted at /usr/bin/dh_installdirs line 243. debian/rules:69: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! By selecting (./switchto.sh v4.0.0) branch and after running the command (./build.sh N210) Error log shows the following: END failed--call queue aborted at /usr/bin/dh_installdirs line 243. debian/rules:69: recipe for target 'install-arch' failed make: *** [install-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 # ERROR: command failed! Can anyone please help me to fix the issue. Thanks in advance. Farah |
From: oscar l. <osc...@gm...> - 2018-05-17 09:39:01
|
Hi everyone Right, straight to the poing! Objective: I am looking for a way to measure how much power in dBm is OpenBTS RX Frontend receiving from a certain MS using the MS and/or OpenBTS CLI information, in other words: the RSSI on the uplink signal. My network consists on an OpenBTS implementation using a laptop with OpenBTS + USRP B210 with omnidirectional antennas (Gain=1-3dBi) in 90º degree configuration to minimize interference from Tx on Rx antenna. My handset device is a Lonet SIM808 GPRS module which is Class1 device (max Tx Power = 30dBm). Its TX/RX antenna has a 0dBi gain. SIM808 is able to provide Radio Information through the execution of AT Commands. So after some value interpretation, the RSSI on the Downlink can be known. The distance between the USRP (Base Station) and the Lonet SIM808 (MS) is about 4 m. Though it is susceptible to multipath interference, I effort to create a LOS scenario between Tx and Rx, so the Path Loss calculated can be considered coherent. OpenBTS allows to modify the Base Station (BS) Tx Power with the "power" command on OpenBTS CLI. If power is set to 10, then it prompts a message indicating that: current downlink power is -10 dB with respect to full scale I know that on USRPB210, the max Tx power is 10 dBm. So if OpenBTS power parameter is set to 0, then BS Tx power would be 10 dBm + 3 dBi of Antenna Gain = 13 dBm. To be sure of this I measured the USRP Tx power connecting the Tx port directly to a spectrum analyzer with power parameter set on 0 (cero) and the spectrum analyzer screen showed a signal with its peak close to 10 dBm, I guess some losses are due to the coaxial cable. Therefore, the Path Losses on the DL can be calculated by subtracting the SIM808 RSSI on dBm value minus the BS Tx Power on dBm value. Until now, all of that has been the downlink path. On the Uplink path Lonet SIM808 doesn't provide info about its Tx power and OpenBTS doesn't provide a way to check RSSI levels from the handsets attached. I don't find any radio info on the GPRS timeslots running the "chans -a -l" command on OpenBTS CLI. So one way to figure out the Uplink Channel Radio is to solve the GPRS Uplink Power Control equation which is [1]: Pt = min ( Gamma_0 - Gamma_C - alpha ( C + 48 ) , Pm) On OpenBTS default configuration: * Pt = handset Tx power in dBm * Gamma_0 = 36 dBm for DCS 1800 Band * Gamma_C = 31 (default) * alpha = 10 (default) * C = RSSI on the DL (it does not specify if it is on dBm so I assume it) Now, this GPRS Uplink Power Control algorithm on the BS sets the handset Tx Power, so the RSSI on the Uplink, in other words: the power level received by the BS from the handset is above the "GSM.Radio.RSSITarget" which is an OpenBTS parameter. The definition of the "GSM.Radio.RSSITarget" parameter is: OpenBTS> devconfig GSM.Radio.RSSITarget GSM.Radio.RSSITarget -65 - description: Target uplink RSSI (Received Signal Strength Indication) for MS power control loop, in dB wrt to A/D full scale. The MS power control loop adjusts MS TXPWR (transmit power) to try to keep RSSI at this level, or to satisfy GSM.Radio.SNRTarget, whichever requires more power. Should be 6-10 dB above the noise floor. - units: dB - type: value range - default value: -50 - visibility level: customer tune - should only be changed to tune an installation to better suit the physical environment or MS usage pattern - static: 0 - valid values: from -75 to -25 I am sorry to have bother you with all this but I don't understand what means: "... in dB wrt to A/D full scale" on the GSM.Radio.RSSITarget description. My questions are: * What means A/D full scale in terms of dBm? I thought that Target Uplink RSSI was -65dBm but that "wrt to A/D full" term makes me think that it is -65dB with respect the absolute USRP B210 Rx sensitivity * If Uplink RSSI is known then I will use DL Path Loss as the UL Path Loss to calculate how much Tx Power the handset is sending, so a Link Budget can be figure out. Anyone considers another point of view? References: [1]: http://openbts.org/site/wp-content/uploads/2014/07/OpenBTS-4.0-Manual.pdf Page = 82/83 http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2015-January/012209.html Oscar Llerena Tlf: 997575596 |
From: Vincent H. <vin...@gm...> - 2018-05-15 04:54:20
|
Hello, I read somewhere (I don't remember where) that it was possible to detect the mobile network signal even if there is no antenna connected on the RangeNetwork hardware. What do you think ? Is there any risk for the hardware ? The different power (attenuation, output) are very very slow. Thank you, Vincent. |
From: Siavash A. <201...@gm...> - 2018-05-12 09:25:21
|
Hi, May someone help me how to enable RRLP support in openbts? BR Siavash |
From: bala e. <bal...@gm...> - 2018-05-09 06:07:06
|
Dear All, Any one can help me with the followings. 1. In Open BTS, how timing advance calculation is performed ? 2. How OpenBTS is synchronizing in the uplink side to receive the access burst at a proper time? 3. Where is the source file, where actual timing advance calculation is happening in the git repository? Thanks Balaji D |
From: Dang K. P. <Dan...@ni...> - 2018-05-02 05:58:54
|
Hi, I installed OpenBTS using the master branch on Ubuntu Desktop 16.04 and set up a multi-BTS configuration with 2 towers and 1 central-services PC. I used two N210s (USRP-2920) with externally supplied OCXO 10 MHz Ref Clock. It looks like everything works fine except that it could not handover active call. I received the handover failure cause 0x4 in the log file. "Apr 27 11:30:53 openbts-tower-2 openbts: NOTICE 14635:14718 2018-04-27T11:30:53.0 L3Handover.cpp:338:outboundHandoverTransfer: failed handover, C0T1 TCH/F state=Established received L3Frame( Primitive=L3_DATA Sapi=SAPI0 PD=Radio Resource MTI=0x28(Handover Failure) TI=0 raw=(062804))RR Handover Failure cause=0x4" Sometimes I got handover failure cause 0x3, as seen in the log file below. "Apr 27 11:44:40 openbts-tower-2 openbts: NOTICE 15402:15478 2018-04-27T11:44:40.3 L3Handover.cpp:338:outboundHandoverTransfer: failed handover, C0T2 TCH/F state=Established received L3Frame( Primitive=L3_DATA Sapi=SAPI0 PD=Radio Resource MTI=0x28(Handover Failure) TI=0 raw=(062803))RR Handover Failure cause=0x3" I set GSM.Handover.Margin = 10 on both towers and have confirmed that power difference was greater than 10 dB when I received the above mentioned handover failures. Does anyone have any idea what causes that? Thanks and best regards, Pham Dang Khoa Application Engineering Specialist (RF) National Instruments |
From: <Sep...@gm...> - 2018-04-27 08:14:36
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> </div> <div class="signature"> <p>Hi,</p> <p> </p> <p>I would like to know if there is any possibility to get the adalm-pluto sdr to work with openbts.</p> <p><a href="http://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/adalm-pluto.html#eb-overview">http://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/adalm-pluto.html#eb-overview</a></p> <p> </p> <p>Its a cheap little sdr which seems to fullfill the technical requirements (full duplex, 75MHz - 6GHz (with a little hack), etc).</p> <p> </p> <p>Thanks in advance for your answers.</p> </div></div></body></html> |
From: Keval P. <kev...@gm...> - 2018-04-18 04:47:45
|
Hello , I would like to know that Is Commercial OpenBTS support all traffic channels according to ETSI 145 003 v13.1.0 ? Following traffic channels are there in the Specifications. 1) TCH/FS 2) TCH/EFS 3) TCH/HS 4) TCH/F9.6 5) TCH/F4.8 6) TCH/H4.8 7) TCH/F2.4 8) TCH/H2.4 9) TCH/F14.4 10) TCH/AFS 11) TCH/AHS 12) TCH/WFS 13) O-TCH/AHS 14) O-TCH/WFS 15) O-TCH/WHS 16) E-TCH/F28.8 17) E-TCH/F32.0 18) E-TCH/F43.2 |
From: Antony L. <an...@fu...> - 2018-04-16 14:33:18
|
Hello folks, My setup : - Code from tag v4.0.0. - I have followed the install guide ( http://openbts.org/w/index.php?title=BuildInstallRun), setup OpenBTS with "config Control.LUR.OpenRegistration .*". - The transceiver is connected to a Fairwaves UmTRX v2.3.1 board and the spectrometer "says" that everything is OK. - I have started "smqueue" and "sipauthserve", but not "asterisk" because our current target is only sending SMS. What works : - My phone detects correctly the LAC and CID that I have configured (also I have taken the MCC and MNC of my operator just to be sure my SIM is happy) - My phone receives SMSCB messages. What does not works : - I don't receives the "Welcome SMS" from 101. - I know the IMSI of my phone/SIM and I try to send a SMS (via OpenBTSCLI sendsms or sendsimple) but I don't receive anything. Do anybody have some clue where to look at? Have a nice day, Antony |