Bug #3433
Transponder 11464 gets no scan
0%
Description
Hi there,
I have a MOI Pro running with the following cards:
TurboSight TBS 62x1 DVBC frontend
TurboSight TBS 6982SE DVBS/S2 frontend
both with 2 tuners on.
I set up the cards with SATConfig "Universal LNB only" leaving the rest as default, activated both tuners and set up a network called "ASTRA".
Muxes will be recognized and most transponders get a scan, some of the have status FAIL.
The bad is that also the Transponder 11464 gets no scan and this one is carrying essential channels like "PRO7 HD" which I like to watch.
According to some guys on IRC channel i tried to play the mux, the result is:
015-12-22 11:33:27.278 mpegts: 11464H in SAT - tuning on DVB-S #1 2015-12-22 11:33:27.289 linuxdvb: DVB-S #1 - failed to tune [e=Invalid argument] 2015-12-22 11:33:29.000 mpegts: 11464H in SAT - tuning on DVB-S #0 2015-12-22 11:33:29.012 linuxdvb: DVB-S #0 - failed to tune [e=Invalid argument] 2015-12-22 11:33:34.000 subscription: 0201: No input source available for subscription "HTTP" to mux "11464H in SAT" 2015-12-22 11:33:34.001 webui: Couldn't start streaming /s
In dmesg I noticed the following:
[1634888.826863] SAA716x TBS 0000:06:00.0: DVB: adapter 2 frontend 0 frequency 864000 out of range (950000..2150000)
I have no idea why this wrong frequency is used there, other programs like w_scan are able to scan the transponder and generate a servicelist.
History
Updated by Jaroslav Kysela almost 9 years ago
1) very old tvh
2) provide '--trace linuxdvb,diseqc' - but it looks like a driver fault
Updated by Daniel Guenther almost 9 years ago
2015-12-23 15:44:22.714 [ INFO]:mpegts: 11464H in ASTRA - tuning on TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0
2015-12-23 15:44:22.714 [ DEBUG]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - stopping 12699V in ASTRA
2015-12-23 15:44:22.714 [ TRACE]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - waiting for dvr thread
2015-12-23 15:44:23.031 [ INFO]:capmt: Local: normal socket shutdown
2015-12-23 15:44:23.032 [ INFO]:capmt: Local: Automatic reconnection attempt in in 3 seconds
2015-12-23 15:44:23.127 [ DEBUG]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - stopped dvr thread
2015-12-23 15:44:23.127 [ INFO]:subscription: 0017: "epggrab" unsubscribing
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: tuner TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 tunning to DVBS2 19.2E freq 114$
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 17 => 6
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 03 => 864000
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 06 => 2
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 08 => 22000000
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 09 => 2
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 04 => 9
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 12 => 2
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 13 => 0
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 43 => 4294967295
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 01 => 0
2015-12-23 15:44:23.194 [ ERROR]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - failed to tune [e=Invalid argument]
2015-12-23 15:44:23.194 [ INFO]:mpegts: 12699V in ASTRA - tuning on TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: tuner TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 tunning to DVBS2 19.2E freq 126$
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 17 => 6
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 03 => 2099000
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 06 => 2
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 08 => 22000000
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 09 => 2
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 04 => 9
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 12 => 2
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 13 => 0
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 43 => 4294967295
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 01 => 0
2015-12-23 15:44:23.216 [ TRACE]:diseqc: initial tone off
2015-12-23 15:44:23.327 [ TRACE]:diseqc: set diseqc tone on
Unfortunatly I am unable to update TVheadend myself since no newer version is available for the MOI Pro.
Updated by Daniel Guenther almost 9 years ago
Sorry, just recognized that the log lines were truncated...
2015-12-23 15:44:22.714 [ INFO]:mpegts: 11464H in ASTRA - tuning on TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0
2015-12-23 15:44:22.714 [ DEBUG]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - stopping 12699V in ASTRA
2015-12-23 15:44:22.714 [ TRACE]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - waiting for dvr thread
2015-12-23 15:44:23.031 [ INFO]:capmt: Local: normal socket shutdown
2015-12-23 15:44:23.032 [ INFO]:capmt: Local: Automatic reconnection attempt in in 3 seconds
2015-12-23 15:44:23.127 [ DEBUG]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - stopped dvr thread
2015-12-23 15:44:23.127 [ INFO]:subscription: 0017: "epggrab" unsubscribing
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: tuner TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 tunning to DVBS2 19.2E freq 1146
4000 H sym 22000000 fec 2/3 mod PSK/8 roff 35 is_id -1 pls_mode ROOT pls_code 1 (freq 864000)
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 17 => 6
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 03 => 864000
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 06 => 2
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 08 => 22000000
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 09 => 2
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 04 => 9
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 12 => 2
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 13 => 0
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 43 => 4294967295
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 01 => 0
2015-12-23 15:44:23.194 [ ERROR]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - failed to tune [e=Invalid argument]
2015-12-23 15:44:23.194 [ INFO]:mpegts: 12699V in ASTRA - tuning on TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: tuner TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 tunning to DVBS2 19.2E freq 1269
9000 V sym 22000000 fec 2/3 mod PSK/8 roff 35 is_id -1 pls_mode ROOT pls_code 0 (freq 2099000)
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 17 => 6
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 03 => 2099000
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 06 => 2
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 08 => 22000000
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 09 => 2
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: S2CMD 04 => 9
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 12 => 2
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 13 => 0
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 43 => 4294967295
2015-12-23 15:44:23.128 [ TRACE]:linuxdvb: S2CMD 01 => 0
2015-12-23 15:44:23.194 [ ERROR]:linuxdvb: TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 - failed to tune [e=Invalid argument]
2015-12-23 15:44:23.194 [ INFO]:mpegts: 12699V in ASTRA - tuning on TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0
2015-12-23 15:44:23.195 [ TRACE]:linuxdvb: tuner TurboSight TBS 6982SE DVBS/S2 frontend : DVB-S #0 tunning to DVBS2 19.2E freq 1269
9000 V sym 22000000 fec 2/3 mod PSK/8 roff 35 is_id -1 pls_mode ROOT pls_code 0 (freq 2099000)
Updated by Jaroslav Kysela almost 9 years ago
- Status changed from New to Rejected
Upgrade, the 4.1-360~g0916e52-dirty version is really old and unsupported. The problem is that frequency 11464000 should be converted to 1714000 (11464000 - 9750000) - see src/input/mpegts/linuxdvb/linuxdvb_lnb.c - universal LNB values, but in your case, there's value 864000 (which seems like 11464000 - 10600000). So the .lnb_high value is used instead .lnb_low (but 11464000 is lower than 11700000).
Updated by Mark Clarkstone almost 9 years ago
Jaroslav Kysela wrote:
Upgrade, the 4.1-360~g0916e52-dirty version is really old and unsupported. The problem is that frequency 11464000 should be converted to 1714000 (11464000 - 9750000) - see src/input/mpegts/linuxdvb/linuxdvb_lnb.c - universal LNB values, but in your case, there's value 864000 (which seems like 11464000 - 10600000). So the .lnb_high value is used instead .lnb_low (but 11464000 is lower than 11700000).
Unfortunately for Daniel this means he'll have to beg TBS to upgrade the version used on their firmware.
Updated by Daniel Guenther almost 9 years ago
Thats my Problem actually, yes... :-(
The Software & Board Support of TBS ist realy a shame, they have e.g. Opkg as package manager but no repository for it. Also they supply a cross compiler but no single word on how to use it...
I tried to get help on their forum but without any response yet, lets keep fingers crossed...
Too bad I never saw any alternative to the MOI device...