Project

General

Profile

LimeSDR Family » History » Version 39

roh, 10/01/2019 02:39 PM

1 1 laforge
{{>toc}}
2
3 30 pespin
h1. LimeSDR USB
4 1 laforge
5 4 laforge
The "LimeSDR":https://myriadrf.org/projects/limesdr/ is a low-cost SDR board featuring the Lime Microsystems LMS7002 RF chip.
6
7 20 laforge
!{width:700px}LimeSDR_transp_3.jpg!
8
9 4 laforge
Key characteristics include:
10
* RF Transceiver: Lime Microsystems LMS7002M MIMO FPRF
11
* FPGA: Altera Cyclone IV EP4CE40F23 – also compatible with EP4CE30F23
12 6 ahuemer
* Memory: 256 MBytes DDR2 SDRAM
13 4 laforge
* USB 3.0 controller: Cypress USB 3.0 CYUSB3014-BZXC
14
* Oscillator: Rakon RPT7050A @ 30.72MHz
15
* Continuous frequency range: 100 kHz – 3.8 GHz
16
* Bandwidth: 61.44 MHz
17
* RF connection: 10 U.FL connectors (6 RX, 4 TX)
18
* Power Output (CW): up to 10 dBm
19
* Multiplexing: 2×2 MIMO
20
* Power: micro USB connector or optional external power supply
21
* Status indicators: programmable LEDs
22
* Dimensions: 100 mm x 60 mm
23 1 laforge
24 3 laforge
h2. RF Output Power
25
26 39 roh
* +11dB in gsm900 (arfcn 5)
27
* +3dB in dcs1800 (arfcn 871)
28
29
in dcs1800 a reduction in rx power improves phase noise (e.g. max_power_red 5)
30
31
there is a graph from myriad showing the power vs frequency plot in this thread: https://discourse.myriadrf.org/t/limesdr-s-maximum-transmitting-power-at-different-frequencies/1649
32 1 laforge
33
h2. Clock
34
35
The on-board clock is a 250ppb VCTCXO.  GSM strictly requires 30ppb, but 250ppb _should_  be sufficient for laboratory use.
36
37
h3. Clock Calibration
38
39
TBD
40
41
h3. Using external clock reference
42
43
TBD
44
45 19 pespin
h1. LimeSDR Mini
46
47
The "LimeSDR Mini":https://myriadrf.org/projects/limesdr/ is a smaller, less expensive version of the original LimeSDR.
48
49 22 laforge
!{width:600px}limesdr-mini-1024x561.jpg!
50
51 19 pespin
Key characteristics include:
52
* RF Transceiver: Lime Microsystems LMS7002M FPRF
53
* FPGA: Altera MAX 10 (10M16SAU169C8G)
54
* EEPROM memory: 2 x 128 KB for RF transciever MCU firmware and data
55
* Flash memory: 1 x 4 MB flash memory for data
56
* USB 3.0 controller: FTDI FT601
57
* Rakon 30.72 MHz VCTCXO
58
* Continuous frequency range: 10 MHz – 3.5 GHz
59
* Bandwidth: 30.72 MHz
60
* RF Connection: 2 x SMA connectors (each can be switched between high and low frequency bands) + 1x U.FL REF CLK
61
* Power Output (CW): up to 10 dBm
62
* Dimensions: 69 mm x 31.4 mm
63
64
h2. RF Output Power
65
66
TBD
67
68 37 roh
h2. Clock
69
70 38 roh
internal clock is ok, but not stable enough (longterm) to run a gsm network. for short term lab use it should be ok. (few minutes).
71
providing an external clock is tricky:
72
according to the spec from the clockchip used (ti LMK00105) the input signal needs to have "sharp rectangles 2V/ns or better".
73
this is a limitation of the LimeSDR mini due to no extra pll chip being present, in contrast to the LimeSDR-USB.
74 37 roh
75 35 roh
h1. LimeNet Micro
76 21 laforge
77 35 roh
!{width:700px}640px-LimeSDR-Micro_v2.1_board.png!
78 21 laforge
79 36 roh
LimeNet Micro is a small all-in-one board combining the sdr, a gpsdo and some rf filters with a raspberry pi compute module3.
80
Due to the integrated gpsdo it should have no problems running tdma networks like gsm.
81
82
setup: install default raspbian (see getting started link below) and osmocom latest or nightly feeds.
83
config: use LNAL or LNAH for rx-path, BAND1 for tx
84
85
h2. RF Output Power
86
87
* +7dB in gsm900 (arfcn 5)
88
* -5dB in dcs1800 (arfcn 871)
89
90
in dcs1800 a reduction in rx power improves phase noise (e.g. max_power_red 5)
91
92
h2. Clock
93
94
do not select a specific clock on LimeNet Micro. (remove clock-ref line)
95
when this type of hardware is detected osmo-trx defaults to the gps synchronized clock from the fpga (gpsdo).
96
see led4/led5 for gps status https://wiki.myriadrf.org/LimeNET-Micro_v2.1_hardware_description#Indication_LEDs
97
98
h2. further information
99
100
https://wiki.myriadrf.org/LimeNET_Micro
101
https://wiki.myriadrf.org/Getting_Started_with_the_LimeNET-Micro
102
https://wiki.myriadrf.org/LimeNET-Micro_v2.1_hardware_description
103 1 laforge
104 35 roh
h1. LimeSDR PCIe
105 21 laforge
106 35 roh
!{width:700px}limesdr-pcie-1-1_jpg_project-body.jpg!
107
108
TBD
109 34 roh
110 19 pespin
h1. OsmoTRX on LimeSDR
111 1 laforge
112 32 pespin
In terms of OsmoTRX for LimeSDR, we now have @osmo-trx-lms@ which avoids the previously complex driver stack with UHD, SoapyUHD, SoapySDR, etc. All you need in terms of specific dependencies is:
113
* "LimeSuite":https://github.com/myriadrf/LimeSuite.git containing the actual drivers and utilities for LimeSDR (*version 17.09 or later required*, last release @18.06.0@ or @master@ really advised)
114
** for LimeSDR-mini, you will need 17.10 or later (last release @18.06.0@ or @master@ really advised)
115 1 laforge
116 32 pespin
If your distro doesn't ship with a LimeSuite new enough, it is advised that you install LimeSuite from osmocom repositories, see [[cellular-infrastructure:MacroBinaryPackages]].
117
118
119 1 laforge
{{graphviz_link()
120 5 laforge
digraph G{
121
  rankdir = LR;
122 29 laforge
  LimeSDR -> LimeSuite [label = "USB/libusb"];
123 5 laforge
  LimeSuite -> OsmoTRX [label = "osmo-trx-lms"];
124
}
125 1 laforge
}}
126
127
h3. Verifying the driver stack
128
129
You can ensure that LimeSuite recognizes your device using the *LimeUtil* part of LimeSuite:
130
131
<pre>
132 18 pespin
$ LimeUtil --find
133
  * [LimeSDR-USB, media=USB 3.0, module=STREAM, addr=1d50:6108, serial=0009060B00xxyyzz]
134
</pre>
135 27 laforge
136 31 pespin
h3. Running osmo-trx-lms with LimeSDR
137
138 33 pespin
If @rt-prio@ is set in .cfg file, running as root may be required.
139 31 pespin
140
A sample cfg file to run @osmo-trx-lms@ with a LimeSDR device can be found in @osmo-trx.git@ in @doc/examples/osmo-trx-lms/osmo-trx-limesdr.cfg@.
141
142
<pre>
143
osmo-trx-lms -C osmo-trx.git/doc/examples/osmo-trx-lms/osmo-trx-limesdr.cfg
144
</pre>
145
146 27 laforge
h2. Other LimeSDR related information
147
148
{{child_pages()}}
Add picture from clipboard (Maximum size: 48.8 MB)