Hi,
Can anybody confirm the USB debug serial port settings. I have downloaded
the FTDI drivers and can connect. However I do not get any meaningful
output.
Based on the source code I assume the settings are:
· baudrate = 115200
· stop bits = 1
· parity = none
· flow-control = off
Regards
Craig
---------- Forwarded message ----------
From: "Joel Yabut" <joel.yabut(a)gmail.com>
Date: Feb 18, 2013 9:25 AM
Subject: Re: UmTRX beta samples shipping address check
To: "Alexander Chemeris" <alexander.chemeris(a)gmail.com>
Cc:
May i know the following specs
1. What is the tx and rx isolation of umtrx?
2. What is the power output in dbm of your umtrx?
3. How is the lna on the rx input and is an external lna and bpf
recommended?
4. What is the main advantage of umtrx compared to usrp by ettus?
Thanks!
Joel
Sent from my Ipad
On Feb 15, 2013, at 7:23 PM, Alexander Chemeris <
alexander.chemeris(a)gmail.com> wrote:
> Ok, I'll ask to ship to this address.
>
> On Fri, Feb 15, 2013 at 11:41 AM, joel yabut <joel.yabut(a)gmail.com> wrote:
>> ok. thanks..
>> if you can set this value and follow shipping instruction below to avoid
any
>> transhipment.
>> cCan you just ship it straight to Manila, Philippines
>>
>> just declare it as PCB parts
>> Joint Venture Sound light entertainment concepts, Inc.
>> 2 scout rallos, quezon City
>> MM, Philippines
>> Attn: Louie Domingsil
>> tel. 3742969
>>
>>
>>
>> On Thu, Feb 14, 2013 at 11:17 PM, Alexander Chemeris
>> <alexander.chemeris(a)gmail.com> wrote:
>>>
>>> Thanks. I think we'll set this value for this package as well if you
>>> don't object.
>>>
>>> On Fri, Feb 15, 2013 at 11:05 AM, joel yabut <joel.yabut(a)gmail.com>
wrote:
>>>> ok. it seems fine.
>>>> in the future, a 150 usd for the future.
>>>>
>>>>
>>>> On Thu, Feb 14, 2013 at 10:59 PM, Alexander Chemeris
>>>> <alexander.chemeris(a)gmail.com> wrote:
>>>>>
>>>>> Here is a packing list:
>>>>>
>>>>> * UmTRXv2, flashed and ready to use.
>>>>> * Power supply, 12V/30W -
>>>>> http://www.phihong.com/assets/pdf/PSAC30U.pdf
>>>>> Note, that it comes without a 220V power cord. Make sure to prepare
>>>>> one before you receive the UmTRX to be able to power it on
>>>>> immediately.
>>>>> * Converter cable from a Molex power connector to a standard round DC
>>>>> connector.
>>>>> * U.FL-to-SMA-F pigtail cables
>>>>> * Two small antennas - one for Tx and one for Rx.
>>>>>
>>>>> Note, that for safe operation you'll need either a heatsink (external
>>>>> HDD enclosures work well) or a fan. Otherwise you could overheat your
>>>>> UmTRX during a long operation.
>>>>>
>>>>> On Fri, Feb 15, 2013 at 10:45 AM, joel yabut <joel.yabut(a)gmail.com>
>>>>> wrote:
>>>>>> What is included with the order?
>>>>>> Does it include the cables for antenna and psu?
>>>>>>
>>>>>>
>>>>>> On Thu, Feb 14, 2013 at 10:42 PM, joel yabut <joel.yabut(a)gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> thanks!!!
>>>>>>> in the future, can you declare lower value for shipping purposes?
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Feb 14, 2013 at 10:26 PM, Alexander Chemeris
>>>>>>> <alexander.chemeris(a)gmail.com> wrote:
>>>>>>>>
>>>>>>>> Ok, corrected.
>>>>>>>>
>>>>>>>> On Fri, Feb 15, 2013 at 8:01 AM, Joel Yabut <joel.yabut(a)gmail.com>
>>>>>>>> wrote:
>>>>>>>>> Just correct to Amazing speed..
>>>>>>>>> Thank you
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Sent from my Ipad
>>>>>>>>>
>>>>>>>>> On Feb 15, 2013, at 4:18 AM, Alexander Chemeris
>>>>>>>>> <alexander.chemeris(a)gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Joel,
>>>>>>>>>>
>>>>>>>>>> We're ready to ship UmTRX beta samples to our first customers
>>>>>>>>>> and
>>>>>>>>>> we
>>>>>>>>>> want to check that your shipping address is correct:
>>>>>>>>>>
>>>>>>>>>> Jose Q. Yabut
>>>>>>>>>> AMAZIN SPEED INTL LTD
>>>>>>>>>> K1 4FL NORTH TWR KWAI SHUN IND CTR
>>>>>>>>>> 51-63 CONTAINER PORT ROAD
>>>>>>>>>> Hong Kong
>>>>>>>>>> 85293354413
>>>>>>>>>>
>>>>>>>>>> We apologize for the delay with the production. We've made all
>>>>>>>>>> we
>>>>>>>>>> could to solve the issue quickly and ensure the quality of the
>>>>>>>>>> further
>>>>>>>>>> production at the same time. We appreciate your patience and
>>>>>>>>>> looking
>>>>>>>>>> forward to your feedback when you receive your UmTRX!
>>>>>>>>>>
>>>>>>>>>> PS T-shirts will be sent as a separate package from our
>>>>>>>>>> headquarter
>>>>>>>>>> in
>>>>>>>>>> Moscow, so expect two tracking numbers.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Regards,
>>>>>>>>>> Alexander Chemeris.
>>>>>>>>>> CEO, Fairwaves LLC / ООО УмРадио
>>>>>>>>>> http://fairwaves.ru
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards,
>>>>>>>> Alexander Chemeris.
>>>>>>>> CEO, Fairwaves LLC / ООО УмРадио
>>>>>>>> http://fairwaves.ru
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Mother Ignacia Avenue corner Scout Rallos St.
>>>>>>> Quezon City, Metro Manila, Philippines
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Mother Ignacia Avenue corner Scout Rallos St.
>>>>>> Quezon City, Metro Manila, Philippines
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Alexander Chemeris.
>>>>> CEO, Fairwaves LLC / ООО УмРадио
>>>>> http://fairwaves.ru
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Mother Ignacia Avenue corner Scout Rallos St.
>>>> Quezon City, Metro Manila, Philippines
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Alexander Chemeris.
>>> CEO, Fairwaves LLC / ООО УмРадио
>>> http://fairwaves.ru
>>
>>
>>
>>
>> --
>> Mother Ignacia Avenue corner Scout Rallos St.
>> Quezon City, Metro Manila, Philippines
>>
>
>
>
> --
> Regards,
> Alexander Chemeris.
> CEO, Fairwaves LLC / ООО УмРадио
> http://fairwaves.ru
Hi,
I have a couple questions about the RX PLL in the LMS chip:
- What are the various LOBUF for ? (1/2/3). Do they correspond the
the 3 input of the RX side ? I see they're controlled by the SELOUT
bits, but I have no idea how to choose. Should it be matched to
LNASEL_RXFE ?
- What's the expected levels of the LO harmonics ? In my tests I see
to measure around -10 dB for 3xLO and ~ -22 dB for 5x LO. Is there any
way to improve this ?
The method I used to measure is to feed 400 MHz narrow bw signal to
the input. Tune LMS to 400 MHz and measure the received strength, then
change the signal generator to TX a signal at 1.2 GHz and measure
again, then at 2GHz, and so on ...
Cheers,
Sylvain
Hi all,
A one more bit of good news - we've been assigned with a range of MAC
addresses we could use for UmTRX's. Many thanks for Openmoko Inc and
Harald Welte for generously offering this service to open-source
hardware projects for free!
Now we have to setup a procedure to make sure all UmTRX's get out of
the fab with unique MAC addresses.
---------- Forwarded message ----------
From: Harald Welte <laforge(a)gnumonks.org>
Date: Mon, Feb 4, 2013 at 1:04 AM
Subject: Re: Request for the OUI range for UmTRX board
To: Alexander Chemeris <alexander.chemeris(a)gmail.com>
Hi Alexander.
00-1F-11-02-19-00 to 00-1F-11-02-28-ff
see http://wiki.openmoko.org/wiki/OUI#MAC_addresses
Regards,
Harald
On Mon, Feb 04, 2013 at 12:08:45AM +0400, Alexander Chemeris wrote:
> Hi,
>
> I'd like to request a range of 0xfff MAC addresses for the use with
> UmTRX boards.
>
> Project information
> ==============
>
> Name: UmTRX
> Short description: UmTRX is a dual-channel wide-band SDR transceiver
> with 1GbE connection.
> Software License: GPLv3
> Hardware License: CC BY-SA 3.0
> Link: https://code.google.com/p/umtrx/
> Number of MAC addresses: 0xfff
>
> --
> Regards,
> Alexander Chemeris.
> CEO, Fairwaves LLC / ООО УмРадио
> http://fairwaves.ru
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi all,
Just to let everyone know - in addition to working on manufacturing
issues we're improving our UmTRX firmware and software support right
now. And today we've got dual-channel finally working. Thanks to
Andrew Karpenkov for his awesome work on implementing the second
channel support in FPGA!
I plan to push the pre-built FPGA image to the download area in the
during the weekend and Andrew will publish the FPGA code changes soon
too.
What's ahead of us is to teach OpenBTS to use the second channel of
UmTRX. This includes support of two independent channels and then
implementation of switched diversity receive.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi all,
For the purpose of tuning our Rx performance I've started putting
together an UmTRX specific GUI for GnuRadio. Source code is published
on github and will be gradually developed there. As usual, patches and
improvements are welcome:
https://github.com/chemeris/umtrx_scripts
GUI
===
GUI code is located at 'gui' directory. At this moment it is very
basic and has FFT, waterfall and scope views together with a minimal
set of controls for the Rx side of LMS6002D.
Type './umtrx_fft.py --help' to get a list of command-line options.
Note, that you have to select Rx channel from the command line.
If you want to run an LMS control GUI without spectrum display you
could run './lms_ctrl_panel.py' from 'python_lib' directory.
Screenshots are attached:
umtrx_fft.png - FFT view (default)
umtrx_fft_waterfall.png - Waterfall view
umtrx_ctrl_panel.png
Library
=====
Our Python library is under the 'python_lib' directory. It consists of
three parts:
* umtrx_ctrl.py - Base library which defines primitives for LMS SPI
control and UmTRX network discovery. It is pretty well abstracted, so
you cuold replace it with your own implementation if you want to talk
to some other board with LMS6002D chip, e.g. MyriadRF.
* umtrx_lms.py - library which implements all our LMS control logic.
* lms_ctrl_panel.py - implementation of the LMS control panel. Also
could be used as a standalone control app for LMS.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi,
While I'm waiting for my umtrx to show up, I'm following the "let's play
newbie" route and trying to use the instructions on
https://code.google.com/p/umtrx/wiki/BuildingUHD
I got stuck for a short while on step #2. It would probably be useful
to add at the beginning of step 2 something like:
git clone git://github.com/chemeris/UHD-Fairwaves.git
Also I see the FPGA instructions use ISE 14.2, should I download that
version rather than the more recent one (14.4) on Xilinx' site?
Finally, is the Ethernet flashing going to work off-the-box on the beta
umtrx or is it better I buy a JTAG cable? In that later case is the
Digilent HS-1 the recommended cable?
S.
Dear all,
We want to make a Christmas gift for the community and it's my
pleasure to announce the start of sales of UmTRXv2 beta samples aka
Limited Edition.
What is UmTRX?
==============
UmTRX is an SDR transceiver, which we, Fairwaves, developed
specifically for OpenBTS. It's similar to USRPs, but is heavily
modified to be the best hardware for OpenBTS. More details are
available at the project web-site:
https://code.google.com/p/umtrx/
Ordering and Shipping
=====================
To claim your UmTRXv2 Limited Edition, please fill in this form:
https://docs.google.com/spreadsheet/viewform?formkey=dGVHNlNDaXVoSHp2eC1EcV…
You will receive a payment link shortly after we receive your answer.
The shipping cost will be estimated when we have everything ready for
shipping, we'll contact you again by then.
There are only 14 units in this Limited Edition batch, so we allow you
to claim only 1 or 2 units.
The base price for a UmTRX is $1500 just as we promised. Since we are
relying on your support to fund further development, we encourage you
to donate an additional amount. You donations are critical for us to
produce the best ever hardware for OpenBTS. The 5 highest pledgers
will become the proud owners of UmTRX Serial Numbers 1 through 5 and
will be recognized on the UmTRX project site.
Shipping will be from Paris, France with FedEx or some other express
carrier. We plan to ship as soon as we receive orders for all 14
units, so the shipping date is not fixed yet. We'll contact you when
we fix it.
What does "beta" mean?
======================
Hardware is fully functional, as far as we could tell. There may be
further improvements in quality, but in its current form it works
smoothly for laboratory testing.
Software is what makes it "beta":
* Only 1st channel is supported in the software at this moment.
* Not all LMS6002D controls are properly integrated into the software.
* Safe/production bitstreams switching is not working in the FPGA yet.
* Result of the TCXO frequency synchronization from GPS is not stored
to EEPROM.
* I/Q imbalance and DC leakage calibration are not automatic.
We accept patches to fix these and other issues. You participation
will make the stable release closer. ;)
The software is based on UHD from Etttus Research, so if you're
familiar with it, it'll be easy for you to get into.
UmTRXv2 package contents
========================
* UmTRXv2, flashed and ready to use.
* Power supply, 12V/30W - http://www.phihong.com/assets/pdf/PSAC30U.pdf
Note, that it comes without a 220V power cord. Make sure to prepare
one before you receive the UmTRX to be able to power it on
immediately. ;)
* Converter cable from a Molex power connector to a standard round DC
connector.
* U.FL-to-SMA-F pigtail cables
* Two small antennas - one for Tx and one for Rx.
* An Open-Source Telecom T-shirt! (see the picture attached)
Feedback
=======
Do not hesitate to contact us if you have any questions, suggestion or
comment. We love your feedback!
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi Alexander,
Please try the last commit at
git://github.com/ttsou/openbts-p2.8.git laurent
I tested with 4 samples per symbol as we did in the past. Reducing the
start/end phase error involved adding bits so that there is no partial
phase transition to/from nothing. We then zero out the excess bits
with a simple power mask.
Thomas
(forwarding to the UmTRX mailing list)
On Fri, Oct 19, 2012 at 7:33 PM, Ivan Kluchnikov
<Ivan.Kluchnikov(a)fairwaves.ru> wrote:
> Just sketch :)
Nice idea. The last symbol would be better to have in the form of a
SIM-card, imho.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi all.
Here are two bad news.
I got two UmTRXv2 and both with the problems of inaccurate assembling.
1st Thomas sent to me and 2nd was new and clear (say, virgin).
Thomas said about power supply symptoms few days ago.
I fixed assembling error in DC/DC - power coil (L37) was 90 degrees rotated.
It was too big surprise for me, because I replaced all components around
coil before I saw that it soldered incorrect.
Anyhow,This board began to work, but LMS2 still didn't hears SPI and didn't
work.
Also I found that mashine lost one 0.1uF cap (C86-1) near LMS1, but it was
easily to fix.
LMS1 and all other parts, seems working fine.
Second board programmed and working, but FPGA too hot and 3.3V loaded a lot.
Seems, I have to find BGA reworking station to fix both boards finally.
Also needed new Spartan-6 FPGA for replace.
Alexander, do we have spare on hands?
Best regards,
Andrey Sviyazov.
> Decreasing power consumption to 10-11W would allow us to use lighter
> enclosure for the lab version, which is nice.
at 20w of power consumption, this comes to roughly 68btu of generated
heat -Is there a reason convection cooling in a sheetmetal enclosure
wouldent work for this board?
Hi Jean-Samuel.
As known, hardware developing impossible without soldering iron.
With UmTRXv2 I found that was used very infusible solder paste.
As I understand it is due to compliance to Pb-free.
Nevertheless, could you please to ask fab to use more fusible solder paste .
I ask, because lab users can easy damage PCB due to the local overheat.
For example, I was forced to use simultaneously soldering iron (300 deg C)
and air heater (350 deg C) to solder linear regulators.
Best regards,
Andrey Sviyazov.
Hi Andrey,
Do you think it will be possible to decrease the power consumption and to
keep the best possible performances for industrial applications ?
I know you cannot be sure about this but I would like to know how confident
you feel about this ?
Best regards.
Jean-Samuel.
:-)
On Wed, Oct 31, 2012 at 7:40 PM, Andrey Sviyazov <andreysviyaz(a)gmail.com>wrote:
> Hi Jean-Samuel, Alexander.
>
> Tomorrow I'll let you know what possible to make on time.
> And we should set time limit for this.
> For example, next morning.
>
> Best regards,
> Andrey Sviyazov.
> (Sent from my mobile client)
> 31.10.2012 22:24 пользователь "Jean-Samuel Najnudel - BJT PARTNERS SARL" <
> jsn(a)bjtpartners.com> написал:
>
> Hi Alexander,
>>
>> Thank you very much for your reply.
>>
>> Why skip/populate LMS power supply block ?
>> As I understand we always need the LMS power supply block. I probably
>> missed something. Could you explain this in more details to let me better
>> understand ?
>>
>> Thanks a lot for your help.
>>
>> Best regards.
>>
>> Jean-Samuel.
>> :-)
>>
>>
>> On Wed, Oct 31, 2012 at 7:14 PM, Alexander Chemeris <
>> alexander.chemeris(a)gmail.com> wrote:
>>
>>> Yes, lesser input voltage range makes sense only if it saves >$10
>>> and/or considerably increases power efficiency. I think this not the
>>> case, and then only these changes will be needed:
>>>
>>> * traditional power connector
>>> * MCX RF connector, because they sustain much more connect-disconnect
>>> cycles
>>> * lower power consumption mod
>>>
>>> I would appreciate if we could keep the same PCB for both versions and
>>> populate the proper version of power connector/RF connector and
>>> skip/populate LMS power supply block.
>>>
>>> On Wed, Oct 31, 2012 at 9:56 PM, Jean-Samuel Najnudel - BJT PARTNERS
>>> SARL <jsn(a)bjtpartners.com> wrote:
>>> > Hi Alexander,
>>> >
>>> > This would be much easier to have the same board for both lab and
>>> > deployment. Only the UmSEL would make the difference.
>>> > For deployment, I really need wide input voltage range as I plan to
>>> power
>>> > the whole system (UmTRX + PA) with a single 28V supply.
>>> > Even if this can save a few euros, I would really prefer we do not
>>> make the
>>> > input voltage range smaller.
>>> > By the way, even for lab, it might be convenient and it can avoid
>>> damages in
>>> > case of wrong voltage supply.
>>> >
>>> > Best regards.
>>> >
>>> > Jean-Samuel.
>>> > :-)
>>> >
>>> >
>>> >
>>> > On Wed, Oct 31, 2012 at 6:50 PM, Alexander Chemeris
>>> > <alexander.chemeris(a)gmail.com> wrote:
>>> >>
>>> >> Andrey, how much time do you need to create 2.1? If it's mire than a
>>> day,
>>> >> we should postpone this. I believe that enclosure is a much more
>>> important
>>> >> issue at this moment.
>>> >>
>>> >> I think we need following changes for the lab version:
>>> >> * traditional power connector
>>> >> * MCX RF connector, because they sustain much more connect-disconnect
>>> >> cycles
>>> >> * lower power consumption mod
>>> >> * smaller input voltage range (only if this makes things cheaper)
>>> >>
>>> >> Sent from my Android device.
>>> >>
>>> >> --
>>> >> Regards,
>>> >> Alexander Chemeris
>>> >> CEO, Fairwaves LLC
>>> >> http://fairwaves.ru
>>> >>
>>> >> 31.10.2012 14:05 пользователь "Andrey Sviyazov" <
>>> andreysviyaz(a)gmail.com>
>>> >> написал:
>>> >>
>>> >>> Hi Jean-Samuel.
>>> >>>
>>> >>> First of all, you didn't said about delay duration :)
>>> >>> I can't delay this batch just due to my wishes that each next batch
>>> >>> should work more and more ideally.
>>> >>>
>>> >>>> These modifications looks interesting. I think it is a good idea.
>>> >>>
>>> >>> Hope so.
>>> >>>
>>> >>>>
>>> >>>> I just have a few question.
>>> >>>>
>>> >>>> Why do you call this board revision 2.1 "a special batch for labs" ?
>>> >>>> Would these modifications make this revision 2.1 also more suitable
>>> for
>>> >>>> field deployment, at least as much as the revision 2.0 ?
>>> >>>
>>> >>> Because of I can fix only known issues.
>>> >>> Also not all really required improvements are known yet.
>>> >>>
>>> >>>> Decreasing power consumption to 10..11 W would be great. Is there
>>> any
>>> >>>> drawbacks of this modification ? Would it decrease some
>>> performances ? If
>>> >>>> not, this modifiction to decrease power consumption is a
>>> significant very
>>> >>>> good modification.
>>> >>>
>>> >>> Decreasing of performances it is only spurs with DC/DC conversion
>>> freq
>>> >>> ~500kHz.
>>> >>> Now I searching more good LC filter to suppress it better than
>>> TI2012U601
>>> >>> can.
>>> >>>
>>> >>>> Do you have enough space on the board to replace some U_FL
>>> connectors
>>> >>>> with MCX connectors as you suggest ?
>>> >>>
>>> >>> Yes, but may be not all should be MCX.
>>> >>> Of course I did not insist, but just asking whether there is a
>>> reason to
>>> >>> do it or not.
>>> >>>
>>> >>>> An external LNA would probably need around 5 Volts instead of 6V. A
>>> >>>> small PA would probably need a little bit higher voltage. Do you
>>> think it
>>> >>>> would be possible to have a variable voltage low power connector ?
>>> >>>
>>> >>> On my opinion, variable voltage is not good idea.
>>> >>> For example for LNA's better to place low noise LDO 6V to 5V near to
>>> IC's
>>> >>> to get Vcc clean too.
>>> >>>
>>> >>>> By the way, could you pelase also add the 2 LMS output matching
>>> >>>> capacitors we need to improve output power figures in the 1800 band
>>> ?
>>> >>>
>>> >>> Of course, because it is issue which should be fixed, but not
>>> >>> improvement.
>>> >>>
>>> >>> Best regards,
>>> >>> Andrey Sviyazov.
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Alexander Chemeris.
>>> CEO, Fairwaves LLC / ООО УмРадио
>>> http://fairwaves.ru
>>>
>>
>>
Forwarding to the mailing list.
---------- Forwarded message ----------
From: Jean-Samuel Najnudel - BJT PARTNERS SARL <jsn(a)bjtpartners.com>
Date: Tue, Oct 30, 2012 at 6:25 PM
Subject: LNA and Noise Figure improvement
Hi Andrey,
I understand you plan to prepare the UmTRXv3.
I would need to discuss about the Rx Noise Figure improvement.
With UmSEL, according to your calculations, NF would be around 0.7 dB
(excluding duplexer IL) with the MGA-13116.
It would be interesting to try to improve this figure with a very
first stage LNA based on the MGA-633P8. This would let us reach a NF
as low as about 0.4 dB.
Adding this very first stage LNA in the Rx path brings a few questions.
1/ To improve isolation with the other RF parts, would we need to have
this LNA in a separate shielded enclosure ?
If yes, we would need a 5V power supply for this LNA. To have a better
shielding between the voltage regulator circuitery and the LNA, it
should be nice to have the 5V voltage regulator outside of the LNA
enclosure. To make this possible, it would be very useful to add a 5V
voltage regulator and connector on the UmTRXv3.
If not, we do not need specific modifications on the UmTRXv3 but we
would need to add an MGA-633P8/634P8 as a very first stage in the
UmSEL.
2/ Whatever external or on the UmSEL, this extra LNA will increase the
total gain. Considering your calculation, the UmSEL IIP3 is already as
low as around 1 dBm. If we add a very first stage LNA, this IIP3 will
go down to about -15 dBm. This could be a problem for inband blockers.
Even if, in real life situation in the field, I am not sure it will be
a very big problem, it will be a problem to pass the spec.
Would you have another idea to improve the NF ?
If not, could you please let me know what NF we could expect with the
current design (UmSEL with MGA-13116/13216) in both 900 and 1800 bands
?
Best regards.
Jean-Samuel.
:-)
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi Thomas,
Could you please describe symptoms which you observe on your UmTRX? We
have to figure out the reason for the improper behavior and if this is
a manufacturing issue - make sure this won't happen for the next
batch.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi Alexander,
Thank you very much for your reply and detailled explainations.
Now I understand.
My point of view is we do not really care of a few watts power consumption
saving for the lab version. At worst, we can still add a fan in the lab
enclosure, as for the USRP which also dissipate up to about 15 Watts.
On the other side, it makes a lot of sense to save some power consumption
for the industrial version as, on the field, every watt counts and we also
need to dissipate the heat without fan for better reliability.
Considering this, I believe as follow.
Either we are able to decrease the power consumption and keep good enough
performances for industrial applications. In this case, we should make this
modification for both lab and industrial versions.
Either decreasing the power consumption will decrease the performances. In
this case, I do not think this worth making this modification at all.
In both cases, I would suggest we keep the same design for both lab and
industrial versions, either with or without the modification.
Moreover, if both lab and industrial versions are the same, except
connectors may be, debug from lab users may help industrial users and debug
from industrial users may help lab users. This would be really easier to
get a reliable single board for both lab and industrial applications.
Best regards.
Jean-Samuel.
:-)
On Wed, Oct 31, 2012 at 7:30 PM, Alexander Chemeris <
alexander.chemeris(a)gmail.com> wrote:
> On Wed, Oct 31, 2012 at 10:23 PM, Jean-Samuel Najnudel - BJT PARTNERS
> SARL <jsn(a)bjtpartners.com> wrote:
> > Why skip/populate LMS power supply block ?
> > As I understand we always need the LMS power supply block. I probably
> missed
> > something. Could you explain this in more details to let me better
> > understand ?
>
> If I understand correctly, this is the modification which Andrey is
> testing - avoid additional power conversion near LMS. We may need it
> for better performance for industrial version, but we most likely do
> not need it for the lab version.
>
> Decreasing power consumption to 10-11W would allow us to use lighter
> enclosure for the lab version, which is nice.
>
> PS I'd love to move this discussion to the public UmTRX mailing list.
> Is it fine with you? Actually, if you feel fine, you could start such
> discussion at the public UmTRX mailing list from the beginning.
>
> --
> Regards,
> Alexander Chemeris.
> CEO, Fairwaves LLC / ООО УмРадио
> http://fairwaves.ru
>
Hi all,
I spent some time yesterday testing UmTRX with MCBTS. Aside from some
trivial fixes (inverted sample rate), the code ran fine with no
issues. The default bandwidth of the LPF was insufficient, so that was
widened. I tested with 9 handsets between 3 and 7 carriers on a Core2
Duo (P7570) laptop.
git://github.com/ttsou/openbts-multi-arfcn.git umtrx
Configuration is through sqlite database, which is unchanged from
mainline; just set the number of ARFCN (7 max) and C1 channels.
Because of the bandwidth involved, be sure to increase the maximum
buffer sizes for UHD. The uhd_usrp_probe utility will warn if the
target size cannot be set.
http://files.ettus.com/uhd_docs/manual/html/transport.html#linux-specific-n…
Design
=====
There are three resampling stages.
1. Outer resampler converts from the device rate to a multiple of the
400 kHz channel spacing.
2. Channelizer demultiplexes input stream to M channels
3. Inner resampler converts from 400 kHz to a multiple of the GSM symbol rate.
UmTRX rates:
Channelizer Rate Device Rate Decimation
1.6 Msps 1.625 Msps 8
3.2 Msps 3.250 Msps 4
Options
======
To broadcast dummy bursts on all carriers for spectrum testing,
uncomment the following preprocessor declaration in radioParams.h.
#define ENABLE_ALL_CHANS
With dummy bursts on all carriers:
http://filebox.vt.edu/users/ttsou/http/7carrier_umtrx.PNG
Calibration
========
Calibration remains a concern. With single carrier, the carrier
leakage and and IQ imbalance appear as in-band distortion. For MCBTS,
OpenBTS offsets C0 on to the lowest carrier. This makes the carrier
and image quite visible, as shown in the following uncalibrated
capture. I checked with a swept tone to verify that this issue was not
a result of baseband DSP. The USRP also shows similar effects.
http://filebox.vt.edu/users/ttsou/http/carrier_image.PNG
Any idea how much carrier and image suppression we should expect with
calibration on UmTRXv2?
Thomas
Hello,
I've read that the # of maximum callers is 15.
Since there are "Beta" version coming out will these be able to handle 15
simultaneous callers too?
SoftwareDefinesRadio
Alexander,
Superb potential of the device you and the Fairwaves team are bringing to
fruition.
I also look forward to your future potential product, UmTRXv3 4G/LTE.
I know its just something your team and you have thought about publically,
alot of us would love to see such.
Thank you for your responses.
SoftwareDefinesRadio
On Tue, Oct 30, 2012 at 5:07 AM, Alexander Chemeris <
alexander.chemeris(a)gmail.com> wrote:
> Hi,
>
> On Tue, Oct 30, 2012 at 12:36 PM, SoftwareRadioGuy
> <softwaredefinesradio(a)gmail.com> wrote:
> > I've read that the # of maximum callers is 15.
> >
> > Since there are "Beta" version coming out will these be able to handle 15
> > simultaneous callers too?
>
> A short answer is "yes, after a software update".
>
> A longer answer is that hardware supports dual-TRX operation, but
> software support is not there yet. We might be able to fix software
> before we ship beta units, but even if not - you will be able to get
> the software update later.
> Also keep in mind, that UmTRX should be able to run multi-ARFCN
> OpenBTS and in this case it'll be able to handle much more calls. We
> haven't tested this mode of operation extensively yet, but
> theoretically we might be able to support 14ARFCNs (2x7ARFCN) which
> equals to (14*8-1)=111 calls. At this scale you're most likely limited
> by computing power of your PC rather then UmTRX hardware. Whether we
> could get UmTRX in Multi-ARFCN mode through certification or not is
> still a question, but it should be fine for lab testing.
>
>
> --
> Regards,
> Alexander Chemeris.
> CEO, Fairwaves LLC / ООО УмРадио
> http://fairwaves.ru
>
>
> Alexander,
>
>
>> >> Does this mean people whom purchase the UmTRXv2 Samples will be able to
>> >> obtain the Schematics/Gerber Files ?
>> >
>> > Yes.
>> > Schematics are already published, btw:
>> > https://github.com/chemeris/umtrx-schematics
>>
>
>
>> Just curious - what do you need gerbers for? Want to make some
>> improvements?
>>
>
> Prospectively, but if that wasn't in your plans, no problems.
>
> I support your efforts!
>
>
> --
> Regards,
> Alexander Chemeris.
> CEO, Fairwaves LLC / ООО УмРадио
> http://fairwaves.ru
>
> Sincerely,
>
>
> SoftwareDefinesRadio
>
>>
>
Alexander,
" UmTRXv2 samples for early adopters should be ready in just few weeks
" per here:
http://lists.osmocom.org/pipermail/umtrx/2012-October/000252.html
And this page states:
" Note: PCB layout will be published here when we start selling UmTRX
boards. Prior to that it's available per request to our partners. "
https://github.com/chemeris/umtrx-schematics
Does this mean people whom purchase the UmTRXv2 Samples will be able to
obtain the Schematics/Gerber Files ?
Sincerely,
SoftwareDefinedRadio
1. Power supply, 12V-18V DC, >=20W.
I think it's easier to find a PSU with a standard round DC connector,
like this one and thus we need a converter cable to our Molex power
connector.
http://domino2.kycon.com/catalog_PDF/KLDX_SMT2.pdf
Not knowing center pin polarity or exact center pin size, it seems as
though digikey (http://www.digikey.com/product-search/en/power-supplies-external-internal-o…)
has 348 that are 12-18v output, 10-20w, and have connectors that are
2.1mm ID to 2.5mm ID
On a side note, for power -Something that could come in useful since
its got ethernet, PoE?
2. Enclosure. We'd love to have a nice table-top enclosure for UmTRX,
but it requires a significant effort to source, design and assemble.
If anyone has some preexisting case designs, there's always protocase
(protocase.com) or Rapid sheet metal
(http://www.rapidsheetmetal.com/parts/enclosures.aspx) -Im sure theres
plenty of other sheetmetal fabshops that will do custom work though,
If youre wanting to use something a bit more generic -Theres
enclosurehub.com
Hi all,
UmTRXv2 samples for early adopters should be ready in just few weeks
and we're looking at what to put an a package. Below is a preliminary
list of items which I think we should include. Please comment on the
list and suggest particular items:
1. Power supply, 12V-18V DC, >=20W.
I think it's easier to find a PSU with a standard round DC connector,
like this one and thus we need a converter cable to our Molex power
connector.
http://domino2.kycon.com/catalog_PDF/KLDX_SMT2.pdf
2. Converter cable from the Molex power connector to a standard round
DC connector.
3. U.FL-to-SMA-F pigtail cable.
4. Two small antennas - omni or patch. One for Tx and one for Rx.
Below is a list of items which are non-essential and which we unlikely
to include in the package for this batch. We do no have them ready yet
and we don't want to delay shipping. We focus our effort on polishing
UmTRX and UmSEL performance and software development which we see as a
more important tasks at this moment.
1. Duplexer. Without a power amplifier UmTRXv2 is pretty low-power
(50-100mW) and thus it works good enough without a duplexer in a
normal environment. For our testing we use two small antennas - one
for Rx and one for Tx without any issues.
2. Enclosure. We'd love to have a nice table-top enclosure for UmTRX,
but it requires a significant effort to source, design and assemble.
3. UmSEL. It's not clear whether we will have UmSEL production setup
in time. Software to control UmSEL is yet to be developed as well.
Since it's only an improvement frontend, I don't think we should
include it into the basic package.
If you want to help us make those items faster - by all means feel
free to offer your help! :)
* If you provide a valuable contribution, you'll get the item you're
contributed to for free.
* If you provide significant contributions on a regular basis, you'll
get all our future hardware versions for free and recognition on the
web-site.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi all,
I've pushed an update to git to store some LMS6002D calibration values
in UmTRX's EEPROM. The idea is to perform calibration once and do not
worry about it anymore no matter what PC you connect UmTRX to.
Intro
====
Right now we have the following values which could be stored in EEPROM:
* tx-vga1-dc-i - DC offset calibration value for LMS6002D Tx I channel
* tx-vga1-dc-q - DC offset calibration value for LMS6002D Tx I channel
* tcxo-dac - TCXO calibration value
Now, when the framework for UmTRX EEPROM is in place, we could store
more values there as we see the need. E.g. we may want to store Rx DC
offset calibration values or power limits of this exact units to be
used by OpenBTS.
The only limitation here is the size of the EEPROM. EEPROM is only 256
bytes large and some of them are already used, so we have about 200
bytes to use. With the strong dependency of calibration values on
temperature and frequency, we might need a two-dimensional array for
each value. In this case we may want to move those calibration values
to flash instead of EEPROM. This would need some more work and thus is
in our wish-list for now.
Writing values
===========
You could write values mentioned above to EEPROM as any other EEPROM value:
./host/build/utils/usrp_burn_mb_eeprom --key <name> --val <dec_val>
(from the root of your UHD source tree)
Reading values
=============
You could read individual values from EEPROM as any other EEPROM value:
./host/build/utils/usrp_burn_mb_eeprom --key <name> --val <dec_val>
(from the root of your UHD source tree)
Or you could use `uhd_usrp_probe` to see them all at once at the
top-level section:
_____________________________________________________
/
| Device: UmTRX Device
| _____________________________________________________
| /
| | Mboard: UMTRX-REV0
| | hardware: 64000
| | mac-addr: 00:50:c2:85:3f:ff
| | ip-addr: 192.168.10.4
| | gpsdo: none
| | serial: 1
| | tx-vga1-dc-i: 114
| | tx-vga1-dc-q: 138
| | tcxo-dac: 2022
| |
| | Time sources: none, external, _external_, mimo
| | Clock sources: internal, external, mimo
| | Sensors: ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | | Freq range: -6.500 to 6.500 Mhz
| | _____________________________________________________
| | /
| | | RX DSP: 1
| | | Freq range: -6.500 to 6.500 Mhz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | ID: LMS RX (0xfa09)
| | | Serial: 1
| | | _____________________________________________________
| | | /
| | | | RX Subdev: 0
| | | | Name: LMS RX (0xfa09) - 0
| | | | Antennas: RX0, RX1, RX2, RX3, CAL
| | | | Sensors:
| | | | Freq range: 232.500 to 3720.000 Mhz
| | | | Gain range VGA2: 0.0 to 30.0 step 3.0 dB
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: LMS_RX
| | | | Gain Elements: None
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | | Freq range: -32.500 to 32.500 Mhz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | ID: LMS TX (0xfa07)
| | | Serial: 1
| | | _____________________________________________________
| | | /
| | | | TX Subdev: 0
| | | | Name: LMS TX (0xfa07) - 0
| | | | Antennas: TX0, TX1, TX2, CAL
| | | | Sensors:
| | | | Freq range: 232.500 to 3720.000 Mhz
| | | | Gain range VGA: -35.0 to 21.0 step 1.0 dB
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: LMS_TX
| | | | Gain Elements: None
PS I've added this text to the wiki for future reference:
https://code.google.com/p/umtrx/wiki/UmTRXCalibration
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi Jean-Samuel.
Pdet1&2 dedicated for Output power detectors and Vcnt1&2 for test points
voltage control.
For example, PA +24V and feeder supply voltage 28..36V of DC-DC converter
(in case of positive type, i.e. minus connected to chassis).
Each input of ADS1015 contains divider of 1:10, so it makes possible to
measure up to 41V with 0.01V resolution.
Best regards,
Andrey Sviyazov.
2012/10/22 Jean-Samuel Najnudel - BJT PARTNERS SARL <jsn(a)bjtpartners.com>
> Hi Andrey,
>
> I can see in the UmSEL 4 channels ADC.
>
> What do you plan to do with this ?
> What is Pdet and Vcnt ?
>
> I ask you this because it would be really nice to use 2 of these ADC
> channels to monitor each of the 2 PA RF Pout.
> What would you think about this ?
>
> Best regards.
>
> Jean-Samuel.
> :-)
>
>
I think the front of the T-shirt should read "FREE GSM" with the logo of a SIM card with little feet running. The back should have the Fairwaves Logo / URL. "FREE GSM" because it's a pun: free of cost thanks to open source, and free it from the shackles of the evil big black box infrastructure vendors.
In terms of color, if a deep dark midnight blue (like Nike's "Obsidian" blue) would be awesome. This is for selfish reasons since all my gym wear is Obsidian blue :-) Oh and some T-shirts in European XXL or American XL would be nice for me.
--
Aaron deMello
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Saturday, October 20, 2012 at 4:20 PM, umtrx-request(a)lists.osmocom.org wrote:
> Send UmTRX mailing list submissions to
> umtrx(a)lists.osmocom.org (mailto:umtrx@lists.osmocom.org)
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.osmocom.org/cgi-bin/mailman/listinfo/umtrx
> or, via email, send a message with subject or body 'help' to
> umtrx-request(a)lists.osmocom.org (mailto:umtrx-request@lists.osmocom.org)
>
> You can reach the person managing the list at
> umtrx-owner(a)lists.osmocom.org (mailto:umtrx-owner@lists.osmocom.org)
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of UmTRX digest..."
>
>
> Today's Topics:
>
> 1. Re: Open-source telecom t-shirts (Andrey Sviyazov)
> 2. Re: Open-source telecom t-shirts (Andrey Bakhmat)
> 3. Re: Open-source telecom t-shirts (Andrey Bakhmat)
> 4. Re: Open-source telecom t-shirts (Andrey Sviyazov)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 20 Oct 2012 14:12:48 +0400
> From: Andrey Sviyazov <andreysviyaz(a)gmail.com (mailto:andreysviyaz@gmail.com)>
> To: Alexander Chemeris <alexander.chemeris(a)gmail.com (mailto:alexander.chemeris@gmail.com)>
> Cc: Sylvain Munaut <246tnt(a)gmail.com (mailto:246tnt@gmail.com)>, umtrx(a)lists.osmocom.org (mailto:umtrx@lists.osmocom.org), Andrey
> Bakhmat <Andrey.Bakhmat(a)fairwaves.ru (mailto:Andrey.Bakhmat@fairwaves.ru)>, Mahyuddin Husairi
> <mahyuddin(a)gmail.com (mailto:mahyuddin@gmail.com)>, Christian Gagneraud <chris(a)techworks.ie (mailto:chris@techworks.ie)>
> Subject: Re: Open-source telecom t-shirts
> Message-ID:
> <CAE9AREzGtueztHbZ3ak-sA9zAJ-TgBU9Kt6LJSKFJghp5OR7LA(a)mail.gmail.com (mailto:CAE9AREzGtueztHbZ3ak-sA9zAJ-TgBU9Kt6LJSKFJghp5OR7LA@mail.gmail.com)>
> Content-Type: text/plain; charset="koi8-r"
>
> Hmm, I missed it.
> But really not sure that Fairwaves will associated to the blue colors (and
> vice versa) due to the blue logo.
> It doesn't mean that all around must be in blue.
>
> Best regards,
> Andrey Sviyazov.
> (Sent from my mobile client)
> 20.10.2012 13:43 ???????????? "Alexander Chemeris" <
> alexander.chemeris(a)gmail.com (mailto:alexander.chemeris@gmail.com)> ???????:
>
> > Because blue is the Fairwaves color :)
> >
> > On Sat, Oct 20, 2012 at 1:42 PM, Andrey Sviyazov <andreysviyaz(a)gmail.com (mailto:andreysviyaz@gmail.com)>
> > wrote:
> > > And about colors - why blue?
> > > On my opinion, dark green and golden contacts looks better.
> > > At least blue and gold is not good combination for me.
> > > It looks like church painting.
> > >
> > > Best regards,
> > > Andrey Sviyazov.
> > > (Sent from my mobile client)
> > >
> > > 20.10.2012 13:32 ???????????? "Andrey Sviyazov" <andreysviyaz(a)gmail.com (mailto:andreysviyaz@gmail.com)>
> > > ???????:
> > >
> > > > Andrey.
> > > > You could add HARDWARE word, to align text with vertical Sim.
> > > >
> > > > Best regards,
> > > > Andrey Sviyazov.
> > > > (Sent from my mobile client)
> > > >
> > > > 20.10.2012 13:01 ???????????? "Andrey Bakhmat"
> > > > <Andrey.Bakhmat(a)fairwaves.ru (mailto:Andrey.Bakhmat@fairwaves.ru)> ???????:
> > > > >
> > > > > I suggest "Unlock communications for the rest of us!" - just another
> > > > > option bring to a vote.
> > > > > Vertical SIM looks good, but it was difficult for me to arrange it with
> > > > > the text. If somebody wants to play with it, I can provide vector (AI)
> > > > > files.
> > > > > Superman style - good idea, previous versions of T-shirt was slightly
> > > > > boring. So I propose make something informal at the back side.
> > > > >
> > > > > On Sat, Oct 20, 2012 at 1:03 AM, Sylvain Munaut <246tnt(a)gmail.com (mailto:246tnt@gmail.com)>
> > wrote:
> > > > > >
> > > > > > > > I like "Telecom wants to be free" slogan more, but that's just me.
> > > > > >
> > > > > > > "Telecom Wants to be Open"?
> > > > > >
> > > > > > I prefer "Telecom wants to be Free" too. (upper case F)
> > > > > >
> > > > > > and I also prefer the sim to be vertical.
> > > > > >
> > > > > >
> > > > > > Just my 2c
> > > > > >
> > > > > > Cheers,
> > > > > >
> > > > > > Sylvain
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Andrey Bakhmat
> > > > > COO, Fairwaves LLC
> > > > > http://fairwaves.ru
> > > > >
> > > >
> > >
> >
> >
> >
> >
> > --
> > Regards,
> > Alexander Chemeris.
> > CEO, Fairwaves LLC / ??? ???????
> > http://fairwaves.ru
> >
>
>
Hi all,
We're thinking about making T-shirts with open-source telecom. I've
posted a call for ideas in my OpenBTS blog - please contribute.
Telecom needs more openness and you could help us promote this!
http://openbts.chemeris.ru/2012/10/reklama-open-source-telecom/
We plan to give them for free to the first 10-20 UmTRX buyers. Then
you'll be able to buy them from our web-shop or from one of our
friends and distributors.
If you proposal gets printed, you'll get a free T-shirt as well.
PS If you know a good online T-shirt printing service in US or Europe
- drop me a line. I've never done this in US/Europe before.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi Srdjan,
We're looking into re-purposing UmTRX for LTE and there a few things which
we need to understand better.
1. Is it possible to support 15MHz and 20MHz LTE channel bandwidths? To
achieve this we at least need to sample at 23.04Msps and 30.72Msps
respectively. LMS6002D datasheet specifies the maximum I/Q samplerate of
14Msps, which is not enough. But at the same time, datasheet claims that
ADC and DAC are specified up to 50Msps. How does this fits together?
2. Do you have any experience what maximum output power we could achieve
with LMS and proper amplifiers, while still staying in the bounds of the
LTE Standard? What would be the limiting factor for the further power
increase?
3. Is there any issues using TDD mode in LMS6002D? We've been using onnly
FDD mode so far and it would be great to know what issues could we expect
when switching to TDD mode.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi All,
I ported UmTRX project to the new UmTRX v2 board. Now you can compile FPGA
project for UmTRX v2 board with "make UmTRXv2" command from fairwaves/umtrx
branch.
Now, my next goal is to get a working second transmission channel in fpga
project.
Regards,
Andrew Karpenkov
Andrey Sviyazov, this question is probably for you,
IIRC, both nanoBTS and SysmoBTS have separate antennas for Rx andTx and do
not use duplexers. Do we need duplexer for UmTRXv2 if it operates in the
low power mode, without an additional PA/LNA?
--
Regards,
Alexander Chemeris
CEO, Fairwaves LLC
http://fairwaves.ru
Hi,
I'm having a problem while trying to do a LPF Bandwidth tuning as described in a Programming and Calibration guide page 40, figure 4.5 and on https://github.com/chemeris/UHD-Fairwaves/blob/fairwaves/umtrx/host/utils/u…. Currently it seems to always fail when it's trying to find the VCOCAP value. I'm only getting Low printed before it fails. I was wondering why it takes a 320MHz frequency, because it's not described anywhere in the documents, could I try to do a bandwidth tuning with some other frequency as well? I'm running my code in a following order (http://lists.osmocom.org/pipermail/umtrx/2012-July/000075.html),
Example setup for ARFCN 925:
Initialization and auto-calibration:
./umtrx_lms.py --lms 1 --lms-init
./umtrx_lms.py --lms 1 --lms-tx-enable 1
./umtrx_lms.py --lms 1 --lms-rx-enable 1
./umtrx_lms.py --lms 1 --pll-ref-clock 26e6 --lpf-bandwidth-code
0x0f --lms-auto-calibration
RX LNA and RXVGA2 selection and gain control
./umtrx_lms.py --lms 1 --reg 0x75 --data 0xf0
./umtrx_lms.py --lms 1 --reg 0x65 --data 10
TX LPF control
./umtrx_lms.py --lms 1 --reg 0x34 --data 0x3e
LO leakage cancellation (calibration data values may vary)
./umtrx_lms.py --lms 1 --reg 0x42 --data 0x67
./umtrx_lms.py --lms 1 --reg 0x43 --data 0x89
TX/RX PLL charge pump current
./umtrx_lms.py --lms 1 --reg 0x16 --data 0x93
Tuning
./umtrx_lms.py --lms 1 --lms-rx-pll-tune 925.2e6
./umtrx_lms.py --lms 1 --lms-tx-pll-tune 880.2e6
TXVGA2 gain to max and enable PA
./umtrx_lms.py --lms 1 --reg 0x45 --data 0xc8
./umtrx_lms.py --lms 1 --lms-pa-on 2
Andrey, Jean-Samuel,
I wanted to check pricing for ET1011C2-CI-DT - 1GbE PHY chip we use
and I haven't found it neither in DigiKey, nor at Mouser. At Arrow
they are "Call for Quote":
http://components.arrow.com/part/search/ET1011C2
Do you know what happened to this chip? Is there any pin-to-pin
replacements or could we buy enough of those chips from some other
source?
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Alexander is visiting Boston after the Open Hardware Summit last week in
NYC. We powered up the umTRXv2 for the first time yesterday afternoon and
immediately captured a GSM signal on the Signal Hound after launching
OpenBTS. Echo Test with the test handset worked like a charm.
Congratulations to the Fairwaves team!
-Robin
--
Robin Coxe | Close-Haul Communications, Inc. | Boston, MA
+1-617-470-8825
All,
I've put together a short step-by-step on how to build FPGA image for
UmTRX and how to flash it over Ethernet or a JTAG cable. Feel free to
amend/comment on it:
http://code.google.com/p/umtrx/wiki/BuildingUHD
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi all,
I've just pushed changes to the 'fairwaves/umtrx' branch which allow
UHD to actually control UmTRX tuning. This means that now we don't
need to calculate Rx/Tx frequencies by hands to run OpenBTS - it will
tune automatically. I've updated the wiki to reflect those changes as
well.
Changes are based on the Sergey Kostanbaev's work to move all our
LMS6002 control from umtrx_lms.py script to the UHD. The next most
important things to get working there are:
* gains control aka VGA1/VGA2 in LMS
* antenna control aka PA/LNA selection in LMS
* bandwidth filtering control aka LPF filters in LMS
* automatic calibration utilities
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi guys,
Could anyone tell me, the software guy, what may be the purpose of
VCOREG block in LMS6002D (Figure 3.4 at the Programming Guide)? In our
current code it's always powered down and not used, and I just wonder
whether it could be used for frequency hopping and what are other
potential uses. If I understand correctly, it's a kind of fine tuning
for the PLL output frequency.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi,
Very nice to see the progress UmRTX.
I checked out the git found the GPS 1pps signal was terminated to
FPGA, and wonder how the discipline algorithm was implemented. Someone
would give me a hint or introductory?
thanks in advance.
Regards.
Jerry
Hi Thomas,
I recall you had some patch to add a second Tx channel to the host
UHD. Could you push it to git or send as a patch here? We're testing
dual-channel FPGA firmware now and it would be of good help.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi all,
I've started putting together a ToDo list for UmTRX features which are
missing support on the host side or the FPGA side. I invite everyone
to add more tickets, fill details in existing tickets and discuss
implementation strategies in comments.
You could use this filter in our issues tracker to select at the tasks
open at the moment:
http://code.google.com/p/umtrx/issues/list?can=2&q=label%3AComponent-Host
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Andrey Sviyazov,
How much space do we have in the EEPROM right now?
I'm thinking which calibration data we could store there and which we
should store on a host.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi all,
Today we've received first units of UmTRXv2 from a fab. The unit is lovely
to look at - find the picture attached. I hope it will show no less great
performance when we turn it on.
In addition to fixed bugs this version has following major changes. I may
have forgotten something, but these are the most important changes:
* better form factor (10x16cm Eurocard)
* doesn't have RF switches on board (the're moved to a frontend for higher
flexibility)
* newer GPS module (EB-570)
* U.FL connectors by default (to simplify automated mounting)
* optional connector for external front panel (for waterproof casing)
* tantalum capacitors instead everywhere (for longer life)
* wider input power voltage range (8-28VDC)
We consider this version as pre-production. I.e. it will go into production
if there are no serious bugs. Now our task is to bring up the board and
check for all possible bugs before we go forward.
PS White squares on the picture is not because we obscure the photo - it's
white thermal pads which the fab placed atop of chips instead of placing
them at the bottom of PCB.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi Daud,
I've copied the mailing list, as I believe the question belongs there.
On Wed, Sep 19, 2012 at 1:20 AM, Daud Suleiman <msdaudi(a)gmail.com> wrote:
> I am very excited and glad and happy for the UmTRX project. I would like to
> know if you have plans for stacking capability for the RF frontend. I am
> assuming that there is only 2TXs. Int he event that a client needs more TXs,
> say 12TXs, have you any plans to stack as many RF frontends and or UmTRXs?
Yes, we have an option to stack UmTRX'es, but it is only to share
clock source and/or GPS source, i.e. you still have to connect each
UmTRX to the Ethernet. As long as connecting to an Ethernet switch
works fine, so we don't see this as an issue.
Later we may consider implementing true stacking when stacked units
share Ethernet port, like with USRPs. This might be a useful endeavor,
but we don't want to dive into this until we have everything else
settled.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi all,
Some good news for today. We've had a small fairwaves hackathon here
in Moscow and we've done a good progress in UmTRX development. I'm
quite exhausted, thus in short:
1. A software issue has been fixed in PLL tuning code. It works
reliably now. Previously it didn't correctly handle edge cases when
the best VCOCAP value was at the end of a range.
2. A software issue has been fixed in automatic LMS calibration code.
Turns out a process described in the datasheet is not complete - you
have read FAQ, question 4.7 for an amendment.
3. Now we correctly select Rx input. You have to change _two_
registers to do that - 0x75 and 0x25. This wasn't obvious from the
brief reading of the manual.
4. A hardware bug was fixed - RF diversity switch required a bias to
work correctly. Luckily we decided to move the switch from the main
board to a frontend in the rev2 of UmTRX. So we don't have to re-make
the UmTRX schematics.
Huge thanks to Andrey Sviyazov ("RF guy"), Andrew Karpenkov ("FPGA
guy") and Srdjan Milenkovic ("remote LimeMicro guy") for going through
all the issues.
Fixes for the code will be pushed to github in the next few days after
I clean it up.
PS Another good news is that we should have first UmTRXv2 units on
hands in the next few days, when we get them from customs. Can't wait
to put my hands on them.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Thomas,
Do you have an idea why we get this messages when running OpenBTS?
Also we configured OpenBTS to output all received bursts to a screen
and it looks like it starts receiving a lot of noise. Then this noise
almost stops and shows only sometimes.
$ tail -f syslog
Sep 6 19:13:16 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: An internal send buffer
has emptied at 826.035 sec.
Sep 6 19:13:16 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: Packet time was too late
or too early at 826.037 sec.
Sep 6 19:13:47 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: An internal send buffer
has emptied at 856.255 sec.
Sep 6 19:13:47 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: Packet time was too late
or too early at 856.257 sec.
Sep 6 19:13:47 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: Packet time was too late
or too early at 856.257 sec.
Sep 6 19:14:04 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: An internal send buffer
has emptied at 874.005 sec.
Sep 6 19:14:04 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: Packet time was too late
or too early at 874.009 sec.
Sep 6 19:14:04 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: Packet time was too late
or too early at 874.009 sec.
Sep 6 19:14:07 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: An internal send buffer
has emptied at 877.01 sec.
Sep 6 19:14:07 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: Packet time was too late
or too early at 877.013 sec.
Sep 6 19:14:07 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: Packet time was too late
or too early at 877.013 sec.
Sep 6 19:14:09 kluchnikov transceiver:
ERR 3043572592 UHDDevice.cpp:785:recv_async_msg: An internal send buffer
has emptied at 878.466 sec.
Sep 6 19:14:09 kluchnikov transceiver: ERR 3043572592
UHDDevice.cpp:785:recv_async_msg: Packet time was too late or too early at
878.468 sec.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru
Hi All,
I added control logic of LMS reset pins into ZPU firmware (commit
25a89e337b98f89d542a8bd51a3bfb6dc2a9f441
<https://github.com/chemeris/UHD-Fairwaves/commit/25a89e337b98f89d542a8bd51a…>at
the akarpenkov/dual-channel branch).
I need to take control under Diversity switches and LMS reset pins from
host. As I understand, python script "umtrx_ctrl.py" is not able write FPGA
registers, it's can talk only with SPI devices.
Max, Sylvain or anyone else, can you help me get access to FPGA registers
(they connected to wishbone bus) from host? I'm not very good at
programming on python..
UHD can do this (example here: host\lib\usrp\usrp2\usrp2_impl.cpp:530).
Also I added second RX and TX channels to the FPGA firmware and according
with that changed memory maps in ZPU and HOST firmwares (all changes at
the akarpenkov/dual-channel branch on github).
Work of TX and RX DSP 2 units I can't check due to complete lack of support
in the HOST software. Could anyone make needed changes at HOST firmware?
Regards,
Andrew Karpenkov