Bug #3211
closed
SNR/Signal on DVB-T of SAT>IP OctopusNet
Added by Mario D over 9 years ago. Updated over 9 years ago.
0%
Description
The reported values look wrong (see screenshot). The tuning works well so the shown values are not real. On the DVB-S2 tuners the bars are fine.
It could be a non-compliance of the adapter output.
Files
| Schermata da 2015-10-26 12-30-43.png (54.7 KB) Schermata da 2015-10-26 12-30-43.png | screenshot of the status tab | Mario D, 2015-10-26 12:35 |
Updated by Jaroslav Kysela over 9 years ago
Could you provide trace for the satip subsystem ? You should see lines with 'satip: Status string: 'ver=1.0;src=1;tuner=3,187,1,15,....' there. Second value after tuner= is signal strength (0-240) and fourth value is signal quality (0-15) - according SAT>IP specification.
Anyway - these errors should be reported to the firmware vendor.
Updated by Mario D over 9 years ago
ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=1;tuner=1,194,1,10,12054,h,dvbs,qpsk,,0.35,29900,56;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=2;tuner=2,181,1,12,11170,h,dvbs2,8psk,,0.35,22000,34;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=3,13,1,0,706.000,8,dvbt,8k,64qam,14,,0,0,0;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=4,17,1,0,514.000,8,dvbt,8k,64qam,132,,0,0,0;pids=0,18,424,434,445,586' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=1;tuner=1,194,1,10,12054,h,dvbs,qpsk,,0.35,29900,56;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=2;tuner=2,181,1,12,11170,h,dvbs2,8psk,,0.35,22000,34;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=3,13,1,0,706.000,8,dvbt,8k,64qam,14,,0,0,0;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=4,17,1,0,514.000,8,dvbt,8k,64qam,132,,0,0,0;pids=0,18,424,434,445,586' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=1;tuner=1,194,1,10,12054,h,dvbs,qpsk,,0.35,29900,56;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=2;tuner=2,181,1,12,11170,h,dvbs2,8psk,,0.35,22000,34;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=3,13,1,0,706.000,8,dvbt,8k,64qam,14,,0,0,0;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=4,17,1,0,514.000,8,dvbt,8k,64qam,132,,0,0,0;pids=0,18,424,434,445,586' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=1;tuner=1,194,1,10,12054,h,dvbs,qpsk,,0.35,29900,56;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=2;tuner=2,181,1,12,11170,h,dvbs2,8psk,,0.35,22000,34;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=3,13,1,0,706.000,8,dvbt,8k,64qam,14,,0,0,0;pids=0,16,17,18' ott 26 15:14:52 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=4,17,1,0,514.000,8,dvbt,8k,64qam,132,,0,0,0;pids=0,18,424,434,445,586' ott 26 15:14:53 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=1;tuner=1,194,1,10,12054,h,dvbs,qpsk,,0.35,29900,56;pids=0,16,17,18' ott 26 15:14:53 sauron tvheadend[12504]: satip: Status string: 'ver=1.0;src=2;tuner=2,181,1,12,11170,h,dvbs2,8psk,,0.35,22000,34;pids=0,16,17,18' ott 26 15:14:53 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=3,13,1,0,706.000,8,dvbt,8k,64qam,14,,0,0,0;pids=0,16,17,18' ott 26 15:14:53 sauron tvheadend[12504]: satip: Status string: 'ver=1.1;tuner=4,17,1,0,514.000,8,dvbt,8k,64qam,132,,0,0,0;pids=0,18,424,434,445,586'
It looks that the signal strength uses another scale and that signal quality is always 0. I guess you are right: this should not/cannot be fixed (read "workaround") on tvheadend-side. I'll try to report to the firmware vendor.
Updated by Jaroslav Kysela over 9 years ago
Example for DVB-T in SAT>IP spec:
ver=1.1;tuner=1,240,1,7,754.00,8,dvbt,4k,16qam,116,23,,,;pids=0,16,56,112,168,1709
so..
signal level reported 0-240 13,17 signal quality reported 0-15 0
It's not about scale - it's buggy firmware.
Updated by Mario D over 9 years ago
I had a quick reply from DD support:
Hi, unfortunately it is currently not possible to get a compliant signal value for DVB-T reception through the used linux Version which are used on the Octopus NET. Currently it's only possible to see whether the Octopus NET gets a "Signal lock" or "No Signal" message. Mit freundlichem Gruß / Kind regards Jörg Rösner