Autor Thema: Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem  (Gelesen 9972 mal)

linron

  • Newbie
  • *
  • Beiträge: 7
    • Profil anzeigen
Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« am: November 23, 2012, 01:44:02 Nachmittag »
Hallo,

habe gerade meinen neuen Sundtek DVS-S/S2 (III) erhalten und leider schon das erste Problem  :'( daher hoffe ich auf Support! Nun zu den Details:

Qnap 259 Pro+ Firmwareversion: 3.8.0 Build 20121114
# uname -a
Linux 2.6.33.2 #1 SMP Wed Nov 14 03:31:11 CST 2012 i686 unknown
[/] # cat proc/version
Linux version 2.6.33.2 (root@NasX86-10) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Wed Nov 14 03:31:11 CST 2012

Stick: Sundtek DVS-S/S2 (III)

installierte QPKG's:

TVH_Dev_Sundtek_0.4
TVHeadend_0.5.0_x86
xmltv_0.3_x86

befolgte Anleitung:

Als erstes muss man in tvheadend unter Konfiguration - TV Adapter - Sat config die LNB anlegen. (nur ASTRA)
Name: LNB1 (oder was auch immer)
Switchport: 0 (ist der erste diseqc Port)
LNB Type: universal

default war bereits hinterlegt

Nun sollte man eigentlich auf General - Add DVB Network by location - den Satellit raussuchen und unten in diesem Fenster in der Liste das soeben angelegte LNB1 auswählen.
Damit wird der initiale Transponder definiert. Aber das funktioniert bei Astra nicht, es werden nur die Hälfte der Transponder gefunden.
Also diesen Schritt weglassen.

Nun siehst du im Reiter Multiplexes nach. Wenn da schon welche drinstehen, alle markieren und löschen.

Nun legt man den initialen Transponder einfach manuell an.
Unter Multiplexes - Add Muxes manually:

Für Astra 19,2 folgendes eingeben:
"frequency": 11953500,
"symbol_rate": 27500000,
"fec": "3/4",
"polarisation": "Horizontal",
"modulation oder constellation": "QPSK",
"delivery_system": "SYS_DVBS", -> nicht auswählbar!!! Fehlermeldung: /dvb/feopts/delsys/_dev_dvb_adapter0_Sundtek_DVB_S_S2__III_ -- 400
Satellite config: LNB1 oder was du vorher definiert hast für Astra



Zusammenfassung:

beim Versuch unter "delivery_system" etwas hinzuzufügen erscheint die Fehlermeldung:
/dvb/feopts/delsys/_dev_dvb_adapter0_Sundtek_DVB_S_S2__III_ -- 400

[/share/MD0_DATA/.qpkg/TVH_Dev_Sundtek] # more mediasrv.log
2012-11-22 20:50:58 [16661] Starting up Multimedia Framework (Nov 13 2012 17:49:10)
2012-11-22 20:50:58 [16661]
2012-11-22 20:50:58 [16661] *** Autostarting Networksupport ***
2012-11-22 20:50:58 [16661]
2012-11-22 20:50:58 [16661] API Version: 5.5
2012-11-22 20:50:58 [16661] Running on Linux (2.6.33.2)
2012-11-22 20:50:58 [16661] Detected: GenuineIntel
2012-11-22 20:50:58 [16661] This CPU supports: MMX and SSE
2012-11-22 20:50:58 [16661] scanning devices
2012-11-22 20:50:58 [16661]
2012-11-22 20:50:58 [16661] Scanning for drivers
2012-11-22 20:50:58 [16661] found lib: libdrv_fm.so
2012-11-22 20:50:58 [16661] found lib: libdrv_hikarisoft_isdb.so
2012-11-22 20:50:58 [16661] found lib: libdrv_em28xx.so
2012-11-22 20:50:58 [16661] found lib: libdrv_vivi.so
2012-11-22 20:50:58 [16661] found lib: libdrv_net.so
2012-11-22 20:50:58 [16661] found lib: libdrv_tntdvb.so
2012-11-22 20:50:58 [16661] found lib: libdrv_ngTV.so
2012-11-22 20:50:58 [16661]
2012-11-22 20:50:58 [16661] Scanning for plugins
2012-11-22 20:50:58 [16661] found lib: libencoder_plugin.so
2012-11-22 20:50:58 [16661] MediaAVPlugin: MPEG Encoder
2012-11-22 20:50:58 [16661] Copyright: (C) Tpe 2011/2012
2012-11-22 20:50:58 [16661]
2012-11-22 20:50:58 [16661] Starting up device manager
2012-11-22 20:50:58 [16664] Starting service processor (PID 16664)
2012-11-22 20:50:58 [16661] unable to open /dev/misc
2012-11-22 20:50:58 [16661] scanning devices done
2012-11-22 20:50:58 [16661] attached devices:
2012-11-22 20:50:58 [16661] Starting listener
2012-11-22 20:50:58 [16661] registering ID: 0
2012-11-22 20:50:58 [16661] Listening on 9234
2012-11-22 20:50:58 [16661] disconnecting kernel driver
2012-11-22 20:50:58 [16664] Autostarting scripts in /etc/sundtek/
2012-11-22 20:50:58 [16664] executed all available items
2012-11-22 20:50:58 [16661] received notification client request
2012-11-22 20:50:59 [16661] attaching second generation DVB-S/S2 demodulator
2012-11-22 20:51:02 [16661] demodulator successfully attached (DVB_S/S2)!
2012-11-22 20:51:02 [16661] Allocation using pg for type 65678
2012-11-22 20:51:02 [16661] requesting to attach tuner(s) now
2012-11-22 20:51:02 [16661] registering: adapter0/0
2012-11-22 20:51:02 [16661] registered virtual: /dev/dvb/adapter0/frontend0
2012-11-22 20:51:02 [16661] registered virtual: /dev/dvb/adapter0/demux0
2012-11-22 20:51:02 [16661] registered virtual: /dev/dvb/adapter0/dvr0
2012-11-22 20:51:02 [16661] Setting RC Protocol to NEC
2012-11-22 20:51:02 [16661] registered virtual: /dev/mediainput0
2012-11-22 20:51:02 [16661] Remote Control Layout: 0
2012-11-22 20:51:02 [16664] trying to load uinput module
2012-11-22 20:51:02 [16664] loading uinput kernel extention failed, remote control will not work with lirc
2012-11-22 20:51:02 [16661] No remote control support available
2012-11-22 20:51:02 [16661] Trying to load ffmpeg codecs
2012-11-22 20:51:02 [16661] could not load libavutil.so
2012-11-22 20:51:02 [16661] could not load libswscale.so
2012-11-22 20:51:02 [16661] could not load libavcodec.so
2012-11-22 20:51:02 [16661] could not load libavformat.so
2012-11-22 20:51:02 [16661] AnalogTV encoding won't be possible in driver's side
2012-11-22 20:51:02 [16661]
2012-11-22 20:51:02 [16661] Sundtek MediaTV Driver loaded. This driver is licensed for non-commercial use
2012-11-22 20:51:02 [16661] with Sundtek MediaTV only
2012-11-22 20:51:02 [16661] Driver loaded within 4007 milliseconds
2012-11-22 20:51:02 [16661] Serial(0): XXXX
2012-11-22 20:51:02 [16661] received device attach message
2012-11-22 20:51:02 [16664] notify request: media device connected
2012-11-22 20:51:05 [16661] Initial devicescan done, switching detection mode
2012-11-22 20:51:17 [16661] Enabling standby
2012-11-22 20:51:17 [16661] Device is now in standby
2012-11-22 20:55:14 [16661] Waking up device
2012-11-22 20:55:15 [16661] voltage is off
2012-11-22 21:08:18 [16661] voltage is low/0
2012-11-22 21:08:18 [16661] Diseqc execution time: 92 ms
2012-11-22 21:08:18 [16661] diseqc send burst Unmodulated (SEC_MINI_A)
2012-11-22 21:08:18 [16661] Frequency: 1951
2012-11-22 21:08:18 [16661] Symbolrate: 22000
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (2068 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (2374 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (3192 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (3568 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (3776 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (4324 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (4523 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (5452 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (5824 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (6016 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (6768 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (7180 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (7708 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (7918 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (8173 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (8648 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (9057 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (9588 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (9842 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (10528 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (10917 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (11280 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (11663 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (11942 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (12220 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (13160 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (13368 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (14100 // 0)
2012-11-22 21:08:19 [16661] TS Sync byte not aligned, realigning stream (14565 // 0)



!!!!!!!!!!!!!!!!!!  HILFE !!!!!!!!!!!!!!!


mediasrv.log bereits 1336305355 bytes groß (TVHEADEND nun wieder disabled) damit die Logs nicht noch mehr Platz einnehmen....

Zur Info: Quad LNB (Astra) -> diseqc schalter hängt im Dachgeschoss dran weil ich irgendwann mal einen zweiten SAT dran hängen wollte.
Sat-Kabel hängt an einer Dreambox DM7020s (kein DVB-S2, guter Empfang)

Sundtek DVS-S/S2 (III) hängt am Netzteil und ist per USB mit dem QNAP verbunden.
SAT KABEL zum Sundtek provisorisch vom SAT-OUT der Dreambox genommen (hatte bereits mal eine DBOX2 so hinter der Dreambox in Betrieb -> Dreambox dabei im Standby)

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8517
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #1 am: November 23, 2012, 02:17:50 Nachmittag »
Hallo,

versuche erst mal die Logfile auszuschalten


/opt/bin/mediaclient --loglevel=off
und eventuell auch die ts settle time etwas justieren

/opt/bin/mediaclient --ts-settle-timeout=2000

Um es statisch zu konfigurieren

Bei dem ts-settle-timeout wuerde ich Werte zwischen 1000-2000 Millisekunden (=1-2 Sekunden) vorschlagen eventuell schaltet dein LNB nicht schnell genug, damit wird der Treiber dann für diese Zeit blockiert bis die ersten Daten an die Applikation weitergibt

/etc/sundtek.conf
loglevel=off
ts_settle_timeout=2000
« Letzte Änderung: November 23, 2012, 02:30:25 Nachmittag von Sundtek »
Failure is a good thing! I'll fix it

linron

  • Newbie
  • *
  • Beiträge: 7
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #2 am: November 23, 2012, 02:38:53 Nachmittag »
irgendwie scheint es als würden die Einträge nicht ziehen. Trotz:

[/] # /opt/bin/mediaclient --loglevel=off
switching off loglevel
[/] # /opt/bin/mediaclient --ts-settle-timeout=2000
Using device: /dev/dvb/adapter0/frontend0
[/] #  /opt/bin/mediaclient --enablenetwork=off
Disabling network support

sieht meine sundtek.conf so aus:

[/] # cat /etc/sundtek.conf
#
#
loglevel=min
device_attach=/share/MD0_DATA/.qpkg/TVH_Dev_Sundtek/restart_tvh.sh
enablenetwork=on

werde ich jetzt mal manuell wie vorgeschlagen ändern auf:
#
loglevel=off
ts_settle_timeout=2000
device_attach=/share/MD0_DATA/.qpkg/TVH_Dev_Sundtek/restart_tvh.sh
enablenetwork=off


RICHTIG?! Hier noch ein paar Debuginfo's:

[/share/MD0_DATA/.qpkg/TVH_Dev_Sundtek] # /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0 --band UNIVERSAL
== reading digital TV signal ==
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 12551500   Hz LOCKED: YES SYS: DVB-S2 SYM: 22000000 FEC: FEC_5_6 MOD: QPSK VOLTAGE: V(13V) TONE: ON

[/] # /opt/bin/mediaclient -e
**** List of Media Hardware Devices ****
device 0: [Sundtek SkyTV Ultimate III (USB 2.0)]  DVB-S/S2, REMOTE-CONTROL
  [SERIAL]:
     ID: XXXX
  [DVB-S/S2]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0

   
   
[/] # mediaclient --lc
**** List of Media Clients ****
/dev/dvb/adapter0/frontend0:
  6026 ... tvheadend
/dev/dvb/adapter0/dvr0:
  6026 ... tvheadend
/dev/dvb/adapter0/demux0:
  No client connected
/dev/mediainput0:
  No client connected
 
[/] # top

Mem: 916552K used, 105148K free, 0K shrd, 86088K buff, 482768K cached
Load average: 0.00, 0.13, 0.24    (State: S=sleeping R=running, W=waiting)

  PID USER     STATUS   RSS  PPID %CPU %MEM COMMAND
16661 admin    S       5760     1 35.5  0.5 mediasrv
 6026 admin    S       5036     1  1.9  0.4 tvheadend

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8517
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #3 am: November 23, 2012, 02:46:12 Nachmittag »
oh

/opt/bin/mediaclient --ts-settle-timeout=2000 -d /dev/dvb/adapter0/frontend0

das Netzwerk kann an bleiben.
Failure is a good thing! I'll fix it

linron

  • Newbie
  • *
  • Beiträge: 7
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #4 am: November 23, 2012, 03:51:46 Nachmittag »
ok, habe ich nun ausgeführt:
/opt/bin/mediaclient --ts-settle-timeout=2000 -d /dev/dvb/adapter0/frontend0

anschließend den Qnap gebootet und TVHeadend wieder aktiviert.

meine sundtek.conf sieht noch immer so aus:
loglevel=min
device_attach=/share/MD0_DATA/.qpkg/TVH_Dev_Sundtek/restart_tvh.sh
enablenetwork=on

die mediasrv.log läuft nun nicht mehr voll sondern zeigt folgendes:

[/share/MD0_DATA/.qpkg/TVH_Dev_Sundtek] # cat mediasrv.log
2012-11-23 14:27:32 [10859] Starting up Multimedia Framework (Nov 13 2012 17:49:10)
2012-11-23 14:27:32 [10859]
2012-11-23 14:27:32 [10859] *** Autostarting Networksupport ***
2012-11-23 14:27:32 [10859]
2012-11-23 14:27:32 [10859] API Version: 5.5
2012-11-23 14:27:32 [10859] Running on Linux (2.6.33.2)
2012-11-23 14:27:32 [10859] Detected: GenuineIntel
2012-11-23 14:27:32 [10859] This CPU supports: MMX and SSE
2012-11-23 14:27:32 [10859] scanning devices
2012-11-23 14:27:32 [10859]
2012-11-23 14:27:32 [10859] Scanning for drivers
2012-11-23 14:27:32 [10859] found lib: libdrv_fm.so
2012-11-23 14:27:32 [10861] Starting service processor (PID 10861)
2012-11-23 14:27:32 [10859] found lib: libdrv_hikarisoft_isdb.so
2012-11-23 14:27:32 [10859] found lib: libdrv_em28xx.so
2012-11-23 14:27:32 [10859] found lib: libdrv_vivi.so
2012-11-23 14:27:32 [10859] found lib: libdrv_net.so
2012-11-23 14:27:32 [10859] found lib: libdrv_tntdvb.so
2012-11-23 14:27:32 [10859] found lib: libdrv_ngTV.so
2012-11-23 14:27:32 [10859]
2012-11-23 14:27:32 [10859] Scanning for plugins
2012-11-23 14:27:32 [10859] found lib: libencoder_plugin.so
2012-11-23 14:27:32 [10859] MediaAVPlugin: MPEG Encoder
2012-11-23 14:27:32 [10859] Copyright: (C) Tpe 2011/2012
2012-11-23 14:27:32 [10859]
2012-11-23 14:27:32 [10859] Starting up device manager
2012-11-23 14:27:32 [10859] unable to open /dev/misc
2012-11-23 14:27:32 [10859] scanning devices done
2012-11-23 14:27:32 [10859] attached devices:
2012-11-23 14:27:32 [10859] Starting listener
2012-11-23 14:27:32 [10859] Listening on 9234
2012-11-23 14:27:32 [10859] registering ID: 0
2012-11-23 14:27:32 [10859] disconnecting kernel driver
2012-11-23 14:27:32 [10861] Autostarting scripts in /etc/sundtek/
2012-11-23 14:27:32 [10861] executed all available items
2012-11-23 14:27:32 [10859] received notification client request
2012-11-23 14:27:33 [10859] attaching second generation DVB-S/S2 demodulator
2012-11-23 14:27:36 [10859] demodulator successfully attached (DVB_S/S2)!
2012-11-23 14:27:36 [10859] Allocation using pg for type 65678
2012-11-23 14:27:36 [10859] requesting to attach tuner(s) now
2012-11-23 14:27:36 [10859] registering: adapter0/0
2012-11-23 14:27:36 [10859] registered virtual: /dev/dvb/adapter0/frontend0
2012-11-23 14:27:36 [10859] registered virtual: /dev/dvb/adapter0/demux0
2012-11-23 14:27:36 [10859] registered virtual: /dev/dvb/adapter0/dvr0
2012-11-23 14:27:36 [10859] Setting RC Protocol to NEC
2012-11-23 14:27:36 [10859] registered virtual: /dev/mediainput0
2012-11-23 14:27:36 [10859] Remote Control Layout: 0
2012-11-23 14:27:36 [10861] trying to load uinput module
2012-11-23 14:27:36 [10861] loading uinput kernel extention failed, remote control will not work with lirc
2012-11-23 14:27:36 [10859] No remote control support available
2012-11-23 14:27:36 [10859] Trying to load ffmpeg codecs
2012-11-23 14:27:36 [10859] could not load libavutil.so
2012-11-23 14:27:36 [10859] could not load libswscale.so
2012-11-23 14:27:36 [10859] could not load libavcodec.so
2012-11-23 14:27:36 [10859] could not load libavformat.so
2012-11-23 14:27:36 [10859] AnalogTV encoding won't be possible in driver's side
2012-11-23 14:27:36 [10859]
2012-11-23 14:27:36 [10859] Sundtek MediaTV Driver loaded. This driver is licensed for non-commercial use
2012-11-23 14:27:36 [10859] with Sundtek MediaTV only
2012-11-23 14:27:36 [10859] Driver loaded within 4008 milliseconds
2012-11-23 14:27:36 [10859] Serial(0): U120411121134
2012-11-23 14:27:36 [10859] received device attach message
2012-11-23 14:27:36 [10861] notify request: media device connected
2012-11-23 14:27:39 [10859] Initial devicescan done, switching detection mode
2012-11-23 14:27:51 [10859] Enabling standby
2012-11-23 14:27:51 [10859] Device is now in standby
2012-11-23 14:30:31 [10859] Waking up device
2012-11-23 14:30:33 [10859] voltage is off


Beim Versuch den MUX (Delivery System:) manuell hinzuzufügen bekomme ich leider noch immer die Felermeldung:

/dvb/feopts/delsys/_dev_dvb_adapter0_Sundtek_DVB_S_S2__III_ -- 400


[/share/MD0_DATA/.qpkg/TVH_Dev_Sundtek] # /opt/bin/mediaclient --readsignal=0 -d /dev/dvb/adapter0/frontend0 --band UNIVERSAL
== reading digital TV signal ==
SIGNAL: [                                 ] (  0%)  BER:      0 FREQ: 9750000    Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%)  BER:      0 FREQ: 9750000    Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%)  BER:      0 FREQ: 9750000    Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%)  BER:      0 FREQ: 9750000    Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%)  BER:      0 FREQ: 9750000    Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF
SIGNAL: [                                 ] (  0%)  BER:      0 FREQ: 9750000    Hz LOCKED:  NO SYS: DVB-S2 SYM: 0 FEC: FEC_NONE MOD: QPSK VOLTAGE: OFF TONE: OFF



und nun ?!  :'( eine Idee woran es liegen könnte oder wie ich weiter vorgehen sollte?!


Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8517
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #5 am: November 23, 2012, 04:09:39 Nachmittag »
Laut tvheadend Forum deutet der Wert 400 auf falsche Parameter hin, die Frequenz muss in KHZ angegeben werden.
« Letzte Änderung: November 23, 2012, 04:13:27 Nachmittag von Sundtek »
Failure is a good thing! I'll fix it

linron

  • Newbie
  • *
  • Beiträge: 7
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #6 am: Dezember 11, 2012, 12:16:56 Nachmittag »
es scheint wohl an dem TVHeadend-QPKG zu liegen. Mit einer XBMC-Frodo Installation auf meinem Laptop lässt sich der Sundtek Stick per Netzwerk mounten und auch dort in TVHeadend einbinden.. Was mich nur wundert ist das mehrere Qnap Besitzer hier geschrieben haben das sie es zum laufen gebracht haben. Da ich ein Linux-Newbie bin weiß ich nicht wie ich mir selber ein TVHeadend für die Qnap kompilieren kann. Wäre super wenn sich hier ein Qnap Besitzer findet der Lust hat mir zu helfen  ;D

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8517
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #7 am: Dezember 11, 2012, 01:13:11 Nachmittag »
Es kann durchaus an der anderen tvheadend Konfiguration auf dem QNAP liegen, es funktioniert auf jeden Fall am QNAP und das bereit seit ca einem Jahr.

Wenn tvheadend auf dem QNAP installiert ist wird der Netzwerksupport unseres Wissens nach ausgeschalten um gegenseitige Störungen zu verhindern.
Die Fehlercodes lassen sich ziemlich einfach mit google in aussagekräftigere Meldungen übersetzen.
Failure is a good thing! I'll fix it

Vrolix

  • Newbie
  • *
  • Beiträge: 1
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #8 am: Januar 23, 2013, 10:18:16 Nachmittag »
Hallo,

ich habe leider das gleiche Problem wie linron mit dem nicht auswählbaren "Delivery_System".
Allerdings ist bei mir ein QNAP TS-459Pro+ mit der Version 3.8.1 Build 20121205 im Einsatz.
Konnte jemand das Problem bisher lösen?

An meinem zweiten QNAP TS-419p läuft TVHeadend tadellos.



Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8517
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #9 am: Januar 23, 2013, 10:26:15 Nachmittag »
Das mit dem Delivery System Problem sind doch falsche Parameter.

Hast du die Frequenz und Parameter mit Lyngsat abgeglichen?
http://www.lyngsat.com/Astra-1KR-1L-1M-2C.html
Failure is a good thing! I'll fix it

linron

  • Newbie
  • *
  • Beiträge: 7
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #10 am: April 23, 2013, 04:56:44 Nachmittag »
es liegt meines Erachtens nicht an den Parametern sondern dass das QPKG nicht mit DVB-S/S2 Support compiliert wurde. Es laufen wohl nur DVB-T & DVB-C Sticks damit...

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8517
    • Profil anzeigen
Re:Qnap 259 Pro+ -> TVHeadend -> Sundtek DVS-S/S2 (III) Problem
« Antwort #11 am: April 25, 2013, 08:05:39 Nachmittag »
Genau, wir haben dies soweit auch via TVHeadend Mailingliste geklärt.
TVHeadend wurde einfach nur mit der alten DVB-S API gebaut, ein weiteres Paket mit DVB-S2 Support ist im TVHeadend Supportbereich verlinkt

https://tvheadend.org/boards/4/topics/7408?r=8153#message-8153
Failure is a good thing! I'll fix it