mirror of
https://github.com/f4exb/sdrangel.git
synced 2024-11-22 08:04:49 -05:00
XTRX: updated documentation
This commit is contained in:
parent
bbec66c662
commit
e3069d3a69
11
Readme.md
11
Readme.md
@ -43,6 +43,7 @@ Since version 3 transmission or signal generation is supported for BladeRF, Hack
|
||||
- [HackRF output plugin](https://github.com/f4exb/sdrangel/tree/dev/plugins/samplesink/hackrfoutput)
|
||||
- [LimeSDR output plugin](https://github.com/f4exb/sdrangel/tree/dev/plugins/samplesink/limesdroutput)
|
||||
- [PlutoSDR output plugin](https://github.com/f4exb/sdrangel/tree/dev/plugins/samplesink/plutosdroutput)
|
||||
- [XTRX output plugin](https://github.com/f4exb/sdrangel/tree/dev/plugins/samplesink/xtrxoutput)
|
||||
- [File output or file sink plugin](https://github.com/f4exb/sdrangel/tree/dev/plugins/samplesink/filesink)
|
||||
- [Remote device via Network with SDRdaemon](https://github.com/f4exb/sdrangel/tree/dev/plugins/samplesink/sdrdaemonsink) Linux only
|
||||
|
||||
@ -204,15 +205,19 @@ If you use your own location for libmirisdr-4 install directory you need to spec
|
||||
|
||||
<h2>XTRX</h2>
|
||||
|
||||
Compile from source.
|
||||
Experimental. Compile from source.
|
||||
|
||||
[XTRX](https://www.crowdsupply.com/fairwaves/xtrx) is supported through the set of [xtrx libraries](https://github.com/xtrx-sdr/images).
|
||||
[XTRX](https://xtrx.io) is supported through the set of [xtrx libraries](https://github.com/xtrx-sdr/images).
|
||||
|
||||
If you use your own location for the install directory (ex: `/opt/install/xtrx-images`) you need to specify it with `-DXTRX_DIR=/opt/install/xtrx-images` on the `cmake` command line.
|
||||
|
||||
In addition before starting SDRangel you have to add the library directory to the `LD_LIBRARY_PATH` variable with `export LD_LIBRARY_PATH=/opt/install/xtrx-images/lib:$LD_LIBRARY_PATH`.
|
||||
|
||||
⚠ Although you will find a plugin for the transmission side transmission with XTRX is not actually working. Reception is not very stable either particularly with sample rates lower than 5 MS/s.
|
||||
⚠ It seems eception is not very stable either particularly with sample rates lower than 5 MS/s. You may need to stop and restart the device (stop/start button) to recover.
|
||||
|
||||
⚠ Right after (re)start you may need to move the main frequency dial back and forth if you notice that you are not on the right frequency.
|
||||
|
||||
⚠ At the moment simultaneous Rx and Tx is not supported.
|
||||
|
||||
<h1>Plugins for special devices</h1>
|
||||
|
||||
|
BIN
doc/img/XTRXOutput_plugin.png
Normal file
BIN
doc/img/XTRXOutput_plugin.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 34 KiB |
BIN
doc/img/XTRXOutput_plugin.xcf
Normal file
BIN
doc/img/XTRXOutput_plugin.xcf
Normal file
Binary file not shown.
133
plugins/samplesink/xtrxoutput/readme.md
Normal file
133
plugins/samplesink/xtrxoutput/readme.md
Normal file
@ -0,0 +1,133 @@
|
||||
<h1>XTRX output plugin</h1>
|
||||
|
||||
<h2>Introduction</h2>
|
||||
|
||||
This output sample sink plugin sends its samples to a [XTRX device](https://xtrx.io).
|
||||
|
||||
XTRX is a 2x2 MIMO device so it has two transmitting channels that can run concurrently. To activate the second channel when the first is already active just open a new sink tab in the main window (Devices -> Add sink device) and select the same LimeSDR device.
|
||||
|
||||
⚠ Simultaneous Tx and Rx is not supported at this moment
|
||||
|
||||
⚠ You need a hardware interpolation of at least 4 (default)
|
||||
|
||||
<h2>Build</h2>
|
||||
|
||||
The plugin will be built only if XTRX libraries are installed in your system.
|
||||
|
||||
If libraries are installed in a custom place like `/opt/install/xtrx-images` add the following defines on `cmake` command line:
|
||||
|
||||
`-DXTRX_DIR=/opt/install/xtrx-images`
|
||||
|
||||
<h2>Interface</h2>
|
||||
|
||||
![XTRX output plugin GUI](../../../doc/img/XTRXOutput_plugin.png)
|
||||
|
||||
<h3>1: Start/Stop</h3>
|
||||
|
||||
Device start / stop button.
|
||||
|
||||
- Blue triangle icon: device is ready and can be started
|
||||
- Green square icon: device is running and can be stopped
|
||||
- Magenta (or pink) square icon: an error occurred. In the case the device was accidentally disconnected you may click on the icon to stop, plug back in, check the source on the sampling devices control panel and start again.
|
||||
|
||||
<h3>2: DAC sample rate</h3>
|
||||
|
||||
This is the sample rate at which the DAC runs in kS/s (k) or MS/s (M) after hardware interpolation (9). Thus this is the host to device sample rate (11) multiplied by the hardware interpolation factor (9). Please note that a hardware decimation of 4 is required for the device to work properly.
|
||||
|
||||
<h3>3: Center frequency</h3>
|
||||
|
||||
This is the center frequency of transmission in kHz.
|
||||
|
||||
<h3>4: Channel number</h3>
|
||||
|
||||
LimeSDR is a 2x2 MIMO device so it has two transmitting channels. This shows the corresponding Tx channel index (0 or 1).
|
||||
|
||||
|
||||
<h3>5: Stream sample rate</h3>
|
||||
|
||||
Baseband I/Q sample rate in kS/s. This is the device to host sample rate (11) divided by the software interpolation factor (10).
|
||||
|
||||
<h3>6: NCO toggle</h3>
|
||||
|
||||
The button is lit when NCO is active and dark when inactive.
|
||||
|
||||
Use this button to activate/deactivate the TSP NCO. The LMS7002M chip has an independent NCO in each Tx channel that can span the bandwidth sent to the DAC. This effectively allows non zero digital IF.
|
||||
|
||||
<h3>7: NCO frequency shift</h3>
|
||||
|
||||
This is the frequency shift applied when the NCO is engaged thus the actual LO frequency is the center frequency of transmission minus this value. Use the thumbwheels to adjust frequency as done with the LO (1.1). Pressing shift simultaneously moves digit by 5 and pressing control moves it by 2. The boundaries are dynamically calculated from the LO center frequency, sample rate and hardware interpolation factor.
|
||||
|
||||
☞ In the LMS7002M TSP block the NCO sits after the interpolator (see Fig.14 of the [datasheet](http://www.limemicro.com/wp-content/uploads/2015/09/LMS7002M-Data-Sheet-v2.8.0.pdf) p.7) so it runs at the actual DAC rate. Hence the NCO limits are calculated as +/- half the device to host sample rate multiplied by the hardware interpolation factor. For example with a 4 MS/s device to host sample rate (10) and a hardware interpolation of 16 (9) you have +/- 32 MHz span around the LO for the NCO. In this example you can tune all HF frequencies with the center frequency set at its lowest (30 MHz).
|
||||
|
||||
<h3>8: External clock control</h3>
|
||||
|
||||
Use this button to open a dialog that lets you choose the external clock frequency and enable or disable it. When disabled the internal 30.72 MHz VCTCXO is used.
|
||||
|
||||
![LimeSDR input plugin gain GUI](../../../doc/img/LimeSDR_plugin_extclock.png)
|
||||
|
||||
<h4>8.1: External clock frequency</h4>
|
||||
|
||||
Can be varied from 5 to 300 MHz
|
||||
|
||||
Use the thumbwheels to adjust frequency as done with the LO (1.1). Pressing shift simultaneously moves digit by 5 and pressing control moves it by 2. The boundaries are dynamically calculated from the LO center frequency, sample rate and hardware decimation factor.
|
||||
|
||||
<h4>8.2: Enable/disable external clock input</h7A>
|
||||
|
||||
Use this checkbox to enable or disable the external clock input
|
||||
|
||||
<h4>8.3: Confirm changes</h4>
|
||||
|
||||
Use the "OK" button to confirm your changes
|
||||
|
||||
<h4>8.4: Dismiss changes</h4>
|
||||
|
||||
Use the "Cancel" button to dismiss your changes
|
||||
|
||||
<h3>9: LMS7002M hardware interpolation factor</h3>
|
||||
|
||||
The TSP block in the LMS7002M hardware has an interpolation chain that acts on both Tx channels. It is composed of 5 halfband interpolation stages and therefore can achieve interpolation between 1 (no interpolation) and 32 in increasing powers of 2: 1, 2, 4, 8, 16, 32. Please note that a factor of at least 4 is required. Lower values are experimental.
|
||||
|
||||
Thus the actual sample rate of the DAC is the stream sample rate (11) multiplied by this factor. In the screenshot example this yields a 12.288 MS/s rate at the DAC (3.072 * 4).
|
||||
|
||||
<h3>10: Software interpolation factor</h3>
|
||||
|
||||
The I/Q stream from the baseband is upsampled by a power of two by software inside the plugin before being sent to the LimeSDR device. Possible values are increasing powers of two: 1 (no interpolation), 2, 4, 8, 16, 32.
|
||||
|
||||
<h3>11: Host to device stream sample rate</h3>
|
||||
|
||||
This is the LMS7002M device to/from host stream sample rate in S/s. It is the same for the Rx and Tx systems.
|
||||
|
||||
Use the wheels to adjust the sample rate. Pressing shift simultaneously moves digit by 5 and pressing control moves it by 2. Left click on a digit sets the cursor position at this digit. Right click on a digit sets all digits on the right to zero. This effectively floors value at the digit position. Wheels are moved with the mousewheel while pointing at the wheel or by selecting the wheel with the left mouse click and using the keyboard arrows.
|
||||
|
||||
The LMS7002M uses the same clock for both the ADCs and DACs therefore this sample rate affects all of the 2x2 MIMO channels.
|
||||
|
||||
<h3>12: Tx hardware filter bandwidth</h3>
|
||||
|
||||
This is the Tx hardware filter bandwidth in kHz in the LMS7002M device for the given channel. Boundaries are updated automatically but generally are from 5 to 130 MHz in 1 kHz steps. Use the wheels to adjust the value. Pressing shift simultaneously moves digit by 5 and pressing control moves it by 2.
|
||||
|
||||
<h3>13: LMS002M power saving mode</h3>
|
||||
|
||||
<h3>14: Gain</h2>
|
||||
|
||||
Use this slider to adjust the PAD gain of the Tx chain. With the current version of libxtrx this does not seem to be effective.
|
||||
|
||||
<h3>15: Antenna selection</h3>
|
||||
|
||||
- ** Hi **: Tx high range
|
||||
- ** Wi **: Tx wide range: you should use this one (default)
|
||||
|
||||
<h3>16: Stream status indicator</h3>
|
||||
|
||||
This label turns green when status can be obtained from the current stream. Usually this means that the stream is up and running but not necessarily streaming data. The various status elements appear next on the same line (16, 17, 18)
|
||||
|
||||
<h3>17: GPSDO lock indicator</h3>
|
||||
|
||||
This label turns green when the GPS used for the GPSDO is locked.
|
||||
|
||||
<h3>18: Stream global (all Tx) throughput in MB/s</h3>
|
||||
|
||||
This is the stream throughput in MB/s and is usually about 3 times the sample rate for a single stream and 6 times for a dual Tx stream. This is due to the fact that 12 bits samples are used and although they are represented as 16 bit values only 12 bits travel on the USB link.
|
||||
|
||||
<h3>19: Board temperature</h3>
|
||||
|
||||
This is the board temperature in degrees Celsius updated every ~5s. Before the first probe the display marks "00C" this is normal.
|
@ -2,11 +2,11 @@
|
||||
|
||||
<h2>Introduction</h2>
|
||||
|
||||
This input sample source plugin gets its samples from a [XTRX device](https://www.crowdsupply.com/fairwaves/xtrx).
|
||||
This input sample source plugin gets its samples from a [XTRX device](https://xtrx.io).
|
||||
|
||||
XTRX is a 2x2 MIMO device so it has two receiving channels that can run concurrently. To activate the second channel when the first is already active just open a new source tab in the main window (Devices -> Add source device) and select the same LimeSDR device. You may need to change frequency back and forth in case reception is not working properly.
|
||||
|
||||
Sometimes XTRX does not start properly and the spectrum looks frozen. In such a case just stop and start the device again.
|
||||
⚠ Sometimes XTRX does not start properly and the spectrum looks frozen. In such a case just stop and start the device again.
|
||||
|
||||
<h2>Build</h2>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user