1
0
mirror of https://github.com/f4exb/sdrangel.git synced 2024-11-09 01:56:05 -05:00
sdrangel/plugins/channelrx/remotesink
Davide Gerhard f61d1c3908
add gettimeofday() compatibility function for windows
plugins that need that:
  - remotesink
  - remotesource
2019-05-28 15:19:19 +02:00
..
CMakeLists.txt add gettimeofday() compatibility function for windows 2019-05-28 15:19:19 +02:00
readme.md Remote sink and input: update documentation 2019-04-30 21:23:49 +02:00
remotesink.cpp add gettimeofday() compatibility function for windows 2019-05-28 15:19:19 +02:00
remotesink.h Single channel API 2019-05-09 17:27:12 +02:00
remotesinkgui.cpp Propagate change to channel UIs 2019-05-09 21:07:05 +02:00
remotesinkgui.h Remote channel sink: decimation and shift: core changes 2019-04-26 01:27:36 +02:00
remotesinkgui.ui Remote channel sink: decimation and shift: GUI changes 2019-04-25 15:48:47 +02:00
remotesinkplugin.cpp fix windows code to build with MSVC 2019-05-28 15:19:19 +02:00
remotesinkplugin.h Single channel API 2019-05-09 17:27:12 +02:00
remotesinksettings.cpp Remote channel sink: decimation and shift: GUI changes 2019-04-25 15:48:47 +02:00
remotesinksettings.h Remote channel sink: decimation and shift: GUI changes 2019-04-25 15:48:47 +02:00
remotesinkthread.cpp cm256cc: fix path and pkgconfig discovery 2019-04-15 15:39:57 +02:00
remotesinkthread.h cm256cc: fix path and pkgconfig discovery 2019-04-15 15:39:57 +02:00

Remote sink channel plugin

Introduction

This plugin sends I/Q samples from the baseband via UDP to a distant network end point. It can use FEC protection to prevent possible data loss inherent to UDP protocol.

It is present only in Linux binary releases.

Build

The plugin will be built only if the CM256cc library is installed in your system. For CM256cc library you will have to specify the include and library paths on the cmake command line. Say if you install cm256cc in /opt/install/cm256cc you will have to add -DCM256CC_DIR=/opt/install/cm256cc to the cmake commands.

Interface

Remote sink channel plugin GUI

1: Decimation factor

The device baseband can be decimated in the channel and its center can be selected with (5). The resulting sample rate of the I/Q stream sent over the network is the baseband sample rate divided by this value. The value is displayed in (2).

2: Network I/Q stream sample rate

This is the sample rate in kS/s of the I/Q stream sent over the network.

3: Half-band filters chain sequence

This string represents the sequence of half-band filters used in the decimation from device baseband to resulting I/Q stream. Each character represents a filter type:

  • L: lower half-band
  • H: higher half-band
  • C: centered

4: Center frequency shift

This is the shift of the channel center frequency from the device center frequency. Its value is driven by the device sample rate , the decimation (1) and the filter chain sequence (5).

5: Half-band filter chain sequence

The slider moves the channel center frequency roughly from the lower to the higher frequency in the device baseband. The number on the right represents the filter sequence as the decimal value of a base 3 number. Each base 3 digit represents the filter type and its sequence from MSB to LSB in the filter chain:

  • 0: lower half-band
  • 1: centered
  • 2: higher half-band

6: Distant address

IP address of the distant network interface from where the I/Q samples are sent via UDP

7: Data distant port

Distant port to which the I/Q samples are sent via UDP

8: Validation button

When the return key is hit within the address (1) or port (2) the changes are effective immediately. You can also use this button to set again these values.

9: Desired number of FEC blocks per frame

This sets the number of FEC blocks per frame. A frame consists of 128 data blocks (1 meta data block followed by 127 I/Q data blocks) and a variable number of FEC blocks used to protect the UDP transmission with a Cauchy MDS block erasure correction. The two numbers next are the total number of blocks and the number of FEC blocks separated by a slash (/).

10: Delay between UDP blocks transmission

This sets the minimum delay between transmission of an UDP block (send datagram) and the next. This allows throttling of the UDP transmission that is otherwise uncontrolled and causes network congestion.

The value is a percentage of the nominal time it takes to process a block of samples corresponding to one UDP block (512 bytes). This is calculated as follows:

  • Sample rate on the network: SR
  • Delay percentage: d
  • Number of FEC blocks: F
  • There are 127 blocks of I/Q data per frame (1 meta block for 128 blocks) and each I/Q data block of 512 bytes (128 samples) has a 8 bytes header (2 samples) thus there are 126 samples remaining effectively. This gives the constant 127*126 = 16002 samples per frame in the formula

Formula: ((127 ✕ 126 ✕ d) / SR) / (128 + F)

The percentage appears first at the right of the dial button and then the actual delay value in microseconds.