openBTS
-
- Posts: 33
- Joined: Thu Jul 18, 2013 6:14 am
Re: openBTS
ah its /var/run/TMSITable.db by default. Too many parameters in openbts.db!
Thanks for your help.
You mentions that yate worked, did YateBTS work on the up and downlink?
Thanks for your help.
You mentions that yate worked, did YateBTS work on the up and downlink?
-
- Posts: 70
- Joined: Fri Mar 01, 2013 3:23 am
Re: openBTS
Ahh, we must not mix up things 
I am only using yate as a SIP PABX, not the yatebts project. I have one virtual machine with a normal OpenBTS setup together with libusrp and a USRP1 radio, and another VM with OpenBTS and a rangenetworks RAD1 radio. Both with identical config, both with OpenBTS in its original version and yate as switch. On this second VM I installed this nuand OpenBTS version into a second directory, and only this one does not work.
Yate only is responsible for phone calls, phones of course do register with or without yate.
So it clearly has to do something with the bladeRF radio, other radios do their job fine, I can use them like normal public GSM BTSs.
Nuand calls us to test OpenBTS, but where is the channel to exchange experiences, if not here?

I am only using yate as a SIP PABX, not the yatebts project. I have one virtual machine with a normal OpenBTS setup together with libusrp and a USRP1 radio, and another VM with OpenBTS and a rangenetworks RAD1 radio. Both with identical config, both with OpenBTS in its original version and yate as switch. On this second VM I installed this nuand OpenBTS version into a second directory, and only this one does not work.
Yate only is responsible for phone calls, phones of course do register with or without yate.
So it clearly has to do something with the bladeRF radio, other radios do their job fine, I can use them like normal public GSM BTSs.
Nuand calls us to test OpenBTS, but where is the channel to exchange experiences, if not here?

-
- Posts: 11
- Joined: Tue Feb 04, 2014 2:43 pm
Re: openBTS
Hello,
When I start the OpenBTS (sudo ./OpenBTS) i got the following output:
1395786852.767746 3074549504:
Starting the system...
ALERT 3074549504 23:34:17.7 TRXManager.cpp:434:powerOff: POWEROFF failed with status -1
Using internal clock reference
EMERG 3074316032 23:34:18.2 bladeRFDevice.cpp
open: bladeRF transceiver only supports SuperSpeed mode at the moment
ALERT 3074316032 23:34:18.2 runTransceiver.cpp:160:main: Transceiver exiting...
EMERG 3073973056 23:34:18.2 OpenBTS.cpp:156:startTransceiver: Transceiver quit with status 256. Exiting.
Do you know what could be the problem?
The printout of the version command in bladeRF-cli -i is :
bladeRF> version
bladeRF-cli version: 0.10.7-git-b876a96-ppasaucy
libbladeRF version: 0.14.0-git-b876a96-ppasaucy
Firmware version: 1.6.1-git-b7e6642
FPGA version: 0.0.3
I'm loading the fpga with /openbts/trunk/Transceiver52M/hostedx40bts.rbf
Any help apprecated!
With Best Regards,
Blagoja
When I start the OpenBTS (sudo ./OpenBTS) i got the following output:
1395786852.767746 3074549504:
Starting the system...
ALERT 3074549504 23:34:17.7 TRXManager.cpp:434:powerOff: POWEROFF failed with status -1
Using internal clock reference
EMERG 3074316032 23:34:18.2 bladeRFDevice.cpp
ALERT 3074316032 23:34:18.2 runTransceiver.cpp:160:main: Transceiver exiting...
EMERG 3073973056 23:34:18.2 OpenBTS.cpp:156:startTransceiver: Transceiver quit with status 256. Exiting.
Do you know what could be the problem?
The printout of the version command in bladeRF-cli -i is :
bladeRF> version
bladeRF-cli version: 0.10.7-git-b876a96-ppasaucy
libbladeRF version: 0.14.0-git-b876a96-ppasaucy
Firmware version: 1.6.1-git-b7e6642
FPGA version: 0.0.3
I'm loading the fpga with /openbts/trunk/Transceiver52M/hostedx40bts.rbf
Any help apprecated!
With Best Regards,
Blagoja
-
- Posts: 70
- Joined: Fri Mar 01, 2013 3:23 am
Re: openBTS
Look at this:
>EMERG 3074316032 23:34:18.2 bladeRFDevice.cpp
open: bladeRF transceiver only supports SuperSpeed mode at the moment
Obviously you do not have an USB3.0 or port, or the USB3.0 connection is not functioning properly...
Ralph.
>EMERG 3074316032 23:34:18.2 bladeRFDevice.cpp
Obviously you do not have an USB3.0 or port, or the USB3.0 connection is not functioning properly...
Ralph.
-
- Posts: 11
- Joined: Tue Feb 04, 2014 2:43 pm
Re: openBTS
Yes I don't have USB 3.0 port on my Laptop.
I didn't know that USB 3.0 port is a requirement for the OpenBTS.
Thanks for the provided info.
I have found info regarding the OpenBTS, bladeRF and USB 3.0 here:
https://github.com/Nuand/bladeRF/issues/227
junik wrote:
"The bladeRF functions on USB 2.0 and USB 3.0; I'm not sure what's going on in the OpenBTS code that requires this restriction. If I had to guess, I would expect it to have something to do with some buffers being tailored to the USB SuperSpeed MaxPacketSize of 1024 bytes, as opposed to the USB Hi-Speed MaxPacketSize of 512 bytes... don't quote me on that though."
I didn't know that USB 3.0 port is a requirement for the OpenBTS.
Thanks for the provided info.
I have found info regarding the OpenBTS, bladeRF and USB 3.0 here:
https://github.com/Nuand/bladeRF/issues/227
junik wrote:
"The bladeRF functions on USB 2.0 and USB 3.0; I'm not sure what's going on in the OpenBTS code that requires this restriction. If I had to guess, I would expect it to have something to do with some buffers being tailored to the USB SuperSpeed MaxPacketSize of 1024 bytes, as opposed to the USB Hi-Speed MaxPacketSize of 512 bytes... don't quote me on that though."
-
- Posts: 15
- Joined: Fri Mar 01, 2013 11:28 am
Re: openBTS
Iam runing OpenBTS
tell me why?
Code: Select all
[ERROR] Failed to access peripheral: LIBUSB_ERROR_NO_DEVICE
[ERROR] Failed to access peripheral: LIBUSB_ERROR_NO_DEVICE
[ERROR] Failed to access peripheral: LIBUSB_ERROR_NO_DEVICE
[ERROR] Failed to access peripheral: LIBUSB_ERROR_NO_DEVICE
[ERROR] Failed to access peripheral: LIBUSB_ERROR_NO_DEVICE
[ERROR] Failed to access peripheral: LIBUSB_ERROR_NO_DEVICE
1396338345.637254 140253908068160:
use the OpenBTSCLI utility to access CLI
EMERG 140253906519808 11:46:55.6 TRXManager.cpp:102:clockHandler: TRX clock interface timed out, assuming TRX is dead.
Code: Select all
bladeRF> version
bladeRF-cli version: 0.10.7-git-5af73b8
libbladeRF version: 0.14.0-git-5af73b8
Firmware version: 1.6.1-git-b7e6642
FPGA version: 0.0.3
-
- Posts: 33
- Joined: Thu Jul 18, 2013 6:14 am
Re: openBTS
Just make sure you have libusb installed with this;
sudo apt-get install libusb-1.0-0-dev libusb-1.0.0
(I am assuming you are running this on a Linux based OS)
sudo apt-get install libusb-1.0-0-dev libusb-1.0.0
(I am assuming you are running this on a Linux based OS)
-
- Posts: 15
- Joined: Fri Mar 01, 2013 11:28 am
Re: openBTS
install
libusb-1.0-0.
libusb-1.0-0-dbg.
libusb-1.0-0-dev.
libusb-1.0-0.
libusb-1.0-0-dbg.
libusb-1.0-0-dev.
Code: Select all
use the OpenBTSCLI utility to access CLI
[ERROR] Failed to access peripheral: LIBUSB_ERROR_TIMEOUT
[ERROR] Failed to access peripheral: LIBUSB_ERROR_TIMEOUT
[ERROR] Failed to access peripheral: LIBUSB_ERROR_TIMEOUT
[ERROR] Failed to access peripheral: LIBUSB_ERROR_TIMEOUT
[ERROR] Failed to access peripheral: LIBUSB_ERROR_TIMEOUT
transceiver: /home/veranson/bladeRF/host/libraries/libbladeRF/src/backend/libusb.c:2064: submit_transfer: Assertion `stream_data->transfer_status[stream_data->i] == TRANSFER_AVAIL' failed.
EMERG 140208831444736 13:00:55.2 OpenBTS.cpp:156:startTransceiver: Transceiver quit with status 134. Exiting.
DatagramSocket::read() failed: Bad file descriptor
-
- Posts: 15
- Joined: Fri Mar 01, 2013 11:28 am
Re: openBTS
strange. There is a suspicion that the fault controller usb 3.0 (Express card 54)
Taken another system with usb 3.0 controller NEC D720200F1 all is well and there are no problems
Taken another system with usb 3.0 controller NEC D720200F1 all is well and there are no problems
-
- Posts: 70
- Joined: Fri Mar 01, 2013 3:23 am
Re: openBTS
Last changes to bladeRF did not change anything regarding non-working OpenBTS, but broke gqrx usage and maybe other stuff
See my other topic...
Ralph.

Ralph.
-
- Posts: 9
- Joined: Sat Mar 01, 2014 7:36 pm
Re: openBTS
Did anybody get it working ?
Compiling and installing went like a charm...I see my GSM network on my phone but can't log in...
Tried several arfcn's...nope...
As for legal issues...working with a dummy load
Compiling and installing went like a charm...I see my GSM network on my phone but can't log in...
Tried several arfcn's...nope...

As for legal issues...working with a dummy load

-
- Posts: 9
- Joined: Sat Mar 01, 2014 7:36 pm
Re: openBTS
I did follow this "tutorial" but got some strange noise figures...( http://code.google.com/p/umtrx/wiki/RunningOpenBTS )
-
- Posts: 1
- Joined: Tue Feb 25, 2014 8:04 pm
Re: openBTS
I have the same problem.
Like can't solve this problem.
Code: Select all
OpenBTS> EMERG 3271:3278 2014/04/14 20:25:27.3 TRXManager.cpp:101:clockHandler: TRX clock interface timed out, assuming TRX is dead.
Aborted (core dumped)
-
- Posts: 15
- Joined: Fri Mar 01, 2013 11:28 am
Re: openBTS
https://github.com/Nuand/dev
Code: Select all
git clone https://github.com/Nuand/dev
Cloning into 'dev'...
remote: Counting objects: 134, done.
remote: Compressing objects: 100% (47/47), done.
remote: Total 134 (delta 87), reused 134 (delta 87)
Receiving objects: 100% (134/134), 38.00 KiB | 0 bytes/s, done.
Resolving deltas: 100% (87/87), done.
Checking connectivity... done
veranson@veranson-VirtualBox:~$ cd dev/
veranson@veranson-VirtualBox:~/dev$ ./clone.sh
# cloning asterisk from RangeNetworks
git clone [email protected]:RangeNetworks/asterisk.git
Cloning into 'asterisk'...
The authenticity of host 'github.com (192.30.252.129)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,192.30.252.129' (RSA) to the list of known hosts.
[b]Permission denied (publickey).[/b]
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
# ERROR: command failed!
veranson@veranson-VirtualBox:~/dev$
-
- Posts: 11
- Joined: Tue Feb 04, 2014 2:43 pm
Re: openBTS
Hi,
I have the same problem while clonning.
The solution is presented on this page: https://help.github.com/articles/generating-ssh-keys
BR,
Blagoja
I have the same problem while clonning.
The solution is presented on this page: https://help.github.com/articles/generating-ssh-keys
BR,
Blagoja