Sundtek Wiki - User contributions [en]

Driver Installation

2025-10-09T04:57:20Z

Sundtek: /* Kaffeine */

== Driver Installation ==

=== Linux ===

==== Regular Linux with Terminal ====

On linux the driver Installation is quite easy, just download the netinstall script and it will install the correct driver. The install script will pick the correct build for your particular architecture (ARM, MIPS, PPC, SH4, X86).

<pre>
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh
</pre>

==== Kaffeine ====

We have patched the latest Kaffeine Version (8. Oct 2024) to detect our devices again.

Install the updated Kaffeine Version:
<pre>
cd /tmp
wget http://sundtek.de/support/updatekaffeine.sh
sudo bash updatekaffeine.sh
</pre>

This script will download and install the latest Kaffeine Version from the opensuse build system, which fortunately also provides packages for Ubuntu.

https://build.opensuse.org/package/show/home:mrec/kaffeine-ubuntu

----

The patch:
* https://www.sundtek.de/support/kaffeine-2.0.18_support_sundtek_devices.diff

the binary:
* https://www.sundtek.de/support/kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb

The binary can be installed the following way:
<pre>
cd /tmp
sudo -s
wget http://sundtek.de/support/kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb
apt install ./kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb
apt hold kaffeine # to lock this version on the system and prevent auto updates.
</pre>

==== LibreElec ====

LibreElec comes with a Sundtek Addon, this will take care about the installation of our driver on this system. 
Do not use sundtek_netinst.sh on LibreElec - because LibreElec uses custom Paths and custom startup Scripts - everything will be handled by the Sundtek Addon!

==== Docker ====

* https://sundtek.de/wiki/index.php?title=Docker

==== Deutsche Anleitung / German manual ====

https://support.sundtek.com/index.php?topic=2.0

==== Synology NAS ====

===== Deutsch =====

Unter Synology muss zuerst TVHeadend im Paketmanager und anschließend der Treiber installiert werden. Der Sundtek Treiber nimmt einige Modifikationen im TVHeadend Startskript vor und muss daher zuletzt installiert werden.

Im Paketmanager folgenden Link hinzufügen: http://sundtek.de/synology

Anschließend gibt sich ein App Sundtek Linux Treiber unter Community im Paketmanager.

Bitte beachten DSM 7.0 Beta wird von dem Paket aktuell noch nicht unterstützt (Synology muss hier noch die Dokumentation aktualisieren, der Treiber lässt sich dort nur auf der Konsole installieren).

===== English =====

In Synology first tvheadend should be installed, and afterwards the driver. The driver installation will
modify the tvheadend startup script a little bit.

Add following link in the Synology Package Manager:
http://sundtek.de/synology

Afterwards there's an app Sundtek Linux Driver available in the Community Section of the package manager.

Driver Installation

2025-10-03T07:16:20Z

Sundtek: /* Kaffeine */

== Driver Installation ==

=== Linux ===

==== Regular Linux with Terminal ====

On linux the driver Installation is quite easy, just download the netinstall script and it will install the correct driver. The install script will pick the correct build for your particular architecture (ARM, MIPS, PPC, SH4, X86).

<pre>
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh
</pre>

==== Kaffeine ====

We have patched the latest Kaffeine Version (8. Oct 2024) to detect our devices again.

Install the updated Kaffeine Version:
<pre>
sudo -s
cd /tmp
wget http://sundtek.de/support/updatekaffeine.sh
chmod +x
./updatekaffeine.sh
apt install kaffeine
</pre>

This script will download and install the latest Kaffeine Version from the opensuse build system, which fortunately also provides packages for Ubuntu.

https://build.opensuse.org/package/show/home:mrec/kaffeine-ubuntu

----

The patch:
* https://www.sundtek.de/support/kaffeine-2.0.18_support_sundtek_devices.diff

the binary:
* https://www.sundtek.de/support/kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb

The binary can be installed the following way:
<pre>
cd /tmp
sudo -s
wget http://sundtek.de/support/kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb
apt install ./kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb
apt hold kaffeine # to lock this version on the system and prevent auto updates.
</pre>

==== LibreElec ====

LibreElec comes with a Sundtek Addon, this will take care about the installation of our driver on this system. 
Do not use sundtek_netinst.sh on LibreElec - because LibreElec uses custom Paths and custom startup Scripts - everything will be handled by the Sundtek Addon!

==== Docker ====

* https://sundtek.de/wiki/index.php?title=Docker

==== Deutsche Anleitung / German manual ====

https://support.sundtek.com/index.php?topic=2.0

==== Synology NAS ====

===== Deutsch =====

Unter Synology muss zuerst TVHeadend im Paketmanager und anschließend der Treiber installiert werden. Der Sundtek Treiber nimmt einige Modifikationen im TVHeadend Startskript vor und muss daher zuletzt installiert werden.

Im Paketmanager folgenden Link hinzufügen: http://sundtek.de/synology

Anschließend gibt sich ein App Sundtek Linux Treiber unter Community im Paketmanager.

Bitte beachten DSM 7.0 Beta wird von dem Paket aktuell noch nicht unterstützt (Synology muss hier noch die Dokumentation aktualisieren, der Treiber lässt sich dort nur auf der Konsole installieren).

===== English =====

In Synology first tvheadend should be installed, and afterwards the driver. The driver installation will
modify the tvheadend startup script a little bit.

Add following link in the Synology Package Manager:
http://sundtek.de/synology

Afterwards there's an app Sundtek Linux Driver available in the Community Section of the package manager.

Docker

2025-09-09T00:38:25Z

Sundtek: /* Forum Posts */

== Docker ==

=== External Documentation ===

* Synology Wiki (German):
https://www.synology-wiki.de/index.php/TvHeadend_mit_Docker_und_Sundtek_SkyTV_Ultimate

=== On the host ===

This is the step that has to be taken care about on the native host (outside of the docker image). The driver can run in non-privileged mode inside the docker.
Various libc / musl / uclibc images are supported.

If you want to install the linux driver in a docker environment a few things need to be taken care of.

==== Device Nodes on the Host ====

Very important /dev/bus/usb contain the interface to the raw USB devices which is used by the sundtek driver.
However one special (and a little bit messy part of docker) is that it also needs to know the major/minor IDs which are allowed to be forwarded - before creating and before starting the docker image, that's why nodes in /dev/dvb need to be pre-created on the host.

If you install the driver on the host you should create a configuration file which contains following text:
enabledocker=on

this will cause that the driver on the native host (not in the docker) will create dummy adapter nodes in /dev/dvb, the driver itself will not try to access the USB device - it will only create the files if enabledocker=on is set in the configuration file and exit immediately. 
On the host:
<pre>
sudo -s
echo "enabledocker=on" > /etc/sundtek.conf
</pre>

You can also create them manually if you want (see next section):

===== Without installing the driver on the host =====

So the driver on the host has no special function it would just create /dev/dvb devicenodes and exist immediately.
You can create those dummies manually (but those need to be there before creating the docker image and before starting the docker image)

<pre>
mkdir -p /dev/dvb/adapter0
mknod /dev/dvb/adapter0/frontend0 c 212 1
mknod /dev/dvb/adapter0/dvr0 c 212 5
mknod /dev/dvb/adapter0/demux0 c 212 3
mkdir -p /dev/dvb/adapter1
mknod /dev/dvb/adapter1/frontend0 c 212 7
mknod /dev/dvb/adapter1/dvr0 c 212 11
mknod /dev/dvb/adapter1/demux0 c 212 9
mkdir -p /dev/dvb/adapter2
mknod /dev/dvb/adapter2/frontend0 c 212 13
mknod /dev/dvb/adapter2/dvr0 c 212 17
mknod /dev/dvb/adapter2/demux0 c 212 15
</pre>

===== Synology NAS =====

You can install the driver on the host and check the option "Enable Docker" in the Configuration menu. When this is checked the driver will only create those dummy nodes on the host and exit immediately.

==== Creating a Docker Image ====

The docker itself needs to be created with some -device flags

Alpine Linux:

<pre>
docker create --name alpinelinux
--net=bridge
-p 9981:9981
-p 9982:9982
--device=/dev/dvb
--device=/dev/bus/usb
-t alpine /bin/sh
</pre>

Linuxserver / Tvheadend

<pre>
docker create \
--name=tvheadend \
--net=bridge \
-v <path to data>:/config \ <- Pfad anpassen! / modify path (and remove the comment of course)
-v <path to recordings>:/recordings \ <- Pfad anpassen! / modify path (and remove the comment of course)
-p 9981:9981 \
-p 9982:9982 \
--device=/dev/dvb \
--device=/dev/bus/usb
linuxserver/tvheadend
</pre>

=== Inside the docker ===

Inside the docker unfortunately you only have one shot if you do it wrong you have to re-create the docker and re-do this step.
Usually our customers install the drivers inside the docker in /config

To enter a docker image:
<pre>
docker exec -it tvheadend /bin/sh
</pre>

Download the netinstall script:
<pre>
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh -docker -use-custom-path /config
</pre>

The installer will rename the tvheadend binary in /usr/bin to tvheadend.bin and places a script instead which will automatically start the driver.

this will place the driver in /config

Usually you will want to mount a local directory inside the docker, this can basically be configured via the Synology Webfrontend.
When doing that you need to take care that the user inside the docker also has access to that folder otherwise you will get a permission denied.

You can use the tvheadend start script to change the permissions if you need that, /usr/bin/tvheadend add chmod 777 /path/to/videodirectory

=== Misc ===

one customer also needed to modify the preset current limit of the tuner, he had to place lnblimit=1000ma (case sensitive in sundtek.conf inside the docker)

== Unraid ==

All the sundtek devices work with Unraid. The installation is comfortably handled by a Sundtek Driver plugin in the Unraid environment. So just install the plugin and you're set.

--- the old documentation for unraid follows here, we just keep it here for the record ---

1. Set up the driver on the host system

Open a terminal as root (console) and run:
<pre>
cd /tmp
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh -dockerhost
</pre>

(this will only take care that some dummy nodes are created in /dev/dvb/, access control will be handled by major/minor numbers of the existing files. When the driver is started on the host it will exit directly due to the dockerhost flag and only create the nodes)

basically all this does is
<pre>
mkdir -p /dev/dvb/adapter0
mkdir -p /dev/dvb/adapter1
#crwxrwxrwx 1 root root 212, 1 Dec 19 20:44 frontend0
#crwxrwxrwx 1 root root 212, 5 Dec 19 20:44 dvr0
#crwxrwxrwx 1 root root 212, 3 Dec 19 20:44 demux0
mknod /dev/dvb/adapter0/frontend0 c 212 1
mknod /dev/dvb/adapter0/dvr0 c 212 5
mknod /dev/dvb/adapter0/demux0 c 212 3
#crwxrwxrwx 1 root root 212, 7 Dec 19 20:44 frontend0
#crwxrwxrwx 1 root root 212, 11 Dec 19 20:44 dvr0
#crwxrwxrwx 1 root root 212, 9 Dec 19 20:44 demux0
mknod /dev/dvb/adapter1/frontend0 c 212 7
mknod /dev/dvb/adapter1/dvr0 c 212 11
mknod /dev/dvb/adapter1/demux0 c 212 9
</pre>

2. Set up the driver inside the tvheadend docker

... install the tvheadend docker, add an extra device driver for /dev/bus/usb

open the host terminal and enter the tvheadend docker image:
<pre>
docker exec -it tvheadend /bin/sh
cd /tmp
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh -docker -use-custom-path /config
</pre>

(this will rename the tvheadend binary to tvheadend.bin and put a script in between which will start the driver inside the docker - followed by the actual tvheadend binary).

3. that's it restart the tvheadend docker.

== FAQ ==

=== Stick wird nicht im Docker angezeigt ===

Er findet leider den Stick nicht per Docker, warum auch immer…im Verzeichnis ist er aber vorhanden.
[[File:lsusbdocker.png]]

----

1. Die Pfade sollen nicht zwischen den Klammern stehen, diese sollen entfernt werden (<, >)
<pre>
-v /home/pi/tvheadend/data:/config
-v /home/pi/tvheadend/recordings:/config
</pre>
2. Zur Sicherheit kein Space zwischen --device= /dev/bus/dvb

3. ls /dev/dvb auf dem Host muss adapter1 usw . anzeigen.

Wurde der Treiber installiert, /config/opt/bin/mediaclient -e sollte den Tuner im Docker anzeigen.
https://sundtek.de/wiki/index.php?title=Docker#Inside_the_docker (so springt man in's Docker rein).

=== Forum Posts ===

* https://support.sundtek.com/index.php?topic=2394.0
* https://support.sundtek.com/index.php?topic=2394.msg20813#msg20813

Docker

2025-09-09T00:37:36Z

Sundtek: /* FAQ */

Driver Installation

2025-08-04T12:37:45Z

Sundtek:

== Driver Installation ==

=== Linux ===

==== Regular Linux with Terminal ====

On linux the driver Installation is quite easy, just download the netinstall script and it will install the correct driver. The install script will pick the correct build for your particular architecture (ARM, MIPS, PPC, SH4, X86).

<pre>
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh
</pre>

==== Kaffeine ====

We have patched the latest Kaffeine Version (8. Oct 2024) to detect our devices again.

The patch:
* https://www.sundtek.de/support/kaffeine-2.0.18_support_sundtek_devices.diff

the binary:
* https://www.sundtek.de/support/kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb

The binary can be installed the following way:
<pre>
cd /tmp
sudo -s
wget http://sundtek.de/support/kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb
apt install ./kaffeine_2.0.18+git20230226.439cd0d-1build2_amd64.deb
apt hold kaffeine # to lock this version on the system and prevent auto updates.
</pre>

==== LibreElec ====

LibreElec comes with a Sundtek Addon, this will take care about the installation of our driver on this system. 
Do not use sundtek_netinst.sh on LibreElec - because LibreElec uses custom Paths and custom startup Scripts - everything will be handled by the Sundtek Addon!

==== Docker ====

* https://sundtek.de/wiki/index.php?title=Docker

==== Deutsche Anleitung / German manual ====

https://support.sundtek.com/index.php?topic=2.0

==== Synology NAS ====

===== Deutsch =====

Unter Synology muss zuerst TVHeadend im Paketmanager und anschließend der Treiber installiert werden. Der Sundtek Treiber nimmt einige Modifikationen im TVHeadend Startskript vor und muss daher zuletzt installiert werden.

Im Paketmanager folgenden Link hinzufügen: http://sundtek.de/synology

Anschließend gibt sich ein App Sundtek Linux Treiber unter Community im Paketmanager.

Bitte beachten DSM 7.0 Beta wird von dem Paket aktuell noch nicht unterstützt (Synology muss hier noch die Dokumentation aktualisieren, der Treiber lässt sich dort nur auf der Konsole installieren).

===== English =====

In Synology first tvheadend should be installed, and afterwards the driver. The driver installation will
modify the tvheadend startup script a little bit.

Add following link in the Synology Package Manager:
http://sundtek.de/synology

Afterwards there's an app Sundtek Linux Driver available in the Community Section of the package manager.

DVB-S/S2/S2X

2025-02-08T17:30:15Z

Sundtek:

== Diseqc ==

<pre>
Those are for 4x1 diseqc
E0 10 38 F0 = 1st Port
E0 10 38 F4 = 2nd Port
E0 10 38 F8 = 3rd Port
E0 10 38 FC = 4th Port

example:
/opt/bin/mediaclient -V V
/opt/bin/mediaclient --diseqc="E0 10 38 F0"
</pre>

https://sundtek.de/wiki/index.php?title=Mediaclient#DVB-S.2FS2.2FS2X_Tuning

please note that the tuner by default will cut off the LNB voltage after 15 seconds inactivity, this might reset the diseqc port if no voltage is applied. To avoid that you can
open a second terminal and just leave /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0 --band universal running.

You can adjust the timeout settings in /etc/sundtek.conf (by default it doesn't exist and default values are loaded from the driver), you can create it and add a parameter standby_timeout=n
Where n is the timeout in seconds.

== DAB/DAB+ ==

DAB/DAB+ channels can be found on satellite 7.0 east.

<pre>
Frequency:12572 MHz
Symbolrate: 10215000
Modulation: DVB-S2/QPSK
Polarization: Vertical
</pre>

Locking on Transponder:

<pre>
/opt/bin/mediaclient -m DVBS2 -f 12572000 -M QPSK -S 10215000 -V V -E 3/4
</pre>

=== FileOutput ===

capturing and replaying the stream:

/opt/bin/mediaclient --cat /dev/dvb/adapter0/dvr0 | ../eti-tools/fedi2eti 101 239.16.242.17 60017 | ./odr-dabmod -C doc/example.ini > test.iq

hackrf_transfer -t test.iq -f 180064000 -x 47 -a 1 -s 2048000 -b 1750000

<pre>
example.ini (parts of it):

[output]
; choose output: possible values: uhd, file, zmq, soapysdr
output=file
[fileoutput]
; Two output formats are supported: In the default mode,
; the file output writes I/Q float values (i.e. complex
; float) to the file. The I and Q samples can take values up
; to 810000 in absolute magnitude with gainmode FIX. With
; gainmode VAR and FIX, they should never exceed 50000.
;format=complexf
;
; The complexf_normalised format applies a compensation factor to the complexf
; output to bring the range of the I and Q components to [-1.0 .. 1.0]. The
; digital_gain is still applied on top of that normalisation.
;format=complexf_normalised
;
; When the format is set to s8, the output writes I/Q 8-bit
; signed integers, where the magnitude is multiplied by 128/50000
; effectively mapping the gainmode VAR range of -50000 -- 50000
; to -128 -- 128. For other gainmodes, use the digital_gain setting
; to make sure you don't create clipping.
;
; The format u8 is the same as s8, except that the values are mapped
; between 0 and 255. Use u8 for welle.io, qt-dab or other tools.
;
; Also supported is s16, with system endianness (little endian on x86_64 and ARM)
format=s8

; The output file:
filename=/dev/stdout

show_metadata=0
</pre>

=== Soapy Output ===

<pre>
/opt/bin/mediaclient --cat /dev/dvb/adapter0/dvr0 | ../eti-tools/fedi2eti 101 239.16.242.17 60017 | ./odr-dabmod -C doc/example.ini
</pre>

<pre>
[soapyoutput]
; These options are given to the SoapySDR library:
device=driver=hackrf
;master_clock_rate=32768000
txgain=47
frequency=180064000
</pre>

==== Soapy Config ====

Full Sample configuration:

<pre>
; Sample configuration file for ODR-DabMod

[remotecontrol]
; The RC feature is described in detail in doc/README-RC.md

; enable the telnet remote control on localhost:2121
telnet=1
telnetport=2121

; Enable zmq remote control.
zmqctrl=1
zmqctrlendpoint=tcp://127.0.0.1:9400
; accepted formats according to man zmq_bind, i.e.
; tcp://<interface>:<port>, e.g. tcp://lo:9400
; and tcp://<ipaddress>:<port>

[log]
; Write to a logfile or to syslog.
; Setting filename to stderr is not necessary, as all messages are
; automatically written to stderr.
syslog=0
filelog=0
filename=odr-dabmod.log

[input]
; A file or fifo input is using transport=file
transport=file
source=/dev/stdin

; When the end of file is reached, it is possible to rewind it
loop=0

; ETI-over-TCP example:
;transport=tcp
;source=localhost:9200

; When recieving data using ZeroMQ, the source is the URI to be used
;transport=zeromq
;source=tcp://localhost:9100
; The option max_frames_queued defines the maximum number of ETI frames
; (frame duration: 24ms) that can be in the input queue
;max_frames_queued=100

; EDI input.
; Listen for EDI data on a given UDP port, unicast or multicast.
;transport=edi
;
; EDI over TCP:
;
; Connect to TCP server on a given host
;source=tcp://localhost:9201
;
; EDI over UDP:
;
; Supported syntax for the source setting:
; Bind to default interface and receive data from port 12000
;source=udp://:12000
;
; Bind to interface with IP:192.168.1.22 and receive data from port 12000
;source=udp://192.168.1.22:12000
;
; Bind to interface with IP:192.168.1.22 and join multicast group:
; 239.100.101.22 and receive data from port 12000
;source=udp://192.168.1.22@239.100.101.22:12000
;
; Bind to default interface (which routes to multicast) and join multicast
; group: 239.100.101.22 and receive data from port 12000
;source=udp://@239.100.101.22:12000
;
; Maximum delay in milliseconds that the EDI input is willing to wait
; before it timeouts
;edi_max_delay=240
; This EDI implementation does not support EDI Packet Resend

[modulator]
; Mode 'fix' uses a fixed factor and is really not recommended. It is more
; useful on an academic perspective for people trying to understand the DAB
; modulation.
;
; Mode 'max' is the normalization of every OFDM symbol. No overshoot, no
; truncating, but varying output power (around 3dB) which might not be the best
; for some power amplifier. The output samples are limited to a magnitude
; of 32768.
;
; Mode 'var' uses the method specified in ETSI 300 798 Clause 5.3. This method
; normalizes to 4 times the standard deviation for an approximation of the RMS
; power. So around 6/100000 samples will be truncated and will introduce some
; really minor distortion. But this mode also maximizes the output power. This
; is the gain mode recommended for real world operation as it is based on a DAB
; standard; the only difference is that ODR-DabMod internally calculates this with
; 32-bit floats instead of 8 bits.
gainmode=var
;
; In mode var, you can choose to normalise the samples to something else than
; 4 times the standard deviation.
;normalise_variance=4

; Transmission mode
; If not defined, use Transmission Mode 1
;mode=1

; The digital gain is a value that is multiplied to each sample. It is used
; to tune the chain to make sure that no non-linearities appear up to the
; USRP daughterboard programmable gain amplifier (PGA).
; If there is clipping, the spectral quality of the signal will quickly deteriorate,
; and wide-band noise will be generated.
;
; Be aware that there is a dependency with resampling.
digital_gain=0.8

; Output sample rate. Values other than 2048000 enable
; resampling.
; Warning! digital_gain settings are different if resampling
; is enabled or not !
rate=2048000

; (DEPRECATED) CIC equaliser for USRP1 and USRP2
; These USRPs have an upsampler in FPGA that does not have a flat frequency
; response. The CIC equaliser compensates this. This setting is specific to
; the USRP1 and USRP2 devices.
; Set to 0 to disable CicEqualiser
;dac_clk_rate=0

; The USRP1 does not have flexible clocking, you will need
;rate=3200000
; and
;dac_clk_rate=128000000

; When nonzero, overlap ofdmwindowing samples from each OFDM symbol
; onto the previous and next symbol, using a raised cosine window function.
; This has the effect of smoothing the transition from one symbol to the next,
; which improves spectrum shape.
; In Transmission Mode I, every data symbol is composed of 2552 samples.
;ofdmwindowing=10

; Settings for crest factor reduction. Statistics for ratio of
; samples that were clipped are available through the RC.
[cfr]
enable=0

; At what amplitude the signal should be clipped
clip=50.0

; How much to clip the error signal used to compensate the effect
; of clipping
error_clip=0.1

[firfilter]
; The FIR Filter can be used to create a better spectral quality.
enabled=1

; The filter taps can be calculated with the python script
; doc/fir-filter/generate-filter.py
; If filtertapsfile is not given, the default taps are used.
;filtertapsfile=simple_taps.txt

[poly]
;Predistortion using memoryless polynom, see dpd/ folder for more info
enabled=0
polycoeffile=polyCoefs

[output]
; choose output: possible values: uhd, file, zmq, soapysdr
output=soapysdr

[fileoutput]
; Two output formats are supported: In the default mode,
; the file output writes I/Q float values (i.e. complex
; float) to the file. The I and Q samples can take values up
; to 810000 in absolute magnitude with gainmode FIX. With
; gainmode VAR and FIX, they should never exceed 50000.
;format=complexf
;
; The complexf_normalised format applies a compensation factor to the complexf
; output to bring the range of the I and Q components to [-1.0 .. 1.0]. The
; digital_gain is still applied on top of that normalisation.
;format=complexf_normalised
;
; When the format is set to s8, the output writes I/Q 8-bit
; signed integers, where the magnitude is multiplied by 128/50000
; effectively mapping the gainmode VAR range of -50000 -- 50000
; to -128 -- 128. For other gainmodes, use the digital_gain setting
; to make sure you don't create clipping.
;
; The format u8 is the same as s8, except that the values are mapped
; between 0 and 255. Use u8 for welle.io, qt-dab or other tools.
;
; Also supported is s16, with system endianness (little endian on x86_64 and ARM)
format=s8

; The output file:
filename=/dev/stdout

show_metadata=0

[uhdoutput]
; The UHD output can be directly used with the Ettus USRP devices
;
; You have to set master_clock_rate to a multiple of the
; sample_rate. Ideally, it should be
; master_clock_rate = 4 * sample_rate
; or even a higher factor.
;
; Settings for the B200:
device=
master_clock_rate=32768000
type=b200
txgain=40
; The B200 needs larger gains (up to 89dB) but,
; "Gain settings are application specific, but it is recommended that users
; consider using at least half of the available gain to get reasonable dynamic
; range."
; From the B200 User Manual
; http://files.ettus.com/uhd_docs/manual/html/usrp_b200.html
;
; More information and measurements available on:
; http://wiki.opendigitalradio.org/index.php/USRP_B200_Measurements

; You can set what TX and RX antennas to use. This will depend on the
; USRP model you are using.
;tx_antenna=
;rx_antenna=RX2

; Settings for a USRP B100:
;device=
; you can put additional UHD device settings here
;master_clock_rate=32768000
;type=b100
;txgain=2.0
; Try first with small gain values
; Also set rate to 2048000

; For the USRP1
;device=
;type=usrp1
; the usrp1 can have two daughterboards, the subdevice parameter allows you
; to choose which one to use
;subdevice=A:0
; The USRP1 doesn't support master_clock_rate, you need to enable resampling

; You must specify either frequency or channel, but not both.
;frequency=234208000
channel=13C

; Override automatic analog frontend bandwidth calculation. Units: Hz
;bandwidth=2000000

; Some USRP boards/frontends support setting an LO offset that has the
; effect of shifting DC out of the signal bandwidth. This should also
; improve IQ imbalance effects, because the mirror will centered on another
; frequency (it should be on frequency + 2*lo_offset)
;
; The value can be negative, and its absolute value must be smaller than
; master_clock_rate/2.
;lo_offset=2048000

; The reference clock to use. The gpsdo is the ODR LEA-M8F board, the
; official Ettus GPSDO is selected with gpsdo-ettus
; possible values : internal, external, MIMO, gpsdo, gpsdo-ettus
refclk_source=internal

; The reference one pulse-per second to use
; possible values : none, external, MIMO, gpsdo
pps_source=none

; Behaviour when external clock reference lock lost
; possible values: ignore, crash
behaviour_refclk_lock_lost=ignore

; The maximum accepted holdover time for the gpsdo once it
; started operating. Initial check interval for GPSDO lock
; at startup is always 180s.
; Valid only if the refclk and pps_source are set to gpsdo.
; Units: seconds
; Set to 0 to disable holdover check
; default value: 0
max_gps_holdover_time=600

; Enable the TCP server to communicate TX and RX feedback for
; digital predistortion.
; Set to 0 to disable
;dpd_port=50055

; section defining ZeroMQ output properties
[zmqoutput]

; on which port to listen for connections
; please see the Transports section in man zmq
; for more information regarding the syntax
listen=tcp://*:54001

; what ZMQ socket type to use. Valid values: PUB, REP
; Please see man zmq_socket for documentation
socket_type=pub

; section defining the SoapySDR output settings.
[soapyoutput]
; These options are given to the SoapySDR library:
device=driver=hackrf
;master_clock_rate=32768000
txgain=61
; 47
frequency=180064000
; channel=5D
; 13C
;lo_offset=2048000

; Override automatic analog frontend bandwidth calculation. Units: Hz
;bandwidth=2000000

; You can set what TX antenna to use. This will depend on the
; SDR device you are using.
;tx_antenna=

; Enable the TCP server to communicate TX and RX feedback for
; digital predistortion.
; Set to 0 to disable
;dpd_port=50055

; Used for running single-frequency networks
[delaymanagement]
; Enable handling of timestamps for SFN
synchronous=0

; Whether to mute the TX when incoming frames have no timestamp
mutenotimestamps=0

; This offset is added to the TIST, and the sum defines the
; TX time of the transmission frame. It can by changed at runtime
; through the remote control.
offset=0.002

; The way the timestamps are interpreted in ODR-DabMod up to v1.1.0 was not
; specified, and you should not assume that two different versions will
; transmit synchronously given the same settings. Always run SFNs with
; identical versions!
; Furthermore, when combining ODR-DabMod with third-party modulators, always
; measure!

[tii]
; If these options are set, TII transmission is enabled.
; DAB modes I and II are supported, and must be set explicitly in
; this file. Reading DAB mode from ETI is not supported.
enable=0
; comb is also known as sub-identifier.
comb=1
; pattern is also known as main-identifier. If you run several transmitters
; in SFN, it is better to use the same pattern for all, and vary the comb.
; Otherwise identification of the transmitters may be more difficult.
pattern=11
; There are two variants of TII being used. The old variant that uses the wrong
; phase on the second carrier in each carrier pairs and is therefore not
; conforming to the specification. Modern analysers can decode both variants,
; while others, like the Philips DAB752 and the VAD v2 monitor are known to
; decode only the old non-conforming variant.
old_variant=0
</pre>

=== Further Links ===

* https://radioempfang.digital/dab-ueber-satellit
* https://github.com/piratfm/eti-tools

DVB-S/S2/S2X

2025-02-08T17:24:47Z

Sundtek:

== Diseqc ==

<pre>
Those are for 4x1 diseqc
E0 10 38 F0 = 1st Port
E0 10 38 F4 = 2nd Port
E0 10 38 F8 = 3rd Port
E0 10 38 FC = 4th Port
</pre>

== DAB/DAB+ ==

DAB/DAB+ channels can be found on satellite 7.0 east.

<pre>
Frequency:12572 MHz
Symbolrate: 10215000
Modulation: DVB-S2/QPSK
Polarization: Vertical
</pre>

Locking on Transponder:

<pre>
/opt/bin/mediaclient -m DVBS2 -f 12572000 -M QPSK -S 10215000 -V V -E 3/4
</pre>

=== FileOutput ===

capturing and replaying the stream:

/opt/bin/mediaclient --cat /dev/dvb/adapter0/dvr0 | ../eti-tools/fedi2eti 101 239.16.242.17 60017 | ./odr-dabmod -C doc/example.ini > test.iq

hackrf_transfer -t test.iq -f 180064000 -x 47 -a 1 -s 2048000 -b 1750000

<pre>
example.ini (parts of it):

[output]
; choose output: possible values: uhd, file, zmq, soapysdr
output=file
[fileoutput]
; Two output formats are supported: In the default mode,
; the file output writes I/Q float values (i.e. complex
; float) to the file. The I and Q samples can take values up
; to 810000 in absolute magnitude with gainmode FIX. With
; gainmode VAR and FIX, they should never exceed 50000.
;format=complexf
;
; The complexf_normalised format applies a compensation factor to the complexf
; output to bring the range of the I and Q components to [-1.0 .. 1.0]. The
; digital_gain is still applied on top of that normalisation.
;format=complexf_normalised
;
; When the format is set to s8, the output writes I/Q 8-bit
; signed integers, where the magnitude is multiplied by 128/50000
; effectively mapping the gainmode VAR range of -50000 -- 50000
; to -128 -- 128. For other gainmodes, use the digital_gain setting
; to make sure you don't create clipping.
;
; The format u8 is the same as s8, except that the values are mapped
; between 0 and 255. Use u8 for welle.io, qt-dab or other tools.
;
; Also supported is s16, with system endianness (little endian on x86_64 and ARM)
format=s8

; The output file:
filename=/dev/stdout

show_metadata=0
</pre>

=== Soapy Output ===

<pre>
/opt/bin/mediaclient --cat /dev/dvb/adapter0/dvr0 | ../eti-tools/fedi2eti 101 239.16.242.17 60017 | ./odr-dabmod -C doc/example.ini
</pre>

<pre>
[soapyoutput]
; These options are given to the SoapySDR library:
device=driver=hackrf
;master_clock_rate=32768000
txgain=47
frequency=180064000
</pre>

==== Soapy Config ====

Full Sample configuration:

<pre>
; Sample configuration file for ODR-DabMod

[remotecontrol]
; The RC feature is described in detail in doc/README-RC.md

; enable the telnet remote control on localhost:2121
telnet=1
telnetport=2121

; Enable zmq remote control.
zmqctrl=1
zmqctrlendpoint=tcp://127.0.0.1:9400
; accepted formats according to man zmq_bind, i.e.
; tcp://<interface>:<port>, e.g. tcp://lo:9400
; and tcp://<ipaddress>:<port>

[log]
; Write to a logfile or to syslog.
; Setting filename to stderr is not necessary, as all messages are
; automatically written to stderr.
syslog=0
filelog=0
filename=odr-dabmod.log

[input]
; A file or fifo input is using transport=file
transport=file
source=/dev/stdin

; When the end of file is reached, it is possible to rewind it
loop=0

; ETI-over-TCP example:
;transport=tcp
;source=localhost:9200

; When recieving data using ZeroMQ, the source is the URI to be used
;transport=zeromq
;source=tcp://localhost:9100
; The option max_frames_queued defines the maximum number of ETI frames
; (frame duration: 24ms) that can be in the input queue
;max_frames_queued=100

; EDI input.
; Listen for EDI data on a given UDP port, unicast or multicast.
;transport=edi
;
; EDI over TCP:
;
; Connect to TCP server on a given host
;source=tcp://localhost:9201
;
; EDI over UDP:
;
; Supported syntax for the source setting:
; Bind to default interface and receive data from port 12000
;source=udp://:12000
;
; Bind to interface with IP:192.168.1.22 and receive data from port 12000
;source=udp://192.168.1.22:12000
;
; Bind to interface with IP:192.168.1.22 and join multicast group:
; 239.100.101.22 and receive data from port 12000
;source=udp://192.168.1.22@239.100.101.22:12000
;
; Bind to default interface (which routes to multicast) and join multicast
; group: 239.100.101.22 and receive data from port 12000
;source=udp://@239.100.101.22:12000
;
; Maximum delay in milliseconds that the EDI input is willing to wait
; before it timeouts
;edi_max_delay=240
; This EDI implementation does not support EDI Packet Resend

[modulator]
; Mode 'fix' uses a fixed factor and is really not recommended. It is more
; useful on an academic perspective for people trying to understand the DAB
; modulation.
;
; Mode 'max' is the normalization of every OFDM symbol. No overshoot, no
; truncating, but varying output power (around 3dB) which might not be the best
; for some power amplifier. The output samples are limited to a magnitude
; of 32768.
;
; Mode 'var' uses the method specified in ETSI 300 798 Clause 5.3. This method
; normalizes to 4 times the standard deviation for an approximation of the RMS
; power. So around 6/100000 samples will be truncated and will introduce some
; really minor distortion. But this mode also maximizes the output power. This
; is the gain mode recommended for real world operation as it is based on a DAB
; standard; the only difference is that ODR-DabMod internally calculates this with
; 32-bit floats instead of 8 bits.
gainmode=var
;
; In mode var, you can choose to normalise the samples to something else than
; 4 times the standard deviation.
;normalise_variance=4

; Transmission mode
; If not defined, use Transmission Mode 1
;mode=1

; The digital gain is a value that is multiplied to each sample. It is used
; to tune the chain to make sure that no non-linearities appear up to the
; USRP daughterboard programmable gain amplifier (PGA).
; If there is clipping, the spectral quality of the signal will quickly deteriorate,
; and wide-band noise will be generated.
;
; Be aware that there is a dependency with resampling.
digital_gain=0.8

; Output sample rate. Values other than 2048000 enable
; resampling.
; Warning! digital_gain settings are different if resampling
; is enabled or not !
rate=2048000

; (DEPRECATED) CIC equaliser for USRP1 and USRP2
; These USRPs have an upsampler in FPGA that does not have a flat frequency
; response. The CIC equaliser compensates this. This setting is specific to
; the USRP1 and USRP2 devices.
; Set to 0 to disable CicEqualiser
;dac_clk_rate=0

; The USRP1 does not have flexible clocking, you will need
;rate=3200000
; and
;dac_clk_rate=128000000

; When nonzero, overlap ofdmwindowing samples from each OFDM symbol
; onto the previous and next symbol, using a raised cosine window function.
; This has the effect of smoothing the transition from one symbol to the next,
; which improves spectrum shape.
; In Transmission Mode I, every data symbol is composed of 2552 samples.
;ofdmwindowing=10

; Settings for crest factor reduction. Statistics for ratio of
; samples that were clipped are available through the RC.
[cfr]
enable=0

; At what amplitude the signal should be clipped
clip=50.0

; How much to clip the error signal used to compensate the effect
; of clipping
error_clip=0.1

[firfilter]
; The FIR Filter can be used to create a better spectral quality.
enabled=1

; The filter taps can be calculated with the python script
; doc/fir-filter/generate-filter.py
; If filtertapsfile is not given, the default taps are used.
;filtertapsfile=simple_taps.txt

[poly]
;Predistortion using memoryless polynom, see dpd/ folder for more info
enabled=0
polycoeffile=polyCoefs

[output]
; choose output: possible values: uhd, file, zmq, soapysdr
output=soapysdr

[fileoutput]
; Two output formats are supported: In the default mode,
; the file output writes I/Q float values (i.e. complex
; float) to the file. The I and Q samples can take values up
; to 810000 in absolute magnitude with gainmode FIX. With
; gainmode VAR and FIX, they should never exceed 50000.
;format=complexf
;
; The complexf_normalised format applies a compensation factor to the complexf
; output to bring the range of the I and Q components to [-1.0 .. 1.0]. The
; digital_gain is still applied on top of that normalisation.
;format=complexf_normalised
;
; When the format is set to s8, the output writes I/Q 8-bit
; signed integers, where the magnitude is multiplied by 128/50000
; effectively mapping the gainmode VAR range of -50000 -- 50000
; to -128 -- 128. For other gainmodes, use the digital_gain setting
; to make sure you don't create clipping.
;
; The format u8 is the same as s8, except that the values are mapped
; between 0 and 255. Use u8 for welle.io, qt-dab or other tools.
;
; Also supported is s16, with system endianness (little endian on x86_64 and ARM)
format=s8

; The output file:
filename=/dev/stdout

show_metadata=0

[uhdoutput]
; The UHD output can be directly used with the Ettus USRP devices
;
; You have to set master_clock_rate to a multiple of the
; sample_rate. Ideally, it should be
; master_clock_rate = 4 * sample_rate
; or even a higher factor.
;
; Settings for the B200:
device=
master_clock_rate=32768000
type=b200
txgain=40
; The B200 needs larger gains (up to 89dB) but,
; "Gain settings are application specific, but it is recommended that users
; consider using at least half of the available gain to get reasonable dynamic
; range."
; From the B200 User Manual
; http://files.ettus.com/uhd_docs/manual/html/usrp_b200.html
;
; More information and measurements available on:
; http://wiki.opendigitalradio.org/index.php/USRP_B200_Measurements

; You can set what TX and RX antennas to use. This will depend on the
; USRP model you are using.
;tx_antenna=
;rx_antenna=RX2

; Settings for a USRP B100:
;device=
; you can put additional UHD device settings here
;master_clock_rate=32768000
;type=b100
;txgain=2.0
; Try first with small gain values
; Also set rate to 2048000

; For the USRP1
;device=
;type=usrp1
; the usrp1 can have two daughterboards, the subdevice parameter allows you
; to choose which one to use
;subdevice=A:0
; The USRP1 doesn't support master_clock_rate, you need to enable resampling

; You must specify either frequency or channel, but not both.
;frequency=234208000
channel=13C

; Override automatic analog frontend bandwidth calculation. Units: Hz
;bandwidth=2000000

; Some USRP boards/frontends support setting an LO offset that has the
; effect of shifting DC out of the signal bandwidth. This should also
; improve IQ imbalance effects, because the mirror will centered on another
; frequency (it should be on frequency + 2*lo_offset)
;
; The value can be negative, and its absolute value must be smaller than
; master_clock_rate/2.
;lo_offset=2048000

; The reference clock to use. The gpsdo is the ODR LEA-M8F board, the
; official Ettus GPSDO is selected with gpsdo-ettus
; possible values : internal, external, MIMO, gpsdo, gpsdo-ettus
refclk_source=internal

; The reference one pulse-per second to use
; possible values : none, external, MIMO, gpsdo
pps_source=none

; Behaviour when external clock reference lock lost
; possible values: ignore, crash
behaviour_refclk_lock_lost=ignore

; The maximum accepted holdover time for the gpsdo once it
; started operating. Initial check interval for GPSDO lock
; at startup is always 180s.
; Valid only if the refclk and pps_source are set to gpsdo.
; Units: seconds
; Set to 0 to disable holdover check
; default value: 0
max_gps_holdover_time=600

; Enable the TCP server to communicate TX and RX feedback for
; digital predistortion.
; Set to 0 to disable
;dpd_port=50055

; section defining ZeroMQ output properties
[zmqoutput]

; on which port to listen for connections
; please see the Transports section in man zmq
; for more information regarding the syntax
listen=tcp://*:54001

; what ZMQ socket type to use. Valid values: PUB, REP
; Please see man zmq_socket for documentation
socket_type=pub

; section defining the SoapySDR output settings.
[soapyoutput]
; These options are given to the SoapySDR library:
device=driver=hackrf
;master_clock_rate=32768000
txgain=61
; 47
frequency=180064000
; channel=5D
; 13C
;lo_offset=2048000

; Override automatic analog frontend bandwidth calculation. Units: Hz
;bandwidth=2000000

; You can set what TX antenna to use. This will depend on the
; SDR device you are using.
;tx_antenna=

; Enable the TCP server to communicate TX and RX feedback for
; digital predistortion.
; Set to 0 to disable
;dpd_port=50055

; Used for running single-frequency networks
[delaymanagement]
; Enable handling of timestamps for SFN
synchronous=0

; Whether to mute the TX when incoming frames have no timestamp
mutenotimestamps=0

; This offset is added to the TIST, and the sum defines the
; TX time of the transmission frame. It can by changed at runtime
; through the remote control.
offset=0.002

; The way the timestamps are interpreted in ODR-DabMod up to v1.1.0 was not
; specified, and you should not assume that two different versions will
; transmit synchronously given the same settings. Always run SFNs with
; identical versions!
; Furthermore, when combining ODR-DabMod with third-party modulators, always
; measure!

[tii]
; If these options are set, TII transmission is enabled.
; DAB modes I and II are supported, and must be set explicitly in
; this file. Reading DAB mode from ETI is not supported.
enable=0
; comb is also known as sub-identifier.
comb=1
; pattern is also known as main-identifier. If you run several transmitters
; in SFN, it is better to use the same pattern for all, and vary the comb.
; Otherwise identification of the transmitters may be more difficult.
pattern=11
; There are two variants of TII being used. The old variant that uses the wrong
; phase on the second carrier in each carrier pairs and is therefore not
; conforming to the specification. Modern analysers can decode both variants,
; while others, like the Philips DAB752 and the VAD v2 monitor are known to
; decode only the old non-conforming variant.
old_variant=0
</pre>

=== Further Links ===

* https://radioempfang.digital/dab-ueber-satellit
* https://github.com/piratfm/eti-tools

Windows Driver Installation

2025-01-15T13:58:24Z

Sundtek: /* Sundtek G2 Driver */

== Windows Drivers ==

Since we have been using various chipsets in the past, there are different drivers available.

=== Sundtek G2 Driver ===

==== Sundtek SkyTV 8 ====
==== Sundtek SkyTV Dual ====
11. February 2021 (Initial Release) 
Please note in win10 you will have to start the command "cmd" as administrator and run following command:

bcdedit.exe /set nointegritychecks on

this modification disables the signature check in Windows 10 (on older Windows Systems, press F8 during boot up and
select disable the driver signature/certificate check)
We will sign the driver and let microsoft cross-sign it after a few more updates and some more testing.

15.01.2025: 
http://www.sundtek.de/media/SundtekG2_WinDriver_Release_15012025.zip

* added unicable support
* added support for sundtek control center
* signed (not crosssigned by microsoft yet - there will be another release in a week)
* updated Sundtek Control Center to support Unicable with those devices.

http://sundtek.de/media/Windows_SundtekControlCenter_2025-01-15.zip

The sundtek control center allows to set the SCR and Unicable Frequency

Testing 14.02.2021: 
https://sundtek.de/media/SundtekG2_WinDriver_Release_14022021.zip 
- added support for signal strength 
- displaying SNR as signal Quality 
- added Diseqc Support (using the Microsoft Interface) 

----

=== Sundtek MTV Driver ===

==== Sundtek MediaTV Pro 3 ====
==== Sundtek MediaTV Digital Home 3 ====
==== Sundtek SkyTV 5 ====
==== Sundtek SkyTV 6 ====

https://www.sundtek.de/media/sundtek_driver_windows_mtvIII_2016-07-13.zip

----

=== Sundtek EM Driver (Tuners before 2014) ===

==== Sundtek Media TV Pro 2 ====
==== Sundtek Media TV Pro 1 ====
==== Sundtek SkyTV 3 ====
https://www.sundtek.de/media/sundtek_driver_windows_131218.zip

2024-10-08T09:49:43Z

Sundtek:

Docker

2024-10-08T09:41:17Z

Sundtek:

== Docker ==

=== External Documentation ===

* Synology Wiki (German):
https://www.synology-wiki.de/index.php/TvHeadend_mit_Docker_und_Sundtek_SkyTV_Ultimate

=== On the host ===

This is the step that has to be taken care about on the native host (outside of the docker image). The driver can run in non-privileged mode inside the docker.
Various libc / musl / uclibc images are supported.

If you want to install the linux driver in a docker environment a few things need to be taken care of.

==== Device Nodes on the Host ====

Very important /dev/bus/usb contain the interface to the raw USB devices which is used by the sundtek driver.
However one special (and a little bit messy part of docker) is that it also needs to know the major/minor IDs which are allowed to be forwarded - before creating and before starting the docker image, that's why nodes in /dev/dvb need to be pre-created on the host.

If you install the driver on the host you should create a configuration file which contains following text:
enabledocker=on

this will cause that the driver on the native host (not in the docker) will create dummy adapter nodes in /dev/dvb, the driver itself will not try to access the USB device - it will only create the files if enabledocker=on is set in the configuration file and exit immediately. 
On the host:
<pre>
sudo -s
echo "enabledocker=on" > /etc/sundtek.conf
</pre>

You can also create them manually if you want (see next section):

===== Without installing the driver on the host =====

So the driver on the host has no special function it would just create /dev/dvb devicenodes and exist immediately.
You can create those dummies manually (but those need to be there before creating the docker image and before starting the docker image)

<pre>
mkdir -p /dev/dvb/adapter0
mknod /dev/dvb/adapter0/frontend0 c 212 1
mknod /dev/dvb/adapter0/dvr0 c 212 5
mknod /dev/dvb/adapter0/demux0 c 212 3
mkdir -p /dev/dvb/adapter1
mknod /dev/dvb/adapter1/frontend0 c 212 7
mknod /dev/dvb/adapter1/dvr0 c 212 11
mknod /dev/dvb/adapter1/demux0 c 212 9
mkdir -p /dev/dvb/adapter2
mknod /dev/dvb/adapter2/frontend0 c 212 13
mknod /dev/dvb/adapter2/dvr0 c 212 17
mknod /dev/dvb/adapter2/demux0 c 212 15
</pre>

===== Synology NAS =====

You can install the driver on the host and check the option "Enable Docker" in the Configuration menu. When this is checked the driver will only create those dummy nodes on the host and exit immediately.

==== Creating a Docker Image ====

The docker itself needs to be created with some -device flags

Alpine Linux:

<pre>
docker create --name alpinelinux
--net=bridge
-p 9981:9981
-p 9982:9982
--device=/dev/dvb
--device=/dev/bus/usb
-t alpine /bin/sh
</pre>

Linuxserver / Tvheadend

<pre>
docker create \
--name=tvheadend \
--net=bridge \
-v <path to data>:/config \ <- Pfad anpassen! / modify path (and remove the comment of course)
-v <path to recordings>:/recordings \ <- Pfad anpassen! / modify path (and remove the comment of course)
-p 9981:9981 \
-p 9982:9982 \
--device=/dev/dvb \
--device=/dev/bus/usb
linuxserver/tvheadend
</pre>

=== Inside the docker ===

Inside the docker unfortunately you only have one shot if you do it wrong you have to re-create the docker and re-do this step.
Usually our customers install the drivers inside the docker in /config

To enter a docker image:
<pre>
docker exec -it tvheadend /bin/sh
</pre>

Download the netinstall script:
<pre>
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh -docker -use-custom-path /config
</pre>

The installer will rename the tvheadend binary in /usr/bin to tvheadend.bin and places a script instead which will automatically start the driver.

this will place the driver in /config

Usually you will want to mount a local directory inside the docker, this can basically be configured via the Synology Webfrontend.
When doing that you need to take care that the user inside the docker also has access to that folder otherwise you will get a permission denied.

You can use the tvheadend start script to change the permissions if you need that, /usr/bin/tvheadend add chmod 777 /path/to/videodirectory

=== Misc ===

one customer also needed to modify the preset current limit of the tuner, he had to place lnblimit=1000ma (case sensitive in sundtek.conf inside the docker)

== Unraid ==

All the sundtek devices work with Unraid. The installation is comfortably handled by a Sundtek Driver plugin in the Unraid environment. So just install the plugin and you're set.

--- the old documentation for unraid follows here, we just keep it here for the record ---

1. Set up the driver on the host system

Open a terminal as root (console) and run:
<pre>
cd /tmp
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh -dockerhost
</pre>

(this will only take care that some dummy nodes are created in /dev/dvb/, access control will be handled by major/minor numbers of the existing files. When the driver is started on the host it will exit directly due to the dockerhost flag and only create the nodes)

basically all this does is
<pre>
mkdir -p /dev/dvb/adapter0
mkdir -p /dev/dvb/adapter1
#crwxrwxrwx 1 root root 212, 1 Dec 19 20:44 frontend0
#crwxrwxrwx 1 root root 212, 5 Dec 19 20:44 dvr0
#crwxrwxrwx 1 root root 212, 3 Dec 19 20:44 demux0
mknod /dev/dvb/adapter0/frontend0 c 212 1
mknod /dev/dvb/adapter0/dvr0 c 212 5
mknod /dev/dvb/adapter0/demux0 c 212 3
#crwxrwxrwx 1 root root 212, 7 Dec 19 20:44 frontend0
#crwxrwxrwx 1 root root 212, 11 Dec 19 20:44 dvr0
#crwxrwxrwx 1 root root 212, 9 Dec 19 20:44 demux0
mknod /dev/dvb/adapter1/frontend0 c 212 7
mknod /dev/dvb/adapter1/dvr0 c 212 11
mknod /dev/dvb/adapter1/demux0 c 212 9
</pre>

2. Set up the driver inside the tvheadend docker

... install the tvheadend docker, add an extra device driver for /dev/bus/usb

open the host terminal and enter the tvheadend docker image:
<pre>
docker exec -it tvheadend /bin/sh
cd /tmp
wget http://sundtek.de/media/sundtek_netinst.sh
chmod 777 sundtek_netinst.sh
./sundtek_netinst.sh -docker -use-custom-path /config
</pre>

(this will rename the tvheadend binary to tvheadend.bin and put a script in between which will start the driver inside the docker - followed by the actual tvheadend binary).

3. that's it restart the tvheadend docker.

== FAQ ==

=== Stick wird nicht im Docker angezeigt ===

Er findet leider den Stick nicht per Docker, warum auch immer…im Verzeichnis ist er aber vorhanden.
[[File:lsusbdocker.png]]

----

Wurde der Treiber installiert, /config/opt/bin/mediaclient -e sollte den Tuner anzeigen.

2022-11-01T11:51:45Z

2021-02-10T12:37:52Z

Sundtek:

Windows Driver Installation

2021-02-10T12:37:21Z

Sundtek: /* Sundtek G2 Driver */

Windows Driver Installation

2021-02-10T12:37:11Z

Sundtek: /* SkyTV 8 */