no snr level

Support forum for minisatip
ghost
Posts: 9
Joined: Wed Feb 22, 2017 6:13 am

no snr level

Post by ghost »

Hi everyone. After update up to 0.7.6 snr level no longer avail and CC error indicates 1-20, but no any visible errors on screen and tvheadend.
at my 0.7.4 installation no problems with snr level and no CC errors
Image

also I have problem with cyrilic channel name
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: no snr level

Post by cata »

Hi,

could you please provide the log with:

-l pmt,dvbapi,dvb,adapter

Thank you
ghost
Posts: 9
Joined: Wed Feb 22, 2017 6:13 am

Re: no snr level

Post by ghost »

cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: no snr level

Post by cata »

Hi,

try in the latest commit with:

-M *:1-0

Basically, this means that the strength will be left as is, and the snr will be set to maximum.

Thanks
ghost
Posts: 9
Joined: Wed Feb 22, 2017 6:13 am

Re: no snr level

Post by ghost »

good
now it shows 100% but how to get real values ? and why when minisatip shows 100% same value at tvheadend looks like 102% ( SNR or STR ) 96% in minisatip = 100% in tvh
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: no snr level

Post by cata »

Hi,

I tried also with -M *:1-0 and the SNR is reported correctly (100% in tvh). I am using one of the latest master branches.

You can upload the logs again with -l dvb,http,adapter

Thanks
Space
Posts: 6
Joined: Tue Oct 24, 2017 8:34 am

Re: no snr level

Post by Space »

Hi,

I have the same issue ... but if I use a multiplier of 256 for SNR then I get sensible values ... not sure why it has changed that much. I tried to understand the flow and saw there there is a get_signal and get_signal_new (which seems to use the new DVB API) but I did not understand when that is used ...

Code: Select all

[24/10 12:18:52.472]: get_signal adapter 0: status 31, strength 48730, snr 179, BER: 0
[24/10 12:18:52.472]: get_signal took 25 ms for adapter 0 handle 7 (status: 31, ber: 0, strength:190, snr: 179, force scan 0)
If I use a multiplier of 1 then in the second line the SNR is 0 ... is it divided by 256 two times maybe?

Best regards,

Space
Space
Posts: 6
Joined: Tue Oct 24, 2017 8:34 am

Re: no snr level

Post by Space »

Hi,

I had the same issue ... to me it seems as if the adapter already sends values in the range of 0 .. 255 for SNR. So if I use a multiplier of 256 then the values match:

Code: Select all

[24/10 13:12:45.064]: get_signal adapter 1: status 31, strength 44184, snr 177, BER: 1
[24/10 13:12:45.064]: get_signal took 26 ms for adapter 1 handle 9 (status: 31, ber: 1, strength:172, snr: 177, force scan 0)
Best regards,

Space
ghost
Posts: 9
Joined: Wed Feb 22, 2017 6:13 am

Re: no snr level

Post by ghost »

Still have problem with SNR level . Multiplier 256 doesn't help.
minisatip log
Message repeated 2 times
[05/02 14:36:03.682 signal]: BW 354KB/s, Total BW: 4 MB, ns/read 42, r: 37, w: 292 fw: 0, tt: 1 ms
[05/02 14:36:03.783 signal]: get_signal_new adapter 1: status 31, strength -33590 dBm -> 43521, snr 0 (none) -> 0, BER: 0, err 0
Message repeated 3 times
[05/02 14:36:04.686 signal]: BW 349KB/s, Total BW: 4 MB, ns/read 43, r: 36, w: 288 fw: 0, tt: 1 ms
[05/02 14:36:04.987 signal]: get_signal_new adapter 1: status 31, strength -33590 dBm -> 43521, snr 0 (none) -> 0, BER: 0, err 0
Message repeated 2 times
[05/02 14:36:05.689 signal]: BW 342KB/s, Total BW: 4 MB, ns/read 43, r: 36, w: 282 fw: 0, tt: 1 ms
[05/02 14:36:05.890 signal]: get_signal_new adapter 1: status 31, strength -33590 dBm -> 43521, snr 0 (none) -> 0, BER: 0, err 0
Message repeated 2 times


at the same time

femon -H -a1
FE: Montage Technology DS3000 (DVBS)
status SCVYL | signal 92% | snr 64% | ber 1 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
status SCVYL | signal 92% | snr 64% | ber 0 | unc 0 | FE_HAS_LOCK
^C


DVB card is Tevii S464, S480

system Linux dvbip2 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 GNU/Linux
ghost
Posts: 9
Joined: Wed Feb 22, 2017 6:13 am

Re: no snr level

Post by ghost »

UPD
root@dvbip2:~# femon -a0
FE: Montage Technology DS3000 (DVBS)
status SCVYL | signal eb84 | snr 7fee | ber 00000001 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal eb84 | snr 7fee | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal eb84 | snr 7fee | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal eb84 | snr 9984 | ber ffffffff | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal eb84 | snr 9984 | ber 00000e42 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal eb84 | snr 9984 | ber 00000968 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal eb84 | snr 9984 | ber 00000971 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal eb84 | snr 9984 | ber 00000965 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal eb84 | snr 9984 | ber 00000970 | unc 00000000 | FE_HAS_LOCK
root@dvbip2:~# femon -a1
FE: Montage Technology DS3000 (DVBS)
status SCVYL | signal ee13 | snr e128 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal ee13 | snr e128 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal ee13 | snr e128 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status SCVYL | signal ee13 | snr e128 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
Post Reply