Page 2 of 3

Re: OpenBTS

Posted: Sat Sep 28, 2013 8:40 am
by bpadalino
Yes - I'm talking with the osmocom folks mostly on a daily basis to try to build in support. Slowly but surely we will get there. The software is full duplex and requires the timestamps to ensure the software can recover in the case of an underflow on the transmit side.

I have had a thought of trying to fake that part out for now, just to see if I could get it working but other developments have so far stopped me.

Getting a GSM basestation solution running out of the box is extremely important to us and is our top priority after getting the software platforms stable.

Re: OpenBTS

Posted: Mon Sep 30, 2013 2:51 pm
by bnt2025
That's good news then. Is there anything I can help with?
I don't really have any experience in C++. Is there any indications on how long it will take?

Thanks
Ash

Re: OpenBTS

Posted: Thu Nov 07, 2013 11:21 pm
by dk5ras
Any news regarding OpenBTS? I'd be happy to test it if there already some pre version has been built...

Ralph.

Re: OpenBTS

Posted: Sun Nov 24, 2013 5:01 pm
by bpadalino
New FPGA code has been written which is a refactoring of what was currently in there. I like it better.

We're implementing the VRT/timestamps right now. We are targeting the end of December for timestamping working completely and OpenBTS being able to use them at that same time.

Sorry for the long delay. Things should hopefully be better during the winter and with all the holidays.

Re: OpenBTS

Posted: Sun Dec 01, 2013 12:50 pm
by dk5ras
Great, looking forward to this!

Will it be integrated into the normal public repo at rangenetworks, or is some special BladeRF-OpenBTS fork established?

Ralph.

Re: OpenBTS

Posted: Sun Dec 01, 2013 4:01 pm
by bnt2025
Would the same also apply to OpenBSC? Really looking forward to this!

Many thanks
Bnt2025

Re: OpenBTS

Posted: Sat Dec 21, 2013 8:51 am
by bpadalino
I am not awfully familiar with OpenBSC but it seems like it needs some timestamping capabilities as well. I will try to clear it up with the Osmo folks as to what they need for that, but I would imagine whatever OpenBTS needs this would be able to leverage as well.

Re: OpenBTS

Posted: Tue Dec 24, 2013 4:34 pm
by Montezuma
bpadalino wrote:I am not awfully familiar with OpenBSC but it seems like it needs some timestamping capabilities as well. I will try to clear it up with the Osmo folks as to what they need for that, but I would imagine whatever OpenBTS needs this would be able to leverage as well.
A BSC is a parent to multiple BTSs. So, with open BSC, people can setup more complicated cellular networks.

Re: OpenBTS

Posted: Fri Jan 03, 2014 5:28 am
by bnt2025
Hello,

the board has been pretty quiet on this front recently. How is the development going?

Many thanks

Re: OpenBTS

Posted: Mon Jan 06, 2014 2:41 am
by dk5ras
Have a look here:

http://www.nuand.com/blog/

Ralph.

Re: OpenBTS

Posted: Thu Jan 30, 2014 1:25 am
by veranson
More on this, and full instructions for OpenBTS in early January.
Any news?

Re: OpenBTS

Posted: Tue Feb 04, 2014 11:00 am
by bnt2025
veranson wrote:
More on this, and full instructions for OpenBTS in early January.
Any news?
Seconded, are their any instructions yet?

Re: OpenBTS

Posted: Thu Feb 13, 2014 12:41 pm
by bnt2025
Anything at all?

Re: OpenBTS

Posted: Thu Feb 13, 2014 3:43 pm
by blagoja
I'm also interested in the progress of OpenBTS functionality.

Re: OpenBTS

Posted: Fri Feb 14, 2014 7:36 am
by bpadalino
Status is that it's coming along but not quite there yet.

We have the timed FPGA image checked into the main bladeRF git repository under the dev-openbts branch and with the dev-libbladeRF_sync branch, we are able to remove complexity to the RadioDevice implementation for our board. We have a preliminary amount of the transceiver written but not tested.

When we have done enough internal testing that we're comfortable with, we'll probably look to contribute back to the other project and see what works and doesn't work for them.

I don't want to push out a fork of their code to our github since that just creates a lot of confusion.

I hope that has been insightful. Sorry for the long delay in status updates.

Brian